> 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/operational-governance/external_udp_2222.md).

# external\_udp\_2222

Explanation The external\_udp\_2222 NDM flags connections from outside the customer network to servers on the customer network listening on UDP port 2222. Rockwell Automation ICS systems use UDP port 22

**Explanation**

The external\_udp\_2222 NDM flags connections from outside the customer network to servers on the customer network listening on UDP port 2222. Rockwell Automation ICS systems use UDP port 2222. These kinds of systems should never be exposed to the open Internet.

**What to Look For**

Verify that the server (the source IP in this case) is expected to receive connections from this source (the destination IP in this case) on port 2222. While traffic to this port could be innocuous, very few networks intentionally expose this service to external hosts. This event could false positive in a situation where Netography has not been configured with the appropriate internal network IP address ranges.

**Related MITRE ATT\&CK Categories**

[Initial Access: Exploit Public-Facing Application, Technique T1190 - Enterprise](https://attack.mitre.org/techniques/T1190)


---

# 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/operational-governance/external_udp_2222.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.
