secrets-acl.html.md.erb

---
title: Tracking Access Control
last_reviewed_on: 2024-07-26
review_in: 6 months
---
# <%= current_page.data.title %>

You should track the list of users who have access to secrets by logging the permissions, such as accounts and credentials, associated with a security resource in a single, centralised Access Control List (ACL). 

The ACL specifies who or what is allowed to access the resource containing secrets and the operations which are allowed to be performed on the resource. See [Principle of Least Privilege](/standards/principle-least-access.html) for guidance on minimising access rights.

User access rights must be reviewed when people change roles or teams as part of your joiners, leavers and movers process. ACLs should also be regularly reviewed on a predefined cadence (e.g. monthly, quarterly).

Identified exceptions should be raised with the colleague responsible for risk management in the directorate for escalation.

Teams ACL review should be documented to reflect:

* who (colleague) completed the review
* date review is undertaken
* next review date
* any changes to user status granted access, and the reason for change (if any)

## Further guidance
- [How to manage access to your third-party service accounts](/standards/accounts-with-third-parties.html)
- [NCSC Cyber Assessment Framework - Principle B2 Identity and Access Control](https://www.ncsc.gov.uk/collection/cyber-assessment-framework/caf-objective-b/principle-b2-identity-and-access-control)