- Connector Migration Overview
- Cloud Collectors Overview
- Navigate the Cloud Collectors UI
- Which Collector to Use?
- Hybrid Deployment Experience
- Supported Regions for Cloud Collectors
- Access the Cloud Collectors Service
- Set up a New Cloud Connectors Instance
- 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
Configure the Claude Enterprise Cloud Collector
Set up the Claude Enterprise Cloud Collector to continuously ingest logs from Claude Compliance API. The logs include user activity data containing user role changes, workspace creations, and administrative updates, and chats containing user prompts.
Use the following steps to set up the Claude Enterprise Cloud Cloud Collector.
Before you configure the Claude Enterprise Cloud Collector, ensure that you complete the prerequisites.
Log in to the New-Scale Security Operations Platform with your registered credentials as an administrator.
Navigate to Collectors > Cloud Collectors.
Click New Collector.
Click Claude Enterprise.
Enter the following information for the cloud collector.
NAME – Specify a name for the Cloud Collector instance.
API KEY – Enter the Compliance Access key or the Admin key that you obtained while completing the prerequisites.
DATA SOURCES – Select one or more data sources from which you want the collector to collect logs; from the list.
Activity Logs – Includes user activity data containing user role changes, workspace creations, and administrative updates.
Chats – Includes chats data containing user prompts.
Claude Code Sessions – Includes local session API data containing specific files, text, and computer commands pertaining to local devices.
CoWork Remote Sessions – Includes cloud session API data containing specific files, text, and computer commands on cloud hosted applications.
CoWork Sessions – Includes local session API data containing specific files, text, and computer commands pertaining to local devices.
(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 events ingested through this collector.
A cloud collector determines whether Daylight Saving Time (DST) is active based on the current date and automatically adjusts the time by adding or subtracting one hour, ensuring more accurate time reporting.
To confirm that the New-Scale Security Operations Platform communicates with the service, click Test Connection.
Click Install.
A confirmation message informs you that the new Cloud Collector is created.