The answer is code signing with a trusted certificate, along with cryptographic hashing and secure build pipelines. These techniques ensure software integrity during the build and deployment process by creating a verifiable chain of custody for every artifact. Cryptographic hashes like SHA-256 generate a unique, fixed-size digest of a file’s contents; comparing this hash against a known-good value immediately detects any unauthorized modification, corruption, or tampering that occurred during transit or storage. On the CISSP exam, this concept tests your understanding of the Software Development Security domain, specifically how to protect against supply chain attacks and malicious code injection. A common trap is confusing integrity verification with authentication—remember that hashing proves the file hasn’t changed, while code signing proves who signed it. For a memory tip, think “Hash to catch a smash, sign to know the line”—the hash catches tampering, and the signature verifies the source.
CISSP Software Development Security Practice Question
This CISSP practice question tests your understanding of software development security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which THREE of the following are valid techniques to ensure software integrity during the build and deployment process? (Select THREE.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Using cryptographic hashes (e.g., SHA-256) to verify files
Cryptographic hashes like SHA-256 produce a unique fixed-size digest of a file's contents. By comparing the hash of a built artifact against a known-good hash, you can detect any unauthorized modification, corruption, or tampering that occurred during the build or deployment process. This directly ensures software integrity by verifying that the file has not been altered.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Implementing role-based access control on the build server
Why it's wrong here
RBAC controls access but does not verify integrity.
✓
Using cryptographic hashes (e.g., SHA-256) to verify files
Why this is correct
Hashes detect unauthorized changes.
Related concept
Read the scenario before looking for a memorised answer.
✗
Continuous integration automated builds
Why it's wrong here
CI automates builds but does not inherently verify integrity.
✓
Performing checksum verification after deployment
Why this is correct
Checksums ensure the deployed artifact matches the source.
Related concept
Read the scenario before looking for a memorised answer.
✓
Code signing with a trusted certificate
Why this is correct
Digital signatures provide authenticity and integrity.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is confusing process controls (like RBAC or CI automation) with integrity verification mechanisms; candidates often think that restricting access or automating builds inherently ensures the software hasn't been tampered with, but only cryptographic techniques like hashing and signing provide direct integrity assurance.
Detailed technical explanation
How to think about this question
Under the hood, cryptographic hash functions like SHA-256 are one-way and collision-resistant, meaning it is computationally infeasible to find two different inputs that produce the same hash. In practice, build pipelines often generate a hash of the final artifact (e.g., using `sha256sum`), store it in a secure manifest, and then re-compute the hash after deployment to ensure the artifact was not altered during transit or storage. A real-world scenario is the SolarWinds attack, where attackers compromised the build environment and signed malicious code; hash verification alone would not catch a signed malicious build, which is why code signing (option E) is also critical.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CISSP question in full detail.
Software Development Security — This question tests Software Development Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Using cryptographic hashes (e.g., SHA-256) to verify files — Cryptographic hashes like SHA-256 produce a unique fixed-size digest of a file's contents. By comparing the hash of a built artifact against a known-good hash, you can detect any unauthorized modification, corruption, or tampering that occurred during the build or deployment process. This directly ensures software integrity by verifying that the file has not been altered.
What should I do if I get this CISSP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This CISSP 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 CISSP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.