> 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/operational-governance/ipfs_usage.md).

# ipfs\_usage

Explanation The ipfs\_usage NDM is designed to detect any IPFS related traffic on your network. IPFS (InterPlanetary File System) is a distributed protocol for sharing and storing files in a peer-to-pe

**Explanation**

The ipfs\_usage NDM is designed to detect any IPFS related traffic on your network. IPFS (InterPlanetary File System) is a distributed protocol for sharing and storing files in a peer-to-peer network. The event triggers whenever IPFS traffic is detected on the network.

**What to Look For**

To examine the results of the ipfs\_usage event, you should look for any IPFS traffic on your network. This could be observed in network traffic logs and packet captures. It is important to examine any IPFS traffic to ensure that it is legitimate and authorized. Unauthorized use of IPFS could pose a security risk to your organization. Additionally, endpoint analysis should be conducted to determine which users or devices may be initiating IPFS traffic. Ensure that any IPFS activity is in compliance with your organization's security policies and guidelines.


---

# 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/operational-governance/ipfs_usage.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.
