STIGQter 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 protect against an individual falsely denying having performed organization-defined actions to be covered by non-repudiation.

DISA Rule

SV-217313r960864_rule

Vulnerability Number

V-217313

Group Title

SRG-APP-000080-NDM-000220

Rule Version

JUNI-ND-000210

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Configure the router to log configuration changes as shown in the following example:

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 10.1.58.2 any info

Check Contents

Review the router configuration to determine if it logs configuration changes as shown in the following example:

system {
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.

system {
syslog {
host 10.1.58.2 {
any info;
}
file LOG_FILE {
change-log info;
}
console {
any error;
}
}
}

If configuration change activity is not logged, this is a finding.

Vulnerability Number

V-217313

Documentable

False

Rule Version

JUNI-ND-000210

Severity Override Guidance

Review the router configuration to determine if it logs configuration changes as shown in the following example:

system {
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.

system {
syslog {
host 10.1.58.2 {
any info;
}
file LOG_FILE {
change-log info;
}
console {
any error;
}
}
}

If configuration change activity is not logged, this is a finding.

Check Content Reference

M

Target Key

4034