The Juniper router must be configured to generate log records for a locally developed list of auditable events.

Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or 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 verify that it is compliant with this requirement. The example below illustrates how selected events can be logged.

syslog { file LOG_FILE { authorization info; any info; change-log info; } }

Note: A syslog server can be configured in lieu of logging to a file as shown in the example below.

system { syslog { host x.x.x.x { authorization info; any info; change-log info; } }

If the router is not configured to generate log records for a locally developed list of auditable events, this is a finding.

Configure the router to generate log records for a locally developed list of auditable events as shown in the example below.

[edit system] set syslog file LOG_FILE authorization info set syslog file LOG_FILE any info set syslog file LOG_FILE change-log info

Note: A syslog server can be configured in lieu of logging to a file as shown in the example below.

set syslog host x.x.x.x authorization info set syslog host x.x.x.x any info set syslog host x.x.x.x change-log info