> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/getting-started/onboarding/connectors.md).

# Connectors

*<mark style="color:$info;">Bring the tools you already use into one place</mark>*

Connectors link CybaOps to the security and IT tools you already have, so their data flows into the right modules without anyone copying it across. That gives you a single source of truth: devices and users appear in Asset Manager, and alerts and events reach Investigate and CybaVerse Managed Detection and Response (MDR). Most connectors are one-way. They read from your tool and never change anything in it.

***

## <mark style="color:$primary;">Where to Find Connectors</mark>

You'll see the connectors included in your licence on the Connectors screen. To open it, select your username in the bottom left to open **Settings**, then select **Connectors** in the top right. If the button is greyed out, ask your tenant admin. Choose a connector, select **Connect** and enter the details from your tool. Once a connector is connected, a regular sync schedule is created for it.

{% hint style="info" %}
You can check the health of every connector, and bump a sync, on the [Connector and Schedule Screen](/settings/connector-and-schedule-screen.md).
{% endhint %}

Some data sources, such as Flare and LimaCharlie, are part of the service and managed for you, so they don't appear as connectors you add yourself. See [Connector and Schedule Screen](/settings/connector-and-schedule-screen.md#connectors-by-licence) for what each licence includes.

***

## <mark style="color:$primary;">Choose a Connector</mark>

**Devices and users.** [Microsoft Entra ID](/getting-started/onboarding/connectors/microsoft-entra-id.md) brings your users and devices into Asset Manager, so your inventory includes everything in your directory.

**Endpoint and security alerts.** Connect your existing endpoint or security platform so CybaVerse MDR can see its alerts and incidents: [BitDefender](/getting-started/onboarding/connectors/bitdefender.md), [CrowdStrike](/getting-started/onboarding/connectors/crowdstrike.md), [Microsoft Defender](/getting-started/onboarding/connectors/microsoft-defender.md), [Microsoft Sentinel](/getting-started/onboarding/connectors/microsoft-sentinel.md), [SentinelOne](/getting-started/onboarding/connectors/sentinelone.md), [Sophos](/getting-started/onboarding/connectors/sophos.md) and [Cortex](/getting-started/onboarding/connectors/cortex.md).

**Microsoft 365.** [Microsoft 365 (ITDR)](/getting-started/onboarding/connectors/microsoft-365-itdr.md) brings in Microsoft 365 activity for identity threat detection and response. [Advanced Threat Hunting](/getting-started/onboarding/connectors/advanced-threat-hunting.md) brings Microsoft threat hunting events into Investigate. [Microsoft 365 Vulnerability Assessment](/getting-started/onboarding/connectors/microsoft-365-vulnerability-assessment.md) reviews key security settings across your Microsoft 365 environment.

***

## <mark style="color:$primary;">Next steps</mark>

* [Microsoft Entra ID](/getting-started/onboarding/connectors/microsoft-entra-id.md): Fill Asset Manager with your users and devices.
* [Microsoft Defender](/getting-started/onboarding/connectors/microsoft-defender.md): Send your Defender incidents to CybaVerse MDR.
* [Connector and Schedule Screen](/settings/connector-and-schedule-screen.md): Check each connector is healthy after you set it up.


---

# 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.cybaops.com/getting-started/onboarding/connectors.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.