Oracle recommends that you audit your databases. See Auditing Specific Activities with Fine-Grained Auditing. You can create fine-grained audit policies that capture data such as the time an action occurred. See Auditing Activities with the Predefined Unified Audit Policies.Ĭreate fine-grained audit policies. Oracle Database provides three default unified audit policies that encompass the standard audit settings that most regulatory agencies require. Use one of the default unified audit policies. Auditing Activities with Unified Audit Policies and the AUDIT Statement describes how to accomplish this. You can create one or more unified audit policies that define all the audit settings that your database needs. Group audit settings into one unified audit policy. ![]() You can configure auditing by using any of the following methods: After you have associated the tablespace, you cannot modify it because partitioning is only supported on Enterprise Edition. You should perform this association before you generate any audit records for the unified audit trail. Be aware that for most Oracle Database editions except for Enterprise Edition, you can only associate the tablespace for unified auditing once. Oracle recommends that you configure a different tablespace for the unified audit trail. The audit records are stored in the SYSAUX tablespace by default. These records reside in the AUDSYS schema. All audit records are written to the unified audit trail in a uniform format and are made available through the UNIFIED_AUDIT_TRAIL view. In addition to auditing the standard activities the database provides, auditing can include activities from Oracle Database Real Application Security, Oracle Recovery Manager, Oracle Data Pump, Oracle Data Mining, Oracle Database Vault, Oracle Label Security, and Oracle SQL*Loader direct path events.Īuditing is enabled by default. In a multitenant environment, you can audit individual actions of the pluggable database (PDB) or individual actions in the entire multitenant container database (CDB). You can configure auditing for both successful and failed activities, and include or exclude specific users from the audit. You can base auditing on individual actions, such as the type of SQL statement executed, or on combinations of data that can include the user name, application, time, and so on. To audit this type of user, you can use a unified audit policy condition, a fine-grained audit policy, or Oracle Database Real Application Security. ![]() ![]() "Nondatabase users" refers to application users who are recognized in the database using the CLIENT_IDENTIFIER attribute. Auditing is the monitoring and recording of configured database actions, from both database users and nondatabase users.
0 Comments
Leave a Reply. |