The Juniper router must be configured to generate log records for privileged activities.

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.

Audit records can be generated from various components within the network device (e.g., module or policy filter).

Review the router configuration to verify that it is compliant with this requirement as shown in the example configurations below.

syslog { file LOG_FILE { change-log info; interactive-commands info; } }

Note: The parameter "any" can be in place of "change-log" and “interactive-commands” as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below.

system { syslog { host x.x.x.x { any info; } }

If the router is not configured to generate log records for privileged activities, this is a finding.

Configure the router to generate log records for privileged activities as shown in the example below.

[edit system] set syslog file LOG_FILE change-log info set syslog file LOG_FILE interactive-commands info

Note: The parameter "any" can be in place of "change-log" and “interactive-commands” as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below.

set syslog host x.x.x.x any info