HP-UX System Administrator's Guide: Security Management HP-UX 11i v3 (B3921-90020, September 2010)

Table Of Contents
1. Create an entry (or entries) in the PAM configuration file (/etc/pam.conf)
including the keystroke library as a session module:
login session optional libpam_keystroke.so.1
dtlogin session optional libpam_keystroke.so.1
sshd session optional libpam_keystroke.so.1
rcomds session optional libpam_keystroke.so.1
OTHER session optional libpam_keystroke.so.1
Note that this module may be configured for one or more services, depending on
the intended effect of the logging. For more information on pam.conf and the
syntax of the entries, see pam.conf(4).
2. Enable keystroke logging in /etc/rbac/rbac.conf:
KEY_STROKE_LOGGING = 1
3. Create a keyfilter file under /etc/rbac specifying what users to log. For more
information on customizing specific policies, see key_filter(4m).
Once these steps are completed, subsequent access by the targeted users will cause a
keystroke log file to be generated and stored in the location specified in
/etc/rbac/rbac.conf file. Note that in the event that a user has privileged access
to this location (for example, they are granted a root shell), they may be able to modify
these files. In this situation, HP recommends that modification of the files be monitored
(for example, by HP-UX Host IDS) or that they periodically be transferred off-host.
NOTE: The keystroke logging feature does not currently work with Secure Shell (SSH)
login.
8.6.4.2 Alternate Logging
The alternate logging feature enables you to log access control events and RBAC-invoked
commands. It is no longer necessary to enable HP-UX auditing to generate RBAC logs.
An administrator can enable RBAC logging and specify the location of the alternate
logging files simply by editing the /etc/rbac/rbac.conf file. For more information
on the specific keyword/value pairs, see rbac_conf(4m).
Alternate logging works in an identical fashion to the audit logging and may be
configured using the /etc/rbac/aud_filter file. The traditional RBAC audit log
generation continues to work. If both auditing and logging are enabled, two sets of
logs will be generated.
8.7 Troubleshooting HP-UX RBAC
The following is a list of the primary mechanisms used to troubleshoot and debug
HP-UX RBAC:
The rbacdbchk utility verifies HP-UX RBAC database syntax.
The privrun -v command reports additional and relevant information.
162 HP-UX Role-Based Access Control