Rule ID
SV-255618r961863_rule
Version
V1R2
CCIs
CCI-000366, CCI-001274
By immediately displaying an alarm message, potential security violations can be identified more quickly even when administrators are not logged into the network device. An example of a mechanism to facilitate this would be through the use of SNMP traps or a Syslog server where messages are sent to an SNMP console or Syslog server that is monitored by the CNDSP.
Verify a log destination is configured for a CNDSP or other mechanism that is monitored by security personnel. Obtain the IP address of a Syslog server monitored by the CNDSP. Review the device configuration. The following command shows the portion of the device configuration that includes the word "host": show run | inc host If the output does not display the "logging host" and "logging auditlog host" commands, or does not include the IP address of the Syslog server used by the CNDSP, this is a finding. The following command shows the logging policy: show log policy If Syslog logging is disabled, this is a finding.
Obtain the IP address of a Syslog server monitored by the CNDSP. The following command specifies a Syslog server to which to send event messages: logging host ipaddr [ipaddr...][port protocol-port] "ipaddr" is the IP address of the Syslog server. IP addresses can be entered for up to 10 remote logging Syslog servers. "protocolport" is the port number to which to send messages. Only one protocol port can be specified with the command. All servers must use the same port to listen for syslog messages. Since the Audit log is separate from the Event log, it must have its own target to write messages to: logging auditlog host [ipaddr | hostname][facility facility-name] "ipaddr | hostname" is the IP address or hostname of the server. "facility-name" is the name of a log facility.