Safeguard Docs
Compliance ConnectorsSetup by categoryCloud Infrastructure

Oracle Cloud Government

Connect Oracle Cloud Government to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Connect Oracle Cloud Government to collect cloud infrastructure evidence automatically.

CategoryCloud Infrastructure
Connect withAPI token
What a connection producesAutomated evidence collection

Connect with an API token

  1. In Oracle Cloud Government:

    1. Sign in to the Oracle US Government Cloud Console at https://console.us-langley-1.oraclegovcloud.com/ or https://console.us-luke-1.oraclegovcloud.com/.
    2. Open the Profile menu and select User settings.
    3. On the Tokens and keys tab, go to the Auth tokens section and select Generate token.
    4. Enter a description (no confidential information), then select Generate token.
    5. Copy the auth token immediately to a secure location: you won't see it again in the Console.

    Where to find the other values:

    • Base URL (optional): Government Cloud API endpoints use the oraclegovcloud.com domain per region, for example https://identity.us-langley-1.oraclegovcloud.com (US Gov East, us-langley-1) or the us-luke-1 (US Gov West) equivalent.
    • Account / Org / Workspace (optional): Open the Profile menu and select Tenancy: <your_tenancy_name>; the tenancy OCID is under Tenancy Information (select Copy).

    Oracle Cloud Government shows the secret only once, so copy it before you leave the page.

    The token-generation steps are from Oracle's commercial-cloud page; Oracle documents the same Console for the US Government Cloud realm (OC2), but the Government-specific page was not checked for the token steps. The token carries the creating user's IAM permissions, so create it as a user whose group policies only allow inspect/read. Console sessions time out after 15 minutes of inactivity.

    Source: docs.oracle.com, docs.oracle.com, docs.oracle.com, checked 2026-10-07.

  2. On Compliance › Connectors, open Oracle Cloud Government, click Connect, choose API token and fill in:

    FieldWhat to enter
    API token / Personal access tokenRequired. Stored encrypted and never shown again.
    Base URL (optional)—
    Account / Org / Workspace (optional)—
  3. Click Connect with token.

Frameworks

Safeguard's automated tests read Oracle Cloud Government 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.

FrameworkEvidenceControlsTests
SOC2Automated testsA1.2, C1.1, CC2.1, CC6.1, CC6.2, CC6.3, CC6.6, CC6.7, CC6.8, CC7.1, CC7.266
ISO/IEC 27001Automated testsA.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.3266
HIPAA Security RuleAutomated tests164.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 DSSAutomated tests1.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.156
NIST CSF 2.0Automated testsDE.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-0466
CIS Oracle Cloud Infrastructure Foundations BenchmarkAutomated tests1.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.240

For a CIS benchmark, the numbers are its recommendations.

These tests are switched on per workspace by the Safeguard team.

Oracle Cloud connect to the same provider as Oracle Cloud Government, and these tests run for a connection made through any of them.

On this page