The correct answer is code signing and verification throughout the pipeline. Code signing creates a digital signature for code artifacts at each stage of the build and deployment pipeline, allowing verification that the code has not been tampered with between stages. This directly ensures the integrity of the software as it moves from development to production.
Regular backups of source code help with availability and disaster recovery but don't directly protect against tampering during the build and deployment process. Backups preserve code but don't verify its integrity throughout the pipeline.
Penetration testing of the pipeline environment may identify vulnerabilities and therefore protect the integrity of the build pipeline. However, it's a detective rather than preventive control for pipeline integrity.
Implementing strong network firewalls helps protect the infrastructure hosting the pipeline but doesn't specifically verify the integrity of code artifacts moving through the pipeline. Firewalls primarily control network access rather than detecting code tampering.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is code signing and how does it work?
Open an interactive chat with Bash
What are the main differences between preventive and detective controls?
Open an interactive chat with Bash
Why are regular backups of source code not sufficient for integrity?
Open an interactive chat with Bash
ISC2 CISSP
Software Development Security
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access