- 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
Prerequisites to Configure the Symantec CloudSOC Cloud Collector
Before you configure the Symantec CloudSOC Cloud Collector you must obtain the API Key, also called Key ID, Key Secret, and Tenant.
Obtain the API Key, Key Secret, and Tenant
Symantec CloudSOC APIs are authenticated via application keys. You must obtain the API key, key secret, and tenant to use while configuring the Symantec CloudSOC cloud collector.
To obtain an application key ID, key secret, and tenant:
Log in to the Symantec CloudSOC console as an administrator.
Navigate to Settings by clicking your username.
Click API Keys on the Settings page.
On the API Keys page, in the Add a New API Key box, type a name for the key, then click Add New API Key.
In the API Key List area, in the row for the new key that you created, click the download icon to download the config.json file.
Open the config.json file in a text editor and record the values for:
Key ID
Key Secret
Tenant
Note the values for the API key that is key ID, key secret, and tenant. Use the values while configuring the Symantec CloudSOC cloud collector. For more information see CloudSOC Management API Guide.