> 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/file-sharing_wetransfer.md). # file-sharing\_wetransfer Explanation This event is triggered when file sharing occurs using the Wetransfer application on the network. Wetransfer is a cloud-based file-sharing service that allows users to transfer large files **Explanation** This event is triggered when file sharing occurs using the Wetransfer application on the network. Wetransfer is a cloud-based file-sharing service that allows users to transfer large files between computers. **What to Look For** To examine the results of this event, look for any instances of file sharing using Wetransfer on the network. This may indicate that sensitive files are being shared without proper authorization or encryption, potentially putting the organization at risk of data breaches or regulatory non-compliance. Additionally, endpoint analysis may reveal which user or device is responsible for the file sharing activity. It is important to take immediate action to prevent further unauthorized file sharing and investigate any potential data breaches. --- # 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/file-sharing_wetransfer.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.