Check ID:
Provider: Oracle Cloud (OCI)
Service:
Severity: HIGH
Categories:
Resource type:
compute_instance_legacy_metadata_endpoint_disabledProvider: Oracle Cloud (OCI)
Service:
computeSeverity: HIGH
Categories:
secrets, identity-accessResource type:
InstanceWhat this check verifies
OCI compute instance metadata service is configured so legacy IMDS v1 endpoints are disabled, requiring session-authorized IMDS v2 requests for metadata accessRisk
Enabled IMDS v1 permits unauthenticated metadata reads via local access or SSRF, compromising confidentiality of instance credentials, SSH keys, and custom data. Stolen tokens enable cloud API abuse, driving privilege escalation, lateral movement, and unauthorized changes that impact integrity.Recommendation
Disable IMDS v1 and require IMDS v2 across all instances. Migrate applications to session-authorized requests and confirm image support. Enforce least privilege for instance principals, restrict untrusted processes from reaching169.254.169.254, and monitor metadata access to provide defense in depth.
Remediation
- CLI
- Terraform
- Dashboard steps
References
- https://docs.oracle.com/en-us/iaas/Content/Compute/Tasks/gettingmetadata.htm
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/oci/OCI-Compute/enforce-imds-v2.html
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 = compute_instance_legacy_metadata_endpoint_disabled. 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