TMA-ORACLE-SAAS-2.1
Ensure Network Perimeters are Configured in IAM or the Identity Provider
Description
Network Perimeters restrict where users can sign in to Oracle SaaS applications by enforcing trusted IP ranges or network sources. For upgraded environments, this is configured natively in Oracle Identity Domains. Restricting access to approved IPs or network locations at the identity layer reduces the risk of compromised credentials being used from untrusted or malicious networks. 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. For upgraded environments: Sign in to the Oracle Cloud Console. Navigate to Identity & Security, Domains, Security, Network Perimeters. Verify that at least one Network Perimeter is defined with authorized IP ranges and attached to sign-on policies. 2. For non-upgraded environments: Review conditional access or equivalent policies in the IdP. Confirm that rules are applied to restrict authentication attempts to approved IP ranges or network locations.
How it is fixed
Fix method: Guidance or infrastructure patch
1. Upgraded environments (OCI IAM): Go to Identity & Security, Domains, Security, Network Perimeters. Create a perimeter with approved IP ranges. Attach the perimeter to sign-on policies. 2. Non-upgraded environments (external IdP): Configure conditional access rules in the IdP (Azure AD, Okta, etc.). Define approved IP ranges or geolocation-based conditions. Apply these rules to authentication policies used by Oracle SaaS.
Properties
- Operating systems
- Any
- Tags
- oracle-saasnetwork
- Reference
- CIS Oracle SaaS Cloud Applications Benchmark v1.0.0 - 2.1 Ensure Network Perimeters are Configured in IAM or the Identity Provider