What it means
Sudo policy design grants named users or groups tightly scoped administrative commands while preserving accountability, command context, and safer alternatives to persistent root sessions.
Why it matters
Sudo improves accountability only when its rules constrain what can be run; broad command patterns can become root access under another name.
Practical focus
- Define the administrative tasks that require elevation and the identities, roles, and resources it covers
- Implement command-specific sudo rules, controlled environment handling, and group-based assignment through least-privilege, reviewable policy
- Use sudo logs, effective rule tests, and periodic entitlement reviews to confirm that effective access matches intended access
- Plan for a rule permitting shell escape, environment abuse, or emergency lockout, including safe recovery and break-glass handling
Common mistakes
- Granting broad access because it is easier to administer
- Changing policy without testing the effective identity context
- Allowing exceptions to persist without an owner or expiration
- Treating a rule permitting shell escape, environment abuse, or emergency lockout as a user problem instead of a control failure
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: