Join our Newsletter — 33% off our NHI Course
Home› FAQ› Authentication, Authorisation & Trust› How should security teams decide when to use…
Authentication, Authorisation & Trust

How should security teams decide when to use SAML request signing?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 30, 2026 Domain: Authentication, Authorisation & Trust

Use request signing whenever the IdP supports it, especially if authentication traffic passes through proxies, reverse gateways, or any layer that can alter the request. Signing gives the IdP cryptographic proof that the AuthnRequest came from the expected SP and was not modified in transit. It is most valuable where transport security alone does not cover the full message path.

What SAML request signing is actually proving

SAML request signing is not just a checkbox for federation hygiene. It gives the identity provider cryptographic evidence that the AuthnRequest originated from the expected service provider and that the message was not altered before the IdP processed it. That matters most when the request can traverse intermediaries that inspect, forward, cache, or rewrite traffic.

Transport encryption protects the channel between hops, but it does not by itself prove message origin or protect the request end to end. If a reverse proxy or gateway sits in the path, signing closes the trust gap between “arrived over TLS” and “arrived intact from the right SP.”

When teams should make signing the default

The practical rule is to sign whenever the IdP supports it, then make exceptions only with a clear reason. That is especially important for SP initiated SSO flows, mixed network paths, and environments where routing or security appliances can touch the SAML request before it reaches the IdP. In those cases, the signature is part of the trust model, not an optional extra.

Teams should also treat signing as more valuable when they operate federated SSO across multiple estates or trust boundaries. If a request might be modified in transit, the IdP needs a strong way to distinguish a legitimate SP request from a forged or tampered one. For broader federation hardening, see the Identity Provider and SSO Security Guide and the Identity Federation Failure Modes guide, which both cover how trust assumptions break in real SSO deployments.

What to check before turning it on or relying on it

Before enforcing request signing, confirm that the IdP validates the signature against the correct SP metadata and that the SP certificate is governed like any other trust anchor. Signing only works if certificate distribution, rollover, and retirement are controlled. If the certificate used for signing is stale, misbound, or left unmanaged, the control becomes brittle instead of protective.

Teams should also verify whether the request path includes products that terminate or transform traffic, because the signing decision should follow the actual message path, not the nominal architecture diagram. Where certificate lifecycle is already a pain point, the operational answer is to fix that governance first rather than weaken federation protections. The How to find expiring app secrets and certificates in Entra ID guide is useful when the signing certificate is one of several credentials that must be monitored and rotated on time.

Risk and Threat Considerations

Unsigned or improperly validated SAML requests create a trust boundary that attackers can abuse through request tampering, forged initiation, or manipulation by an intermediary. The main concern is not just eavesdropping, but the ability to influence what the IdP believes the SP asked it to do.

Failure mechanism: A proxy, gateway, or malicious relay alters request parameters, injects an unexpected destination or relay state, or forwards a forged AuthnRequest that the IdP accepts because it lacks cryptographic origin proof.

Impact: The IdP can issue authentication decisions for a request that did not come from the expected SP or that no longer reflects the SP's intent, which can lead to account takeover paths, federation abuse, or session confusion.

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 and NIST SP 800-63 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-2 — Identification and Authentication (Organizational Users)SAML request signing protects federated user authentication assertions.
IA-5 — Authenticator ManagementSigning certificates are authenticators that need lifecycle control and rollover.
IA-9 — Identification and Authentication (Non-Organizational Users)Federated SAML requests from an SP to an IdP are inter-system authentication exchanges.
Recommendation — Validate SAML request signatures to preserve authenticated federation trust. Manage SAML signing certificates with rotation, revocation, and expiry monitoring. Require cryptographic proof for federated requests exchanged between trust domains.
NIST SP 800-63Federation and AssertionsFederation guidance directly addresses assertion trust and message protection in SSO.
Recommendation — Apply federation controls that protect assertions and request integrity end to end.
ISO/IEC 27001:2022A.5.15 — Access controlSigned requests reinforce trusted access decisions in federated SSO.
Recommendation — Ensure federated access decisions rely on authenticated, integrity-protected requests.

Practitioner Guidance

Decision rule: If the IdP supports signed requests, enable them by default and treat any exception as a documented risk acceptance with expiry. If a path includes proxies, load balancers, or security middleware that can touch the payload, signing should be considered mandatory rather than nice to have.

What to verify: Confirm that the IdP actually enforces signature validation for the correct SP, that certificate rollover is tested before production change windows, and that the trust relationship still works after any routing or federation topology change.

Practitioner takeaway: The key question is not whether TLS is present, but whether the IdP can trust the request itself. If the message can be altered between the SP and the IdP, request signing is the control that preserves federation integrity.

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