Be able to select the right supply chain control for a given scenario: signature verification for provenance, scoped registries and pinned digests for dependency integrity, and evidence-based fourth-party oversight. The single most important thing is distinguishing integrity from authenticity — only signatures prove origin.
Start practicing
Secure Software Supply Chain — choose a session length
Free · No account required
Domain overview
This domain covers securing everything that enters your build and release pipeline from outside your team: third-party libraries, container base images, vendor software, and SaaS dependencies. Questions present concrete supply chain scenarios — signed artifacts, npm registries, Docker tags, vendor risk programs — and ask you to pick the control or practice that actually closes the integrity, provenance, or fourth-party risk gap described.
Exam objectives
Verifying code signing and artifact signatures to confirm integrity and origin authenticity
Configuring npm scoped packages and .npmrc registry settings to prevent dependency confusion
Evaluating vendor risk management programs for fourth-party and subcontractor oversight
Pinning Docker image digests instead of mutable tags like ':latest' in build pipelines
Treating a checksum or hash as proof of origin — it only proves integrity, not who produced the artifact; signatures bind identity.
Assuming a private registry alone stops dependency confusion without scoping packages or pinning the registry in .npmrc.
Believing a vendor's own security questionnaire answers constitute mature fourth-party risk management rather than independent verification.
Click any question to see the full explanation and answer options, or start a focused practice session above.
When evaluating a vendor's open-source usage, which factor is the strongest indicator of a proactive security posture?
2During a vendor security assessment, you require a supplier to provide proof that their software is signed. Which mechanism should you verify to ensure the code's integrity and origin authenticity?
3An organization is concerned about 'Typosquatting' in their build system. Which strategy is most effective at preventing the accidental inclusion of malicious, similarly-named packages?
4You are setting up an automated policy in GitHub Actions to block builds that contain dependencies with known high-severity vulnerabilities. Which tool is standard for this type of automated gated check?
5Your development team is integrating a new third-party library via npm. To prevent dependency confusion attacks where a malicious package is pulled from a public registry instead of your internal private registry, which configuration should be applied?
6You are using 'in-toto' to secure your software supply chain. What is the primary purpose of a 'layout' file in this framework?
7What is the primary function of a 'Vulnerability Disclosure Policy' (VDP) in a vendor's secure development lifecycle?
8You notice that your build server environment pulls Docker images from a public registry with the ':latest' tag. Why is this a major supply chain security flaw?
9A supplier asks you to describe your 'Supply Chain Security Policy'. What is the most appropriate foundational element to include?
10When assessing a SaaS provider's supply chain, you are concerned about their 'Vendor Risk Management' (VRM) program. Which practice indicates a mature approach to fourth-party risk?
11An organization is adopting the SLSA (Supply-chain Levels for Software Artifacts) framework. To achieve Level 3, what requirement must be met regarding the build platform?
12When performing a vendor security assessment for a new SaaS product, which THREE of the following should be requested to evaluate their supply chain resilience?
13To protect against a compromised build pipeline, which TWO of the following configurations should be implemented to ensure 'Hermetic Builds'?
14Which THREE of the following are common threats to the Software Supply Chain that an SBOM can help mitigate?
15When designing an automated pipeline to prevent supply chain attacks, which THREE of the following features should be included in your artifact registry?
16Which TWO of the following are essential components of an effective Vendor Security Assessment program?
17A financial services firm mandates that every open-source component pulled into its build pipeline must carry a cryptographically signed provenance attestation from the original project maintainer. During a review, you discover that Sigstore's cosign verification succeeds, but the attestation was generated by an internal CI runner rather than the upstream maintainer. What is the most significant supply chain risk introduced by this configuration?
18You are designing a secure software supply chain for a healthcare application that must comply with FDA premarket cybersecurity guidance. Your team proposes using the OWASP Dependency-Check tool within the CI pipeline to identify vulnerable third-party libraries. Which TWO additional practices are essential to establish a defensible component governance process that meets regulatory expectations? (Choose two.)
19A software vendor provides a critical component to your organization. During contract negotiations, you request that the vendor provide a Software Bill of Materials (SBOM) for each release. The vendor agrees to provide a document listing all open-source libraries and their versions. Which additional attribute is most important to include in the SBOM to support rapid vulnerability response?
20Your organization is adopting the SLSA framework to improve supply chain security. You are evaluating a build system that claims to meet SLSA level 3. During an assessment, you find that the build system generates provenance but does not sign it, and the provenance is stored on the same server that performs builds. Which SLSA level requirement is most directly violated by this finding?
Be able to select the right supply chain control for a given scenario: signature verification for provenance, scoped registries and pinned digests for dependency integrity, and evidence-based fourth-party oversight. The single most important thing is distinguishing integrity from authenticity — only signatures prove origin.
The Courseiva CSSLP question bank contains 20 questions in the Secure Software Supply Chain domain. Click any question to see the full explanation and answer breakdown.
Start with a 10-question focused session to identify your baseline accuracy in this domain. Read every explanation — even for questions you answer correctly — to understand the reasoning. Once you score consistently above 80%, move to a 20–30 question session to confirm depth before moving to the next domain.
Yes — the session launcher on this page draws questions exclusively from the Secure Software Supply Chain domain. Choose 10, 20, 30, or 50 questions for a focused session, or click individual questions to review them one by one.
Save your results, see per-domain analytics, and get readiness scores — free, for every certification.
Sign Up FreeFree forever · Every certification included