Audit Sys Logins (Doc ID 462564.1)

Last updated on OCTOBER 13, 2016

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4
Information in this document applies to any platform.

Goal

Setting AUDIT_SYS_OPERATIONS = TRUE to audit SYS user actions.

The documentation
http://download.oracle.com/docs/cd/B19306_01/network.102/b14266/cfgaudit.htm#i1008977
.
says that the TERMINAL should be written to the OS audit files as well (regardless the type of connection).
.
But while testing the same it is found only bequeath connections on both Linux and Windows are showing the TERMINAL whereas the connections through the listener are not showing the TERMINAL.
.

EXAMPLE:

1) connect via the listener to the database as sysdba ( Windows). The following audit entry is produced within the Event Viewer:

Audit trail:
ACTION : 'CONNECT'
DATABASE USER: 'SYS'
PRIVILEGE : SYSDBA
CLIENT USER: <--------------------------------Missing
CLIENT TERMINAL: UNKNOWN
STATUS: 0

2) Use bequeath connection as sysdba ( Windows). The following audit entry is produced within the Event Viewer:

Audit trail:
ACTION : 'CONNECT'
DATABASE USER: 'sys'
PRIVILEGE : SYSDBA
CLIENT USER: PVELUSAM-IN\PVELUSAM
CLIENT TERMINAL: PVELUSAM-IN 
STATUS: 0 .

3) connect via the listener to the database as sysdba ( Linux). The following audit entry is produced within the OS audit file:

ACTION : 'CONNECT'
DATABASE USER: 'SYS'
PRIVILEGE : SYSDBA
CLIENT USER: <---------------------------------------------------Missing
CLIENT TERMINAL: UNKNOWN
STATUS: 0

4) Use bequeath connection as sysdba ( Linux ). The following audit entry is produced within the OS audit file:

ACTION : 'CONNECT'
DATABASE USER: '/'
PRIVILEGE : SYSDBA
CLIENT USER: oracle
CLIENT TERMINAL: pts/2
STATUS: 0


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms