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

# connectwise\_usage

Explanation The connectwise\_usage NDM is designed to detect any usage of the ConnectWise software, a popular remote management and monitoring tool used by IT service providers. This event is triggered

**Explanation**

The connectwise\_usage NDM is designed to detect any usage of the ConnectWise software, a popular remote management and monitoring tool used by IT service providers. This event is triggered when any activity is detected related to ConnectWise on the network or endpoints being monitored.

**What to Look For**

When examining the results of the connectwise\_usage event, customers should search for any unauthorized usage of the ConnectWise software. This could include unapproved installations, unauthorized user access, or abnormal activity related to the application. Administrators should review logs to determine the scope of the event and take appropriate action to remediate any potential security risks.

**Related MITRE ATT\&CK Categories**

[Exfiltration: Exfiltration Over Alternative Protocol, Technique T1048 - Enterprise](https://attack.mitre.org/techniques/T1048)

[Initial Access, Persistence: External Remote Services, Technique T1133 - Enterprise](https://attack.mitre.org/techniques/T1133)


---

# 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/connectwise_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.
