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

# tcpfrag

Explanation This event is designed to detect a TCP fragmentation flood on the network. TCP fragmentation occurs when a large data packet is divided into smaller packets for transmission across the net

**Explanation**

This event is designed to detect a TCP fragmentation flood on the network. TCP fragmentation occurs when a large data packet is divided into smaller packets for transmission across the network. This can be used as a method of attack to flood a network with large volumes of fragmented packets, causing network congestion and denial of service.

**What to Look For**

If this event is triggered, it is important to examine the network traffic for signs of a TCP fragmentation flood. This can be identified by analyzing the TCP packets for fragmentation flags and identifying packets with the same identification number. It is also important to examine the endpoint behavior to determine if any systems are experiencing high CPU or memory usage, which can be a sign of network congestion. Remediation efforts will involve identifying the source of the flood and blocking the attack at the network level.

**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/informational/tcpfrag.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.
