- Connector Migration Overview
- Cloud Collectors Overview
- Navigate the Cloud Collectors UI
- Hybrid Deployment Experience
- Supported Regions for Cloud Collectors
- Access the Cloud Collectors Service
- New Cloud Collectors
- Apache Kafka Cloud Collector
- Armis Cloud Collector
- Armis Context Collector
- AWS Eventbridge Cloud Collector
- AWS Inspector Cloud Collector
- AWS Redshift Cloud Collector
- AWS Shield Cloud Collector
- Claude Enterprise Cloud Collector
- Egnyte Cloud Collector
- Cybereason Cloud Collector
- Google Alert Center Cloud Collector
- Google Workspace Context Cloud Collector
- OneLogin Cloud Collector
- Palo Alto Networks SaaS Security Cloud Collector
- Rest API Context Cloud Collector
- Symantec CloudSOC Cloud Collector
- Symantec Cloud Secure Web Gateway Cloud Collector
- Symantec Email Security Cloud Collector
- Troubleshooting Cloud Collectors
Connector Migration Overview
Previously, cloud-based data collection required the use of Cloud Connectors, which were onboarded through the Exabeam SaaS Cloud Connectors application. Exabeam is now transitioning to the Cloud Collectors service, which is part of the New-Scale Security Operations Platform.
Exabeam Legacy SaaS Cloud Connectors are officially retiring on March 15, 2027. To keep your environments seamlessly monitored and secure, and to ensure continuous and uninterrupted collection, and data ingestion, complete your transition to the New-Scale Security Operations Platform by March 15, 2027.
If you are already using the New-Scale Cloud Collectors exclusively, no action is required—your data collection will continue seamlessly without interruption.
Milestone | Date |
|---|---|
Retirement announcement date | November 15, 2026 |
Migration completion and legacy service retirement date | March 15, 2027 |
Key Impacts and Required Migration Steps
This section explains how migration affects you and what you can do next.
Access and Licensing – You already have full access to the New-Scale Cloud Collectors at no additional licensing cost—your current agreement covers this transition completely. Your Exabeam license remains intact.
Existing Data – All previously collected data remains safely stored and accessible based on your existing retention policy. No re-ingestion is required, and your retention policies remain exactly as they are.
Collection Configuration (Action Required) – You need to manually configure and validate most of your cloud collections on the New-Scale Security Operations Platform. You must initiate migration and validate collection. Refer to the table below that displays details for the Microsoft and CrowdStrike collectors with a Migrate button, including the required version.
Prerequisites and Modernization – The new scale platform utilizes modern authentication and updated APIs, hence your security team may need to coordinate with your identity, cloud, or application administrators to complete the prerequisites and the setup.
Data Volume and Third-party Costs – The data volume remains comparable however, changes in source selection or duplicate collection during testing can affect overall volume. Additionally, while this upgrade is completely free, your standard third-party cloud hosting and storage fees will continue as usual—Standard cloud provider charges such as Azure Event Hub or cloud storage fees still apply.
Prepare and Migrate
New-Scale Cloud Collectors provide a consistent onboarding experience, automatic scaling, and collector health monitoring within the New-Scale Security Operations Platform.
Refer to the following information to get more information about how to prepare and migrate.
Inventory your legacy connectors and endpoints – List all active legacy connectors, record enabled sources, credentials, permissions, filters and any custom configurations. Refer to the following to identify the corresponding New-Scale collectors. A single legacy connector may require several new configurations.
Review the relevant user guides and align teams – Read the relevant user guides or user documentation and complete authentication and source-side prerequisites. Align your teams and your identity or cloud administrators. Contact your Account Owner if any of your active sources are listed as 'Not supported'.
Follow the migration sequence applicable for specific collectors – Follow the specific step-by-step migration procedure for each collector rather than using the stop and start method. Some collectors require stopping legacy endpoints and waiting for the tasks to finish; while others require starting the new collector before stopping legacy connector. For supported Migrate actions, verify the required Cloud Connectors version and permissions.
Validate the new configuration and flow – Confirm collector health by checking the expected sources and events, correctness of timestamps, parsing, filters, and ingestion volume. To prevent duplicate events or system overload, avoid overlapping ingestion periods and set precise ingestion start time where available.
Retire the legacy endpoints – After you verify that your new collectors are working well, safely stop and remove the old legacy endpoints as directed in the user guide. Ensure all your migrations are fully completed before March 15, 2027.
New-Scale Cloud Collector Benefits
New-Scale Cloud Collectors service provides the following benefits:
Multi-Tenant, Cloud-Native Architecture – Leverages the robust architecture of the New-Scale Security Operations Platform.
Simplified Onboarding – Provides a consistent and user-friendly onboarding experience for quick configuration and data collection.
Auto-Scaling – Automatically adjusts to varying ingest volumes without manual intervention.
No Downtime – Updates can be managed without requiring system downtime.
Service Health Monitoring – Offers a comprehensive range of health information to monitor collector activity.
Find your Collector and Start the Migration Setup
The following table lists the legacy connector catalog, including custom and webhook connectors, and Apache Kafka and Google Alerts /Google Alert Center connectors. To make your transition easy, services like AWS, Azure, and Office 365 are split into individual rows based on their specific data sources. The table lists only active legacy connectors that need to be migrated—completely new New Scale Cloud Collectors are not included.
The Setup links provide access to specific user guides with standard onboarding instructions for the replacement collector when a dedicated migration article isn't available. The setup guide does not guarantee that your old settings or endpoints will transfer over exactly the same way. Rows marked 'Not supported' identify discontinued connectors or sources.
The Key Differences column lists documented migration differences and Migrate-button availability. The symbol (—) indicates that the linked guide does not list any unique differences for your migration. However, this does not guarantee your new settings or configuration will be exactly identical to your old setup. Refer to the linked guide to complete your setup.
Vendor / Product | Data Sources | New Scale Migration or Setup Guide | Key Differences from Legacy |
|---|---|---|---|
Apache Kafka — connector | Events from Kafka topics | Kafka collector replaces Kafka collection within Custom Application. | |
Armis | Alerts, device context | Alerts and device context use separate collectors. | |
AWS —CloudTrail | CloudTrail events | Moves from the shared AWS connector to a dedicated CloudTrail collector. | |
AWS Multi-Tenant | CloudTrail events from multiple AWS accounts or trails | Moves to the CloudTrail collector for consolidated multi-account data. | |
AWS — CloudWatch Logs | CloudWatch log groups, including application and Lambda logs | Moves to a dedicated CloudWatch Logs collector. | |
AWS — CloudWatch Alarms | CloudWatch alarm data | Moves to a dedicated collector, separate from CloudWatch Logs. | |
AWS — CloudWatch Events | Events routed through EventBridge to SQS | Uses the dedicated EventBridge collector with an SQS delivery route. | |
AWS — GuardDuty | GuardDuty findings | Moves to a dedicated GuardDuty collector. | |
AWS — Inspector | Vulnerability and exposure findings | Moves to a dedicated Inspector collector. | |
AWS — Redshift | Legacy Redshift logs | Not supported | No longer supported. |
AWS — Shield | DDoS attack and event data | Moves to a dedicated Shield collector. | |
AWS — Macie | Macie logs or findings | Not supported | No longer supported. |
Azure — Activity Logs | Subscription activity logs | API collection changes to Event Hub Standard or Premium. Azure charges may apply. | |
Azure — Event Hub | Events from Azure Event Hubs | — | |
Azure — Log Analytics | Log Analytics workspace data | Moves from the shared Azure connector to a dedicated Log Analytics collector. | |
Azure — Storage Analytics | Storage account logs | Azure Storage Analytics Cloud Collector Setup (migration) | API collection changes to Event Hub Standard or Premium; Azure charges may apply. |
Azure — Network flow logs | Legacy Storage Services / NSG flow logs; VNet flow logs | Azure Virtual Network Flow Cloud Collector Setup (migration) | NSG flow logs are replaced by VNet flow logs. |
Azure — Graph Security Alerts | Security alerts from Microsoft services | Moves to the dedicated Microsoft Security Alerts collector. | |
Bitglass | Audit events | Not supported | No longer supported. |
Box | Enterprise activity and Box Shield alerts | — | |
VMware Carbon Black Cloud Endpoint Standard | Audit logs, events and alerts | Renamed Broadcom Carbon Black. | |
Centrify | Audit logs | Not supported | No longer supported. |
Cisco AMP for Endpoints | Endpoint security events | Cisco Secure Endpoint Cloud Collector (migration) | Renamed Cisco Secure Endpoint. |
Cisco Meraki | Security events | Cisco Meraki Cloud Collector (migration) | Adds Alerts and Configuration Changes. |
Cisco Umbrella | Security activity exported to S3 | — | |
Citrix ShareFile | Access changes, activity, shared sends and requests | Progress ShareFile Cloud Collector (migration) | Renamed to Progress ShareFile. |
Cloudflare | Firewall activity/events, CDN logs and audit logs | Cloudflare Cloud Collector(migration) | Adds Network Analytics, Gateway DNS, Gateway Network and Access Requests. |
Code42 Incydr | File events | Mimecast Incydr Cloud Collector (migration) | Renamed to Mimecast Incydr. |
CrowdStrike Falcon — API | Streaming API detections and audit events | CrowdStrike API Cloud Collector (migration) | Migrate button available (Cloud Connectors 2.5.483+). |
CrowdStrike Falcon — FDR | Falcon Data Replicator raw event data | CrowdStrike FDR Cloud Collector (migration) | Migrate button available (Cloud Connectors 2.5.483+). |
Cybereason | Malops / security logs | — | |
CylanceProtect | Threats and memory protection | Cylance Protect Cloud Collector (migration) | Renamed as Cylance Protect (now Arctic Wolf). |
Dropbox Business | Team events | Dropbox Cloud Collector (migration) | — |
Duo Security | Administration, authentication and telephony logs | Renamed as Cisco Duo. | |
Egnyte | Login, file, permission, user and group audit activity | — | |
Fidelis | Network activity | Not supported | No longer supported. |
GitHub | Legacy repository events; New Scale enterprise audit logs | Repository-event collection changes to enterprise audit logs; event coverage differs. | |
Google Alerts / Google Alert Center | Google Workspace Alert Center security alerts | — | |
Google Cloud Platform — Logging | Stackdriver / Cloud Logging logs | Stackdriver maps to Cloud Logging; Security Command Center uses a separate collector. | |
Google Cloud Platform — Security Center | Security Command Center findings | Moves to a dedicated Security Command Center collector. | |
Google Cloud Pub/Sub | Messages from Pub/Sub subscriptions | — | |
Google Workspace | Admin, login, Drive, Groups, rules, SAML, mobile, token and calendar activity | Adds Meet. Gmail logs move to the separate Gmail BigQuery collector. | |
Google Workspace — Gmail | Gmail logs | Gmail collection moves to the dedicated Gmail BigQuery collector. | |
LastPass Enterprise | Event reporting | — | |
Mimecast Email Security | Archive search/view, attachment protection, impersonation protection, URL and audit logs; legacy MTA/SIEM logs | Mimecast discontinued the SIEM Logs (MTA) endpoint; it cannot be migrated. | |
Netskope | Alerts and events | Alerts and Events use separate collectors. | |
Office 365 — Entra ID | Directory audit, sign-in and identity protection logs | Migrate button available (Cloud Connectors 2.5.483+). Graph sources move to Microsoft Entra ID Logs. | |
Office 365 — Management Activity | Active Directory, General, SharePoint, Exchange and DLP audit activity | Migrate button available (Cloud Connectors 2.5.483+). Moves to a dedicated Management Activity collector. | |
Office 365 — Exchange Admin Reports | MailDetailSpam, MailDetailDlpPolicy, SpoofMailReport and MailDetailATP | Migrate button available (Cloud Connectors 2.5.483+). Message Trace also requires the update below. | |
Office 365 — Exchange Message Trace | Email send/receive trace: legacy MessageTrace to MessageTraceV2 | Select MessageTraceV2: Microsoft Graph replaces the deprecated Reporting Web Service. Requires ExchangeMessageTrace.Read.All with admin consent, including after using the Migrate option. | |
Office 365 — Microsoft Cloud App Security | MCAS alert and activity endpoints | MCAS sources move to Defender XDR CloudApp events via Event Hub. | |
Okta | System logs; legacy Events endpoint | Thelegacy Events endpoint is deprecated; migrate Logs only. | |
OneLogin | Authentication, directory, application and user-management events | — | |
Palo Alto Networks SaaS Security | SaaS Security events | — | |
Ping Identity | Administrator, directory, provisioning, SSO and PingID audit activity | Replaced by PingOne Identity; adds AD Connect and PingID SDK activity. | |
Proofpoint — On-Demand | Message and Maillog | Message and Maillog move to the dedicated On-Demand collector. | |
Proofpoint — Targeted Attack Protection | Permitted/blocked clicks and delivered/blocked messages | TAP click and message events use a separate collector from On-Demand. | |
Rapid7 InsightVM | Reports | Not supported | No longer supported. |
Salesforce | Login history, setup audit, email, attachment, document and content activity; legacy custom-object create/update/delete events | Custom-object collection is no longer supported. EventLogFile uses a separate collector. | |
Salesforce — EventLogFile | Login, logout and other supported EventLogFile types | EventLogFile collection moves to the dedicated Salesforce EventLog collector. | |
SentinelOne — API | Threats and security alerts | Unified collector combines Threats and Alerts and adds Exclusions, Activities and Device Control Events. | |
SentinelOne — Deep Visibility | Deep Visibility / Cloud Funnel event data | Kafka transport changes to S3 through Cloud Funnel; parser/content updates are required. | |
ServiceNow | Transaction logs, audits (including audit-delete), users, roles, role audits, attachments, events and report views | Adds task, change, incident, interaction, problem and request sources. No legacy sources removed. | |
Slack App | Enterprise Grid audit logs | — | |
Slack Classic App / Enterprise Grid | Enterprise Grid audit logs | Classic App collection moves to the Slack collector. | |
Snowflake | Login History, Query History and Custom Table data | Legacy Events maps to Login History, Query History and Custom Table sources. | |
Sophos Central | Alerts and events | — | |
Symantec CloudSOC | Detect App incidents, Investigate App and Investigate Service App logs | — | |
Symantec Email Security.cloud | Email security / advanced threat protection logs | Symantec Email Security setup | — |
Symantec Endpoint Protection (SEP) Mobile | Mobile security events | Not supported | No longer supported. |
Symantec WSS | Secure web gateway access logs via SyncAPI | Renamed Symantec Cloud Secure Web Gateway. | |
Tenable.io | Vulnerability data | Scan exports change to vulnerability exports across scan types; coverage and volume may increase. | |
Workday | Workday web-services events | — | |
Zoom | Operation logs and sign-in/sign-out activity | Legacy reports map to Operation Logs and Sign In – Sign Out. | |
Custom Cloud Connector — AWS S3 | Events stored in S3, notified through SQS | Moves to AWS S3. Authentication s3-sqs-authn maps to Basic; STSAssumeRole is retained. | |
Custom Cloud Connector — AWS SQS | Events delivered directly to SQS | Moves to AWS SQS. Authentication s3-sqs-authn maps to Basic; STSAssumeRole is retained. | |
Custom Cloud Connector — Azure Storage | Blob Sync and Blob Explorer data | Moves to the dedicated Azure Blob Storage collector. | |
Webhook Cloud Connector | JSON and newline-delimited raw events | Basic authentication changes to token authentication. HEC is unsupported; contact your Account Owner. | |
Zscaler ZIA — legacy webhook | Web and firewall logs | Legacy webhook collection moves to the dedicated Zscaler ZIA collector. |
Frequently Asked Questions
Does this migration change my Exabeam license?
Answer – No, your Exabeam license remains unchanged. Review source-side service prerequisites and any third-party costs when new configuration changes how data is exported or transported.
What happens to the historical data?
Answer – Your existing ingested data is retained under your current retention policy. Use the new collector for ongoing collection. To avoid duplicate records, do not import or reload historical data unless your migration plan explicitly mentions it as a required planned step.
Will migration happen automatically?
Answer – No. You must initiate migration and validate collection. Most legacy connector migrations require manual configuration. Refer to the table that provides details about Microsoft and CrowdStrike collectors that have a Migrate button and the required version. For Exchange Message Trace, configure MessageTraceV2 and the required permissions.
Refer to the related documentation:
Can I run the Legacy connector and the New Scale collector at the same time?
Answer – While you can temporarily run both Legcay and New-Scale collectors at the same time during your transition, collecting data from the same source twice will create duplicate records. To avoid data duplication and ensure accuracy, refer to the linked user guide for each connector’s exact switchover steps. Then, stop the legacy endpoint after successful migration. The Legacy service retires on March 15, 2027.
Are all legacy configurations supported?
Answer – No. Bitglass, Rapid7 InsightVM, Centrify, Fidelis, Symantec SEP Mobile, AWS Macie, and AWS Redshift are no longer supported. Salesforce custom-object collection is also no longer supported. Mimecast has discontinued its SIEM Logs (MTA) endpoint. Refer to the table that identifies changes in authentication, APIs and transport. Review every source you use and contact your Account Owner about unsupported collection requirements.?