> 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-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/oracle-cloud-infrastructure-cloud-onboarding/oracle-cloud-infrastructure-oci-provider-permissions.md). # Oracle Cloud Infrastructure (OCI) provider permissions List of Oracle Cloud Infrastructure provider permissions for Cortex XDR. When you set up Cortex XDR to collect data from your cloud environments, the onboarding wizard will ensure that the correct permissions are granted for Cortex XDR. The following tables list the permissions required for each of the options available in the onboarding wizards. The following reference tables are organized by capability and then the list of the CSP permissions being requested. * [Discovery engine](#discovery-engine) * [ADS](#ads) * [Registry scan](#registry-scan) ## Discovery engine "Discovery Engine" read only access. Grants read-only access to OCI tenancy and resources. ## ADS | Permission | Module | Scope | Purpose | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------ | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | Admit group CortexOutpostGroup of tenancy CortexOutpost to use volumes in tenancy | ADS | In tenancy | Allow creation of backups from volumes | | Admit group CortexOutpostGroup of tenancy CortexOutpost to use key-delegate in tenancy | ADS | In tenancy | Re-encrypt backups during copy/restore operations | | Admit group CortexOutpostGroup of tenancy CortexOutpost to associate keys in tenancy with volumes in tenancy CortexOutpost | ADS | Volumes in tenancy | Associate encryption keys with volumes during backup/restore | | Admit group CortexOutpostGroup of tenancy CortexOutpost to use tag-namespaces in tenancy | ADS | In tenancy | Enable tagging for permission scoping, resource tracking, and cost visibility | | Admit group CortexOutpostGroup of tenancy CortexOutpost to manage boot-volume-backups in tenancy where request.operation != 'DeleteBootVolumeBackup' | ADS | Excludes delete | Allow full management of boot volume backups except deletion | | Admit group CortexOutpostGroup of tenancy CortexOutpost to manage boot-volume-backups in tenancy where target.resource.tag.cortex\_m-o-lcaas\_id.panw\_capability = 'cortex-scan-platform' | ADS | Only boot-volume-backups tagged with panw\_capability = cortex-scan-platform | Restrict deletion to Cortex scan-related resources only | | Admit group CortexOutpostGroup of tenancy CortexOutpost to read all-resources in tenancy | ADS | In tenancy | Read-only access to all resources | ## Registry scan ### Dynamic group permissions | Permission | Scope | Purpose | | ------------------------------------------------------------------- | ------------------------ | -------------------------------------------------------- | | Allow dynamic-group registry-scan to manage buckets in tenancy | Tag-scoped (project\_id) | Manage Object Storage buckets for scan artifacts/results | | Allow dynamic-group registry-scan to manage objects in tenancy | Tag-scoped (project\_id) | Upload/download image layers, manifests, and reports | | Allow dynamic-group registry-scan to read secret-bundles in tenancy | Tag-scoped (project\_id) | Retrieve registry credentials from OCI Vault | | Endorse dynamic-group registry-scan to read repos in any-tenancy | Cross-tenancy | Allow cross-tenancy image pulls for scans | ### Inherited base permissions for registry scanning | Permission | Scope | Purpose | | ---------------------------------------------------------------------------- | ------------------------ | --------------------------------------------------- | | Allow any-user to manage buckets in tenancy | Tag-scoped (project\_id) | Create/manage buckets for scan data | | Allow any-user to manage objects in tenancy | Tag-scoped (project\_id) | Read/write objects (artifacts, logs, results) | | Allow any-user to use keys in tenancy | Tag-scoped (project\_id) | Decrypt secrets for registry access | | Allow any-user to manage secret-versions in tenancy | Tag-scoped (project\_id) | Rotate credentials and manage secret versions | | Allow any-user to manage secrets in tenancy | Tag-scoped (project\_id) | Create/update secrets for scanners | | Allow any-user to manage secret-family in tenancy | Tag-scoped (project\_id) | Broader secret-management rights | | Allow any-user to manage vaults in tenancy | Tag-scoped (project\_id) | Create/administer Vaults for key and secret storage | | Allow any-user to inspect tag-family in tenancy | Global | Discover tag namespaces/definitions | | Allow any-user to use tag-family (namespace=cortex\_cloud, managed\_by=PANW) | Restricted | Restrict tag usage to Palo Alto-managed groups | | Endorse any-group to use tag-namespaces in any-tenancy | Cross-tenancy | Allow tag namespace usage across tenancies | *** --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/oracle-cloud-infrastructure-cloud-onboarding/oracle-cloud-infrastructure-oci-provider-permissions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.