SecurityScorecard Atlas
Connect SecurityScorecard Atlas to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect SecurityScorecard Atlas to collect vendor procurement evidence with automated compliance tests, switched on per workspace.
| Category | Vendor Procurement |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| SecurityScorecard Atlas's guide | support.securityscorecard.com |
Connect with an API token
-
In SecurityScorecard Atlas:
- In SecurityScorecard, go to My Settings › API to generate a personal API token, or (recommended for administrators) create a bot user as below.
- Go to My Settings › Users and click Add User.
- On the top-right, choose create a bot user; optionally set an access level, then click Add.
- On the new bot user's row, click create token and copy the API key.
Where to find the other values:
- Domain: Your company's primary domain as it appears on your SecurityScorecard scorecard (the fetched docs do not show where the UI displays it).
SecurityScorecard Atlas's public documentation does not cover every step.
Docs recommend bot-user tokens for administrators. The token is sent as 'Token <key>'. The docs fetched do not name an access level that limits a bot user to reading the company's own scorecard, nor say whether the token is shown once. support.securityscorecard.com returned 403 to the fetcher.
Source: securityscorecard.readme.io, securityscorecard.readme.io, checked 2026-10-07.
The permissions Safeguard needs:
read the company's own scorecard. -
On Compliance › Connectors, open SecurityScorecard Atlas, click Connect, choose API token and fill in:
Field What to enter API token Required. Stored encrypted and never shown again. Domain Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read SecurityScorecard Atlas 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 | 1 |
| ISO/IEC 27001 | Automated tests | A.8.8 | 1 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1) | 1 |
| PCI DSS | Automated tests | 6.3.3, 11.3.1 | 1 |
| NIST CSF 2.0 | Automated tests | ID.RA-01, ID.RA-06 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Vendor Procurement 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