Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Non-Transitive Trust
Governance, Ownership & Risk

Non-Transitive Trust

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Governance, Ownership & Risk

A non-transitive trust is intended to stop trust from extending outside the two domains that formed it. Administrators use it to limit authentication scope between specific domains. In Kerberos environments, however, referral chaining can undermine that expectation and allow access to additional domains within the trusting forest.

What Non-Transitive Trust Means in Practice

Non-transitive trust is a trust relationship that is meant to stay bounded between the two domains that established it. In practice, that means administrators expect authentication to stop at the intended boundary, rather than cascading farther across a forest or federated environment.

That expectation matters because the trust model is part of the security boundary, not just a configuration detail. When the boundary is not enforced as intended, a relationship created for convenience can become a path for broader access than the organisation planned.

How Non-Transitive Trust Works in Domain Design

In a well-scoped design, a non-transitive trust is used to reduce blast radius. One domain can accept authentication from another domain without automatically inheriting every other trust path that may exist elsewhere in the environment.

This is why the term often appears in Active Directory, forest trust, and federation discussions. The control idea is simple, but the real-world result depends on the whole trust topology, including whether the implementation preserves the intended boundary or introduces referral paths that extend it.

NHIMG’s Federation and Trust Relationships Guide goes deeper on forest trusts, selective authentication, SID filtering, and the ways trust relationships can be abused or overextended.

Why Kerberos Referral Chaining Changes the Risk

Kerberos can complicate the neat theory of non-transitive trust because referral chaining may carry authentication requests beyond the two domains that initially formed the trust. That is the important security nuance: the trust may be configured as non-transitive, yet the access path can still expand if the surrounding Kerberos and forest design allows referrals to keep propagating.

This is not just an architectural curiosity. If an organisation assumes the trust boundary is narrower than it really is, administrators may leave additional domains reachable, underestimate lateral movement potential, or miss where authentication decisions are effectively being delegated beyond the original relationship.

The same boundary problem is often encountered when teams treat zero trust as a slogan instead of a control model. Top 10 Zero Trust Mistakes is useful here because it frames how weak assumptions about trust scope and access paths create avoidable exposure.

What Administrators Need to Verify and Govern

For practitioners, the key question is not whether a trust is labelled non-transitive, but whether the effective authentication path matches that label. That requires checking the trust topology, the domain and forest boundaries, and any authentication behaviours that may widen the reachable set of domains.

It is also important to distinguish the intended trust scope from the actual access scope users and services receive. If referral chaining, cross-forest relationships, or federation settings expand reach, the trust boundary should be reviewed as an active security control rather than a one-time directory setting.

Zero Trust Maturity Model Guide is relevant as a governance lens because it encourages teams to treat access boundaries, policy enforcement, and trust assumptions as measurable maturity concerns.

Risk and Threat Considerations

Non-transitive trust becomes risky when the organisation believes the trust boundary is tighter than the implementation actually allows. The danger is expanded access, especially where Kerberos referral chaining or related trust paths let an attacker move from an initially trusted domain into additional domains that were not meant to be reachable.

Failure mechanism: A trust relationship is configured or understood as bounded, but referral behaviour, forest design, or adjacent trust paths extend authentication farther than expected, undermining the intended containment.

Impact: Attackers or unintended users may gain broader domain reach, increasing lateral movement opportunity, privilege exposure, and the size of any compromise.

Standards & Framework Alignment

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

OWASP Non-Human Identity Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-4 — Information Flow EnforcementNon-transitive trust is about limiting cross-domain authentication flow and boundary reach.
IA-2 — Identification and Authentication (Organizational Users)Domain trust affects how users are authenticated across trusted domain boundaries.
AC-6 — Least PrivilegeTrust scope expansion increases reachable access and can violate least-privilege expectations.
Recommendation — Enforce domain trust boundaries so authentication flow cannot exceed the approved scope. Validate that cross-domain authentication only succeeds where the trust design explicitly allows it. Restrict cross-domain access paths to the minimum required for business need.
CIS Controls v8CIS-6 — Access Control ManagementTrust relationships are an access-control boundary that must be inventoried and reviewed.
Recommendation — Inventory trust relationships and remove or constrain any that expand access beyond intent.
OWASP Non-Human Identity Top 10NHI-05 — Overprivileged NHIDirectory and federation trust expansion can overextend non-human access scope in identity systems.
Recommendation — Review machine and service trust paths so non-human identities do not inherit excessive domain reach.

Practitioner Guidance

What to watch for: Verify the effective authentication path, not just the trust label. If a domain trust is meant to be non-transitive, validate whether referral chaining, forest relationships, or federation settings create a wider path in practice.

Governance implication: Treat trust scope as a security decision that needs ownership, periodic review, and documentation. The operational question is whether the environment still enforces the boundary the design intended.

Practitioner takeaway: A non-transitive trust is only protective when the surrounding directory and Kerberos behaviour preserve that boundary; otherwise the label can overstate the real containment.

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 October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org