Frameworks and connectors
How connectors provide evidence for compliance frameworks, which frameworks the automated tests map to, and how to cover any other framework.
Connectors don't attach to a framework directly. A connector feeds automated tests, each test checks one thing in a connected system, and each test maps to the controls it provides evidence for. When a test passes, that result is evidence toward every control it maps to, in every framework it maps to. Connect a system once, and its tests count everywhere they apply.
Frameworks the tests map to
The test catalogue maps every automated test, with a one-sentence rationale an auditor can check, to these frameworks:
| Framework | Controls with tests | Tests | Connectors with automated evidence |
|---|---|---|---|
| SOC2 | 34 | 855 | 360 |
| ISO/IEC 27001 | 51 | 850 | 360 |
| HIPAA Security Rule | 14 | 675 | 359 |
| PCI DSS | 47 | 658 | 343 |
| NIST CSF 2.0 | 47 | 835 | 360 |
| CIS Oracle Cloud Infrastructure Foundations Benchmark | 51 | 40 | 1 |
| CIS AWS Foundations Benchmark | 41 | 41 | 1 |
| CIS Microsoft Azure Foundations Benchmark | 85 | 72 | 1 |
| CIS Google Cloud Platform Foundations Benchmark | 61 | 49 | 1 |
| CIS Kubernetes Benchmark | 60 | 41 | 1 |
Each framework page lists the connectors that provide its evidence, the controls each one covers, and links to every connector's setup steps. On a framework's page in Safeguard, the Connectors tab shows the same list for your workspace, with which connectors you have connected and whether each connection is healthy.
Through the crosswalk
The crosswalk relates controls across SOC2, ISO/IEC 27001, the HIPAA Security Rule, PCI DSS, NIST CSF 2.0 and NIST SP 800-53. Evidence counts toward a control in another of these frameworks only through an equivalent crosswalk row that has been reviewed, or that your workspace approved, and only while the evidence is accepted and in date. Every other related row is a suggestion for a person to review, never a pass. Credit never chains: evidence that the crosswalk produced is not used as a source again. NIST SP 800-53 has no direct test mappings, so its automated evidence comes through the crosswalk.
Every other framework
Your framework library has many more frameworks than the ones above (see Compliance frameworks). For any of them, link the automated tests you want to count yourself:
- Open the framework on Compliance › Frameworks, then the control.
- Choose Link a test, search for the test, and click Link. The test's result then counts toward that control, the same way a catalogue mapping does.
- To change several at once, use Edit mappings on the framework's tests.
Controls that no test checks are evidenced the usual way: policies, uploaded evidence, records in Safeguard and attestations.
How to connect each system: Compliance connectors.