Ansible
Connect Ansible to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Ansible to collect infrastructure evidence with automated compliance tests, switched on per workspace.
| Category | Infrastructure |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Ansible's guide | docs.ansible.com |
Connect with an API token
-
In Ansible:
- In automation controller, go to Users and click Add to open the Create User dialog.
- Enter the required details and select System Auditor as the user type (auditors have read-only access to all objects), then click Save.
- Signed in as that user, open your user profile, click the Tokens tab, and click Add to open the Create Token window.
- Leave Application blank to create a personal access token, optionally add a Description, choose the Scope (the level of access the token should have), and click Save.
- Copy the token value now; this is the only time it is shown.
Ansible shows the secret only once, so copy it before you leave the page.
Steps are from the automation controller 4.5 user guide (legacy docs site). Newer Ansible Automation Platform 2.5+ unified UI labels may differ. The API path field is optional (default /api/v2/ for controller; AAP 2.5 gateway uses /api/controller/v2/), not confirmed on the fetched page. The fetched page does not list the Scope options, so the Read choice was removed from the steps.
Source: legacy-controller-docs.ansible.com, checked 2026-10-07.
The permissions Safeguard needs:
System Auditor,read scope. -
On Compliance › Connectors, open Ansible, click Connect, choose API token and fill in:
Field What to enter Server URL Required. Your own server: an https address reachable from the internet. Access token Required. Stored encrypted and never shown again. API path (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Ansible 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 | CC6.2, CC6.3 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 3 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- Infrastructure 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