STIGQter: STIG Summary: Juniper Router NDM Security Technical Implementation Guide Version: 3 Release: 2 Benchmark Date: 30 Jan 2025:

The Juniper router must be configured to generate log records when administrator privileges are modified.

DISA Rule

SV-217343r961800_rule

Vulnerability Number

V-217343

Group Title

SRG-APP-000495-NDM-000318

Rule Version

JUNI-ND-001230

Severity

CAT II

CCI(s)

• CCI-000172 - Generate audit records for the event types defined in AU-2 c that include the audit record content defined in AU-3.

Weight

10

Fix Recommendation

Configure the router to generate log records when account privileges are modified as shown in the example below.

[edit system]
set syslog file LOG_FILE change-log info

Note: The parameter "any" can be in place of "change-log" as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below.

set syslog host x.x.x.x any info

Check Contents

Review the router configuration to verify that it is compliant with this requirement as shown in the examples below.

syslog {
file LOG_FILE {
change-log info;
}
}

Note: The parameter "any" can be in place of "authorization info" as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below.

system {
syslog {
host x.x.x.x {
any info;
}
}

If the router is not configured to generate log records when administrator privileges are modified, this is a finding.

Vulnerability Number

V-217343

Documentable

False

Rule Version

JUNI-ND-001230

Severity Override Guidance

Review the router configuration to verify that it is compliant with this requirement as shown in the examples below.

syslog {
file LOG_FILE {
change-log info;
}
}

Note: The parameter "any" can be in place of "authorization info" as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below.

system {
syslog {
host x.x.x.x {
any info;
}
}

If the router is not configured to generate log records when administrator privileges are modified, this is a finding.

Check Content Reference

M

Target Key

4034