STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Juniper Router RTR Security Technical Implementation Guide

V-217026

CAT II (Medium)

The Juniper router must be configured to produce audit records containing information to establish where the events occurred.

Rule ID

SV-217026r604135_rule

STIG

Juniper Router RTR Security Technical Implementation Guide

Version

V3R2

CCIs

CCI-000132

Discussion

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.

Check Content

Review the router configuration to verify that events are logged containing information to establish where the events occurred as shown in the example below.

system {
    host-name XYZ;
    …
    …
    …
    }
    syslog {
        file LOG_FILE {
            any any;
        }
    }
}

If the router is not configured to produce audit records containing information to establish to establish where the events occurred, this is a finding.

Fix Text

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