Privileged Access Review: A Practical Checklist

A privileged access review checks who or what can administer important systems, why that access is needed and how it is controlled. Include people, suppliers and software identities. A list of administrator accounts is a starting point; the review should lead to decisions about actual permissions and how they are used.
Define the systems and identities in scope
Start with the services whose compromise would have the greatest operational effect. Include identity administration, backups, security tooling, cloud management and important applications. Identify direct permissions, group-based access and the supplier accounts that can reach them.
Record the owner and purpose of each privileged identity. Distinguish an individual administrator from an application account, automation identity or emergency account. Those types need different operating controls and review evidence.
Ask what task justifies the permission
For each assignment, ask which real task requires it and whether the scope and duration match that task. “The person works in IT” is not a useful justification. Check whether routine work can use a more limited account or whether elevated access is needed only for a defined period.
The NCSC's privileged access management guidance explains task-limited and time-limited administration. Apply those concepts through controls suitable for your systems rather than assuming one product solves every case.
Use a review record people can act on
- System, identity and accountable owner.
- Permission source, role and effective scope.
- Task requiring access and evidence of continuing need.
- Authentication and administration route.
- Decision: retain, reduce, remove or investigate.
- Implementer, acceptance check and review trigger.
Keep the decision separate from implementation status. A reviewer approving removal does not prove that the permission has actually been removed.
An illustrative supplier-access decision
A supplier received broad administrative access during a migration. The migration is complete, but the account remains enabled for occasional support. Review the actual support tasks and agree a narrower, controlled access route. Test that required support work still succeeds and that unrelated administration is denied.
The purpose of the example is to establish a review method. Do not disable an operational account without checking dependencies and arranging an appropriate change.
Include software identities and credentials
Inventory applications and scheduled jobs with privileged permissions. Confirm their owners, credential storage, renewal process and the systems they can change. An account that has never been used interactively may still be critical to a nightly process.
When access or credentials change, test the integration and monitor its next scheduled run. Record the remaining dependency so the next reviewer does not have to rediscover it.
Protect emergency access without making it unusable
Define when emergency administration is justified, who authorises it and how its use is reviewed. Test the recovery route under controlled conditions. Avoid making the only emergency route depend on the same identity service it is supposed to recover.
Microsoft's Entra role guidance provides product-specific reference material. Confirm feature availability and licensing for your environment before relying on a particular implementation.
When should the review happen again?
Set an appropriate routine, and add triggers such as a role change, supplier exit, system migration or incident. Track unresolved ownership and overdue implementation. A completed annual spreadsheet should not conceal permissions left unchanged after an important event.
Connect the review to joiner, mover and leaver processes, incident coordination and supplier transitions. Discuss an access-control review with Petatec.
Strengthen the setup behind the advice.
Petatec supports cloud migration, cybersecurity, infrastructure optimisation, Microsoft 365, backup, monitoring and operational support.
We will confirm a suitable time with you.
Related Articles

Container Security: Review the Build, Cluster and Recovery Process
Review container images, permissions, isolation, secrets and recovery as one operating process, with evidence from real deployment tests.

Backup Restore Testing for Ransomware Recovery
Test recovery from a protected backup with a clean environment, documented dependencies and evidence that the business task works.

Cybersecurity Training: Practise Safe Decisions and Reporting
Build practical security training around realistic work, easy reporting and technical controls, rather than relying on a yearly quiz.