XYGATE Merged Audit Reference Manual

XYGATE Merged Audit
®
Reference Manual
Appendix G: Data Mapping
XYPRO Technology Corporation 248 Proprietary and Confidential
BASE24 Note 4
When the OBJECTTYPE = USER and the OPERATION = CHANGE, it represents a
change to the SEC file. For each field changed in the SEC record, the before and after
images are formatted:
<File Name> (Screen Number): <before value(s)> "to" <after value(s)>
Example: APCF Screen Access(2): RADU-NNNN to RADU-YYYY
In this Example, permissions [R(ead), A(lter), D(elete), U(update)] for screen 2 of the
APCF application for the BASE24 USERID defined in the SUBJECTLOGIN column
were changed from NNNN to YYYY.
Note: For USER ADDs or DELETEs, the RESULT will be blank.
When the OBJECTYPE = FILE, the RESULT will be blank.
BASE24 Note 5
In BASE24-atm Release 6.0, Version 7 and BASE24-es Release 1.0, Version 09.2
there has been a change to the OMF header record to include an outcome for LOGON
attempts. The field is at offset 51 of the OMF data definition.
OMF Field AUDIT.OUTCOME AUDIT.MESSAGECODE
T 1 Success T
F 3 Failure F
" " (blank)
4 Unknown
" " (blank)
BASE24 Audit Session Table
Column Type Record Contents
PARTITIONKEY See General Note 1, pg 240.
numeric 4 MOVER Generated
RECORDSESSIONKEY timestamp MOVER Generated
RECORDINSTALLKEY timestamp MOVER Generated
SESSIONID char 36 Timestamp + TERM-ID
FOUNDSESSIONSTART char 1
FOUNDSESSIONEND char 1
SESSIONNAME varchar 40
PROCESSTHREADID varchar 50
PROCESSTHREADID2 varchar 50
CLIENTPROGRAM varchar 50
ANCESTORPROCESSTHREADID varchar 50
IPADDRV46 char 46
DNSNAME varchar 100
CLIENTCURRDIR varchar 200