Skip to content
System hardening
ASD ISMISM-1844

ASD ISM 1844 Do not trust computer accounts other than domain controllers for delegation

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.

In plain English

Set every computer account except domain controllers to 'Do not trust this computer for delegation', allowing neither unconstrained nor constrained delegation.

Computer accounts that are not Microsoft AD DS domain controllers must not be trusted for delegation to services. Delegation lets services on a computer act as a user towards other services. On a computer account's Delegation tab, only 'Do not trust this computer for delegation' complies: trusting it for any service (unconstrained) or for specified services only (constrained) both breach it. A business need does not create an exception. Domain controllers are outside this control, and ISM-1843 covers unconstrained delegation on user accounts.

Why it matters

A computer trusted for delegation can act as users towards other services, and with unconstrained delegation it holds reusable Kerberos tickets from everyone who connects. A malicious actor who takes over one such server, usually less protected than a domain controller, gains that power.

How to implement

  1. List computer accounts trusted for delegation.

    Search each domain for computer accounts with the TRUSTED_FOR_DELEGATION or TRUSTED_TO_AUTH_FOR_DELEGATION flag in userAccountControl, or any value in msDS-AllowedToDelegateTo, and for those named in another object's msDS-AllowedToActOnBehalfOfOtherIdentity (resource-based constrained delegation). Set aside domain controllers by matching against the domain's own list of domain controllers, not by name or OU.

  2. Find out what each setting supports.

    Ask the server's owner which application relies on it, such as a web front end passing users' identities to a database. If a product can delegate only as the computer account, the control is not met until it is changed or replaced.

  3. Move any needed delegation to a service account.

    Run the application under a dedicated service account (ISM-1619 requires group Managed Service Accounts), register its SPNs on that account and remove them from the computer, since ISM-1834 bars duplicate SPNs. Configure constrained delegation there to only the services it needs.

  4. Turn delegation off on every other computer account.

    Set each to 'Do not trust this computer for delegation', clear any services listed in msDS-AllowedToDelegateTo and remove it from any object's msDS-AllowedToActOnBehalfOfOtherIdentity. Then rerun the search to confirm only domain controllers remain, apart from managed service accounts, which are service accounts, not computer accounts.

Keep it running

Alert on computer account change events (4742) that turn delegation on, and recheck after installing server software whose setup asks for it. Meet any such need with a service account instead.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    A search run during the audit of every domain for computer accounts with either delegation flag or any msDS-AllowedToDelegateTo value, or named in another object's msDS-AllowedToActOnBehalfOfOtherIdentity, with the domain's own list of domain controllers.

    Look at

    Every account returned that is not on the list of domain controllers.

    Good evidence

    Every account returned is a domain controller on the domain's own list or a managed service account; no other computer account is trusted for delegation, whatever business reason is given.

  2. Check 2 of 3What an auditor asks for

    Ask for

    The holders of the 'Enable computer and user accounts to be trusted for delegation' user right in the policy applied to domain controllers.

    Look at

    Which accounts and groups could turn delegation back on.

    Good evidence

    Only built-in administrator groups hold the right, so no other account can set a computer's delegation flags or msDS-AllowedToDelegateTo.

  3. Check 3 of 3What an auditor asks for

    Ask for

    Computer account change events (4742) from every domain controller since the last audit.

    Look at

    Any change that turned on delegation for a computer that is not a domain controller, and whether events arrived from every domain controller.

    Good evidence

    Events arrived from every domain controller for the whole period, and none turned on delegation for a computer that is not a domain controller.

Mappings

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

ISO 27001

ISO/IEC 27001: 1 mapping

  • A.5.15Access controlPartially meets

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