Onboard the Microsoft O365 data connector.
Overview
Radiant Security needs to establish a trusted relationship with your Microsoft account in order to retrieve user and group data related to your organization, including authentication activity and audit activity events.
To do this, you’ll need to onboard O365 by completing the following steps:
- Register the application with Microsoft Entra ID
- Grant the newly registered application the appropriate permissions
- Add permissions in Azure
- Add assigned role
- Add Microsoft Defender Permissions
- Onboard Hosts to Defender
- Set Up Microsoft Safe Links
- Add the connector in Radiant Security
At the end of this configuration, you will provide Radiant Security with these values:
- Application (client) ID
- Directory (tenant) ID
- Client Secret Value
Prerequisites
This configuration requires that you are an administrator of the O365 account.
Register the application with Microsoft Entra ID
In this step, you'll register a new application with Microsoft Entra ID. The application will pull user and group data on a semi-regular basis.
Note: Make sure to save the Application (client) ID and Directory (tenant) ID values. You will need to provide them to Radiant Security at the end of the configuration.
Important note: Ensure you copy the Client secret value now as you won't be able to look it up again later. You will need to provide it to Radiant Security at the end of the configuration.
Grant the newly registered application the appropriate permissions
- On the left sidebar menu, click API Permissions.
- Click + Add a permission.
- From the pop-out menu, select Microsoft Graph APIs.
- Then click Application permissions to open the permission list.
- Select the following permissions:
API/Service Permission name Required for Data Ingestion? Details Microsoft Graph Application.Read.All Yes Task: Block IP Address Microsoft Graph AuditLog.Read.All Yes Collect user authentication events for investigating abnormal authentication to applications Microsoft Graph Directory.Read.All Yes Permission to read users’ profiles Microsoft Graph IdentityRiskEvent.Read.All Yes Collect identity-based risks/alerts Entra AD Identity Protection Microsoft Graph IdentityRiskyUser.Read.All Yes Collect identity-based risks/alerts Entra AD Identity Protection Microsoft Graph Mail.ReadWrite No Task: Find & Delete Emails Microsoft Graph MailboxSettings.Read No Collect the out-of-office status of the user from Microsoft to help influence identity alert triage outcomes Microsoft Graph MailboxSettings.ReadWrite No Task: Disable all email forward rules, Delete external email forward rules Microsoft Graph Policy.Read.All No Task: Block IP Address Microsoft Graph Policy.ReadWrite.ConditionalAccess No Task: Block IP Address Microsoft Graph User.Read.All Yes Permissions to read users’ profiles Microsoft Graph SecurityAlert.Read.All Yes Permissions to read security alerts Microsoft Graph User.ManageIdentities.All No Tasks: Reset User Password, Disable User Microsoft Graph User.EnableDisableAccount.All No Tasks: Reset User Password, Disable User, Enable User Microsoft Graph Directory.AccessAsUser.All (delegated permission) No Tasks: Reset User Password, Disable User Microsoft Cloud App Security Investigation.Read Yes Permissions to read the Cloud Apps alerts and the related events - Click Add permissions to save the changes.
- Click + Add a permission and select the tab APIs my organization uses, then select the Office 365 Exchange Online option.
- Select Application permissions and add the permissions outlined in the table below:
API/Service Permission name Required for Data Ingestion? Details Office 365 Exchange Online
(APIs my organization uses)Exchange.ManageAsApp No Tasks: Block Sender, Block URL - required for actions that can only be done over PowerShell Office 365 Exchange Online
(APIs my organization uses)ReportingWebService.Read.All Yes Permission to enrich message trace events - Click Add permissions to save the changes.
- Click on + Add a permission again, on the Microsoft APIs tab, select Office 365 Microsoft Management API.
- Select Application permissions and add the permissions outlined in the table below:
API/Service Permission name Required for Data Ingestion? Details Office 365 Management APIs ActivityFeed.Read Yes Collect user authentication events for investigating abnormal authentication to applications Office 365 Management APIs ActivityFeed.ReadDlp Yes Permission to identify impacted users with inbox rules that were newly created or modified to exfiltrate emails - Click Add permissions to save the changes.
Add permissions in Azure
Follow these instructions only if you have Azure enabled in your environment.- Click + Add a permission.
- From the pop-out menu, select Azure Service Management.
- Select the permission user_impersonation.
- Click the Add Permission button.
- You will see the new permissions have been added. However, there is a warning message that admin consent is missing.
- To resolve this, click Grant admin consent for the API permissions.
- Click Yes in the confirmation pop-up window. Now, the warnings have been resolved.
Add assigned role
In this step, you will assign the newly registered application with the necessary roles.
- On the left sidebar menu, click Roles and Administrators.
- On the roles and Administrators page, click here.
- From the search bar, search for
global reader
and select the row (do not select the checkbox). - On the active assignments page, click + Add assignment.
- On the Add assignments page, under Select member(s), click on No member selected and add
radiantsecurity-connector
on the side panel. - Click Next and under Enter justification type the justification in the text box:
Grant Radiant Security access to message trace events
- Click Assign to save the changes.
- Repeat steps 1-7 for the Exchange Administrator role and for the Privileged Authentication Administrator role or Authentication Administrator role.
- The Privileged Authentication Administrator role allows the application to run actions such as reset user password on all user accounts in the environment, no matter their groups or roles.
- The Authentication Administrator role allows the application to run the same actions as the Privileged version, but it limits the scope of access so that the application can't run actions against user accounts with high privilege levels such as Global Admins, Group Admins or even users who own or are members of role-assignable group.
For more information about the two roles, refer to Microsoft's documentation.
Specific configurations
Some data feeds require additional configuration before adding the connector to Radiant Security. Please refer to the following articles if applicable:
Add the connector in Radiant Security
- Log in to Radiant Security.
- From the navigation menu, click Settings > Data Connectors.
- Click + Add Connector.
- From the list of connectors, select Microsoft O365.
- Add the following values you saved from the previous steps:
- Application (client) ID
- Directory (tenant) ID
- Client Secret Value
- Click Add Connector to save the connector configuration.
We value your opinion. Did you find this article helpful? Share your thoughts by clicking here or reach to our Product and Customer Success teams at support@radiantsecurity.ai
Last updated: 2024-09-24