- 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 Palo Alto Networks SaaS Security Cloud Collector
Before you configure the Palo Alto Networks SaaS Security cloud collector you must complete the following prerequisites:
Obtain the client ID.
Obtain the client secret.
Obtain the Client ID and Client Secret
Palo Alto Networks SaaS Security APIs are authenticated via API client ID and client secret. You must obtain the API client ID and client secret to use while configuring the SaaS Security collector.
Use the following steps to obtain client ID and client secret.
Log in to SaaS Security console as an administrator.
Navigate to Settings > External Service.
Click Add Client App to register an API client.
Specify a name for the API client.
Click Save. SaaS Security displays a client ID and a client secret.
The value for a client secret appears in a pop-up only once. If you close the pop-up and lose the key value, you must regenerate the value. For more information, see the SaaS Security documentation.
Record the values for a client ID and a client secret. Use the values to authenticate the API client while configuring the cloud collector.