- Cloud Collectors Overview
- Administration
- Administrative Access
- Shareable Service Accounts
- Add Accounts for AWS Cloud Collectors
- Add Accounts for Cisco Duo Cloud Collector
- Add Accounts for Google Cloud Collectors
- Add Accounts for Microsoft Cloud Collectors
- Add Accounts for Okta Cloud Collectors
- Add Accounts for Salesforce Cloud Collectors
- Add Accounts for Splunk Cloud Collectors
- Add Accounts for Trend Micro Cloud Collectors
- Define a Unique Site Name
- Sign Up for the Early Access Program
- Onboard Cloud Collectors
- AWS CloudTrail Cloud Collectors
- AWS CloudWatch Cloud Collector
- AWS S3 Cloud Collector
- AWS SQS Cloud Collector
- Azure Activity Logs Cloud Collector
- Azure Log Analytics Cloud Collector
- Azure Event Hub Cloud Collector
- Azure Storage Analytics Cloud Collector
- Cisco Duo Cloud Collector
- Cisco Umbrella Cloud Collector
- Cribl Cloud Collector
- CrowdStrike Cloud Collectors
- GCP Pub/Sub Cloud Collector
- Microsoft Defender XDR (via Azure Event Hub) Cloud Collector
- Microsoft Entra ID Context Cloud Collector
- Microsoft Entra ID Logs Cloud Collector
- Microsoft 365 Exchange Admin Reports Cloud Collector
- Supported Sources from Microsoft 365 Exchange Admin Reports
- Migrate to the Microsoft 365 Exchange Admin Reports Cloud Collector
- Prerequisites to Configure the Microsoft 365 Exchange Admin Reports Cloud Collector
- Configure the Microsoft 365 Exchange Admin Reports Cloud Collector
- Troubleshooting the Microsoft 365 Exchange Admin Reports Cloud Collector
- Microsoft 365 Management Activity Cloud Collector
- Microsoft Security Alerts Cloud Collector
- Microsoft Sentinel (via Event Hub) Cloud Collector
- Netskope Alerts Cloud Collector
- Netskope Events Cloud Collector
- Okta Cloud Collector
- Okta Context Cloud Collector
- Palo Alto Networks Cortex Data Lake Cloud Collector
- Proofpoint On-Demand Cloud Collector
- Proofpoint Targeted Attack Protection Cloud Collector
- Salesforce Cloud Collector
- SentinelOne Alerts Cloud Collector
- SentinelOne Cloud Funnel Cloud Collector
- SentinelOne Threats Cloud Collector
- Splunk Cloud Collector
- Symantec Endpoint Security Cloud Collector
- Trend Vision One Cloud Collector
- Zscaler ZIA Cloud Collector
- Webhook Cloud Collectors
- Troubleshooting Cloud Collectors
Configure the Microsoft Security Alerts Cloud Collector
Set up the Microsoft Security Alerts Cloud Collector to continuously ingest security alert logs across the Microsoft platform.
Before you configure the Microsoft Security Alerts Cloud Collector, ensure that you complete the Prerequisite tasks.
Log into the Exabeam Security Operations Platform with your registered credentials as an administrator.
Find the Collectors tab and click the Cloud Collectors tile.
Click the Collectors tab.
Click the Microsoft Security Alerts tile. A configuration pane opens on the right.
Enter the following information for the cloud collector:
Collector Name – Specify a name for the Cloud Collector instance.
Account – Click New Account to add a new Microsoft service account or select an existing account. You can use the same account information across multiple Microsoft cloud collectors. For more information, see Shareable Service Accounts.
API Version – Select the API version Alerts v2 or Legacy Alerts based on the event types that you want to collect.
Alerts v2 – To filter services from which the collector must receive alerts, select Custom filter, then select one or more services from the options listed below.
Azure Active Directory Identity Protection
Microsoft 365 Defender
Microsoft App Governance
Microsoft Defender for Cloud
Microsoft Defender for Cloud Apps
Microsoft Defender for Endpoint
Microsoft Defender for Identity
Microsoft Defend for Office 365
Microsoft Purview Data Loss Prevention
Microsoft Sentinel
Others
Note
If you select Other, the alerts from service sources categorized under unknown and unknownFutureValue are collected. For more information, see serviceSource values in Microsoft documentation.
To receive alerts from all service sources, select No filter.
Legacy Alerts – To filter vendors from which the collector must receive alerts, select Custom filter, then select one or more vendors from the options listed below. For more information see List Alerts in Microsoft documentation.
Azure Security Center
Microsoft Defender for Cloud Apps
Microsoft Defender for Endpoint
Microsoft Defender for Identity
Microsoft Entra ID Protection
Microsoft Sentinel
To receive alerts from all of the vendors, select No filter.
Ingest From – Select the time and date to provide a threshold before which the collector must exclude events. If you want to select a threshold to include events to be ingested from the past, select a date previous to the present date. You can select a date which is backdated to 30 days.
(Optional) SITE – Select an existing site or to create a new site with a unique ID, click manage your sites. Adding a site name helps you to ensure efficient management of environments with overlapping IP addresses.
By entering a site name, you associate the logs with a specific independent site. A sitename metadata field is automatically added to all the events that are going to be ingested via this collector. For more information about Site Management, see Define a Unique Site Name.
(Optional) TIMEZONE – Select a time zone applicable to you for accurate detections and event monitoring.
By entering a time zone, you override the default log time zone. A timezone metadata field is automatically added to all the events that are going to be ingested via this collector.
To confirm that the Exabeam Security Operations Platform communicates with the service, click Test Connection. If the connection is successful a success message displays at the top of the screen.
Click Install. A confirmation message informs you that the new Cloud Collector is created.