Follow these steps to generate a client ID and client
secret so you can add an API client to Data Security.
| Where Can I Use This? | What Do I Need? |
|
|
Or any of the following licenses that include the Data Security license:
|
You can configure a third-party API client
(for example,
Cortex XSOAR)
to
authenticate to
Data Security using an OAuth connection for efficient incident
management and remediation. To do so, you must first add an API
client on
Data Security to retrieve the Client ID and Client
Secret that your API client requires for authentication. When you
add the API client on
Data Security, you specify the incident
management and remediation access you want to grant the third-party
API client. You can only connect one third-party API client.
Data Security currently supports one Syslog receiver
AND one API client app with access to log data. So, you can use the two protocols
and connect SIEM and SOAR software separately. However,
Data Security does not
support using multiple Syslog receivers or multiple API clients concurrently.
Alternatively, if you want to use both Splunk and Cortex XSOAR, directly connect
Splunk to Cortex XSOAR using the
Splunk integration, and create a Client ID and Client
Secret for Cortex XSOAR to directly connect to
Data Security.