Redis Cloud
Connect Redis Cloud to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Redis Cloud 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 |
| Redis Cloud's guide | redis.io |
Connect with an API token
-
In Redis Cloud:
- Make sure a Redis Cloud user with the Viewer (read-only) role exists for Safeguard.
- Sign in to Redis Cloud (cloud.redis.io) as an account owner. From the menu, choose Access Management and select the API Keys tab.
- If an Enable API button appears, select it to enable the REST API for your account.
- Account key: click Show next to the API account key, then Copy it.
- User key: click Add, enter a Key name (10 to 50 characters, letters, digits, hyphens and underscores, no spaces), choose the Viewer user as User name, and select Create.
- In the API user key dialog, copy the key. This is the only time the value of the user key is available; Finish stays inactive until you copy it.
- Optional: in the CIDR allow list column click Manage and add Safeguard's egress addresses.
Redis Cloud shows the secret only once, so copy it before you leave the page.
User keys inherit the selected user's role; Viewer is read-only. Steps to invite the Viewer user were not fetched.
Source: redis.io, checked 2026-10-07.
The permissions Safeguard needs:
Viewer. -
On Compliance › Connectors, open Redis Cloud, click Connect, choose API token and fill in:
Field What to enter Account key Required. Stored encrypted and never shown again. User key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Redis Cloud 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 | A1.2, CC6.1, CC6.2, CC6.3, CC6.6, CC6.7 | 8 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2, A.8.5, A.8.13, A.8.20, A.8.24 | 8 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.308(a)(7), 164.312(a)(1), 164.312(d), 164.312(e)(1) | 8 |
| PCI DSS | Automated tests | 1.3.1, 4.2.1, 7.2.2, 7.2.4, 8.2.5, 8.4.2 | 6 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-03, PR.AA-05, PR.DS-02, PR.DS-11, PR.IR-01 | 8 |
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