> 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/brute-force/pop3_brute_external_internal.md).

# pop3\_brute\_external\_internal

Explanation This event is triggered by Netography's Fusion Portal when it detects a brute force password guessing attack against a Post Office Protocol version 3 (POP3) mail client access server. This

**Explanation**

This event is triggered by Netography's Fusion Portal when it detects a brute force password guessing attack against a Post Office Protocol version 3 (POP3) mail client access server. This event specifically looks for activity from the Internet toward Internet facing POP3 servers on your network.

**What to Look For**

If internal POP3 servers are exposed to the Internet, it is very important to implement a strong password policy as two-factor authentication is not natively supported by the protocol. You should also consider enabling available server controls such as: app-specific passwords, auth-failure delays, temporary account locks, or Fail2ban. Check network logs for additional information and review endpoint security to ensure that sensitive information is secure.

If your organization does not need to use POP3, and your mail server supports a more secure protocol, consider disabling the POP3 protocol or blocking external access of POP3(s) ports (TCP/110 & TCP/995).

**Related MITRE ATT\&CK Categories**

[Credential Access: Brute Force, Technique T1110 - Enterprise](https://attack.mitre.org/techniques/T1110)

[Initial Access, Persistence: External Remote Services, Technique T1133 - Enterprise](https://attack.mitre.org/techniques/T1133)


---

# 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/brute-force/pop3_brute_external_internal.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.
