ASD ISM 1835 Restrict delegation of privileged Active Directory accounts
What it says
Privileged user accounts are configured as sensitive and cannot be delegated.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishEnsure privileged accounts are marked as sensitive and cannot be delegated to maintain security.
This control is about making sure that certain high-level accounts in your system, like those with the power to make big changes, can't have their access easily transferred to others. This matters because if someone maliciously gets control of one of these accounts, they could cause serious harm to your business, like stealing sensitive data or bringing your systems down.
Free. Save your status, tasks and notes.
Why it matters
Without this control, attackers could abuse delegation to compromise critical Active Directory accounts, leading to data breaches or system takedowns.
How to implement
IT teams should mark privileged accounts as sensitive in the Active Directory system.
You can do this by accessing the properties of each account and ticking the option that labels it as sensitive. This setting prevents other accounts from gaining the same privileges by delegation.
System administrators should review all accounts with high privileges regularly.
Go through the list of accounts with the ability to change significant settings or access sensitive data, and confirm that they are marked as sensitive. This helps ensure no account is overlooked.
Managers should set up a policy review to ensure delegation settings are accurate.
Work with IT to create a checklist of accounts that should never be delegated, update policies to reflect this, and communicate the importance to all relevant staff.
Human Resources should coordinate with IT to review account privileges when employees move roles or leave.
Ensure that any changes are reflected immediately in the system to prevent unnecessary or incorrect delegation of power.
Security officers should organise training sessions for staff to understand the importance of protecting privileged accounts.
Use simple scenarios to explain the risks of mishandling these accounts, and offer practical guidance on maintaining vigilance.
Keep it running
Regularly audit privileged AD accounts to confirm "Account is sensitive and cannot be delegated" remains enabled, and alert on any changes to this setting.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
The list of privileged accounts marked as sensitive: Request documentation from the IT department showing which accounts have the sensitive setting activated.
Look at
Whether accounts listed correspond to those holding privileged roles.
Good evidence
Includes a dated record of all such accounts with verification steps.
- Check 2 of 5What an auditor asks for
Ask for
To see the policy document on account privileges: Request the official policy that outlines how privileged accounts should be handled.
Look at
Clear statements about preventing delegation.
Good evidence
Is a policy document with specific guidelines on handling and updating account settings.
- Check 3 of 5What an auditor asks for
Ask for
A recent review report of privileged accounts: Check if there is a report documenting a review of these account settings.
Look at
Dates indicating regular reviews and updates.
Good evidence
Includes a recent report with any adjustments made and the rationales.
- Check 4 of 5What an auditor asks for
Ask for
About training materials provided for staff: Request any presentations or documents used in training sessions about account sensitivity and delegation.
Look at
Content that covers the risks and importance of sensitivity settings.
Good evidence
Includes comprehensive material with structured learning outcomes.
- Check 5 of 5What an auditor asks for
Ask for
To see an example of a response to a role change: Request documentation showing how a role or staff change was managed in terms of account settings.
Look at
Evidence of timely actions to update account privileges.
Good evidence
Provides clear timelines and actions taken by IT and HR teams.
Mappings
Closest match in ISO/IEC 27001: A.8.2, Management of privileged access rights, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.2.
ISM-1835 requires privileged Active Directory (AD) accounts to be configured as sensitive so they cannot be delegated, reducing the risk of credential forwarding and impersonation in AD/Kerberos flows. Annex A 8.2 requires an organisation to restrict and manage the allocation and use of privileged access rights, which includes applying technical controls that prevent misuse of privileged credentials (such as disallowing delegation for high-privilege identities). Annex A 8.2 is broader across all systems and privileged right types, while ISM-1835 is a specific Australian Government ISM hardening requirement for AD privileged account configuration.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




