> 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/fin_flood.md).

# fin\_flood

Explanation Fin Flood is a type of Denial-of-Service (DoS) attack that targets an open connection by bombarding it with numerous TCP packets with the "FIN" flag set. This excessive amount of packets o

**Explanation**

Fin Flood is a type of Denial-of-Service (DoS) attack that targets an open connection by bombarding it with numerous TCP packets with the "FIN" flag set. This excessive amount of packets overwhelms the system and can cause the connection to crash or become unresponsive.

**What to Look For**

When reviewing results for fin\_flood, look for a high volume of TCP packets with the "FIN" flag set. Pay attention to the source IP addresses, destination IP addresses, and ports being targeted. Check whether this activity is occurring across multiple devices on the network or if it is isolated to a particular device. Investigate any anomalies in network traffic patterns and monitor for ongoing attacks. Implement measures to mitigate against DoS attacks, which could include filtering or limiting traffic from suspicious IPs and network segments.

**Related MITRE ATT\&CK Categories**

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

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


---

# 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/fin_flood.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.
