Integration Cloud instance uses a private endpoint or a public endpoint with IP or VCN allowlists
integration_instance_access_restricted
Oracle Integration Cloud instances are evaluated for network endpoint restrictions, confirming access is limited to approved IPs or VCNs. Configurations with 0.0.0.0/0, missing endpoint details, or PUBLIC endpoints without allowlists are identified; PRIVATE endpoints or PUBLIC endpoints with IP/VCN allowlists indicate restricted access.
Risk
Unrestricted OIC endpoints expose integration APIs and consoles to the Internet, enabling credential brute force, token theft, and unauthorized invocations. Attackers can exfiltrate data, alter workflows, and pivot into connected backends, impacting confidentiality and integrity, and causing availability issues via abuse or DoS.
prowler oraclecloud --checks integration_instance_access_restricted
Recommendation
Prefer PRIVATE endpoints and restrict access to specific VCNs. If PUBLIC is required, enforce strict IP allowlists-never 0.0.0.0/0. Apply least privilege at network layers, place OIC behind WAF/VPN, segment with security lists, and monitor access logs. Review allowlists regularly as part of defense in depth.
Remediation
oci integration integration-instance update --integration-instance-id <example_resource_id> --network-endpoint-details '{"networkEndpointType":"PUBLIC","allowlistedHttpIps":["<ALLOWED_CIDR>"]}'
- In the OCI Console, go to Developer Services > Integration > Integration instances
- Open <example_resource_name> and click Edit
- If using Public endpoint: add an entry under Allowed IPs (e.g., <ALLOWED_CIDR>) and remove any 0.0.0.0/0
- Alternatively, switch to Private endpoint if desired and select the required VCN/subnet
- Click Save
Source Code
Resource Type
IntegrationInstance