- 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
- Early Access Cloud Collectors
- Armis Cloud Collector
- Armis Context Collector
- AWS Inspector Cloud Collector
- AWS Redshift Cloud Collector
- Cybereason Cloud Collector
- Google Security Operations Cloud Collector
- Google Workspace Context Cloud Collector
- OneLogin Cloud Collector
- OpenAI Cloud Collector
- Palo Alto Networks SaaS Security Cloud Collector
- Rest API Context Cloud Collector
- Symantec CloudSOC Cloud Collector
- Troubleshooting Cloud Collectors
Configure the Symantec CloudSOC Cloud Collector
Set up the Symantec CloudSOC Cloud Collector to continuously ingest Symantec CloudSoc logs that include Investigate Service App logs, Detect App (Incidents) logs and Investigate App logs.
Use the following steps to set up the Symantec CloudSOC Cloud Cloud Collector.
Before you configure the Symantec CloudSOC 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 Symantec CloudSOC.
Enter the following information for the cloud collector.
NAME – Specify a name for the Cloud Collector instance.
TENANT – Enter the value for tenant that you obtained while completing prerequisites.
KEY ID – Enter the value for key ID that you obtained while completing prerequisites.
KEY SECRET – Enter the value for key secret that you obtained while completing prerequisites.
REGION – Select the region EU or US based on the cloud host URL. If you use US-based production cloud, the host URL is api-vip.elastica.net. Select US. If you use EU-based production cloud, the host URL is api.eu.elastica.net. Select EU.
INGEST FROM – Select the time and date from which the collector must start ingesting events.
DATA SOURCES – Select one or more data sources for which you want the collector to collect data: Detect App (Incidents), Investigate App, and Investigate Service App.
(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.