Techniques › T1606 › T1606.002
T1606.002 SAML Tokens
credential access — SaaS, Windows, IaaS, Office Suite, Identity Provider · attack.mitre.org · JSON
1
MITRE detection strategy
5
analytics
0
Sigma rules tagged attack.t1606.002
0
KEV CVEs mapped here
<p>An adversary may forge SAML tokens with any permissions claims and lifetimes if they possess a valid SAML token-signing certificate. The default lifetime of a SAML token is one hour, but the validity period can be specified in the <code>NotOnOrAfter</code> value of the <code>conditions ...</code> element in a token. This value can be changed using the <code>AccessTokenLifetime</code> in a <code>LifetimeTokenPolicy</code>. Forged SAML tokens enable adversaries to authenticate across services that use SAML 2.0 as an SSO (single sign-on) mechanism.</p><p>An adversary may utilize Private Keys to compromise an organization's token-signing certificate to create forged SAML tokens. If the adversary has sufficient permissions to establish a new federation trust with their own Active Directory Federation Services (AD FS) server, they may instead generate their own trusted token-signing certificate. This differs from Steal Application Access Token and other similar behaviors in that the tokens are new and forged by the adversary, rather than stolen or intercepted from legitimate users.</p><p>An adversary may gain administrative Entra ID privileges if a SAML token is forged which claims to represent a highly privileged account. This may lead to Use Alternate Authentication Material, which may bypass multi-factor and other authentication protection mechanisms.</p>
KEV CVEs mapped to this technique · CTID Mappings Explorer
None. No KEV entry in the public mapping names this technique. Given that 74.7% of KEV has no mapping at all, this says more about the mapping than about the technique.
Detection strategy · ATT&CK Enterprise v19.2
- DET0148 Detection Strategy for Forged SAML Tokens v1.0
AN0418 Identity ProviderForged SAML tokens can be observed as authentication attempts with valid signatures but missing expected preceding Kerberos or authentication events. Defenders may correlate SAML assertions with absent Event IDs 4769, 1200, or 1202, or tokens issued with abnormal lifetimes, issuers, or claims compared to baseline.azure:signinlogs
SAML-based login with anomalous issuer or NotOnOrAfter lifetime→ DC0088 Logon Session MetadataTunable:TokenLifetimeThresholdTrustedIssuerListAN0419 IaaSForged SAML tokens in IaaS environments often manifest as cross-cloud or cross-account authentication without matching STS events. Defenders may see AssumeRole or GetFederationToken API usage without a corresponding SAML assertion log from the trusted IdP.CloudTrail:SigninSAML login without corresponding IdP authentication log→ DC0067 Logon Session CreationTunable:CrossAccountUsageAN0420 WindowsForged SAML tokens may be used on Windows systems to authenticate to federated apps without normal Kerberos activity. Defenders may detect anomalous event correlation, where access to SaaS/O365 via SAML occurs without prior TGT requests or user logons.WinEventLog:ADFSToken issuance events showing anomalous claims or issuers→ DC0006 Web Credential CreationTunable:ClaimAnomalyThresholdAN0421 SaaSForged SAML tokens can appear as SaaS logins where authentication succeeded without MFA, or where tokens contain claims inconsistent with the user profile. Look for concurrent sessions across different geographies with the same SAML assertion ID.m365:unifiedAbnormal user claims or unexpected elevated role assignment in SAML assertion→ DC0088 Logon Session MetadataTunable:GeoVelocityThresholdAN0422 Office SuiteForged SAML tokens may be leveraged to access O365 apps such as Outlook or SharePoint. Defenders should monitor for token replay across multiple clients or access attempts to privileged mailboxes without prior interactive login.m365:exchangeMailbox access using SAML token without corresponding MFA event→ DC0007 Web Credential UsageTunable:ReplayDetectionThreshold
Sigma rules · SigmaHQ da9bb07d64, tag attack.t1606.002
No Sigma rule carries this tag. MITRE publishes a detection strategy above, so the behaviour is specified; what is missing is public detection content.
Rules tagged at the parent level (attack.t1606) 1
These target the parent technique, not this sub-technique specifically. Listed for completeness, not counted as coverage.
Author: Mark Morowczynski '@markmorow', Gloria Lee, '@gleeiamglo'
· 2023-09-03 · logsource: product=azure service=riskdetection · e3393cba-31f0-4207-831e-aef90ab17a8c
Indicates the SAML token issuer for the associated SAML token is potentially compromised. The claims included in the token are unusual or match known attacker patterns