STIGQter: STIG Summary: Juniper EX Series Switches Router Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 24 Jul 2024:

The Juniper out-of-band management (OOBM) gateway router must be configured to have separate IGP instances for the managed network and management network.

DISA Rule

SV-253992r844009_rule

Vulnerability Number

V-253992

Group Title

SRG-NET-000019-RTR-000011

Rule Version

JUEX-RT-000200

Severity

CAT II

CCI(s)

• CCI-001414 - Enforce approved authorizations for controlling the flow of information between connected systems based on organization-defined information flow control policies.

Weight

10

Fix Recommendation

This requirement is not applicable for the DODIN Backbone.

Configure the router to enforce that Interior Gateway Protocol instances configured on the OOBM gateway router peer only with their own routing domain.
set protocols ospf area <number> interface <interface name>.<logical unit>

set routing-instances <name> instance-type virtual-router
set routing-instances <name> protocols ospf area <number> interface <interface name>.<logical unit>

Check Contents

This requirement is not applicable for the DODIN Backbone.

Verify that the OOBM interface is an adjacency in the Interior Gateway Protocol routing domain for the management network. Interfaces can only be assigned to one routing instance.

[edit protocols ospf]
interface <interface name>.<logical unit>; << Cannot be assigned to a virtual routing instance.

[edit routing-instances]
<name> {
instance-type virtual-router;
protocols {
ospf {
area <area number> {
interface <interface name>.<logical unit>; << Cannot be assigned to the default routing instance at [edit protocols].
}
}
}
}

Note: If the same interface is assigned to the default routing instance and to a virtual routing instance, commit fails.

Some platforms support a routing-instance using the reserved name "mgmt_junos". On these platforms, configure the "mgmt_junos" instance and apply at the [edit system] hierarchy.
[edit system]
management-instance;

[edit routing-instances]
mgmt_junos {
routing-options {
static {
route 0.0.0.0/0 next-hop <next-hop address>;
}
}
}
Note: Not all platforms support routing instances.

If the router does not enforce that Interior Gateway Protocol instances configured on the OOBM gateway router peer only with their own routing domain, this is a finding.

Vulnerability Number

V-253992

Documentable

False

Rule Version

JUEX-RT-000200

Severity Override Guidance

This requirement is not applicable for the DODIN Backbone.

Verify that the OOBM interface is an adjacency in the Interior Gateway Protocol routing domain for the management network. Interfaces can only be assigned to one routing instance.

[edit protocols ospf]
interface <interface name>.<logical unit>; << Cannot be assigned to a virtual routing instance.

[edit routing-instances]
<name> {
instance-type virtual-router;
protocols {
ospf {
area <area number> {
interface <interface name>.<logical unit>; << Cannot be assigned to the default routing instance at [edit protocols].
}
}
}
}

Note: If the same interface is assigned to the default routing instance and to a virtual routing instance, commit fails.

Some platforms support a routing-instance using the reserved name "mgmt_junos". On these platforms, configure the "mgmt_junos" instance and apply at the [edit system] hierarchy.
[edit system]
management-instance;

[edit routing-instances]
mgmt_junos {
routing-options {
static {
route 0.0.0.0/0 next-hop <next-hop address>;
}
}
}
Note: Not all platforms support routing instances.

If the router does not enforce that Interior Gateway Protocol instances configured on the OOBM gateway router peer only with their own routing domain, this is a finding.

Check Content Reference

M

Target Key

5479