- Print
- DarkLight
Microsoft Defender for Cloud Apps
Microsoft Defender for Cloud Apps is a solution that helps you secure your cloud applications across Microsoft 365 and other SaaS providers. It is a multimode cloud access security broker (CASB) that offers deep visibility, strong data controls, and enhanced threat protection for your cloud apps.
Integration Method: API
Tables: Account Change, Authentication, Detection Finding, Entity Management, File System Activity
DataBee connects to Microsoft Defender for Cloud Apps APIs to retrieve activities, alerts, and entities. This integration has been tested against Microsoft Defender for Cloud Apps API v1.
Azure Configuration
To use Microsoft Defender for Cloud Apps API, you need client credentials, tenant id, and tenant region.
Log on to Azure with a user account that has the Global Administrator role.
Navigate to Microsoft Entra ID > App registrations > New registration. The Register an application page window appears.
Enter the application's registration information:
In the Name section, enter a meaningful application name that will be displayed to users.
For Supported account types, click the Accounts in any organizational directory option.
Set the Redirect URI to http://localhost.
Click on Register to create the application.
On the app Overview page, copy the Application (client) ID and Directory (tenant) ID for later use.
Add Permissions
Once the application is created, permissions should be provided to get data. The appropriate permissions for the application are needed to configure these endpoints. The following endpoints are needed for this integration
https://<tenant_id>.<tenant_region>.portal.cloudappsecurity.com/api/v1/entities/
https://<tenant_id>.<tenant_region>.portal.cloudappsecurity.com/api/v1/activities/
https://<tenant_id>.<tenant_region>.portal.cloudappsecurity.com/api/v1/alerts/
To add permissions for the one endpoint outlined above, from the Azure Active Directory portal:
On the Application page, select API Permissions > Add permission > APIs my organization uses.
Type Defender for Cloud Apps, and then select it
Select Application permissions > Investigation.Read, and then select Add permissions.
Select Grant admin consent.
The following permissions need to be granted for the endpoints to function properly:
Endpoints | Permission |
/api/v1/entities/ | Investigation.read |
/api/v1/activities/ | Investigation.read |
/api/v1/alerts/ | Investigation.read |
Create the Client ID and Client Secret
The final step in configuring the API is creating a Client ID and Client Secret. To create these items, from the Azure Portal:
Select the application created above.
Click Certificates and Secrets, and then Client Secrets.
Click New client secret. Then Add a client secret window appears.
Enter a Description for this client secret.
Select the desired expiry period from the Expires drop-list.
Click Add.
Copy the Value field, which will be used to initialize the DataBee.
Get Tenant Region
Select Settings.
Select Cloud Apps.
Under System, select About.
The value of Data center represents tenant region.
DataBee Configuration
Login to the DataBee console and navigate to the Data > Data Sources tab
Click on Add New Source
Search for Defender for Cloud Apps and select it
Select API Ingest
Enter basic contact information in the dialog box and click Next
In the detailed configuration boxes, ensure the following fields are filled
Authorization Method: OAuth2
Client Key: Paste the client key generated in the Microsoft console
Secret Key: Paste the client secret generated in the Microsoft console
Token URL: replace the <application_id> with your Tenant Id.
API URL: Replace <tenant_id> and <tenant_region> with above generated values.
Click Submit