11
Auditing Under Oracle Label Security

After you have edited the parameter file, restart the database instance to enable or disable d atabase auditing as specified.

Set the AUDIT_TRAIL parameter before you set audit options. If you do not set this parameter, you are still able to set audit options. However, audit records are not written to the database unt il the parameter is set and the database instance is restarted.

Enabling Oracle Label Security Auditing with SA_AUDIT_ADMIN

After you have enabled systemwide auditing, you can use SA_AUDIT_ADMIN procedures to enable or disable Oracle Label Security audi ting. To use Oracle Label Security auditing, you must have the policy_type role.

• Auditing Options for Oracle Label Security
• Enabling Oracle Label Security Auditing with SA_AUDIT_ADMIN.AUDIT
• Disabling Oracle Label Security Auditing with SA_AUDIT_ADMIN.NOAUDIT
• Examining Audit Option s with the DBA_SA_AUDIT_OPTIONS View

Auditing Options for Oracle Label Security

Enabling Oracle Label Security Auditing with SA_ AUDIT_ADMIN.AUDIT

Use the AUDIT procedure to enable policy-specific auditing.

Syntax:

P
ROCEDURE AUDIT (
     policy_name     IN VARCHAR2,
     users           IN VARCHAR2 DEFAU
LT NULL,
     option          IN VARCHAR2 DEFAULT NULL,
     type            IN VARCHAR2
DEFAULT NULL,
     success         IN VARCHAR2 DEFAULT NULL);

If the admini strator does not specify any audit options, then all options except the privilege-related ones are audited. Auditing of privileges mu st be specified explicitly. For example, if the administrator enters

SA_AUDIT_ADMIN.AUDIT (
'HR');

then default auditing options are set for the HR policy. W hen the administrator enables auditing, it will be performed on all users by session, whether successful or not.

When you set auditing parameters and options, the new values apply only to subsequent sessions, not to the curr ent session.

Consider also a case in which one AUDIT call (with no users specified) enables auditing for APPLY operations for all users, and then a second call enables auditing of REMOVE operations for a specific user. For e xample:

SA_AUDIT_ADMIN.AUDIT ('HR', NULL, 'APPLY');
SA_AUDIT_ADMIN.AU
DIT ('HR', 'SCOTT', 'REMOVE');

In this case, SCOTT is audited for both APPLY and REMOVE operations.

Disabling Oracle Label Security Auditing with SA_AUDIT_ADMIN.NOAUDIT

To disable policy-specific auditing, use the SA_AUDIT_ADMIN.NOAUDIT procedure.

Syntax:

PROCEDURE NOAUDIT (

     policy_name     IN VARCHAR2,
     users           IN VARCHAR2 DEFAULT NULL,

 option          IN VARCHAR2 DEFAULT NULL);

You can disable auditing for all enabl ed options, or only for a subset of enabled options. All auditing for the specified options is disabled for all specified users (or a ll users, if the users parameter is NULL). For example, the following statement disables auditing of the APPL Y and REMOVE operations for users John, Mary, and Scott:

SA_AUDIT_ADMIN.NOAUDIT ('HR', 'JOH
N, MARY, SCOTT', 'APPLY, REMOVE');

Consider also a case in which one AUDIT call enables auditing for a specific user, and a second call (with no user specified) enables auditing for all users. For e xample:

SA_AUDIT_ADMIN.AUDIT ('HR', 'SCOTT');
SA_AUDIT_ADMIN.AUDIT ('
HR');

In this case, a subsequent call to NOAUDIT with no users sp ecified (such as the following)

SA_AUDIT_ADMIN.NOAUDIT ('HR');

does not reverse the auditing that was set for SCOTT explicitly in the first call. Auditing t hus continues to be performed on SCOTT. In this way, even if NOAUDIT is set for all users, Oracle Label Security still audits any use rs for whom auditing was explicitly set.

Auditing of privileged operations must be specifie d explicitly. If you execute NOAUDIT with no options, Oracle Label Security will nonetheless continue to audit privileged operations. For example, if auditing is enabled and you enter

SA_AUDIT_ADMIN.NOAUDIT ('HR');

then auditing will continue to be performed on the privileged operations ( such as WRITEDOWN).

NOAUDIT parameters and options that you set apply only to subsequent se ssions, not to current sessions.

If you try to enable an audit option that has already been set, or if you try to disable an audit option that has not been set, Oracle Label Security processes the statement without indicatin g an error. An attempt to specify an invalid option results in an error message.