The policy that defines which principals can assume an IAM role and under what conditions. It is a core cloud access control boundary, and migrations can break it when role names, principals, or account assumptions change, even if the target platform and workload remain the same.
What the trust relationship does
An IAM role trust relationship is the policy layer that controls who can assume a role, and under what conditions. It sits at the boundary between an external principal and temporary role access, so it is not just metadata, it is an access decision that can open or close a cloud trust path.
The trust policy is separate from the role’s permission policy. That distinction matters because a role can be perfectly scoped on what it is allowed to do, yet still be exposed if the trust side allows the wrong principal, account, service, or federated identity to assume it. In AWS terms, this is where AWS IAM Policies and Roles Guide becomes useful for understanding how trust, chaining, and permissions interact.
Why it is a security boundary
Trust relationships are security boundaries because they decide which identities can cross into a privileged context. If the trust policy is too broad, the role may become assumable by unintended principals, cross-account actors, or services that were never meant to have that reach.
That boundary is especially important in cloud environments where assumption is often indirect. A workload, application, or third party may never hold the role’s permissions directly, but if it can satisfy the trust policy, it can still inherit the role’s authority through temporary credentials. For this reason, Cloud Workload Identity Guide is a good companion when the trust path is tied to workload, service, or federation patterns.
How trust policies fail during migration
Migrations often break or distort trust relationships because the trusted entity changes shape even when the workload does not. Role names may change, account IDs may differ, federation sources may move, or assumptions about who can assume what may no longer hold after landing in the target environment.
These failures can be subtle. A migration can leave a role effectively unusable because the expected principal no longer matches, or dangerously overexposed because a temporary compatibility rule remains in place after cutover. The trust path itself is the thing to review, not only the destination permissions. When migration includes cross-account access, How to review AWS cross-account trust policies for confused deputy is especially relevant because confused-deputy conditions often surface in exactly these transitions.
Signals that the trust policy needs review
Any change to the principal, account boundary, identity provider, external access pattern, or service integration should trigger a trust review. If the policy still contains old account assumptions, wildcard principals, stale third-party access, or conditions copied from another environment, the role can end up trusted by the wrong thing for the wrong reason.
Cross-cloud and third-party setups need extra care because the trust layer may be the only enforcement point before temporary credentials are issued. In those cases, Federation and Trust Relationships Guide helps frame the broader trust model, including how federated paths, cross-tenant relationships, and trust exposure windows behave.
Risk and Threat Considerations
Weak or stale IAM role trust relationships can create unintended privilege paths, especially after migrations, federation changes, or third-party integrations. The main risk is not just misconfiguration, it is durable trust that continues to grant access long after the original business assumption has changed.
Failure mechanism: An attacker, compromised external principal, or misrouted service can satisfy an overly broad trust policy and assume the role, then use the temporary credentials to move laterally or reach sensitive resources.
Impact: The result can be privilege escalation, cross-account exposure, persistence through trusted access paths, and in some environments a fast path from a small configuration mistake to broad cloud 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 CSA Cloud Controls Matrix set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-9 — Identification and Authentication (Service and Non-Organizational Users) | Trust policies govern which external or service principals can assume a role. |
| AC-6 — Least Privilege | Role trust scope determines who can reach privileged access in the first place. | |
| IA-5 — Authenticator Management | Role trust often depends on credentialed federation and temporary access material. | |
| Recommendation — Apply IA-9 to restrict role assumption to trusted non-organizational principals and required conditions. Limit role trust to the minimum principals and conditions needed for the business use case. Manage role-assumption credentials and trust inputs so they remain current, bounded, and revocable. | ||
| CSA Cloud Controls Matrix | IAM — Identity and Access Management | Cloud IAM controls include trust, federation, and role-assumption boundaries. |
| Recommendation — Define and monitor cloud trust relationships as part of the IAM control domain. | ||
| OWASP Non-Human Identity Top 10 | NHI-05 — Overprivileged NHI | Role trust can overexpose non-human principals through excessive assume-role scope. |
| Recommendation — Review role trust to ensure machine and workload identities cannot assume more privilege than required. | ||
Practitioner Guidance
Governance implication: Treat the trust policy as an owned security control, not an implementation detail hidden behind the role. The team responsible for the role should be able to explain exactly who can assume it, why each principal is trusted, and what condition keeps that trust bounded.
What to watch for: Replatforming, account renumbering, federation changes, and inherited templates are the moments when trust policies drift. If the migration plan changes the identity path but the trust policy is copied unchanged, assume the boundary is wrong until proven otherwise.
Practitioner takeaway: Review trust as a separate artifact from permissions, because a least-privilege role can still be unsafe if the wrong principal can get into it.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org