Oracle Analytics Cloud endpoints are evaluated for network exposure. Public endpoints must use restricted allowlists of specific IPs/CIDRs; presence of 0.0.0.0/0 or no allowed sources indicates unrestricted access. Instances using a VCN/private endpoint or public endpoints limited to specific sources align with the intended exposure model.
Risk
Unrestricted OAC endpoints allow Internet-wide access to the login surface, enabling credential stuffing and brute force. Account takeover can expose reports and data sources (confidentiality), permit dashboard/model changes (integrity), and support lateral movement into connected systems.
prowler oraclecloud --checks analytics_instance_access_restricted
Recommendation
Prefer private deployment in a VCN and apply least privilege network access. If public is required, enforce allowlists to specific IPs/CIDRs and never include 0.0.0.0/0. Use private access channels/service gateways, require MFA/SSO, and apply defense in depth (WAF, audit monitoring) to reduce exposure.
Remediation
- In OCI Console, go to Analytics & AI > Analytics Cloud and select your instance
- On Instance Details, under Network Access, click Edit next to Access Control
- Remove any 0.0.0.0/0 entry (if present)
- Add an access rule with the specific allowed public IP or CIDR
- Click Save
Source Code
Resource Type
AnalyticsInstance
References
- https://docs.public.content.oci.oraclecloud.com/en-us/iaas/analytics-cloud/doc/public-endpoints-and-access-control-rules.html
- https://docs.oracle.com/en/cloud/paas/analytics-cloud/acsds/connect-databases-deployed-public-ip-address.html
- https://docs.oracle.com/en/cloud/paas/analytics-cloud/acoci/top-faqs-public-or-private-endpoint-security.html
- https://docs.oracle.com/en/cloud/paas/analytics-cloud/acoci/manage-ingress-access-rules-public-endpoint-using-console.html
- https://docs.oracle.com/en-us/iaas/analytics-cloud/doc/public-endpoints-and-access-control-rules.html