From Cisco IOS XE Release 3 NDM Security Technical Implementation Guide
Part of SRG-APP-000516-NDM-000334
Associated with: CCI-000366
Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack; to recognize resource utilization or capacity thresholds; or to identify an improperly configured network device. If auditing is not comprehensive, it will not be useful for intrusion monitoring, security investigations, and forensic analysis.
Review the router configuration to determine if it is in compliance with this requirement. The configuration should look similar to the example below. logging buffered nnnn informational logging console informational logging trap warning logging host x.x.x.x Note: Severity levels can be set to operational requirements. Informational is the default severity level; hence, if the severity level is configured to informational, the “logging trap” command will not be shown in the configuration. If the router is not configured to generate audit log events for a locally developed list of auditable events, this is a finding.
Configure the router to send logs to the console, buffer, and syslog server as shown in the example below. logging buffered nnnn informational logging console informational logging trap warning logging host x.x.x.x Note: Severity levels can be set to operational requirements.
Lavender hyperlinks in small type off to the right (of CSS
class id, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle or
Accept: application/rdf+xml.
Powered by sagemincer