Splunk SOAR
Connect Splunk SOAR to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Splunk SOAR to collect observability evidence with automated compliance tests, switched on per workspace.
| Category | Observability |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Splunk SOAR's guide | help.splunk.com |
Connect with an API token
-
In Splunk SOAR:
- Log in to Splunk SOAR as an administrative user. From the Main Menu, select Administration.
- Select User Management › Users.
- Click + User and select Automation as the user type.
- Provide a user name and fill in Allowed IPs: use any for unrestricted access, or a single IP or netmask (Safeguard's outbound address).
- Choose one or more roles for the user; the default Automation role is available for this user type.
- Click Create, then click the user name you just created. Copy the ph-auth-token value from the Authentication Configuration for REST API panel.
Where to find the other values:
- Base URL: The server value in the same Authentication Configuration for REST API panel is the URL used for REST requests.
RE-GENERATE AUTH TOKEN issues a new token and invalidates the old one. The token is only valid from the IPs in Allowed IPs. A narrower custom role for read-only container access is not described on the fetched page.
Source: help.splunk.com, checked 2026-10-07.
The permissions Safeguard needs:
automation user, read on containers. -
On Compliance › Connectors, open Splunk SOAR, click Connect, choose API token and fill in:
Field What to enter Base URL Required. Your own server: an https address reachable from the internet. Auth token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Splunk SOAR and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC7.3, CC7.4 | 2 |
| ISO/IEC 27001 | Automated tests | A.5.26 | 2 |
| HIPAA Security Rule | Automated tests | 164.308(a)(6) | 2 |
| PCI DSS | Automated tests | 12.10.1 | 2 |
| NIST CSF 2.0 | Automated tests | RS.MA-03, RS.MI-02 | 2 |
These tests are switched on per workspace by the Safeguard team.
Related
- Observability connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks