Changes to configuration options must be audited.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-270540 | SRG-APP-000516-DB-000363 | O19C-00-011300 | SV-270540r1064898_rule | 2025-02-14 | 1 |
| 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: https://docs.oracle.com/en/database/oracle/oracle-database/19/dbseg/configuring-audit-policies.html |