> 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/dns_amplification_participation.md). # dns\_amplification\_participation Explanation The dns\_amplification\_participation event in the Netography Fusion Portal helps to find potential participants in DNS amplification attacks. DNS amplification attacks exploit the vulnerabi **Explanation** The dns\_amplification\_participation event in the Netography Fusion Portal helps to find potential participants in DNS amplification attacks. DNS amplification attacks exploit the vulnerability of using DNS servers to flood targeted servers with traffic by amplifying a small amount of traffic into a much larger volume. This event helps to identify potentially compromised systems that are unwittingly participating in such attacks. **What to Look For** To analyze the dns\_amplification\_participation event, network administrators should look for outgoing DNS traffic from their networks that exceeds the expected volume. They should also check for any systems or applications that are known to be vulnerable to DNS amplification attacks. Additionally, endpoint devices should be inspected to ensure that they are not infected with malware that could be used in such attacks. By examining the results of this event, customers can identify and remediate potential security risks in their networks. --- # 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/dns_amplification_participation.md?ask=&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.