
CCT 366: Software Supply Chain Security Explained — CISSP Domain 8 (ChainDrop Case Study)
Episode 366
Send us Fan Mail A supply chain attack that leaves your Git history spotless should change how you think about “secure code.” We walk through ChainDrop, a worm discovered in the NPM ecosystem that poisoned 444 packages while evading the places defenders usually look. The unnerving twist is that it can trigger without a classic npm install and can hide in the space between your repository and the package archive your CI/CD pipeline actually pulls, which is exactly why code review alone can’t be your finish line. From there, we tie the real-world scenario directly to CISSP Domain 8 Software Development Security and the secure SDLC. I lay out a clear, exam-friendly framework for assessing third-party and acquired software risk: Software Composition Analysis (SCA), Software Bill of Materials (SBOM), vendor and publisher risk assessment, and runtime plus pipeline controls. We talk about why SCA is necessary but incomplete, how a living SBOM enables fast exposure checks when a new campaign hits, and why Executive Order 14028 is pushing SBOM adoption into “expected” territory for many organisations. We also get practical about CI/CD pipeline security: dependency pinning, trusted publishing workflows, signed commits, OIDC, and package signing and verification approaches like Sigstore and Cosign. Finally, we run through scenario-based practice questions that highlight common CISSP traps and the manager mindset the exam rewards.
Publisher
CISSP Cyber Training Podcast - CISSP Training Program
Published
August 17, 2026
Duration
33 min
Format
Podcast
Category
Lifestyle · Courses
Source
RSS feed
Host
Shon Gerber, vCISO, CISSP, Cybersecurity Consultant and Entrepreneur
CISSP Cyber Training Podcast - CISSP Training Program
@cisspcybertrainingpodcastcis
#softwaresupplychain #cisspdomain #chaindropcasestudy #courses
