ISC2 CC Security Principles Practice Question
A software development company wants to ensure that only authorized code changes are deployed to production. They implement a process where developers submit code changes, and a separate team reviews and approves them before deployment. Which security principle is BEST demonstrated by this process?
⚠ Common exam trap
Many candidates confuse separation of duties with least privilege; while both are access control principles, separation of duties specifically addresses splitting tasks, whereas least privilege focuses on minimizing access rights.
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
✓
Separation of duties
Separation of duties is a preventive control that requires more than one person to complete a task, reducing the risk of unauthorized actions. In this scenario, developers cannot deploy code without a separate team's approval, ensuring that no single person has end-to-end control over the deployment process. This aligns with the principle of separation of duties, which is fundamental in change management and fraud prevention.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Defense in depth
Why it's wrong here
Defense in depth uses multiple layers of controls to protect assets. While the review process adds a layer, the scenario specifically describes a workflow that separates the ability to write code from the ability to approve and deploy it. That is a direct application of separation of duties, not just layered defense.
- ✗
Least privilege
Why it's wrong here
Least privilege means giving users only the access necessary to perform their jobs. While the review process may enforce least privilege by preventing developers from deploying directly, the core principle being demonstrated is the separation of duties, where no single person can both write and approve code. Least privilege is a component but not the primary principle.
- ✓
Separation of duties
Why this is correct
Separation of duties ensures that critical tasks are divided among multiple people to prevent fraud and errors. In this scenario, developers write code but cannot deploy it without approval from a separate team. This division prevents a single individual from making unauthorized changes, directly embodying separation of duties.
- ✗
Non-repudiation
Why it's wrong here
Non-repudiation ensures that a party cannot deny performing an action, often through digital signatures. The scenario does not mention logging or cryptographic proof; it focuses on the workflow of review and approval. Thus, non-repudiation is not the principle being demonstrated.
Go deeper
Related to this question
Learn chapter
Risk Management and Security Controls
Key term
Change management
Change management is the structured process of planning, approving, implementing, and reviewing changes to IT systems to minimize risk and disruption.
Key term
Risk
Risk is the possibility that an event or action will negatively affect an organization's ability to achieve its goals, often measured in terms of likelihood and impact.
About these practice questions
One of 989 original CC practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISC2 exam blueprint
This CC 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 CC exam.