V-255275

Discussion

It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. The HPE 3PAR OS will send an SNMP trap event on any failure of audit components (failure to write a record, failure to send to remote syslog server, etc.). All of these conditions are automatically recovered Q20 in the short term. Configuration of the SNMP consumer is required to facilitate collection of these events.

Check Content

Verify an SNMPv3 user account is configured:
cli%  showsnmpuser

Username                        | AuthProtocol    | PrivProtocol
3parsnmpuser                | HMAC SHA 96   |   CFB128 AES 128

If the output is not displayed in the above format, this is a finding.

Identify the SNMP trap recipient and report SNMP configuration:

cli%  showsnmpmgr

  HostIP                                            | Port  | SNMPVersion  | User
 <snmp trap recipient IP>        | 162    | 3                            | 3parsnmpuser

If the SNMP trap recipient IP address is incorrect, this is a finding.

If the SNMP port is not "162", this is a finding.

If the SNMP version is not "3", this is a finding.

If the SNMP user ID is incorrect, this is a finding.

Generate a test trap:
cli%  checksnmp

Trap sent to the following managers:
< IP address of trap recipient>

If the response does not indicate a trap was successfully sent, this is a finding.