Skip to content
System hardening
ASD ISMISM-1844

ASD ISM 1844 Prevent non-controller accounts from delegating services

What it says

Computer accounts that are not Microsoft AD DS domain controllers are not trusted for delegation to services.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

Ensure non-domain controller accounts can't be used to delegate services in Active Directory.

This control is about ensuring that computer accounts which are not managing the overall network (non-domain controllers) don't have permission to sneakily use services they shouldn't in your organisation through Microsoft Active Directory. If we're not careful here, someone might exploit these accounts to access sensitive information or even disrupt your business operations.

Why it matters

If non-domain controller computer accounts are trusted for delegation, attackers can impersonate services, escalate privileges and move laterally.

How to implement

  1. IT team should review all computer accounts: Go through each account in your Active Directory that's not a domain controller and check their delegations.

    Make sure they don't have unnecessary permissions that allow them to act on behalf of legitimate accounts.

  2. System administrator should update delegation settings: Ensure only domain controllers have the right to delegate services.

    You can do this by accessing the properties of non-controller accounts in Active Directory and adjusting any settings that allow delegation.

  3. Manager should schedule regular training: Ensure staff understand why only domain controllers should delegate services.

    Hold a session where you explain, using examples, how improper settings can lead to security risks.

  4. IT team should implement monitoring tools: Use monitoring tools to alert the team when a non-controller account is granted delegation rights.

    This can be set up within your Active Directory system or with an external monitoring tool that flags these changes.

  5. Security officer should establish a review policy: Set up a policy that includes regular checks on delegation settings as part of your security practices.

    This policy should specify who checks, what they check, and how frequently.

Keep it running

Audit AD delegation (Trusted for delegation/Constrained) and ensure only domain controllers are permitted; remove delegation from all others.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The delegation permissions report: Request a recent export of delegation settings for all non-controller accounts.

    Look at

    The specific permissions given to each account.

    Good evidence

    Is that no unnecessary delegation permissions are listed for non-controller accounts.

  2. Check 2 of 5What an auditor asks for

    Ask for

    Documentation of delegation setting changes: Request logs showing any changes made to delegation rights for non-controller accounts.

    Look at

    The dates and details of the changes.

    Good evidence

    Shows only authorised changes made by the IT team.

  3. Check 3 of 5What an auditor asks for

    Ask for

    The training records: Request the attendance records for any training sessions about delegation rights.

    Look at

    Dates, topics covered, and attendees.

    Good evidence

    Is recent and includes all relevant staff, showing they understand the importance.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Procedures on handling delegation alerts: Request documents outlining steps to follow when a delegation alert is raised.

    Look at

    The step-by-step process.

    Good evidence

    Is detailed and shows clear accountability and rapid response actions.

  5. Check 5 of 5What an auditor asks for

    Ask for

    To see the policy review schedule: Request the schedule and results of recent reviews of delegation settings.

    Look at

    The frequency and thoroughness of reviews.

    Good evidence

    Includes recent, regular reviews and clear documentation of findings.

Mappings

Closest match in ISO/IEC 27001: A.5.15, Access control policies and procedures, which this control partially meets.

ISO 27001

ISO/IEC 27001: 1 mapping

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.