Join our Newsletter — 33% off our NHI Course
Home› Glossary› Agentic AI & Autonomous Identity› Not Delegated Flag
Agentic AI & Autonomous Identity

Not Delegated Flag

← Back to Glossary
By NHI Mgmt Group Updated November 4, 2026 Domain: Agentic AI & Autonomous Identity

A directory attribute that prevents an identity from being used in delegation flows. For machine accounts, it exists even when the administration console does not surface the checkbox, so validation must be performed directly against the object attributes rather than through the UI alone.

What the flag means in practice

The not delegated flag is a directory-level protection bit, not a human-facing convenience setting. It tells the directory and downstream access logic that this identity must not participate in delegation flows, which matters because delegation changes who can act on whose behalf and can expand the blast radius of a compromise.

For machine accounts, the important point is that the object can carry the attribute even when the admin console does not expose a checkbox. That means the authoritative source of truth is the directory object itself, not the UI representation, and validation should be done against the attribute value directly.

Where it matters in identity and access control

This flag sits squarely in access governance because delegation is an authority transfer, not just an authentication detail. When delegation is enabled, the environment is asserting that one identity may obtain or use access in a way that represents another identity, so the flag is effectively a constraint on impersonation, constrained delegation, and related trust paths.

In practical terms, the value matters most for accounts that should never become a stepping stone for lateral movement or service impersonation. If the attribute is set incorrectly, an identity that should be tightly bound to its own permissions can be pulled into a broader trust chain and inherit access it should not have.

How administrators verify it

Verification should start with the object attributes in the directory, then be reconciled against any console view or automation output. That ordering is important because management tooling may hide attributes, simplify them, or present a view that is not complete enough for security validation.

The useful test is whether the effective directory object state matches the intended delegation policy. For audit and troubleshooting, that means checking the raw attribute on the account, confirming whether the identity is expected to be non-delegable, and then verifying that adjacent controls such as service account handling and delegation policy align with that intent.

  • Check the directory object directly, not just the administrative UI.
  • Confirm the intended non-delegable status for privileged, service, or machine identities.
  • Compare the attribute against the access paths that rely on delegation.

What can go wrong if it is wrong

If the flag is absent when it should be present, the main failure mode is unintended delegation. That can allow an attacker who compromises the identity, or a system that uses it, to move through trusted delegation paths and access resources that should have remained out of reach.

Because delegation often sits inside service-to-service workflows, the failure can be quiet: access may still look legitimate from the receiving system’s point of view. That makes incorrect attribute state especially relevant for machine accounts, where the console may not make the setting obvious and the security boundary is easy to misread.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5, CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-2 — Identification and Authentication (Organizational Users)Delegation controls affect how authenticated identities can act on behalf of others.
AC-6 — Least PrivilegeThe flag constrains whether an identity can be used in delegated access paths.
IA-5 — Authenticator ManagementMachine accounts and delegation controls depend on secure account and credential handling.
Recommendation — Review delegation settings alongside IA-2 so authenticated users are not granted unintended on-behalf-of access. Apply AC-6 to prevent identities from inheriting broader delegated access than required. Use IA-5 to keep account state and credential governance aligned with delegation policy.
CIS Controls v8CIS-5 — Account ManagementNon-delegable account state is part of secure account governance and review.
Recommendation — Include delegation-restriction checks in account management reviews and recertification.
NIST CSF 2.0PR.AA-05 — Identity Access ManagementThis control family covers managing access relationships that delegation changes.
Recommendation — Validate delegation-restriction attributes as part of identity access management controls.

Practitioner Guidance

Governance implication: Treat this as an object-level control that needs periodic validation, not a one-time UI check. Ownership should sit with the team that manages the directory source of truth, because the security outcome depends on the actual attribute on the account object.

What to watch for: Look for accounts that are meant to be non-delegable but are created, cloned, or modified through automation that does not preserve the attribute consistently. Those are the cases most likely to create drift between intended policy and effective directory state.

Practitioner takeaway: If delegation is security-sensitive in your environment, assume the console can be incomplete and make raw attribute inspection part of routine validation.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org