Threaticon
Toggle sidebar

You're viewing a limited, public preview. Log in for full access.

Log in User Guide
Log in Get started
Detection Strategies DET0148 — Detection Strategy for Forged SAML Tokens
DET0148

Detection Strategy for Forged SAML Tokens

5 analytic(s) · 1 technique(s) detected

Analytics

5
AN0418 Analytic 0418
Identity Provider

Forged 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 WinEventLog:Security EventCode=4769, 1200, 1202
[TokenLifetimeThreshold] Defines the maximum expected lifetime of a SAML token (e.g., >1 hour considered anomalous).
[TrustedIssuerList] List of approved SAML issuers and certificate thumbprints.
AN0419 Analytic 0419
IaaS

Forged 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.

AWS:CloudTrail AssumeRoleWithSAML CloudTrail:Signin SAML login without corresponding IdP authentication log
[CrossAccountUsage] Flag SAML tokens used across unexpected accounts or cloud tenants.
AN0420 Analytic 0420
Windows

Forged 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:Security EventCode=4624, 4648 WinEventLog:ADFS Token issuance events showing anomalous claims or issuers
[ClaimAnomalyThreshold] Number of unusual claims in a SAML token (e.g., excessive privileges).
AN0421 Analytic 0421
SaaS

Forged 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.

saas:access SAML token accepted without preceding login challenge m365:unified Abnormal user claims or unexpected elevated role assignment in SAML assertion
[GeoVelocityThreshold] Triggers when same SAML token used in different geographies within short timeframe.
AN0422 Analytic 0422
Office Suite

Forged 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:exchange Mailbox access using SAML token without corresponding MFA event m365:sharepoint File access with forged or anomalous SAML claims
[ReplayDetectionThreshold] Number of times a token is reused within short timeframe.

Detected Techniques

1

Credential Access (1)

Details

MITRE ID
DET0148
STIX ID
x-mitre-detection-strategy--b6d7d7cb-b56f-4095-b3ac-21147b0123e5
Analytics
5
Techniques Detected
1
By Tactic
Credential Access
1
Leaving Threaticon

This link opens an external site that isn't part of the platform.