Configuring event logging

In standard operations, these log messages are written to files where they can be viewed either directly by using a text editor, by system tools, or IBM Safer Payments itself. Log messages are needed because users typically do not have access to the IBM Safer Payments server.

IBM Safer Payments contains a fully configurable event logging engine that supports three types of logging targets. The system and audit logs are IBM Safer Payments logs. That is, IBM Safer Payments has built-in viewer facilities to read these log messages.

System log

The system log informs about events relevant to technical operations of IBM Safer Payments.

Audit log

The audit log traces relevant user activities.

Operating system logs

Operating system logs are sent to the operating system. In Linux® operating systems such as RHEL, IBM Safer Payments feeds operating system log messages to the local syslogd as IRIS_n, where n is the ID of the IBM Safer Payments instance as defined by the command-line parameter. Operating system logging is mandatory in PCI DSS-compliant environments to facilitate centralized logging, and must be activated by selecting the Enable operating system logging checkbox in the system configuration.

Make sure that all PCI DSS relevant log messages are forwarded to centralized logging as described in Changing log message settings.