Riot
Connect Riot to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Riot to collect security training evidence with automated compliance tests, switched on per workspace.
| Category | Security Training |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Riot's guide | docs.tryriot.com |
Connect with an API token
-
In Riot:
- Contact Riot's technical team to request an API key; Riot's API reference says customers acquire keys this way, not in the app.
- Ask for a key scoped to your organization (covers every workspace) or to one workspace, limited to the read scopes awareness:read, simulation:read, breach:read and workspace:read.
Where to find the other values:
- Workspace ID (optional): Needed only for an organization-scoped key, to pick one workspace (the API's workspace_id parameter). A workspace-scoped key is already limited to its workspace. Where the Riot app shows the workspace ID is not documented; ask Riot with the key request.
Riot issues this credential through its API or its support team, not through its admin screens.
The key goes in the x-api-key header; base URL https://public-api.tryriot.com/v1. API access must be part of the plan of the organization or workspace the key is scoped to; otherwise requests return 403 feature_not_entitled. The grant 'courses, campaigns and attacks: read' maps to awareness:read and simulation:read; this mapping is inferred from the scope names.
Source: docs.tryriot.com, public-api.tryriot.com, checked 2026-10-07.
The permissions Safeguard needs:
courses, campaigns and attacks: read. -
On Compliance › Connectors, open Riot, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. Workspace ID (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Riot 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 | CC1.4, CC2.2 | 2 |
| ISO/IEC 27001 | Automated tests | A.6.3 | 2 |
| HIPAA Security Rule | Automated tests | 164.308(a)(5) | 2 |
| PCI DSS | Automated tests | 12.6.1, 12.6.3.1 | 2 |
| NIST CSF 2.0 | Automated tests | PR.AT-01 | 2 |
These tests are switched on per workspace by the Safeguard team.
Related
- Security Training 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
Proofpoint Security Awareness
Connect Proofpoint Security Awareness to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
SANS Security Awareness
Connect SANS Security Awareness to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.