> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/detection-models/library/reconnaissance/ping_scan_ext-int.md).

# ping\_scan\_ext-int

Explanation The ping\_scan\_ext-int event monitors for external to internal ping scans on the network. It detects when an external entity is trying to map out the internal infrastructure by pinging vari

**Explanation**

The ping\_scan\_ext-int event monitors for external to internal ping scans on the network. It detects when an external entity is trying to map out the internal infrastructure by pinging various IP addresses.

**What to Look For**

When examining the results of the ping\_scan\_ext-int event, look for any IP addresses that appear to be targets of the ping scan from the external IP. Additionally, look for any patterns or anomalies in the network traffic that could indicate an attempt to map out the network. It is important to tighten network security by restricting external access to the internal network and reviewing firewall rules to block such scans.

**Related MITRE ATT\&CK Categories**

[Reconnaissance: Active Scanning, Technique T1595 - Enterprise](https://attack.mitre.org/techniques/T1595)


---

# 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://docs.fusion.vectra.ai/detection-models/library/reconnaissance/ping_scan_ext-int.md?ask=<question>&goal=<user_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.
