STIGQter: STIG Summary: Juniper Router NDM Security Technical Implementation Guide Version: 1 Release: 5 Benchmark Date: 24 Jul 2020:

The Juniper router must be configured to generate audit records when successful/unsuccessful logon attempts occur.

DISA Rule

SV-101279r1_rule

Vulnerability Number

V-91179

Group Title

SRG-APP-000503-NDM-000320

Rule Version

JUNI-ND-001250

Severity

CAT II

CCI(s)

• CCI-000172 - The information system generates audit records for the events defined in AU-2 d. with the content defined in AU-3.

Weight

10

Fix Recommendation

Configure the router to generate audit records when successful/unsuccessful logon attempts occur as shown in the example below.

[edit system]
set syslog file LOG_FILE authorization info

Note: The parameter "any" can be in place of authorization" 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 {
authorization info;
}
}

Note: The parameter "any" can be in place of "authorization" 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 audit records when successful/unsuccessful logon attempts occur, this is a finding.

Vulnerability Number

V-91179

Documentable

False

Rule Version

JUNI-ND-001250

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 {
authorization info;
}
}

Note: The parameter "any" can be in place of "authorization" 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 audit records when successful/unsuccessful logon attempts occur, this is a finding.

Check Content Reference

M

Target Key

3381

Comments