Ox Security
Connect Ox Security to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Ox Security to collect vulnerability scanning evidence with automated compliance tests, switched on per workspace.
| Category | Vulnerability Scanning |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Ox Security's guide | docs.ox.security |
Connect with an API token
-
In Ox Security:
- In OX, go to Settings › Organization › API Keys.
- Click Create API Key.
- Enter an API Key Name and, under API Key Type, select API Integration.
- Under Assign role, select a read-only role such as Viewer.
- Under Assign scope, select Entire organization (or Custom to limit to applications with specific App Owners and Tags), and set an Expiration Date.
- Click Create, then copy the API key. You won't be able to view it again after closing the dialog.
Where to find the other values:
- Base URL (optional): OX Cloud uses https://api.cloud.ox.security/api/apollo-gateway. On-prem deployments use https://<CustomerDomain>/api/apollo-gateway.
Ox Security shows the secret only once, so copy it before you leave the page.
API keys use the same role and scope model as OX users; OX's docs give a Viewer role as an example. Rate limits are 1,000 requests per hour and 15,000 per day per API key.
Source: docs.ox.security, checked 2026-10-07.
The permissions Safeguard needs:
read-only API key role. -
On Compliance › Connectors, open Ox Security, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. Base URL (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Ox Security 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.1 | 4 |
| ISO/IEC 27001 | Automated tests | A.8.8 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1) | 4 |
| PCI DSS | Automated tests | 6.3.3, 11.3.1 | 4 |
| NIST CSF 2.0 | Automated tests | ID.RA-01, ID.RA-06 | 4 |
These tests are switched on per workspace by the Safeguard team.
Related
- Vulnerability Scanning 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