Microsoft Entra ID: Configuring the Remediation Actions Integration

Prev Next

Overview

XOps integrations let you take response actions in connected third-party applications as part of an investigation. You can revoke a user’s sessions or disable their account in your single sign-on (SSO) provider or a specific application. These actions help you contain threats by restricting access to affected accounts. To enable these actions, configure a connector for the relevant third-party application.

For more information, see Mitigating Threats in XOps Stories.

To configure the Remediation Actions integration, you need to:

  1. Configure the required settings in the SaaS application

  2. Create the API connector in the CMA

A XOps license is required for Remediation Actions integrations.

Benefits of Connecting Microsoft Entra ID

The Remediation Actions connector lets Cato take response actions on Microsoft Entra ID user accounts during an investigation. It uses a separate connector with write permissions, without affecting existing read-only Entra ID connectors.

  • Disable User: Finds the user whose user principal name or email matches the requested email and sets Account enabled to No, blocking new sign-ins

  • Revoke Sign-In Sessions: Finds the user the same way and invalidates the user's refresh tokens and browser session cookies, requiring them to sign in again. Microsoft resets the user's sessions valid from time to the current time

Each action runs on one user, identified by email, and reports Completed or Failed with a reason.

Configuring the Microsoft Entra ID Integration

To configure the integration, create a Microsoft 365 parent connector and authorize the Remediation Actions connector.

Prerequisites

  • A tenant administrator with the Global Administrator or Privileged Role Administrator role who can grant admin consent to Microsoft Graph application permissions

The connector uses Cato's pre-registered Microsoft Graph application. You do not need to create an app registration or a client secret.

Step 1: Create the MS Tenant Integration

First, configure the MS Tenant integration as the parent connector. This connector can be used for all Microsoft integrations. If you have already created the parent connector, go to step 2.

To create the MS Tenant integration:

  1. From the navigation menu, select Resources > Integrations and click the Integrated Apps tab.

  2. Click New. The New Connector panel opens.

  3. In the New Connector panel, select the MS Tenant (Configure a new MS Tenant) app.

  4. Enter the Connector Name.

  5. Click Authorize and Save.

    A new browser tab opens to the Microsoft 365 app.

  6. In the new browser tab, authenticate to the Microsoft 365 app:

    1. Select the Microsoft account for the Microsoft 365 app.

      Otherwise, there may be a Microsoft authentication error.

    2. Enter the password for the app and approve it.

    3. Accept the permissions to let Cato access the Microsoft 365 app.

    4. The screen shows that you have successfully applied the permissions for the app.

      You can close the browser tab and return to the Cato Management Application.

  7. The Microsoft 365 SaaS application is added to the Integrated Apps tab.

Step 2: Create the API Connector in the CMA

After you have set up the parent connector, add the details of the Remediation Actions integration in the CMA.

To create the API connector in the CMA:

  1. From the navigation menu, click Resources > Integrations.

  2. Click the Configured Integrations tab.

  3. Click New.

    The New Integration panel opens.

  4. Select Microsoft Entra ID as the SaaS Application you want to add.

  5. Choose Remediation Actions.

    • In Auth, choose Consent Microsoft

    • Enter a Name

  6. Select the Microsoft Primary Tenant that was created in Step 1.

  7. (Optional) Add a description.

  8. Click Save.

    The CMA connects to the vendor.

  9. Click Authorize.

    A Microsoft permissions screen will appear.

  10. Sign in as a tenant administrator. Review the requested Microsoft Graph Application permissions and click Accept:

  11. The app is visible on the Integrated Apps table with a Connected status.

    Refresh the Integrated Apps view to confirm the status.

Known Limitations

  • Disabling a user does not end active sessions. Tokens the user already holds remain valid until they expire. Run Revoke Sign-In Sessions as well to revoke those sessions, subject to Microsoft's revocation delay

  • Privileged administrators: An application cannot disable a user with a privileged admin role, such as Global Administrator, unless the application holds a higher-privileged role. For those users, the action fails with an authorization error

  • Revocation is not instant: Microsoft may take a few minutes to invalidate existing tokens

  • External (guest) users: Session revocation is not supported for guest accounts (#EXT#). The action reports Failed and makes no change