Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Legacy

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 instead.

Prerequisites

  • A paid Entra ID license. Microsoft Entra ID 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.

1

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.

2

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).

3

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.

4

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:

  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.

5

Transmit information to Stoïk

If you have direct access to your Falcon ITP platform, skip this step and proceed to the next one.

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.

6

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.

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

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.

7

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, review the requested permissions, and click Accept. You will be redirected to a blank page, which you may close.

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.

Last updated