> 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/failed-connections.md).
# Failed Connections
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 1 Day |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
Palo Alto Networks Firewall traffic Logs OR XDR Agent OR Third-Party Firewalls
|
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Remote System Discovery (T1018) |
| Severity | Low |
### Description
The endpoint has failed connections to other endpoints that have been inactive for more than 24 hours, or that Cortex XDR Analytics has never seen on the network. The endpoint has made an abnormally large number of these failed connections and/or is attempting to connect to an abnormal mixture of missing or inactive endpoints.
Your network might contain legitimate scanners that could cause a false positive for this alert. Cortex XDR Analytics attempts to filter these out by checking if a scanner has been active for a long consecutive period of time. Consequently, if this alert is seen, it represents new activity on your network.
An attacker may be trying to move laterally, or to scan different parts of the network to look for other endpoints that expose a specific service. Worms also perform a similar activity to automatically infect additional hosts in the network.
### Attacker's Goals
An attacker does not know your network and is exploring it for new or unknown subnets.
### Investigative actions
* Validate that the source is not a sanctioned port scanner.
* Check for suspicious artifacts in the endpoint profile.
### Variations
Failed Connections
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------- |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Remote System Discovery (T1018) |
| Severity | Informational |
**Description**
The endpoint has failed connections to other endpoints that have been inactive for more than 24 hours, or that Cortex XDR Analytics has never seen on the network. The endpoint has made an abnormally large number of these failed connections and/or is attempting to connect to an abnormal mixture of missing or inactive endpoints.
Your network might contain legitimate scanners that could cause a false positive for this alert. Cortex XDR Analytics attempts to filter these out by checking if a scanner has been active for a long consecutive period of time. Consequently, if this alert is seen, it represents new activity on your network.
An attacker may be trying to move laterally, or to scan different parts of the network to look for other endpoints that expose a specific service. Worms also perform a similar activity to automatically infect additional hosts in the network.
**Attacker's Goals**
An attacker does not know your network and is exploring it for new or unknown subnets.
**Investigative actions**
* Validate that the source is not a sanctioned port scanner.
* Check for suspicious artifacts in the endpoint profile.
Failed Connections with a rare causality and actor processes relations
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------- |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Remote System Discovery (T1018) |
| Severity | Informational |
**Description**
The endpoint has failed connections to other endpoints that have been inactive for more than 24 hours, or that Cortex XDR Analytics has never seen on the network. The endpoint has made an abnormally large number of these failed connections and/or is attempting to connect to an abnormal mixture of missing or inactive endpoints.
Your network might contain legitimate scanners that could cause a false positive for this alert. Cortex XDR Analytics attempts to filter these out by checking if a scanner has been active for a long consecutive period of time. Consequently, if this alert is seen, it represents new activity on your network.
An attacker may be trying to move laterally, or to scan different parts of the network to look for other endpoints that expose a specific service. Worms also perform a similar activity to automatically infect additional hosts in the network. These failed connections originated from a rare relation between an actor process and its causality.
**Attacker's Goals**
An attacker does not know your network and is exploring it for new or unknown subnets.
**Investigative actions**
* Validate that the source is not a sanctioned port scanner.
* Check for suspicious artifacts in the endpoint profile.
---
# 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/failed-connections.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.