Domain 7 · Objective reference 7.4 · Chapter 46 of 62
Apply operational least privilege and accountability
About 5 minutes · Current ISC2 outline effective 15 April 2024; the announced 15 April 2027 replacement requires separate mapping
Session only. Enable saving or download a backup from this course’s hub.
Completion is self-reported and does not certify understanding.
See it · Try it · Recall it
Picture the topic
Remember this: Split dangerous combinations of power.
Explore the anchors
Limit access to necessary operations.
Concept matching activity
Match this task or description to its concept:
Divide conflicting responsibilities.
Choose a concept before checking the explanation.
Access-decision sandbox
Try to edit a fictional record as a reader. Then change one condition and evaluate again. This simplified policy requires authentication, object scope and action permission; real policies have more conditions.
Change the request, then evaluate it.
A quick way to study this topic
- Hide the explanation and redraw these three anchors from memory.
- Explain the difference between the anchors in your own words.
- Apply the distinction to the worked example below. Check the full lesson for assumptions and exceptions.
- Recall it again tomorrow, then after a few days. A memory hint is a retrieval cue, not a replacement for understanding.
Original academy illustrations and fictional exercises. These are learning simulations, not a real virtual machine, network assessment or measure of job readiness. Activities reset when you leave or reload; they do not change quiz scores.
What this chapter explains
- Concepts and mechanisms
- Design, evidence and tradeoffs
Concepts and mechanisms
Need-to-know constrains access to information required for a legitimate purpose. Least privilege constrains authority needed for a task. Separation of duties and responsibilities limits incompatible stages or concentration. Privileged access management can control approval, custody, duration and attributable use. Job rotation can expose process dependencies or irregularities but does not replace authorization and review.
Design, evidence and tradeoffs
Define service-level commitments in terms of outcomes, responsibilities and evidence. An uptime target does not establish response capacity or data integrity. Emergency access should be protected, monitored and reviewed after use. Avoid permanent exceptions that quietly bypass normal controls. Automated processes need the same purpose, ownership and effective-permission evaluation as human accounts.
Worked example
A database administrator receives temporary approved elevation for maintenance rather than permanent access to every production system.
Check your understanding
Why is a second account owned by the same person not always separation of duties?
Show explanation
The same person may still control both incompatible decisions; identity labels alone do not provide independence.
Source and study boundary
Official syllabus source. The reference identifies the topic being taught. Explanations and examples are original academy material; a topic link does not establish independent approval or sufficient exam mastery.