SAML Assertion Forgery is the creation or alteration of a SAML assertion so it is accepted as trusted by a service provider. It targets the XML token used for single sign-on, usually by abusing weak signature validation, incorrect certificate trust, or replayable assertions.
What SAML Assertion Forgery Means in Practice
SAML assertion forgery is not just a malformed token, it is a trust failure. The attacker is trying to make a service provider accept a fabricated or altered assertion as if it came from a legitimate identity provider, which turns a single sign-on transaction into an authentication bypass or impersonation path.
The danger comes from the fact that SAML assertions are security decisions, not ordinary data objects. If signature checks are weak, certificate trust is wrong, or a replayable assertion is accepted more than once, the relying service can end up granting access to the wrong principal while still believing its verification logic worked correctly.
This is why SAML security is often discussed alongside federation trust rather than just login flow. SAML Security Guide is the most direct starting point for the trust, validation and signing assumptions that forged assertions abuse.
How the Forgery Works
At a technical level, forgery usually depends on one of a small number of validation failures. The service provider may accept an assertion without verifying the signature on the exact payload it consumes, trust the wrong certificate chain or metadata source, or fail to bind the assertion to the intended audience, recipient, or time window.
Some attacks alter a valid assertion in transit, while others create a new token that looks structurally correct and is then accepted because the verifier only checks part of the message. That is why the issue is often discussed together with XML signature wrapping and response forgery: the adversary is exploiting a gap between what was signed, what was parsed, and what was actually authorised.
When teams need a clearer distinction between login flows and trust relationships, Federation vs SSO helps separate the identity trust model from the user experience layer.
Where Exposure Usually Comes From
Exposure is rarely caused by SAML alone. It usually appears when a service provider accepts inbound federation from multiple identity providers, relies on stale metadata, or inherits implementation shortcuts in assertion handling, certificate rollover, or replay protection.
Organisations should review where SAML is used for workforce access, partner access, or legacy application onboarding, because the most fragile deployments are often the ones with the oldest integration assumptions. A forged assertion becomes materially more dangerous when it can reach high-value applications, privileged roles, or applications with weak session binding.
For reader navigation across the common decision points around SAML, OIDC and validation controls, SAML vs OIDC Guide is useful because it ties token validation to protocol choice and migration decisions.
Detection, Containment and Recovery
Detection usually starts with looking for impossible or inconsistent federation events, such as unexpected issuer values, audience mismatches, unusual assertion lifetimes, or access granted without the normal user journey. If a forged assertion is accepted, the compromise review should assume the attacker may already have a valid session and may try to persist by abusing trust relationships rather than passwords.
Containment is often about revoking trust rather than only blocking a single account. That can mean rotating signing certificates, invalidating suspicious sessions, reviewing federation metadata changes and checking whether the service provider accepted any assertions during the suspected window.
When a compromise has already reached the identity layer, the right response sequence matters. If your customer identity (CIAM) platform is compromised provides a strong recovery pattern for rotating trust material, resetting sessions and rebuilding confidence after forged-token activity.
Risk and Threat Considerations
SAML assertion forgery is attractive because it targets the trust boundary that turns identity proof into application access. If the relying party accepts a forged or replayed assertion, the attacker may bypass MFA, impersonate a user, inherit entitlements, or pivot into downstream applications that trust the federated login.
Failure mechanism: Weak signature validation, incorrect certificate trust, poor audience or recipient checking, or replayable assertions let an attacker present a token that the service provider treats as authentic.
Impact: The result can be account impersonation, unauthorised application access, session hijacking, privilege abuse, and broader federation trust compromise if the same signing material or trust relationship is reused elsewhere.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and NIST SP 800-63 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | SAML assertions authenticate organizational users into relying apps. |
| IA-5 — Authenticator Management | SAML forgery often exploits signing material, trust, and replay windows. | |
| AC-3 — Access Enforcement | Forged assertions can incorrectly trigger application access decisions. | |
| Recommendation — Verify federated user authentication and enforce strong assertion validation before granting access. Rotate signing credentials, validate trust anchors, and revoke compromised federation material promptly. Enforce access decisions only after audience, recipient, and signature checks succeed. | ||
| NIST SP 800-63 | C.3 — Federation | Defines federation assurance expectations for assertions and trust relationships. |
| Recommendation — Apply federation assurance controls to validate assertion provenance and trust binding. | ||
| MITRE ATT&CK | T1606.002 — SAML Tokens | Covers adversary use of forged SAML assertions to impersonate users. |
| T1484.002 — Domain Trust Modification | Federation trust abuse can alter trusted identity relationships. | |
| Recommendation — Map suspicious federation activity to SAML token abuse and hunt for forged assertion use. Monitor federation trust changes and alert on unauthorized trust modifications. | ||
Practitioner Guidance
Why practitioners should care: SAML assertion forgery is usually not a single bug, it is a verification failure across the federation chain. The practical question is whether your service provider validates the exact assertion it consumes, not just whether the login flow appears to work.
What to watch for: Pay attention to certificate rollover handling, assertion lifetime, audience and recipient enforcement, replay handling, and any application that accepts federation without strong metadata governance. If one of those controls is weak, the trust model is easier to abuse than many teams assume.
Practitioner takeaway: Treat SAML trust material like a security boundary, not configuration plumbing, and review it with the same seriousness you would apply to authentication bypass risk.
Related resources from NHI Mgmt Group
- What are the signs that a service provider may have been targeted by SAML assertion forgery?
- What breaks when SAML signature verification and assertion processing are separated?
- What breaks when SAML signature validation and assertion parsing use different XML libraries?
- How should security teams implement SAML assertion validation in a homegrown service provider?
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 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org