ADMIN-ML1 Restrict Administrative Privileges (ML1)
Requests for privileged access to systems, applications and data repositories are validated when first requested. Privileged users are assigned a dedicated privileged user account to be used solely for duties requiring p
8
artefacts
0
held by a system
3
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Access request workflow records (ServiceNow, Jira) showing privileged access requests with approvers and validation · Identity provider / directory
- Conditional access or named locations evidence restricting privileged accounts to administrative interfaces · Identity provider / directory
- Annual review of who holds privileged accounts vs whose role still requires them · Identity provider / directory
governing documentDocuments that govern the control
- Privileged account naming convention and AD/Entra ID inventory mapping privileged users to dedicated accounts · Policy repository / GRC workspace
- Firewall, proxy or conditional access policy blocking privileged accounts from internet, email and web browsing · Policy repository / GRC workspace
- Tiered admin model documentation (Tier 0 / Tier 1 / Tier 2) with environment boundaries · Policy repository / GRC workspace
- Group Policy Deny Logon rights: 'Deny logon locally', 'Deny logon through RDS' for cross-tier accounts · Policy repository / GRC workspace
- Sample admin workstation showing it cannot send email or browse the internet · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Privileged users use a single account for both daily and admin work
- Email blocked but web browsing still possible because no egress proxy enforced on admin VLAN
- No tiering, all admins log into Tier 0 from regular workstations
- Privileged accounts allowed to log into unprivileged environments (and vice versa) because Deny Logon GPOs missing
- Access request workflow exists but approvers rubber-stamp without validation
- Online-services authorisation applied broadly (e.g. all admins can use Microsoft 365 admin portal)
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet