> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/mdr/deploy/crowdstrike/add-on/itp-legacy.md).

# ITP with Entra ID (legacy)

Set up the legacy Entra ID connector for CrowdStrike ITP by creating an application in Entra ID. This connector is **deprecated** and only available in specific cases, on request to Stoïk: use the [current setup](https://docs.stoik.io/mdr/deploy/crowdstrike/add-on/itp.md) instead.

## Prerequisites

* A paid Entra ID license. [Microsoft Entra ID](https://entra.microsoft.com) Free is not supported.
* An account with global administrator rights to your Entra ID account.

## Purpose of ITP

The ITP (Identity Threat Protection) option continuously monitors account-related activities and Active Directory to detect abnormal behavior.

### Identity-centered behavioral analysis

* Suspicious authentications
* Unusual access patterns
* Unauthorized login attempts
* User account anomalies

Examples of detected events: suspicious workstation-to-server connections, network scans, brute-force attempts, or credential extraction. When a critical event is identified, the module can **automatically block it**.

### Assessment of your Active Directory security posture

The module provides a real-time overview of your Active Directory security, similar to the Stoïk Protect AD scan but with more advanced options:

* Identification of configuration issues
* Detection of accounts with compromised passwords
* Management and control of user privileges

### Cloud threat monitoring (optional)

When configured with your identity service (e.g. Entra ID), ITP can detect threats in your cloud environments:

* Logins from suspicious IP addresses
* Abnormal access attempts to user accounts

## Integration

The integration requires the following steps for **each Azure tenant**.

{% stepper %}
{% step %}

### Create and configure an application in Entra ID

1. In the Azure portal, open the left-hand menu and click `Microsoft Entra ID`.
2. From the `Add` menu, select `App registrations`.
3. On the `Register an application` page:
   * Under `Name`, enter a name matching your internal conventions, or use `stoik-connector-itp`.
   * Under `Supported account types`, select `Accounts in this organizational directory only`.
   * Under `Redirect URI`, select `Web` and enter `https://localhost`.
   * Click `Register`.
4. In the application's left-hand menu, click `API permissions`.
5. Click `Add a permission`.
6. In the `Request API permissions` panel, click `Microsoft Graph`, then select `Application permissions`.
7. In `Select permissions`:
   * Type `directory`, expand `Directory`, and select `Directory.Read.All`.
   * Type `audit`, expand `AuditLog`, and select `AuditLog.Read.All`.
8. Click `Add permissions`, then click `Grant admin consent` and confirm.
   {% endstep %}

{% step %}

### Retrieve the tenant domain

1. In the Azure portal, go to `Microsoft Entra ID`.
2. In the left-hand menu, click `Overview`.
3. Note the value of the `Primary domain` (e.g. `example.onmicrosoft.com`).
   {% endstep %}

{% step %}

### Retrieve the application ID and secret

1. In Microsoft Entra ID, go to `App registrations` and select your application.
2. In `Overview`, note the `Application (client) ID`.
3. In `Certificates & secrets`, create a new client secret: provide a description and an expiration duration.
4. Save the generated value immediately. It will not be visible again.

<figure><img src="https://25674881.fs1.hubspotusercontent-eu1.net/hubfs/25674881/Entra_value-71a566ca11435df656075b4c186be741-png-1.png" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Create a custom role for RBAC access

To display Azure RBAC role assignment information in Identity Protection, the application must be granted permission to read RBAC definitions and assignments.

#### Create the custom role

1. In the Azure portal, go to `Management Groups`.
2. Click `Tenant Root Group`.
3. Select `Access control (IAM)`, then click `Roles`.
4. Click `Add`, then select `Add custom role`.
5. In the `Basics` tab, enter a clear name (e.g. `Identity Protection RBAC Reader`).
6. In the `Permissions` tab, add the following permissions:

   ```
   Microsoft.Authorization/roleDefinitions/read
   ```

   ```
   Microsoft.Authorization/roleAssignments/read
   ```
7. Click `Review + create`, then `Create`.

#### Assign the custom role

1. In the Azure portal, go to `Management Groups`.
2. Click `Tenant Root Group`.
3. Select `Access control (IAM)`, then click `Role assignments`.
4. Click `Add`, then select `Add role assignment`.
5. In the `Role` tab, select the custom role you just created.
6. In the `Members` tab, click `Select members`, search for the previously created application (e.g. `stoik-connector-itp`), select it, and click `Select`.
7. Click `Review + assign`, then `Review + assign` again to confirm.
   {% endstep %}

{% step %}

### Transmit information to Stoïk

{% hint style="info" %}
If you have direct access to your Falcon ITP platform, skip this step and proceed to the next one.
{% endhint %}

Send the following information to <protect@stoik.io>:

* Tenant primary domain name (ends with `onmicrosoft.com`)
* Application ID
* Application secret

Without this information, the connector cannot be activated on our side.
{% endstep %}

{% step %}

### Configure the connector in Identity Protection

1. In the Falcon console, go to `Identity Protection` > `Configure` > `Connectors`.
2. Select `Entra` under the `IDAAS` category.
3. Configure the connector with the tenant primary domain name, the application ID, and the application secret.
4. Enable the login data collection option.
5. Save the configuration.

<figure><img src="https://25674881.fs1.hubspotusercontent-eu1.net/hubfs/25674881/image-png-Jan-28-2025-10-22-05-6569-AM.png" alt=""><figcaption></figcaption></figure>

The status indicator turns green within a minute, confirming the connection has been successfully established.

{% hint style="info" %}
The tenant primary domain name to use is the one generated by Microsoft during the creation of your Azure tenant. It always ends with `onmicrosoft.com`.
{% endhint %}
{% endstep %}

{% step %}

### Grant remediation access to Stoïk

If an account is compromised during nights or weekends, your teams may not be available to perform remediation. We recommend granting access so impacted accounts can be disabled once a compromise is confirmed.

Click the [provided link](https://login.microsoftonline.com/organizations/adminconsent?client_id=72f25200-dfe6-4c66-959d-103731ae6215\&redirect_uri=https://login.microsoftonline.com/common/oauth2/nativeclient), review the requested permissions, and click `Accept`. You will be redirected to a blank page, which you may close.

<figure><img src="https://25674881.fs1.hubspotusercontent-eu1.net/hubfs/25674881/image-png-Feb-20-2025-09-10-33-4687-PM.png" alt=""><figcaption></figcaption></figure>

The application only has the permissions required to enable or disable existing accounts, with no ability to create accounts or modify other attributes. Each action is authenticated via MFA, logged, and timestamped. A complete audit log can be provided upon request.
{% endstep %}
{% endstepper %}


---

# 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.stoik.io/mdr/deploy/crowdstrike/add-on/itp-legacy.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.
