1. Expel Support Center
  2. Connect your technology
  3. SaaS integrations

Microsoft Defender for Cloud Apps setup for Workbench

  • Updated

This article helps you integrate your Microsoft Defender for Cloud Apps installation with the Expel Workbench.

In this article

Step 1: Enable console access

You can create either a local account or an AD user through portal.azure.com.

Having read-only access to the interface of your technology allows Expel to dig deeper during incident investigations. Our device health team uses this access to investigate potential health issues with your tech.

Note

Expel secures all login information our SOC analysts need about your devices in a MFA password product. Access to this login information is protected using our internal MFA processes. To learn more about the IP addresses all Expel traffic comes from, go here.

  1. Go to admin.microsoft.com to create a new user.

  2. Scroll to Users and click Active Users.

  3. Select Add a user.

  4. Set Expel as first name and SOC as last name.

  5. Scroll to the bottom and grant global reader role for the user.

Step 2: Enable Defender for Cloud Apps Enterprise Application

To integrate Defender for Cloud Apps with Expel, we need to create secure credentials to the API. We provide 2 options for enabling API access:

  • Option 1: Enable the Expel Defender for Cloud Apps Integration Enterprise Application within Azure.

  • Option 2: Create a custom Azure Active Directory (AD) Application.

Usually enabling the Enterprise Application (option 1) is the recommended approach. The second option is offered for cases where the absolute minimum permissions are required. In either case, the table below shows the required items to obtain during this step:

Item we need

Description

Azure Directory (tenant) ID

A unique identifier for your Azure instance. Expel needs this information to route our API requests to the right place.

Application (client) ID (Option 2 only)

A unique identifier for the application you create that grants Expel the access it needs to your Defender for Cloud Apps instance.

Application (client) Secret (Option 2 only)

The API secret that allows Expel to authenticate as the created application to your Defender for Cloud Apps instance.

Option 1: Enable Defender for Cloud Apps integration (preferred)

  1. As an Administrator, navigate to the Expel Admin Consent Page.

  2. Review and accept requested permissions.

  3. The Expel Defender for Cloud Apps Integration app now appears under Enterprise Applications. Review properties and make sure that all permissions were properly granted. Note the Directory (Tenant) ID when viewing the Expel Defender for Cloud Apps Integration application for use in later steps.

  4. Skip to step 3.

Option 2: Create custom Azure AD application

  1. Log into your Azure Active Directory account (https://portal.azure.com) and open Azure Active Directory.

  2. Navigate to App registrations and create a new app by clicking + New registration.

  3. Fill in the application details. You can technically fill these in however you want, but we recommend the following:

    • Name: Expel Cloud Service.

    • Supported account types: accounts in this organizational directory only (first option).

  4. After you fill out the fields, click Register to create the new application.

  5. You navigate automatically to the settings page for the Expel Cloud Service app you just created. If not, navigate to Azure Active Directory > App Registrations > View all applications (if you don’t see the new app) > Expel Cloud Service.

  6. Make a note of the Application (client) ID and the Directory (tenant) ID. We need that later.

  7. Navigate to API permissions and click Add a permission.

  8. Add these permissions for the Expel App.

    • Microsoft Cloud App Security

      • discovery.read

      • investigation.read

    • Microsoft Graph

      • User.Read

  9. Select the appropriate API Category (for example, Microsoft Graph).

  10. Select Application Permissions.

  11. Select the appropriate permission(s) and click Add Permissions. (Image is a generic example.)

  12. Repeat these steps for each permission needed. Verify that:

    • All permissions are added as Application permissions and NOT Delegated permissions.

    • All Permissions are assigned.

    • Consent is granted for the permissions by the AAD admin.

  13. After permissions are assigned, click Grant admin consent, and click Yes at the prompt.

  14. Navigate to Expel Cloud Service > Certificates & secrets to begin creating an API key (aka client secret). To create a new key, click +New client secret.

  15. Add a description for the secret (like Expel API) and select Never for expiration. Click Add to create the secret.

  16. You see a new client secret (API Key) appear under Client secrets.

    Important

    Copy the value and save it for later. It disappears after you navigate away from this screen.

Step 3: Configure the technology in Workbench

Now that we have the correct access configured and noted the credentials, we can integrate your tech with Workbench.

  1. In a new browser tab, click this link to open the Add Security Device screen in Workbench.

    MDCA_AddSecDev_Step3_1.png

  2. Fill out the fields like this:

    Field Name

    What to put in it

    Name

    What you want to name the security device.

    Location

    Microsoft Cloud

    Tenant ID

    Azure Directory (tenant) ID from Option 1 or Option 2.

    Client ID (Option 2 only)

    The Azure Application (client) ID created in Option 2.

    Client Secret (Option 2 only)

    The Application (client) Secret created in Option 2.

  3. Click Save.

You can see if the device is healthy on the Security Devices page. It may take a few minutes to see the device listed as healthy.

To check if alerts are coming through, navigate to the Alerts Analysis page. Scroll to the device you want to check and click View alerts. Switch to grid view, then check the list for device alerts. It can take 36 to 72 hours for alerts to appear after setup, as we tune your device.

Tip

This article was accurate at the time of writing, but changes happen. If you find the instructions are outdated, leave a description in the comment field below and let us know!

Related terms

MDCA, MCAS, MS Cloud App Security, MS Defender, Microsoft Cloud Application Security

  • Was this article helpful?

  • 0 out of 1 found this helpful

Related articles