> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/invalid-saml-detected.md).
# Invalid SAML Detected
### Synopsis
| Field | Value |
| -------------------- | -------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Requires all of the following:
AzureAD
Okta
|
| Detection Modules | Identity Threat Module, SaaS Threat Detection |
| Detector Tags | Active Directory Federation Services Analytics |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Forge Web Credentials: SAML Tokens (T1606.002) |
| Severity | Informational |
### Description
A user attempted to sign in using an invalid SAML. This might indicate a Golden SAML attack.
### Attacker's Goals
An attacker might forge a valid SAML token to impersonate other user accounts. This is used to gain persistent, unauthorized access to cloud resources, and bypassing MFA.
### Investigative actions
* Check for recent changes to the SAML signing certificate on both the Identity Provider and the Service Provider to rule out a configuration drift or expiration issue.
* Check for other correlated alerts on on-premises systems that may be related to the Golden SAML attack.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
### Variations
Suspicious Invalid SAML Detected
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Forge Web Credentials: SAML Tokens (T1606.002) |
| Severity | Low |
**Description**
A user attempted to sign in using an invalid SAML. This might indicate a Golden SAML attack.
**Attacker's Goals**
An attacker might forge a valid SAML token to impersonate other user accounts. This is used to gain persistent, unauthorized access to cloud resources, and bypassing MFA.
**Investigative actions**
* Check for recent changes to the SAML signing certificate on both the Identity Provider and the Service Provider to rule out a configuration drift or expiration issue.
* Check for other correlated alerts on on-premises systems that may be related to the Golden SAML attack.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/invalid-saml-detected.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.