Akamai
Connect Akamai to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Akamai to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.
| Category | Cloud Infrastructure |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Akamai's guide | techdocs.akamai.com |
Connect with an API token
-
In Akamai:
- In Akamai Control Center, go to Identity and Access Management (Users and API Clients).
- Click Create API client and choose to create an advanced client.
- In the client details, limit the APIs assigned to the client to the ones Safeguard needs and configure read-only permissions for each of them.
- Click Create API client.
- Under the credentials, click Download (an .edgerc file) or Copy to get the client token, client secret, access token and host.
Where to find the other values:
- Host: The host value in the downloaded credentials, for example akab-xxxx.luna.akamaiapis.net.
Akamai's public documentation does not cover every step.
The fetched page confirms the advanced-client flow (customize the assigned APIs and configure read/write permissions per API) but does not name the individual APIs or the exact access-level labels, so check those in the client details screen. Whether the client secret can be viewed again is not stated; download or copy it at creation.
Source: techdocs.akamai.com, checked 2026-10-07.
The permissions Safeguard needs:
IAM User Admin: READ-ONLY,Application Security: READ-ONLY,CPS: READ-ONLY,Contract API: READ-ONLY. -
On Compliance › Connectors, open Akamai, click Connect, choose API token and fill in:
Field What to enter Host Required. An address under luna.akamaiapis.net. Client token Required. Stored encrypted and never shown again. Client secret Required. Stored encrypted and never shown again. Access token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Akamai 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 | CC6.1, CC6.2, CC6.3, CC6.6, CC6.7 | 6 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2, A.8.5, A.8.20, A.8.24 | 6 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.312(d), 164.312(e)(1) | 5 |
| PCI DSS | Automated tests | 4.2.1, 6.4.2, 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.IR-01 | 6 |
These tests are switched on per workspace by the Safeguard team.
Related
- Cloud 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