TMA-ORACLE-SAAS-2.5
Ensure Geolocation Filtering with WAF for SaaS is enforced
Description
Geolocation filtering in WAF for Oracle Fusion Applications restricts access based on the source country or region of incoming requests. WAF policies can be configured to allow or block traffic from selected geographies, helping organizations limit access to regions where legitimate users are located. Restricting access to only the countries or regions where the organization operates reduces unnecessary exposure to malicious traffic. Reported as a manual review item: these Fusion/EPM/OCI IAM settings are reviewed in the Oracle SaaS and OCI consoles or reports.
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 geolocation filtering has been enabled. 2. Verify the countries or regions included in the allow or block lists match organizational requirements. 3. Optionally log a new Service Request with Oracle SaaS Operations to confirm the current WAF policy configuration. 4. Validate functionality by attempting access from at least one blocked country and confirming that requests are denied.
How it is fixed
Fix method: Guidance or infrastructure patch
1. Submit a Service Request to Oracle SaaS Operations requesting geolocation filtering to be enabled for the Fusion environment. 2. Provide Oracle with the list of countries or regions that should be allowed or blocked. 3. After configuration by Oracle, confirm that the rules are applied and enforced. 4. Test by accessing Fusion from both allowed and blocked regions to ensure expected behavior. 5. Document exceptions if broader access must remain temporarily enabled.
Properties
- Operating systems
- Any
- Tags
- oracle-saasnetwork
- Reference
- CIS Oracle SaaS Cloud Applications Benchmark v1.0.0 - 2.5 Ensure Geolocation Filtering with WAF for SaaS is enforced