The four-eyes principle is a control concept that requires at least two independent people to approve a significant decision. In access governance, it reduces the chance that one mistaken or biased reviewer can authorise access alone. The goal is independent scrutiny, not a second signature from someone who simply repeats the first decision.
What the four-eyes principle means in access governance
The four-eyes principle is a dual-review control, so the security value comes from independence rather than simple repetition. In access governance, that means a second approver should be able to challenge the first decision, spot mistakes, and reduce the chance that one person can grant access without scrutiny.
It is often used where access decisions are sensitive, high-impact, or difficult to reverse. The control is strongest when approvers have different responsibilities or perspectives, because the goal is to lower single-point judgment error and deliberate abuse, not to create a ceremonial approval chain.
Where four-eyes control fits in broader security operations
Four-eyes review is most useful when the action being approved creates lasting privilege, exposure, or operational change. That is why it appears in access requests, privileged changes, break-glass workflows, backup administration, and other actions where a single mistaken approval can create a long-lived security problem.
It also matters in workflows that combine human judgement with automated execution. A well-designed review step can slow down unsafe actions just enough to catch bad assumptions, while still preserving operational speed for routine work. Change Management Policy Template is a useful reference when the approval pattern needs to be embedded into change control and segregation of duties.
How four-eyes approval differs from weak dual approval
Not every two-person process is a true four-eyes control. If the second approver simply rubber-stamps the first decision, the control adds little value. The security outcome depends on genuine independence, meaningful review criteria, and the ability to refuse approval without pressure.
That distinction matters in organisations that rely on maker-checker workflows for privileged access, configuration changes, or administrative actions. Four-eyes approval should force a real second judgment, not a duplicate signature path that preserves the same bias, same assumptions, or same operational blind spot.
In practice, this principle is closely related to separation of duties, but it is narrower: four-eyes focuses on independent approval for a specific action, while broader segregation of duties governs who can request, approve, execute, and review sensitive work across a process.
Typical failure modes and control boundaries
Four-eyes control can fail when the approvers share the same manager, the same operational incentives, or the same access path into the system. It can also fail if the approval happens too late, after the risky action is already queued for execution, or if emergency paths bypass the control without follow-up review.
Another common weakness is scope creep. If every low-risk action needs dual approval, teams tend to treat the control as noise and bypass it in practice. The principle works best when reserved for decisions that are truly significant, sensitive, or hard to recover from.
Dual control and four-eyes approval for privileged and agent actions is especially relevant where organisations need a concrete pattern for keeping approvers independent and preventing self-review.
Risk and Threat Considerations
Four-eyes control exists because approval systems are vulnerable to human error, bias, collusion, and overly casual review. When it is weak or symbolic, a single bad decision can become an access grant, a privileged change, or an administrative action that is hard to unwind.
Failure mechanism: The control breaks when the second reviewer is not truly independent, cannot challenge the request, or approves without examining the underlying risk, allowing the first reviewer’s mistake or intent to pass unchecked.
Impact: Unsafe access, privilege escalation, or incorrect administrative change can be authorised with a false sense of oversight, increasing the chance of misuse, operational disruption, or difficult-to-reverse exposure.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-5 — Account Management | Dual approval helps govern high-risk account and access changes. |
| Recommendation — Use dual review for sensitive account changes and restrict approval authority to independent reviewers. | ||
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Independent approval supports limiting who can authorise privileged access. |
| AC-5 — Separation of Duties | Four-eyes is a direct segregation-of-duties control for sensitive decisions. | |
| Recommendation — Apply least privilege so no single reviewer can both request and authorise excessive access. Separate request, approval, and execution duties for sensitive access and change actions. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Four-eyes governs how access decisions are approved and enforced. |
| A.8.32 — Change management | Dual approval is a common safeguard for controlled operational changes. | |
| Recommendation — Define approval rules for sensitive access decisions and make reviewer independence explicit. Require independent approval for material changes and record the justification for each decision. | ||
Practitioner Guidance
Governance implication: Treat four-eyes as an independence requirement, not a headcount requirement. The most important design choice is whether the second approver can realistically question the decision, reject it, and leave an auditable record of why.
What to watch for: Review paths that repeatedly pass without challenge, approvers who always mirror the first decision, and exceptions that quietly become the normal route. Those patterns usually mean the control exists on paper but not in practice.
Practitioner takeaway: Use four-eyes only where the consequence of a bad decision justifies the friction, and make sure the review is meaningfully independent enough to change the outcome.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org