Oracle Cloud Infrastructure Documentation

For All US Government Cloud Customers

This topic contains information common to both the US Government Cloud with FedRAMP High Joint Authorization Board authorization and to the US Federal Cloud with DISA Impact Level 5 authorization.

Shared Responsibilities

Oracle Cloud Infrastructure for government offers best-in-class security technology and operational processes to secure its enterprise cloud services. However, for you to securely run your workloads , you must be aware of your security and compliance responsibilities. By design, Oracle provides security of cloud infrastructure and operations (cloud operator access controls, infrastructure security patching, and so on), and you are responsible for securely configuring your cloud resources. Security in the cloud is a shared responsibility between you and Oracle.

For more information about shared responsibilities in the Oracle Cloud, see the following white papers:

Setting Up an Identity Provider for Your Tenancy

As a Government Cloud customer, you must bring your own identity provider that meets your agency's compliance requirements and supports common access card/personal identity verification card (CAC/PIV) authentication. You can federate Oracle Cloud Infrastructure with SAML 2.0 compliant identity providers that also support CAC/PIV authentication. For instructions on setting up a federation, see Federating with Identity Providers.

Remove the Oracle Cloud Infrastructure Default Administrator User and Any Other Non-Federated Users

When your organization signs up for an Oracle account and Identity Domain, Oracle sets up a default administrator for the account. This person will be the first IAM user for your company and will have full administrator access to your tenancy. This user can set up your federation.

After you have successfully set up the federation with your chosen identity provider, you can delete the default administrator user and any other IAM service local users you might have added to assist with setting up your tenancy. Deleting the local, non-federated users ensures that only users in your chosen identity provider can access Oracle Cloud Infrastructure.

To delete the default administrator:

  1. Sign in to the Console through your identity provider.

    More details

    1. Open a supported browser and go to the Government Cloud Console URL.

    2. Enter your Cloud Tenant and click Continue.

    3. On the Single Sign-On pane, select your identity provider and click Continue. You will be redirected to your identity provider to sign in.

    4. Enter your user name and password.
  2. Open the navigation menu and click Identity & Security. Under Identity, click Users. The list of users is displayed.
  3. On the User Type filter, select only Local Users.
  4. For each local user, go to the the Actions menu (Actions Menu) and click Delete.

Password Requirements

Password requirements for US Government Cloud tenancies and services must meet or exceed requirements outlined in NIST Special Publication 800-63.

Using a Common Access Card/Personal Identity Verification Card to Sign in to the Console

After you set up CAC/PIV authentication with your identity provider and successfully federate with Oracle Cloud Infrastructure, you can use your CAC/PIV credentials to sign in to the Oracle Cloud Infrastructure Console. See your identity provider's documentation for the specific details for your implementation.

In general, the sign in steps are:

  1. Insert your CAC/PIV card into your card reader.
  2. Navigate to the Oracle Cloud Infrastructure Console sign in page.
  3. If prompted, enter your Cloud Tenant name and click Continue.
  4. Select the Single Sign-On provider and click Continue.
  5. On your identity provider's sign on page, select the appropriate card, for example, PIV Card.
  6. If presented with a certificate picker, choose the appropriate certificate or other attributes set up by your organization.
  7. When prompted, enter the PIN.

IPv6 Support for Virtual Cloud Networks

IPv6 addressing is supported for all commercial and government regions. Government customers have the option to enable IPv6 addressing for their VCNs. For more information, see IPv6 Addresses.

Setting Up Secure Access for Compute Hosts

You can set up CAC/PIV authentication using third-party tools to enable multi-factor authentication for securely connecting to your compute hosts. Example tools include PuTTY-CAC for Windows and Open SC for macOS. For more information see the U.S. Government website, PIV Usage Guidelines.

Enabling FIPS Mode for Your Operating System

Government Cloud customers are responsible for enabling FIPS mode for the operating systems on their Compute hosts. To make your operating system compliant with Federal Information Processing Standard (FIPS) Publication 140-2, follow the guidelines for your operating system:

Oracle Linux

Follow the guidance provided at FIPS 140-2 Compliance in Oracle Linux 8.

Ubuntu

Follow the guidance provided at Ubuntu Security Certifications - Enabling FIPS 140.

Windows Server 2012

Follow the guidance provided at Data Encryption for Web console and Reporting server Connections.

Windows Server 2016 and Windows Server 2019

First, follow the guidance provided at How to Use FIPS Compliant Algorithms.

Next, go to the Microsoft document, FIPS 140 Validation and navigate to the topic Information for System Integrators. Follow the instructions under "Step 2 – Setting FIPS Local/Group Security Policy Flag" to complete the FIPS enablement.

CentOS

The following guidance is for enabling FIPS on CentOS 7.5 and CentOS Stream 8. These procedures are valid for both VM and bare metal instances, and only in NATIVE mode. These procedures can be modified for both Emulated and PV modes as needed. Note that this procedure provides an instance that contains the exact FIPS cryptographic modules EXCEPT kernel. The kernel module is the same major/minor version, however, but is accelerated in revision, so can be considered compliant under most FIPS-compliant models.

After you complete this procedure, Oracle strongly recommends that you do NOT run system-wide yum updates. The system-wide update will remove the FIPS modules contained herein.

Verify that the version of the kernel, FIPS modules, and FIPS software are at the minimum version:

  1. Validate the current version of the kernel package meets the requirement:

    1. Current version: kernel-3.10.0-693.el7

    2. Execute rpm -qa | grep kernel-3

  2. Execute the following and validate the major or minor version is the same as the requirements.

    1. Run

      yum list <package_name>

    2. Verify that the major/minor version matches the required ones.

      Required packages and versions are:

      • fipscheck - fipscheck-1.4.1-6.el7

      • hmaccalc - hmaccalc-0.9.13-4.el7

      • dracut-fips - dracut-fips-033-502.el7

      • dracut-fips-aesni - dracut-fips-aesni-033-502.el7

    3. For each version of package that is not installed, run

      yum install <package_name>
  3. Download and install the following packages:
    1. Packages already installed as part of the image:

      1. Create a directory called preinstall.

      2. Download the following packages into this directory:

        openssl, openssl-libs – 1.0.2k-8.el7

        nss, nss-tools, nss-sysinit – 3.28.4-15.el7_4

        nss-util – 3.28.4-3.el7

        nss-softokn, nss-softokn-freebl – 3.28.3-8.el7_4

        openssh, openssh-clients, openssh-server – 7.4p1-11.el7

      3. In the preinstall directory, run

        yum - -nogpgcheck downgrade *.rpm
    2. Packages to be added to the image:
      1. Create a directory called newpackages.

      2. Download the following packages into this directory:

        libreswan – 3.20-3.el7

        libgcrypt – 1.5.3-14.el7

        gnutls – 3.3.26-9.el7

        gmp – 6.0.0-15.el7

        nettle – 2.7.1-8.el7

      3. In the newpackages directory, run

         yum - -nogpgcheck localinstall *.rpm

The URLs for the packages used for this installation are:

Preinstall:

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/nss-3.28.4-15.el7_4.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/nss-util-3.28.4-3.el7.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/nss-tools-3.28.4-15.el7_4.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/nss-sysinit-3.28.4-15.el7_4.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/nss-softokn-freebl-3.28.3-8.el7_4.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/nss-softokn-3.28.3-8.el7_4.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/openssl-1.0.2k-8.el7.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/openssl-libs-1.0.2k-8.el7.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/openssh-7.4p1-11.el7.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/openssh-clients-7.4p1-11.el7.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/openssh-server-7.4p1-11.el7.x86_64.rpm

Newpackages:

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/libreswan-3.20-3.el7.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/libgcrypt-1.5.3-14.el7.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/gnutls-3.3.26-9.el7.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/gmp-6.0.0-15.el7.x86_64.rpm

http://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/nettle-2.7.1-8.el7.x86_64.rpm

Kernel FIPS module and initramfs validation installation.

Perform this procedure as root:

  1. Regenerate dracut:

    dracut -f -v

  2. Add the fips argument to the end of the default kernel boot command line:

    1. Edit /etc/default/grub

    2. At the end of the line starting with “GRUB_CMDLINE_LINUX”, add 

      fips=1

      inside the double quotes of the command.

    3. Save the result.

  3. Generate a new grub.cfg:

    grub2-mkconfig -o /etc/grub2-efi.cfg

Configure SSH to limit the encryption algorithms.

  1. Sudo to root.

  2. Edit /etc/ssh/sshd_config.

  3. Add the following lines to the bottom of the file:

    Protocol 2
Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc
Macs hmac-sha1
  4. Reboot the instance.
  5. After instance has rebooted, validate that FIPS mode has been enabled in the kernel:

    1. Sudo to root.

    2. Run the following command:

      cat /proc/sys/crypto/fips-enabled

      The result should be '1'.

To further secure CentOS7/RHEL 7.x systems as required by individual agency guidance, follow the checklist contained in the OpenSCAP guide. This guide can be found here: https://static.open-scap.org/ssg-guides/ssg-centos7-guide-index.html

The STIG for evaluating compliance under multiple profiles can be found here: https://iase.disa.mil/stigs/os/unix-linux/Pages/index.aspx . Use the Red Hat Linux 7.x STIG for CentOS 7.5 releases.

Required Site-to-Site VPN Parameters for Government Cloud

If you use Site-to-Site VPN with the Government Cloud, you must configure the IPSec connection with the following FIPS-compliant IPSec parameters.

For some parameters, Oracle supports multiple values, and the recommended one is highlighted in bold text.

Oracle supports the following parameters for IKEv1 or IKEv2. Check the documentation for your particular CPE to confirm which parameters the CPE supports for IKEv1 or IKEv2.

Phase 1 (ISAKMP)

Parameter Options
ISAKMP protocol

Version 1
Exchange type

Main mode
Authentication method

Pre-shared keys *
Encryption algorithm

AES-256-CBC (recommended)

AES-192-CBC

AES-128-CBC
Authentication algorithm

SHA-2 384 (recommended)

SHA-2 256

SHA-1 (also called SHA or SHA1-96)

Diffie-Hellman group

group 14 (MODP 2048)

group 19 (ECP 256)

group 20 (ECP 384) (recommended)
IKE session key lifetime

28800 seconds (8 hours)

* Only numbers, letters, and spaces are allowed characters in pre-shared keys.

Phase 2 (IPSec)

Parameter Options
IPSec protocol

ESP, tunnel mode
Encryption algorithm

AES-256-GCM (recommended)

AES-192-GCM

AES-128-GCM

AES-256-CBC

AES-192-CBC

AES-128-CBC
Authentication algorithm

If using GCM (Galois/Counter Mode), no authentication algorithm is required because authentication is included with GCM encryption.

If not using GCM, use HMAC-SHA-256-128.
IPSec session key lifetime

3600 seconds (1 hour)
Perfect Forward Secrecy (PFS)

Enabled, group 14 (default, recommended)

Supports disabled as well as enabled for group 2, 5, 14, 19, 20, 24.

Oracle's BGP ASN

This section is for network engineers who configure an edge device for FastConnect or Site-to-Site VPN.

Oracle's BGP ASN for the Government Cloud depends on the authorization level:

  • US Government Cloud: 6142
  • US Federal Cloud (Impact Level 5 authorization): 20054

FIPS Compatible Terraform Provider

To use Terraform in US Government Cloud regions, refer to Enabling FIPS Compatibility for installation and configuration information.

Container Engine for Kubernetes

The components installed by Container Engine for Kubernetes are compliant with FIPs. When using Container Engine for Kubernetes in US Government Cloud regions, you should also ensure that the underlying hosts are compliant with FIPs.

TLS Certificates for API Gateway

If you use API Gateway in US Government Cloud regions, you must:

  • Obtain a custom TLS certificate from an approved Certificate Authority.
  • Record the mapping between an API gateway's custom domain name and its public IP address with an approved DNS provider.

For more information, see Setting Up Custom Domains and TLS Certificates for installation and configuration information.

VN Encryption

Virtual network (VN) encryption provides instance-to-instance encryption for in-transit traffic within a region (in the same VCN or between VCNs peered with a local peering gateway) between any of the following compute shapes:

  • E3
  • E4
  • A1
  • X9

VN encryption is enabled by default at the region level and is available in US Government Cloud regions only. To disable VN encryption, you must create a service request.

The encryption keys are fully managed by Oracle Cloud Infrastructure. The mechanism for encryption is based on RFC3948. Specifications for key settings and encryption ciphers comply with FIPS 140-2 requirements.

When enabled, the VN encryption feature will increase latency and decrease throughput due to the encryption/decryption overhead. This may or may not be noticeable at the application layer. For more details around the latency numbers contact customer support.

Requesting a Service Limit Increase for Government Cloud Tenancies

If you need to request a service limit increase, use the following instructions to create a service request in My Oracle Support.

Important

Creating a Service Request

To create a service request for Oracle Government Cloud:

  1. Go to My Oracle Support and log in.

    If you are not signed in to Oracle Cloud Support, click Switch to Cloud Support at the top of the page.

  2. At the top of the page, click Service Requests.
  3. Click Create Technical SR.
  4. Select the following from the displayed menus:
    • Service Type: Select Oracle Cloud Infrastructure from the list.
    • Service Name: Select the appropriate option for your organization.
    • Problem Type: Select Account Provisioning, Billing and Termination, and then select Limit Increase from the submenu.
  5. Enter your contact information.
  6. Enter a Description, and then enter the required fields specific to your issue. If a field does not apply, you can enter n/a.

For help with any of the general fields in the service request or for information on managing your service requests, click Help at the top of the Oracle Cloud Support page.

Locating Oracle Cloud Infrastructure IDs

Use the following tips to help you locate identifiers you might be asked to provide:

Finding Your Tenancy OCID (Oracle Cloud Identifier)

Get the tenancy OCID from the Oracle Cloud Infrastructure Console on the Tenancy Details page:

  1. Open the Profile menu and click Tenancy: <your_tenancy_name>.

  2. The tenancy OCID is shown under Tenancy Information. Click Copy to copy it to your clipboard.

    Tenancy Details page showing the location of the tenancy OCID

Finding the OCID of a Compartment

To find the OCID (Oracle Cloud Identifier) of a compartment:

  1. Open the navigation menu and click Identity & Security. Under Identity, click Compartments.

    A list of the compartments in your tenancy is displayed.

    A shortened version of the OCID is displayed next to each compartment.

    Console page showing the OCID of a compartment

  2. Click Copy to copy the OCID to your clipboard. You can then paste it into the service request form field.
Finding the OCID of a Resource

The OCID (Oracle Cloud Identifier) of a resource is displayed when you view the resource in the Console, both in the list view and on the details page.

For example, to get the OCID for a compute instance:

  1. Open the Console.

  2. Select the Compartment to which the instance belongs from the list on the left side of the page.

    Note that you must have appropriate permissions in a compartment to view resources.

  3. Open the navigation menu and click Compute. Under Compute, click Instances. A list of instances in the selected compartment is displayed.

  4. A shortened version of the OCID is displayed on the instance details page.

  5. Click Copy to copy the OCID to your clipboard. You can then paste it into the service request form field.
Finding Your Customer Service Identifier (CSI)

The Customer Support Identifier (CSI) number is generated after you purchase Oracle Cloud services. This number can be found in several places, including in your contract document and also on your tenancy details page. You’ll need the CSI number to register and log support requests in My Oracle Support (MOS).

Note

The CSI number is not available for OCI Government Cloud regions.

To find your CSI number:

  1. Open the Profile menu and click Tenancy: <your_tenancy_name>.

  2. The CSI number is shown under Tenancy Information.

    Tenancy Details page showing CSI number

Using My Oracle Support for the First Time

Before you can create service requests with My Oracle Support, you need to have an Oracle Single Sign On (SSO) account and you need to register your Customer Support Identifier (CSI) with My Oracle Support.

Tip

Before you begin this procedure, have your CSI handy (see Requesting a Service Limit Increase for Government Cloud Tenancies).
To request an SSO account and register with My Oracle Support
  1. Go to https://support.oracle.com.

  2. Click New user? Register here to create your Oracle Single Sign On (SSO) account.

  3. Enter your company e-mail address in the Email address field, complete the rest of the form, and then click Create Account. A verification email is generated.

  4. Check your email account for an email from Oracle asking your to verify your email address.

  5. Open the email and click Verify Email Address.
  6. Sign in with the credentials you just set up.
  7. At sign in, you are prompted to enter a Note to the Approver and the Support Identifier (your CSI).

  8. Click Request Access.

  9. Enter the first five characters of the name of the organization that owns the Customer Support Identifier (listed in the Welcome letter and on My Services), and then click Validate. The support identifier appears in the table.
  10. Click Next.
  11. Enter your contact information and click Next.
  12. Accept the terms and click Next.

The status of the request is pending until you receive approval from the Customer User Administrator (CUA) or from Oracle Support if you are the first person requesting this support identifier.

If you have previously registered, but need to add the CSI for Oracle Cloud Infrastructure
  1. Go to https://support.oracle.com and log in.
  2. Navigate to the My Account page: Go to your user name at the of the page, open the menu, and then click My Account.
  3. The Support Identifiers region displays the accounts that your user name is currently associated with.
  4. Click Request Access.
  5. Enter a Note to the Approver and then enter the Support Identifier (your CSI).
  6. Click Request Access.
  7. Enter the first five characters of the name of the organization that owns the Customer Support Identifier (listed in the Welcome letter and on My Services), and then click Validate. The support identifier appears in the table.
  8. Click Validate.
  9. The entry is validated. Close the dialog.

The status of the request is pending until you receive approval from the Customer User Administrator (CUA).

For more information about signing in and using My Oracle Support, see Registration, Sign In, and Accessibility Options in My Oracle Support Help.