Skip to main content

Oracle Cloud

Visualize OCI compute instances, virtual machine hosts, domains, access policies, oracle object storage, vaults, nosql services, streaming services , devops, functions, redis, resource manager , map OCI users to employees, and monitor changes through queries and alerts.

Installation

To install Oracle Cloud Infrastructure, you will need access to an admin account within your OCI instance. Additionally, you must provide the following credentials from Oracle Cloud to successfully initiate the integration:

  • Private Key
  • Tenancy OCID
  • User OCID
  • Fingerprint
  • Region
  • Passcode (if used to generate the Private Key)

Configuration on Oracle Cloud

Log into OCI as the root user or user with the required permissions (see below) and navigate to My profile in the top-right corner of the screen. From there:

  1. Under Resources, select API Keys > Add API Key.

  2. Generate a new key pair, choose a public key, or paste your desired public key then click Add.

  3. The configuration file preview will contain your User OCID, Tenancy OCID, Region and Fingerprint. Retain these values for use within the JupiterOne integration configuration.

Required Permissions

  • COMPARTMENT_INSPECT
  • DOMAIN_INSPECT
  • GROUP_INSPECT
  • USER_INSPECT
  • POLICY_READ
  • DEVOPS_BUILD_PIPELINE_INSPECT
  • DEVOPS_DEPLOY_ENVIRONMENT_INSPECT
  • DEVOPS_DEPLOY_PIPELINE_INSPECT
  • DEVOPS_PROJECT_INSPECT
  • DEVOPS_REPOSITORY_INSPECT
  • FN_FUNCTION_LIST
  • FN_APP_LIST
  • INSTANCE_READ
  • DEDICATED_VM_HOST_INSPECT
  • NOSQL_INDEX_READ
  • NOSQL_TABLE_INSPECT
  • BUCKET_READ
  • REDIS_CLUSTER_INSPECT
  • ORM_STACK_INSPECT
  • STREAM_INSPECT
  • STREAM_POOL_INSPECT
  • KEY_INSPECT
  • VAULT_INSPECT
  • SECRET_INSPECT
  • CG_PROBLEM_INSPECT

Example policy

Allow group SandboxGroup to read all-resources in tenancy where any { request.permission='COMPARTMENT_INSPECT', request.permission='DOMAIN_INSPECT', request.permission='GROUP_INSPECT', request.permission='USER_INSPECT', request.permission='POLICY_READ', request.permission='DEVOPS_BUILD_PIPELINE_INSPECT', request.permission='DEVOPS_DEPLOY_ENVIRONMENT_INSPECT', request.permission='DEVOPS_DEPLOY_PIPELINE_INSPECT', request.permission='DEVOPS_PROJECT_INSPECT', request.permission='DEVOPS_REPOSITORY_INSPECT', request.permission='FN_FUNCTION_LIST', request.permission='FN_APP_LIST', request.permission='INSTANCE_READ', request.permission='DEDICATED_VM_HOST_INSPECT', request.permission='NOSQL_INDEX_READ', request.permission='NOSQL_TABLE_INSPECT', request.permission='BUCKET_READ', request.permission='REDIS_CLUSTER_INSPECT', request.permission='ORM_STACK_INSPECT', request.permission='STREAM_INSPECT', request.permission='STREAM_POOL_INSPECT', request.permission='KEY_INSPECT', request.permission='VAULT_INSPECT', request.permission='SECRET_INSPECT', request.permission='CG_PROBLEM_INSPECT'}

Configuration in JupiterOne

To install the Oracle Cloud integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Oracle Cloud. Click New Instance to begin configuring the integration.

Creating an Oracle Cloud instance requires the following:

  • The Account Name used to identify the AirWatch account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Your Oracle Cloud Private Key.

  • The Tenancy OCID, User OCID, and Fingerprint, and Region values associated to your Private Key.

  • Optionally, you may supply the Private Key Passphrase if your Private Key was generated with it.

Click Create once all values are provided to finalize the integration.

Next steps

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.