- 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
- 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 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
Prerequisites to Configure the Symantec Cloud Secure Web Gateway Cloud Collector
Before you configure the Symantec Cloud Secure Web Gateway Cloud Collector you must obtain the user API key, also known as the API credentials.
Obtain the User API Key
Symantec Cloud Secure Web Gateway APIs are authenticated via application keys. You must obtain the user API key to configure the Symantec Cloud Secure Web Gateway cloud collector.
To obtain the user API key:
Log in to the Symantec SWG console as an administrator.
Navigate to Service mode > Account Maintenance > Integrations.
Click New Integration.
Click API Credentials.
The New API Credentials dialog box displays values for username and password, represented by letters and numbers. Note the values to use while configuring the Symantec SWG Collector on the New-Scale Security Operations Platform. For more information see the Create a User API Key section of the Symantec Near Real-Time Log Sync Solution Brief guide.
Understand Symantec Symantec Cloud Secure Web Gateway Log Events
The Symantec Symantec Cloud Secure Web Gateway (SWG) log events are classified into three types by Exabeam cloud connector for filtering them from Symantec SWG data source: informational events, connection failure events, and security related events.
Informational events – Connections events that are passed without any issue by Symantec SWG.
Connection failure events – Events that include connection attempts that are reset, failed, or rejected by Symantec SWG.
Security related events – Events that include:
URLs classified as threat risk by Symantec SWG
Client environment that is identified as a risk based on Symantec SWG compliance policy
Connection that Symantec SWG identified for Data Loss Prevention (DLP) to check if data leak has occurred, according to the ICAP response
Connection in which Symantec SWG identified malware
Connection for which access is denied based on Symantec SWG compliance policy
By default, Exabeam ingests all events pulled by Symantec SWG. During the configuration of the Symantec SWG Cloud Collector, you can choose to filter events that Symantec SWG pulls from a data source. This includes filtering for traffic events, security related events, or connection failure events.
If you want Symantec SWG to pull all the events including security related events, select Yes for normal/informational traffic events and connection failure events. The security related events are included with these events.
If you want Symantec SWG to pull only security related events, select Yes for security related events or select No for normal/informational traffic events and connection failure events.