Manpages - audispd-zos-remote.8

To enable ITSD to process Remote Audit requests, the user ID associated with ITDS must be granted READ access to the IRR.AUDITX FACILITY Class profile (the profile used to protect the R_Auditx service). This user ID can usually be found in the STARTED Class profile for the ITDS started procedure. If the identity associated with ITDS is ITDSUSER, the administrator can configure RACF to grant Remote Auditing processing to ITDS with the following TSO commands:

• TSO Commands: Grant ITDSUSER READ access to IRR.AUDITX FACILITY Class profile ::

  rdefine FACILITY IRR.RAUDITX uacc(none)
  permit IRR.RAUDITX class(FACILITY) id(ITDSUSER) access(READ)

A z/OS RACF user ID is needed by the plugin - Every Audit request performed by the plugin will use a RACF user ID, as configured in the plugin configuration *zos-remote.conf*(5). This user ID needs READ access to FACILITY Class resource IRR.LDAP.REMOTE.AUDIT. If the user ID is BINDUSER, the administrator can configure RACF to enable this user to perform Remote Auditing requests with the following TSO commands:

TSO Commands: Enable BINDUSER to perform Remote Audit requests

  rdefine FACILITY IRR.LDAP.REMOTE.AUDIT uacc(none)
  permit IRR.LDAP.REMOTE.AUDIT class(FACILITY) id(BINDUSER) access(READ)

When performing remote auditing requests, the audispd-zos-remote plugin will use the special @LINUX CDT Class and the audit record type (eg.: SYSCALL, AVC, PATH…) as the CDT Resource Class for all events processed. To make sure events are logged, the RACF server must be configured with a Dynamic CDT Class named @LINUX with correct sizes and attributes. The following TSO commands can be used to add this class:

TSO Commands: Add @LINUX CDT Class

  rdefine cdt @LINUX cdtinfo(posit(493) FIRST(alpha,national,numeric,special) OTHER(alpha,national,numeric,special) RACLIST(REQUIRED) case(asis) generic(allowed) defaultuacc(none) maxlength(246))
  setr classact(cdt)
  setr raclist(cdt)
  setr raclist(cdt) refresh
  setr classact(@LINUX)
  setr raclist(@LINUX)
  setr generic(@LINUX)

Once the CDT Class has been defined, you can add profiles to it, specifying resources (wildcards allowed) to log or ignore. The following are examples:

• TSO Commands: Log only AVC records (One generic and one discrete profile): ::

  rdefine @LINUX * uacc(none) audit(none(read)) 
  rdefine @LINUX AVC uacc(none) audit(all(read)) 
  setr raclist(@LINUX) refresh

TSO Commands: Log everything (One generic profile):

  rdefine @LINUX * uacc(none) audit(all(read))
  setr raclist(@LINUX) refresh

Resources always match the single profile with the best match.

There are many other ways to define logging in RACF. Please refer to the server documentation for more details.

The Linux event serial number, encoded in network-byte order hexadecimal representation. Records within the same Event share the same Link Value.

Always zero (0) - False

Always two (2) - Authorization event

Zero (0) - Success, if the event reported success=yes or res=success, Three (3) - Fail, if the event reported success=no or res=failed, or One (1) - Info otherwise.

Always @LINUX

The Linux record type for the processed record. e.g.: SYSCALL,/AVC/,/PATH/,/CWD/ etc.

Textual message bringing the RACF user ID used to perform the request, plus the Linux hostname and the record type for the first record in the processed event. e.g.: Remote audit request from RACFUSER. Linux (hostname.localdomain):USER_AUTH

Also known as relocates, this list will bring all the field names and values in a fieldname=value format, as a type 114 (Application specific Data) relocate. The plug-in will try to interpret those fields (i.e.: use human-readable username root instead of numeric userid 0) whenever possible. Currently, this plugin will also add a relocate type 113 (Date And Time Security Event Occurred) with the Event Timestamp in the format as returned by *ctime*(3).