STIGQter STIGQter: STIG Summary: Juniper Router RTR Security Technical Implementation Guide Version: 2 Release: 2 Benchmark Date: 12 Feb 2021:

The Juniper out-of-band management (OOBM) gateway router must be configured to block any traffic destined to itself that is not sourced from the OOBM network or the NOC.

DISA Rule

SV-217048r639663_rule

Vulnerability Number

V-217048

Group Title

SRG-NET-000205-RTR-000011

Rule Version

JUNI-RT-000430

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

This requirement is not applicable for the DoDIN Backbone.

Configure the router to only allow traffic to the Routing Engine from the OOBM network.

[edit firewall family inet]
set filter PROTECT_RP term RESTRICT_ADDRESS from source-address 0.0.0.0/0
set filter PROTECT_RP term RESTRICT_ADDRESS from source-address 10.2.14.0/24 except
set filter PROTECT_RP term RESTRICT_ADDRESS then syslog discard
set filter PROTECT_RP term ALLOW_OTHER then accept

[edit interfaces lo0 unit 0 family inet]
set filter input PROTECT_RP

Check Contents

This requirement is not applicable for the DoDIN Backbone.

Review the firewall filter applied to the routers loopback interface to verify that only traffic sourced from the OOBM network or the NOC is allowed to access the router as shown in the example below.

interfaces {



lo0 {
unit 0 {
family inet {
filter {
input PROTECT_RE;
}
address 1.1.1.1/32;
}
}
}
}



firewall {
family inet {
filter PROTECT_RE {
term RESTRICT_ADDRESS {
from {
source-address {
0.0.0.0/0;
10.2.14.0/24 except;
}
}
then {
syslog;
discard;
}
}
term ALLOW_OTHER {
then accept;
}
}
}
}

If the router does not block any traffic destined to itself that is not sourced from the OOBM network or the NOC, this is a finding.

Vulnerability Number

V-217048

Documentable

False

Rule Version

JUNI-RT-000430

Severity Override Guidance

This requirement is not applicable for the DoDIN Backbone.

Review the firewall filter applied to the routers loopback interface to verify that only traffic sourced from the OOBM network or the NOC is allowed to access the router as shown in the example below.

interfaces {



lo0 {
unit 0 {
family inet {
filter {
input PROTECT_RE;
}
address 1.1.1.1/32;
}
}
}
}



firewall {
family inet {
filter PROTECT_RE {
term RESTRICT_ADDRESS {
from {
source-address {
0.0.0.0/0;
10.2.14.0/24 except;
}
}
then {
syslog;
discard;
}
}
term ALLOW_OTHER {
then accept;
}
}
}
}

If the router does not block any traffic destined to itself that is not sourced from the OOBM network or the NOC, this is a finding.

Check Content Reference

M

Target Key

4032

Comments