Changes to configuration options must be audited.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
---|---|---|---|---|---|---|
medium | V-219868 | SRG-APP-000516-DB-000363 | O121-BP-025800 | SV-219868r1018568_rule | 2025-02-12 | 3 |
Description |
---|
When standard auditing is in use, the AUDIT_SYS_OPERATIONS parameter is used to enable auditing of actions taken by the user SYS. The SYS user account is a shared account by definition and holds all privileges in the Oracle database. It is the account accessed by users connecting to the database with SYSDBA or SYSOPER privileges. |
ℹ️ Check |
---|
For Unified or mixed auditing, from SQL*Plus: Select count(*) from audit_unified_enabled_policies where entity_name = 'SYS'; If the count is less than one row, this is a finding. For Standard auditing, from SQL*Plus: Select value from v$parameter where name = 'audit_sys_operations'; If the value returned is FALSE, this is a finding. |
✔️ Fix |
---|
For Standard auditing, from SQL*Plus: alter system set audit_sys_operations = TRUE scope = spfile; The above SQL*Plus command will set the parameter to take effect at next system startup. If Unified Auditing is used: To ensure auditable events are captured: Link the oracle binary with uniaud_on, and then restart the database. Oracle Database Upgrade Guide describes how to enable unified auditing. For additional information on creating audit policies, refer to the Oracle Database Security Guide http://docs.oracle.com/database/121/DBSEG/audit_config.htm#CHDGBAAC |