STIGQter: STIG Summary: Juniper EX Series Switches Network Device Management Security Technical Implementation Guide Version: 2 Release: 5 Benchmark Date: 01 Jul 2026:

The Juniper device must be configured to produce audit log records containing sufficient information to establish what type of event occurred.

DISA Rule

SV-253889r960891_rule

Vulnerability Number

V-253889

Group Title

SRG-APP-000095-NDM-000225

Rule Version

JUEX-NM-000120

Severity

CAT II

CCI(s)

• CCI-000130 - Ensure that audit records containing information that establishes what type of event occurred.

Weight

10

Fix Recommendation

Configure the network device to produce audit log records containing sufficient information to establish what type of event occurred.

set system syslog host <syslog IPv4 or IPv6 address> any info
set system syslog host <syslog IPv4 or IPv6 address> structured-data <<< Includes the 'explicit-priority' and 'time-format year millisecond' directives
set system syslog file <file name> any info
set system syslog file <file name> structured-data <<< Includes the 'explicit-priority' and 'time-format year millisecond' directives
-or-
set system syslog host <syslog IPv4 or IPv6 address> any info
set system syslog host <syslog IPv4 or IPv6 address> explicit-priority <<< Only if log level and severity are required
set system syslog file <file name> any info
set system syslog file <file name> explicit-priority <<< Only if log level and severity are required
set system syslog time-format year

Check Contents

Determine if the network device produces audit log records containing sufficient information to establish what type of event occurred.

Junos standard event log messages are configurable for time format, inclusion of logging facility and severity levels, and format. Setting "structured-data" automatically includes "explicit-priority" and "time-format year millisecond". Verify logging is enabled.

[edit system]
syslog {
host <syslog IPv4 or IPv6 address> {
any info;
structured-data; <<< Includes 'explicit-priority' and 'time-format'
}
host <syslog IPv4 or IPv6 address> {
any info;
explicit-priority; <<< Includes logging facility and severity in standard format
}
file <file name> {
any info; <<< Uses only standard format
}
time-format year; <<< Applied only to standard format
}
Note: In the example, events sent to the first external syslog server include the year and time is expressed in milliseconds. The second syslog server and the file both include the year, but time is expressed in seconds.

If the network device does not produce audit log records containing sufficient information to establish what type of event occurred, this is a finding.

Vulnerability Number

V-253889

Documentable

False

Rule Version

JUEX-NM-000120

Severity Override Guidance

Determine if the network device produces audit log records containing sufficient information to establish what type of event occurred.

Junos standard event log messages are configurable for time format, inclusion of logging facility and severity levels, and format. Setting "structured-data" automatically includes "explicit-priority" and "time-format year millisecond". Verify logging is enabled.

[edit system]
syslog {
host <syslog IPv4 or IPv6 address> {
any info;
structured-data; <<< Includes 'explicit-priority' and 'time-format'
}
host <syslog IPv4 or IPv6 address> {
any info;
explicit-priority; <<< Includes logging facility and severity in standard format
}
file <file name> {
any info; <<< Uses only standard format
}
time-format year; <<< Applied only to standard format
}
Note: In the example, events sent to the first external syslog server include the year and time is expressed in milliseconds. The second syslog server and the file both include the year, but time is expressed in seconds.

If the network device does not produce audit log records containing sufficient information to establish what type of event occurred, this is a finding.

Check Content Reference

M

Target Key

5477