23 Monitoring Oracle Database Vault

About Monitoring Security Violation Attempts

You can check for security violations, such as realm or command rule violations. This feature displays data such as the user name of the person committing the violation, the action they committed, and a time stamp of the activity.

Before you can view these events, if you have not migrated your database to unified auditing, then you must ensure that the AUDIT_TRAIL initialization parameter is set to DB or DB, EXTENDED. If you have migrated your database to use unified auditing, then you do not need to configure any additional settings. You are ready to check for security violations.

Using Oracle Database Vault Administrator to Monitor Security Violations

A user who has been granted the appropriate role can use Oracle Database Vault Administrator to monitor security violations.

1. From Cloud Control, log into Oracle Database Vault Administrator as a user who has been granted the DV_OWNER, DV_ADMIN, DV_MONITOR, or DV_SECANALYST role.

   "Logging into Oracle Database Vault" explains how to log in.

2. In the Home page, under Reports, select Attempted Violations.

3. In the Attempted Violations Report page, set the period of time and other filter settings to define the data that you want to capture, and then click Go.

   The report appears, similar to the following page:

   
   Description of the illustration security_violation_attempts.gif
   
   

4. To exit, click OK.

About Monitoring Security Policy Changes

The Database Vault Policy Change Report in Oracle Database Vault Administrator enables you to track changes that have been made to security settings.

You can check the number of policy changes for the categories in the following list. These categories reflect changes to the database security policy (that is, its configuration) in any given environment. If something changes that is security related, you can use the chart and tables to drill down to find unexpected changes that should be investigated.

Before you can view these events, if you have not migrated your database to unified auditing, then you must ensure that the AUDIT_TRAIL initialization parameter is set to DB or DB, EXTENDED. If you have migrated your database to use unified auditing, you do not need to configure any additional settings. You are ready to check for changes to Database Vault policies.

• Database Vault policy: Shows changes made through the Oracle Database Vault administrative packages or user interface, indicating Oracle Database Vault configuration or policy changes.

• Label Security policy: Shows changes made through the Oracle Database Vault administrative packages or user interface, indicating Oracle Label Security policy or privilege changes.

• Audit Policy: Shows changes to the database audit policy coming from AUDIT or NOAUDIT statements.

• Privilege Grants: Shows changes to system or object privilege GRANT statements.

• Privilege Revokes: Shows changes to system or object privilege REVOKE statements.

• Database Account: Shows changes to CREATE USER, ALTER USER, or DROP USER statements.

• Database Role: Shows changes to CREATE ROLE, ALTER ROLE, or DROP ROLE statements.

Using Oracle Database Vault to Monitor Security Policy Changes by Category

A user who has been granted the appropriate role can use Oracle Database Vault Administrator to monitor security policy changes by category.

1. From Cloud Control, log into Oracle Database Vault Administrator as a user who has been granted the DV_OWNER, DV_ADMIN, DV_MONITOR, or DV_SECANALYST role.

   "Logging into Oracle Database Vault" explains how to log on.

2. In the Home page, under Reports, select Database Vault Policy Changes.

3. In the Attempted Violations Report page, set the period of time and other filter settings to define the data that you want to capture, and then click Go.

   The report appears, similar to the following page:

   
   Description of the illustration sec_policy_changes_detail.gif
   
   

4. To exit, click OK.