Oracle Cloud
Connect Oracle Cloud to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Oracle Cloud to collect cloud infrastructure evidence automatically.
| Category | Cloud Infrastructure |
| Connect with | API token |
| What a connection produces | Automated evidence collection |
Connect with an API token
-
In Oracle Cloud:
- In the Oracle Cloud Console, open the Profile menu and select User settings.
- On the Tokens and keys tab, go to the Auth tokens section and select Generate token.
- Enter a description (no confidential information), then select Generate token.
- Copy the auth token immediately to a secure location: you won't see it again in the Console. Then close the Generate token dialog.
Where to find the other values:
- Account / Org / Workspace (optional): Open the Profile menu and select Tenancy: <your_tenancy_name>; the tenancy OCID is under Tenancy Information (select Copy). The user OCID is under User Information in Profile › User settings.
Oracle Cloud shows the secret only once, so copy it before you leave the page.
An auth token inherits the permissions of the user who creates it; OCI has no per-token scope. For least privilege, create it as a user in a group whose IAM policies only allow inspect/read. Each user can have up to two auth tokens at a time, and they do not expire. Base URL is left blank unless you use a non-default region endpoint.
Source: docs.oracle.com, docs.oracle.com, checked 2026-10-07.
-
On Compliance › Connectors, open Oracle Cloud, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Oracle 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, C1.1, CC2.1, CC6.1, CC6.2, CC6.3, CC6.6, CC6.7, CC6.8, CC7.1, CC7.2 | 66 |
| ISO/IEC 27001 | Automated tests | A.5.9, A.5.15, A.5.16, A.5.17, A.5.18, A.8.2, A.8.3, A.8.5, A.8.7, A.8.8, A.8.9, A.8.13, A.8.14, A.8.15, A.8.16, A.8.20, A.8.24, A.8.32 | 66 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1), 164.308(a)(3), 164.308(a)(4), 164.308(a)(5), 164.308(a)(6), 164.308(a)(7), 164.312(a)(1), 164.312(b), 164.312(d), 164.312(e)(1) | 64 |
| PCI DSS | Automated tests | 1.3.1, 2.2.1, 3.5.1, 3.7.4, 4.2.1, 7.2.1, 7.2.2, 8.2.1, 8.2.6, 8.3.6, 8.4.2, 8.6.3, 10.2.1, 10.4.1, 10.5.1, 11.3.1, 11.5.1 | 56 |
| NIST CSF 2.0 | Automated tests | DE.AE-02, DE.CM-01, DE.CM-03, DE.CM-09, ID.AM-02, ID.RA-01, PR.AA-01, PR.AA-03, PR.AA-05, PR.DS-01, PR.DS-02, PR.DS-11, PR.IR-01, PR.IR-03, PR.PS-01, PR.PS-04 | 66 |
| CIS Oracle Cloud Infrastructure Foundations Benchmark | Automated tests | 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10, 1.12, 1.13, 1.15, 1.16, 1.17, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 3.1, 3.2, 3.3, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7, 4.8, 4.9, 4.10, 4.11, 4.12, 4.13, 4.14, 4.15, 4.16, 4.17, 4.18, 5.1.1, 5.1.2, 5.1.3, 5.2.1, 5.2.2, 5.3.1, 6.1, 6.2 | 40 |
For a CIS benchmark, the numbers are its recommendations.
These tests are switched on per workspace by the Safeguard team.
Oracle Cloud Government connect to the same provider as Oracle Cloud, and these tests run for a connection made through any of them.
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