OCI Autonomous Database (shared) network exposure is evaluated: instances are treated as restricted when using a VCN private endpoint or when ACLs allow only specified IPs/VCNs. It identifies configurations with no ACL and no VCN, or ACLs permitting 0.0.0.0/0.
Risk
With open access, attackers can probe endpoints, brute-force credentials, or abuse leaked wallets to connect.
Impact:
- Confidentiality: unauthorized queries and data exfiltration
- Integrity: malicious changes
- Availability: heavy queries or scans causing service disruption
prowler oraclecloud --checks database_autonomous_database_access_restricted
Recommendation
Prefer VCN private endpoints to eliminate internet exposure. If public access is required, enforce least privilege by limiting ACLs to specific CIDRs or VCNs; never use 0.0.0.0/0.
Add defense in depth with NSGs and private connectivity (VPN/peering), monitor access, and rotate client wallets regularly.
Remediation
oci db autonomous-database update --autonomous-database-id <adb-ocid> --is-access-control-enabled true --whitelisted-ips '["<ALLOWED_IP_OR_CIDR>"]'
- In OCI Console, go to Autonomous Database and select the instance
- Click More Actions > Update
- Under Network Access, enable Access control list (ACL)
- Add an allowed IP/CIDR (exclude 0.0.0.0/0) and remove any 0.0.0.0/0 entry
- Click Save
Source Code
Resource Type
AutonomousDatabase