> 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/sso-password-spray.md).
# SSO Password Spray
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 1 Hour |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
AzureAD OR Azure SignIn Log OR Idira OR Duo OR Google Workspace Authentication OR Okta OR OneLogin OR PingOne
|
| Detection Modules | Identity Analytics |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Brute Force: Password Spraying (T1110.003), Brute Force: Password Guessing (T1110.001), Compromise Accounts (T1586) |
| Severity | Informational |
### Description
An abnormally high amount of SSO authentication attempts were seen within a short period of time. This may have resulted from a login password spray attack.
### Attacker's Goals
An attacker may be attempting to gain unauthorized access to user accounts.
### Investigative actions
* See whether this was a legitimate action.
* Check if the user usually logs in from this country.
* Check whether a successful login was made after unsuccessful attempts.
### Variations
SSO Password Spray Involving a Honey User
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Brute Force: Password Spraying (T1110.003), Brute Force: Password Guessing (T1110.001), Compromise Accounts (T1586) |
| Severity | Medium |
**Description**
An abnormally high amount of SSO authentication attempts were seen within a short period of time. This may have resulted from a login password spray attack.
**Attacker's Goals**
An attacker may be attempting to gain unauthorized access to user accounts.
**Investigative actions**
* See whether this was a legitimate action.
* Check if the user usually logs in from this country.
* Check whether a successful login was made after unsuccessful attempts.
SSO Password Spray Threat Detected
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Brute Force: Password Spraying (T1110.003), Brute Force: Password Guessing (T1110.001), Compromise Accounts (T1586) |
| Severity | Medium |
**Description**
An abnormally high amount of SSO authentication attempts were seen within a short period of time. This may have resulted from a login password spray attack.
**Attacker's Goals**
An attacker may be attempting to gain unauthorized access to user accounts.
**Investigative actions**
* See whether this was a legitimate action.
* Check if the user usually logs in from this country.
* Check whether a successful login was made after unsuccessful attempts.
SSO Password Spray Activity Observed
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Brute Force: Password Spraying (T1110.003), Brute Force: Password Guessing (T1110.001), Compromise Accounts (T1586) |
| Severity | Low |
**Description**
An abnormally high amount of SSO authentication attempts were seen within a short period of time. This may have resulted from a login password spray attack.
**Attacker's Goals**
An attacker may be attempting to gain unauthorized access to user accounts.
**Investigative actions**
* See whether this was a legitimate action.
* Check if the user usually logs in from this country.
* Check whether a successful login was made after unsuccessful attempts.
---
# 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/sso-password-spray.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.