> 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/post-compromise/torrent_usage_detection.md). # torrent\_usage\_detection **Explanation** The torrent\_usage\_detection NDM was developed by the Netography Threat Research team to detect instances of torrent file sharing on a network. **What to Look For** To examine the results of the torrent\_usage\_detection NDM event, security personnel should look for evidence of torrent file sharing activity on the network, such as abnormal spikes in network traffic or large amounts of data being transferred to and from specific endpoints. They should also examine endpoint devices for the presence of torrent client software or other tools commonly used for sharing files via torrent networks. If evidence of torrent file sharing is found, appropriate remediation steps should be taken to prevent further unauthorized activity and ensure the security of the network and its data. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.fusion.vectra.ai/detection-models/library/post-compromise/torrent_usage_detection.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.