Ensure IP-Based Filtering with WAF for SaaS is Enforced

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

1. Review Service Request (SR) records with Oracle SaaS Operations to confirm that IP-based filtering has been enabled. 2. Verify that the allowlist includes only approved public IP addresses or CIDR ranges corresponding to trusted networks. 3. Ensure no overly broad ranges, such as 0.0.0.0/0, are permitted. 4. Optionally log a Service Request with Oracle SaaS Operations to confirm the current WAF policy configuration. 5. Test connectivity from both an allowed and a disallowed IP address to confirm enforcement.

How it is fixed

Fix method: Guidance or infrastructure patch

1. Submit a Service Request to Oracle SaaS Operations requesting IP-based filtering to be enabled for the Fusion environment. 2. Provide Oracle with a list of approved IP addresses or CIDR ranges representing trusted enterprise or VPN networks. 3. Review and approve Oracle's implementation of the filtering policy. 4. Remove any unnecessary or overly broad ranges. 5. Validate enforcement by testing API and UI access from both allowed and disallowed IP addresses. 6. Document exceptions if temporary external access is required.