Check ID:
Provider: Oracle Cloud (OCI)
Service:
Severity: HIGH
Categories:
Resource type:
identity_non_root_compartment_existsProvider: Oracle Cloud (OCI)
Service:
identitySeverity: HIGH
Categories:
identity-access, trust-boundariesResource type:
CompartmentWhat this check verifies
OCI tenancy includes at least one active non-root compartment. Only compartments below theroot level are considered, indicating that resources are organized outside the root scope.
Risk
Using only theroot compartment removes segmentation and forces broad tenancy-wide access. This endangers confidentiality and integrity through cross-project visibility, mis-scoped policies, and accidental changes with global impact, and can affect availability via bulk deletions or misconfigurations.
Recommendation
Create dedicated non-root compartments per workload, environment, or team; avoid placing resources in theroot compartment.
Apply granular policies at the compartment level to enforce least privilege and separation of duties. Use a clear hierarchy and tags, and review the design regularly as the tenancy evolves.
Remediation
- CLI
- Terraform
- Dashboard steps
oci iam compartment create —compartment-id <tenancy_ocid> —name <compartment_name> —description ‘<description>’
References
Where this check fires
This check runs on every scheduled scan against your Oracle Cloud (OCI) account. Findings appear at Cloud Security → Findings filterable byCheck ID = identity_non_root_compartment_exists. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to Oracle Cloud (OCI) checks