> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/oracle-cloud-infrastructure-cloud-onboarding/how-to-onboard-oracle-cloud-infrastructure.md). # How to onboard Oracle Cloud Infrastructure After completing the prerequisites, follow these instructions to onboard your Oracle Cloud Infrastructure (OCI) environment to Cortex Cloud. ### Access the OCI onboarding wizard in Cortex Cloud: 1. In Cortex Cloud, select Settings → Data Sources & Integrations. 2. On the Data Sources & Integrations page, click + Add New. 3. On the Add Data Sources or Integrations page, search for Oracle Cloud Infrastructure, then hover over it and click Add. ### Set the instance name (optional) * In Instance Name, enter a unique instance name. If you don't enter a name, Cortex Cloud applies the default name, `OCI-`. Cortex Cloud does not prevent you from reusing instance names, but it is best practice to use a unique name for every cloud instance. ### Configure advanced settings (optional) * Click Show advanced settings to define the following advanced settings: * **Scope Modifications:** You can modify the scope by including or excluding specific Compartments. If you choose to include specific compartments, only the specified compartments and their sub-compartments will be included. This setting will affect future sub-compartments added to your OCI environment after onboarding. If you choose to exclude specific compartments, this setting will also affect their sub-compartments. **Note**: The root compartment is always onboarded, and only the sub-compartment scope can be modified. Excluded compartments are not visible in Cortex Cloud. * **Additional Security Capabilities:** Choose which security capabilities you want to benefit from. Some security capabilities are enabled by default and can be modified. Adding security capability typically requires additional cloud provider permissions. For detailed information on the permissions required, see [Oracle Cloud Infrastructure (OCI) provider permissions](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/cloud-service-provider-permissions/oracle-cloud-infrastructure-oci-provider-permissions.md). * **Data security posture management:** An agentless data security scanner that discovers, classifies, protects, and governs sensitive data. * **Registry scanning:** A container registry scanner that scans registry images for vulnerabilities, malware, and secrets. For more details, see [Configure registry scanning for cloud accounts](/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/configure-registry-scanning-for-cloud-accounts.md). * **Serverless functions scanning:** Implement serverless scanning to detect and remediate vulnerabilities within serverless functions during the development lifecycle. Seamless integration into CI/CD pipelines enables automated security scans for a continuously secure pre-production environment. * **Agentless disk scanning:** (Recommended) Implement agentless disk scanning to remotely detect and remediate vulnerabilities during the development lifecycle. * **Cloud Tags:** Define tags and tag values to be added to any new resource created by Cortex Cloud in OCI. Note: The `managed_by = paloaltonetworks` tag is automatically added to all resources. This tag is mandatory. You cannot edit or remove this tag. * **Log Collection Configuration:** To maximize security coverage, enable the collection of audit logs. This may require additional cloud service provider permissions. For detailed information on the permissions required, see [Oracle Cloud Infrastructure (OCI) provider permissions](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/cloud-service-provider-permissions/oracle-cloud-infrastructure-oci-provider-permissions.md). Enter the following details for each preexisting OCI storage bucket that you intend to use for log collection: * Region: The geographic OCI region where the bucket is located. For example, "us-phoenix-1". * Bucket Name: The name of the OCI storage bucket. * Compartment OCID: The Oracle Cloud Identifier (OCID) of the compartment that contains the bucket. ### Save the configuration and download the authentication template 1. Click **Save**. Cortex Cloud generates a Terraform authentication template based on the settings you configured in the OCI onboarding wizard. Cortex Cloud creates an instance in the pending state. For details on pending instances, see [Pending cloud instances](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/pending-cloud-instances.md). 2. Download the OCI authentication template by clicking **Download Terraform**. The Terraform authentication template is reusable and can be executed as many times as you want to create new instances with the settings you defined in the wizard. The Terraform authentication template is valid for seven days from when it was created. 3. Click **Close**. **Next step:** [Deploy the Terraform authentication template in OCI](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/oracle-cloud-infrastructure-cloud-onboarding/deploy-the-terraform-authentication-template-in-oci.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/oracle-cloud-infrastructure-cloud-onboarding/how-to-onboard-oracle-cloud-infrastructure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.