|Finding ID||Version||Rule ID||IA Controls||Severity|
|Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Using a syslog logging target, the MQ Appliance logs all audit events, including account creations, modifications, disabling, and termination events. Logging may be set to the following logging levels in descending order of criticality: debug, info, notice, warn, error, alert, emerg. The default is notice. Audit records can be generated from various components within the MQ Appliance network device (e.g., module or policy filter).|
|IBM MQ Appliance v9.0 NDM Security Technical Implementation Guide||2017-06-06|
|Check Text ( C-74863r1_chk )|
| Log on to the MQ Appliance CLI as a privileged user. |
show logging target
All configured logging targets will be displayed. Verify:
- This list includes a remote syslog notification target; and
- It includes all desired log event source and log level parameters, e.g., event audit info.
In the WebGUI, Manage Appliance/User access. Create, disable or modify an account. Verify the administrator receives notification of this event.
If any is not true, this is a finding.
|Fix Text (F-81627r1_fix)|
| Configure a syslog target by using the command line interface (CLI). Log on as an administrative user. |
To enter global configuration mode, enter "config".
To create a syslog target, enter:
event audit info
event auth notice
event mgmt notice
event cli notice
event user notice
event system error
It is the responsibility of the sysadmin to configure the triggers necessary to send alerts based upon information received at the syslog server. To meet the current requirement, the sysadmin should trigger notification upon receiving the following audit events: 0x8240001f and 0x810001f0. All account creations, modifications, disabling, and termination events fall into this event category.