STIGQter: STIG Summary: Juniper EX Series Switches Network Device Management Security Technical Implementation Guide Version: 2 Release: 5 Benchmark Date: 01 Jul 2026: STIGQter: STIG Summary: Juniper EX Series Switches Network Device Management Security Technical Implementation Guide Version: 2 Release: 5 Benchmark Date: 01 Jul 2026:SV-253894r960906_rule
V-253894
SRG-APP-000100-NDM-000230
JUEX-NM-000170
CAT II
10
Configure the network device to generate audit records containing information that establishes the identity of any individual or process associated with the event.
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
Determine if the network device generates audit records containing information that establishes the identity of any individual or process associated with the event. This requirement may be verified by demonstration or validated test results.
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 generate audit records containing information that establishes the identity of any individual or process associated with the event, this is a finding.
V-253894
False
JUEX-NM-000170
Determine if the network device generates audit records containing information that establishes the identity of any individual or process associated with the event. This requirement may be verified by demonstration or validated test results.
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 generate audit records containing information that establishes the identity of any individual or process associated with the event, this is a finding.
M
5477