Courseiva
mediumMultiple Select

CCSP Practice Question: A cloud security architect is implementing a…

A cloud security architect is implementing a CI/CD pipeline for a containerized application on AWS. Which TWO practices should be integrated to enforce container image security?

⚠ Common exam trap

ISC2 often tests the distinction between pipeline-time security controls (like scanning and signing) and runtime or perimeter controls (like RASP and WAF), leading candidates to mistakenly select runtime defenses for a CI/CD enforcement question.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Scan container images for vulnerabilities before push to registry

Option B is correct because scanning container images for vulnerabilities before pushing them to the registry (e.g., using Amazon ECR image scanning, Clair, or Trivy) catches known CVEs in OS packages and application dependencies at build time, preventing vulnerable images from ever entering the pipeline. Option D is correct because signing container images (e.g., with Docker Content Trust/Notary or Sigstore Cosign) and verifying signatures at deploy time ensures image integrity and provenance, blocking tampered or unauthorized images from running. Option A is not appropriate here because RASP protects a running application from attacks at runtime and does not secure the image build/supply chain. Option C is not appropriate because a cloud WAF filters HTTP/S traffic to the application and does not inspect or validate container images. Option E is not appropriate because SAST analyzes source code for flaws, not the built container image and its layers.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Implement runtime application self-protection (RASP)

    Why it's wrong here

    RASP instruments a running application to detect attacks in-process; it operates after the image is deployed and cannot scan or sign image artefacts during the build. It is tempting because RASP protects containerised workloads at runtime, which is the correct choice for blocking exploitation attempts, not for enforcing image integrity in the pipeline.

  • ✓

    Scan container images for vulnerabilities before push to registry

    Why this is correct

    Scanning images before pushing to the registry blocks vulnerable artefacts from ever entering the pipeline, satisfying the shift-left constraint. Vulnerabilities are detected at build time, so compromised layers never reach Amazon ECR or production. This pre-push gate enforces image security earlier than post-registry scanning, which only detects flaws after distribution.

  • ✗

    Use a cloud WAF to protect the containerized application

    Why it's wrong here

    A cloud WAF inspects inbound HTTP/S traffic at the application edge; it cannot scan image layers, base images or package manifests inside a registry, so it does not enforce image security. It is tempting because WAFs protect containerised workloads at runtime, which is the correct choice for filtering malicious web requests, not for validating images during CI/CD.

  • ✓

    Sign container images to ensure integrity

    Why this is correct

    Cryptographic signing produces a verifiable digest that admission controllers validate at deploy time, proving the image was not tampered with after build. This enforces integrity across the registry-to-cluster path, satisfying the pipeline's supply-chain trust requirement.

  • ✗

    Run SAST on the application source code

    Why it's wrong here

    SAST analyses application source code for coding flaws; it does not inspect container image layers, installed OS packages or base image provenance, so it cannot enforce image security. It is tempting because SAST runs early in the CI/CD pipeline, which is the correct choice for catching code-level vulnerabilities before the image is built.

About these practice questions

This CCSP question is part of Courseiva's 934-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This CCSP practice question is part of Courseiva's free ISC2 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCSP exam.