> 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/recurring-access-to-rare-ip.md).

# Recurring access to rare IP

### Synopsis

| Field                | Value                                                                                                                                |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Activation Period    | 14 Days                                                                                                                              |
| Training Period      | 30 Days                                                                                                                              |
| Test Period          | N/A (single event)                                                                                                                   |
| Deduplication Period | 21 Days                                                                                                                              |
| Required Data        | <p>Requires one of the following data sources:<br>Palo Alto Networks Firewall traffic Logs OR XDR Agent OR Third-Party Firewalls</p> |
| ATT\&CK Tactic       | Command and Control (TA0011)                                                                                                         |
| ATT\&CK Technique    | Non-Application Layer Protocol (T1095)                                                                                               |
| Severity             | Low                                                                                                                                  |

### Description

The endpoint is periodically accessing an external fixed-IP address that its peers rarely use. Access to this external IP address has occurred repeatedly over many days. This connection pattern is consistent with malware connecting to its command and control server for updates and operating instructions.

### Attacker's Goals

Communicate with malicious code running on your network enabling further access to the endpoint and network, performing software updates on the endpoint, or for taking inventory of infected machines.

### Investigative actions

* Identify if the IP address belongs to a reputable organization or an asset used in a public cloud.
* Identify if the source of the traffic is malware. If the source of the traffic is a malicious file, Cortex XDR Analytics also raises a malware alert for the file on the endpoint. Malware may contact legitimate IP addresses, therefore check for unusual apps used or unusual ports or volumes accessed.
* View all related traffic generated by the suspicious process to understand the purpose.
* Look for other endpoints on your network that are also contacting the suspicious IP address.
* Examine file-system operations performed by the process to look for potential artifacts on infected endpoints.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/recurring-access-to-rare-ip.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.