TMA-ORACLE-SAAS-3.2
Ensure EPM Audit Data is Exported and Centrally Stored
Description
EPM Cloud Applications generate audit data that records user sign-ins, administrative actions, and configuration changes. This audit data should be exported regularly from the EPM environment to ensure it is retained outside of the application. Audit data retained only inside EPM is limited by default retention policies and is vulnerable to loss or deletion. Exporting ensures durability and independence, while forwarding into OCI Logging Analytics or a SIEM ... 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. Confirm that EPM audit data exports are scheduled and active. 2. Verify that audit data files contain expected details, such as user ID, login time, IP address, and executed functions. 3. Check that exported data is securely stored in an external location, like Object Storage.
How it is fixed
Fix method: Guidance or infrastructure patch
Configure automated export of EPM audit data (for example, with EPM Automate Access Log downloads). Store exported files securely outside the transactional environment. Test and validate that exports and any forwarding pipelines complete successfully, without data loss.
Properties
- Operating systems
- Any
- Tags
- oracle-saaslogging
- Reference
- CIS Oracle SaaS Cloud Applications Benchmark v1.0.0 - 3.2 Ensure EPM Audit Data is Exported and Centrally Stored