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

# psh\_flood

Explanation psh\_flood is a security event in the Netography Fusion Portal that detects potential PSH floods. A Psh flood is when the TCP Push flag is set in the header of a packet, a flood of these ty

**Explanation**

psh\_flood is a security event in the Netography Fusion Portal that detects potential PSH floods. A Psh flood is when the TCP Push flag is set in the header of a packet, a flood of these types of packets may overwhelm the receiver.

**What to Look For**

When analyzing the results of the psh\_flood event, look for an unusually high number of TCP packets with the Push flag set. This type of traffic can cause performance issues on the network and may be indicative of a malicious attack. Look for any patterns or anomalies in the traffic, such as frequent bursts of Psh packets from the same IP address or network. Endpoint analysis may also reveal CPU or memory usage spikes, indicating the flood is impacting the local system. It is important to investigate and remediate any observed Psh floods promptly to prevent network downtime or data loss.

**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/psh_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.
