ASD Essentials IT.PRO-12.1 Periodically review and update privileges to match roles, duties and business requirements
What it says
Periodically review and update access privileges in alignment with current roles, duties and business requirements.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishPeriodically review access privileges and update them so they match current roles, duties and business requirements.
Your organisation must periodically review access privileges and update them in line with current roles, duties and business requirements. Access privileges are the systems, data and functions an account can use. Your organisation sets how often. Both parts apply: a review that records a mismatch but leaves the privilege in place falls short. Privileges are judged against current roles, duties and business requirements, not those that applied when access was granted.
Free. Save your status, tasks and notes.
Where this action applies
What's in each domain?ASD orders the work by domain: apply this action to each ticked domain, phase by phase.
- Phase 3
Why it matters
People change jobs and keep what they had, so a stolen account can reach far more than its owner's current work needs. A review finds the leftover access, and the update removes it, which limits what that account can do.
How to implement
Map privileges to roles, duties and business requirements.
For each system, write down what each role needs and why, starting from the identity platform's groups. This gives reviewers something to judge against besides what the account already holds, and it should match the minimum access IT.PRO-12.3 requires at provisioning.
Set the review cycle and scope.
Your organisation decides how often each system is reviewed, based on its risk, and privileged access usually warrants more frequent review. Cover user, administrative and non-person accounts in every system, including bought services.
Export live access and have someone who knows the work review it.
Pull accounts and privileges directly from each system, not from request records. Send them to the manager, or the system owner for non-person accounts, to confirm or remove each one. Nobody reviews their own access. If a bought service has no export, use its administration console's user list.
Update privileges and record the outcome.
Remove or reduce what no longer fits, then export again to confirm the change applied. Keep each reviewer's decisions and dates. If a privilege outside the role must stay, record the business requirement behind it. Disable or remove accounts found unused, unless they meet the exception conditions in IT.PRO-13.1.
Keep it running
Feed role changes into access updates so they do not wait for the next review. Look again after a restructure, a merger, a new system or an incident involving excessive access.
Evidence and audit
- Check 1 of 4What an auditor asks for
Ask for
A live privilege export from sampled systems, compared with the last review's records.
Look at
Whether accounts and privileges in the live system were all covered, including administrative and non-person accounts.
Good evidence
Every account and privilege in the export was covered by the last review or was granted after it with a recorded approval.
- Check 2 of 4What an auditor asks for
Ask for
People who changed role, selected from workforce records, with their current privileges.
Look at
Their privileges against the new role, duties and business requirements.
Good evidence
Each person's privileges match their current role and duties, and access from the old role has been removed or has a recorded business requirement.
- Check 3 of 4What an auditor asks for
Ask for
Review records from the last cycle, matched to removal tickets and the live system.
Look at
Review dates against the cycle your organisation set, who reviewed, and whether removals really took effect.
Good evidence
Reviews ran within the set cycle, each decision names a reviewer other than the account holder, and every privilege marked for removal is gone from the live system.
- Check 4 of 4What an auditor asks for
Ask for
Privileged group membership from the identity platform, compared with the role mapping.
Look at
Whether each member has a current role, duty or business requirement for the access.
Good evidence
Every member of a sampled privileged group has a current role, duty or business requirement in the mapping that calls for the access.
ASD indicators of good practice (12)
The indicators below are quoted as published from ASD's Assessment evidence guide for enterprise IT. These optional indicators help an assessor judge the action in each domain where it applies: if any not effective statement is true, the action is rated not effective; if every applicable fully effective statement is true and no other statement is, it is rated fully effective; otherwise it is rated partially effective. ASD says the indicators "do not replace expert judgement, nor are they intended to serve as a checklist".
Not effective(4)
- NE-1Access privileges are not reviewed against current roles, duties and business requirements.
- NE-2Access reviews do not identify privileges that are no longer required.
- NE-3Access privileges are not updated when personnel roles, duties or business requirements change.
- NE-4Access privileges are not mapped to roles, duties and business requirements.
Partially effective(4)
- PE-1Access reviews are conducted for some accounts or systems, but coverage is incomplete.
- PE-2Reviews identify excessive or obsolete privileges, but updates are incomplete or not completed within timeframes defined by the organisation.
- PE-3A process to review access privileges exists but only occurs on an ad hoc basis.
- PE-4Some access privileges are mapped to roles, duties and business requirements, but not all.
Fully effective(4)
- FE-1Access privileges for all applicable accounts and systems are reviewed within a cycle defined by the organisation and aligned with current roles, duties and business requirements.
- FE-2Privileges identified as excessive or obsolete are removed or updated within timeframes defined by the organisation.
- FE-3Review outcomes and resulting access changes are documented and available as evidence.
- FE-4Access privileges are mapped to current roles, duties and business requirements.
Mappings
Closest match in ISO/IEC 27001: A.5.18, Access rights, which this control partially meets.
ISO/IEC 27001: 2 mappings
This control partially meets A.5.18.
IT.PRO-12.1 requires access privileges to be periodically reviewed and updated so they stay aligned with current roles, duties and business requirements. This directly implements the review and modification of access rights required by Annex A 5.18. Annex A 5.18 is broader, also covering the provisioning and removal of access rights in line with the access control policy and rules.
This control partially overlaps A.8.2.
IT.PRO-12.1 requires access privileges to be periodically reviewed and updated in line with current roles, duties and business requirements. Applied to privileged accounts, this review is part of restricting and managing privileged access rights under Annex A 8.2. IT.PRO-12.1 also covers non-privileged access, while Annex A 8.2 goes further on privileged access, including how such rights are allocated and how their use is controlled.
ASD Essential Eight: 3 mappings
This control partially overlaps E8-RA-ML1.1.
IT.PRO-12.1 requires access privileges to be periodically reviewed and updated to match current roles, duties and business requirements; E8-RA-ML1.1 requires privileged access requests to be validated when first requested, the initial check that periodic reviews then build on.
This control partially overlaps E8-RA-ML2.1.
IT.PRO-12.1 requires access privileges to be periodically reviewed and updated to match current roles, duties and business requirements; E8-RA-ML2.1 requires privileged access to be disabled after 12 months unless revalidated, a specific periodic review cycle for privileged access.
This control partially overlaps E8-RA-ML3.1.
IT.PRO-12.1 requires access privileges to be periodically reviewed and updated to match current roles, duties and business requirements; E8-RA-ML3.1 limits privileged access to what users and services need for their duties, the outcome those reviews maintain.
ASD Information Security Manual: 1 mapping
This control partially overlaps ISM-1852.
IT.PRO-12.1 requires access privileges to be periodically reviewed and updated to match current roles, duties and business requirements; ISM-1852 limits unprivileged access to what users need for their duties or functions, the outcome those reviews maintain.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




