The Juniper EX switch must be configured to generate audit records when modifying administrator privileges.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-253931	JUEX-NM-000540	SV-253931r843826_rule		Medium

Description
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).

STIG	Date
Juniper EX Series Switches Network Device Management Security Technical Implementation Guide	2022-08-31

Details

Check Text ( C-57383r843824_chk )
Determine if the network device generates audit records when modifying administrator privileges. Verify the system logs the facility "any", or minimally "change-log" and "interactive-commands", and the logging level is appropriate. Generally, the "all" (debug) logging level should be avoided because the number of logged messages is significant. [edit system syslog] host { any info; } file { change-log info; interactive-commands info; } Note: If minimally logging only configuration changes, there will be other files receiving the events from the other logging facilities e.g., "authorizations" or "firewall"). Syslog outputs in standard format unless the "structured-data" directive is configured. Verify the "structured-data" command for all files and external syslog servers requiring that format. For example: [edit system syslog] host { change-log info; interactive-commands info; structured-data; } file { any info; structured-data; } If the network device does not generate audit records when modifying administrator privileges, this is a finding.

Check Text ( C-57383r843824_chk )

Determine if the network device generates audit records when modifying administrator privileges.

Verify the system logs the facility "any", or minimally "change-log" and "interactive-commands", and the logging level is appropriate. Generally, the "all" (debug) logging level should be avoided because the number of logged messages is significant.

[edit system syslog]
host {
any info;
}
file {
change-log info;
interactive-commands info;
}
Note: If minimally logging only configuration changes, there will be other files receiving the events from the other logging facilities e.g., "authorizations" or "firewall").

Syslog outputs in standard format unless the "structured-data" directive is configured. Verify the "structured-data" command for all files and external syslog servers requiring that format. For example:

[edit system syslog]
host {
change-log info;
interactive-commands info;
structured-data;
}
file {
any info;
structured-data;
}

If the network device does not generate audit records when modifying administrator privileges, this is a finding.

Fix Text (F-57334r843825_fix)
Configure the network device to generate audit records when modifying administrator privileges. set system syslog host change-log info set system syslog host interactive-commands info -or- set system syslog host any info set system syslog file change-log info set system syslog file interactive-commands info -or- set system syslog file any info