Details

Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.

In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as router components, modules, device identifiers, node names, and functionality.

Associating information about where the event occurred within the network provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured router.

Solution

Configure the router to log events containing information to establish where the events occurred as shown in the example below.

[edit system syslog]
set file LOG_FILE any any

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Juniper_Router_Y21M02_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Juniper.

References

• 800-53|AU-3
• CAT|II
• CCI|CCI-000132
• Rule-ID|SV-217026r639663_rule
• STIG-ID|JUNI-RT-000210
• STIG-Legacy|SV-101047
• STIG-Legacy|V-90837
• Vuln-ID|V-217026

Source

• Tenable.com/audits