> 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/denial-of-service/ackflood.md).

# ackflood

Explanation The ackflood event is a detection for ACK Flood, a type of DDoS attack where the attacker floods the target with a high volume of ACK packets. This event is triggered when there is a signi

**Explanation**

The ackflood event is a detection for ACK Flood, a type of DDoS attack where the attacker floods the target with a high volume of ACK packets. This event is triggered when there is a significant increase in the number of ACK packets in a short period of time.

**What to Look For**

When analyzing the results of the ackflood event, look for a sudden spike in the number of ACK packets on the network traffic. This can result in network congestion and slow down the network. Additionally, examine the endpoints for any evidence of the attack, such as high CPU or memory usage. To remediate the problem, block any traffic originating from the attacker's IP address and implement mitigation techniques such as rate limiting or ACLs.

**Related MITRE ATT\&CK Categories**

[Impact: Network Denial of Service, Technique T1498 - Enterprise](https://attack.mitre.org/techniques/T1498)


---

# 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/denial-of-service/ackflood.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.
