XYGATE
®
Data Protection
™
Reference Manual
Chapter 6. XDP Auditing and Audit Reports
XYPRO Technology Corporation
32
Proprietary and Confidential
Syntax: Auditing to a diskfile
AUDIT <filename> [EXT(pri,sec,max)] [NO_ROLL_MSGS]
The following Example will send XDP audits to the file called XDPAUDIT in the
subvolume $SECURE.XDPAUDIT.
Example 1: How to configure XDP to audit to a diskfile
AUDIT $SECURE.XDPAUDIT.XDPAUDIT
Refer to the
keyword in Appendix A3:, on page 67 for more
examples.
6.1.3
Process Audit Trails
Any one of the nine available AUDIT positions can be defined as a process audit trail.
The most common process audits are EMS and printing to the CONSOLE.
Syntax: Auditing to EMS
AUDIT $<process-name> [CONSOLEPRINT] [EMS]
The following Example will send XDP audits to the $0 EMS collector and the console.
Example 1: How to configure XDP to audit to EMS and the CONSOLE
AUDIT $0 EMS CONSOLEPRINT
Refer to the
AUDIT (Process Name or Device)
in Appendix A4:, on page 68 for more
examples.
6.1.4
IP Audit Trails
Any one of the nine available AUDIT positions can be defined as an IP address. This
section deals with the IP address form of the AUDIT specification.
Note:
There is no error checking available on an IP port write. In order to facilitate the
detection of missing records, a sequence number is present in the DETAIL
(XDP-C) record that begins with 1 at the start of each new XDP session (each
invocation of an XDP process control command) and increments for each
process manipulated.
Syntax: Auditing to an IP address
The following Example configures XDP to audit to an IP address.
Example 1:
AUDIT $zipv4 IP 172.16.1.12:514 SYSLOG_PREFIX "<134>DP " SYSLOG_CRITICAL_
PREFIX "<130>DP_CR "
Refer to the
keyword in Appendix A5:, on page 69 for more
examples.
Summary of Contents for Trinitron WEGA KV-DZ29M91
Page 2: ......