- 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
- Abnormal Security Cloud Collector
- 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
- Cato Networks 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
Prerequisites to Configure the Abnormal Security Cloud Collector
Before you configure the Abnormal Security Cloud Collector you must complete the following prerequisites:
Obtain the API Authentication Token and Complete IP Allowlisting
The API helps to manage threats to an organization identified by Abnormal Security. Integrate your REST API with Abnormal Security to enable real-time detection of malicious emails.
Use the following steps to obtain the API Authentication Token for REST API integration.
Access the Abnormal Security portal.
Navigate to Settings > Integrations > Additional Integrations > Abnormal REST API > Connect.
The Integration page displays a unique API access token required for your API calls. Record the access token to use it while configuring the cloud collector.
For more information about each Abnormal REST API endpoint, refer to the Abnormal API documentation in SwaggerHub. For assistance, you can contact Abnormal Security Support at [email protected].
On the Integration page, after recording the access token, in the IP Safelist field, enter a specific IPv4 / IPv6 address or enter a range of addresses. See Complete the IP Allowlisting.
Complete the IP Allowlisting
IP allowlisting enables API access for only the IP addresses that belong to your organization and prevents access for users from unauthorized networks. Additionally IP allowlisting helps to keep your data and API token safe from unauthorized users. Hence you must add organization’s IPs to the IP allowlist on the Integration page.