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

The Juniper perimeter router must not be configured to be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider.

DISA Rule

SV-253990r844003_rule

Vulnerability Number

V-253990

Group Title

SRG-NET-000019-RTR-000009

Rule Version

JUEX-RT-000180

Severity

CAT I

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.

Remove BGP neighbors belonging to the alternate gateway service provider.

delete protocols bgp group <name> neighbor <peer AS belonging to alternate gateway service provider>

Configure a static route on the perimeter router to reach the AS of a router connecting to an alternate gateway.

set routing-options rib inet6.0 static route <IPv6 subnet>/<prefix> next-hop <peer AS router>
set routing-options static route <IPv4 subnet>/<mask> next-hop <peer AS router>

Check Contents

This requirement is not applicable for the DODIN Backbone.

Review the configuration of the router connecting to the alternate gateway.

Review the [edit protocols bgp] hierarchy and verify there are no BGP neighbors configured to the remote AS that belongs to the alternate gateway service provider. For example:
[edit protocols bgp]
group eBGP {
type external;
peer-as 2;
neighbor <address-1> {
<bgp neighbor configuration>;
}
neighbor <address-2> {
<bgp neighbor configuration>;
}
}

Note: Neither neighbor can belong to a peer AS belonging to the alternate gateway service provider.

Verify static routing to the peer AS belonging to the alternate gateway service provider. For example:
[edit routing-options]
rib inet6.0 {
static {
route <peer AS IPv6 subnet>/<prefix> next-hop <peer AS router>;
}
}
static {
route <peer AS IPv4 subnet>/<mask> next-hop <peer AS router>;
}

If there are BGP neighbors connecting the remote AS of the alternate gateway service provider, this is a finding.

Vulnerability Number

V-253990

Documentable

False

Rule Version

JUEX-RT-000180

Severity Override Guidance

This requirement is not applicable for the DODIN Backbone.

Review the configuration of the router connecting to the alternate gateway.

Review the [edit protocols bgp] hierarchy and verify there are no BGP neighbors configured to the remote AS that belongs to the alternate gateway service provider. For example:
[edit protocols bgp]
group eBGP {
type external;
peer-as 2;
neighbor <address-1> {
<bgp neighbor configuration>;
}
neighbor <address-2> {
<bgp neighbor configuration>;
}
}

Note: Neither neighbor can belong to a peer AS belonging to the alternate gateway service provider.

Verify static routing to the peer AS belonging to the alternate gateway service provider. For example:
[edit routing-options]
rib inet6.0 {
static {
route <peer AS IPv6 subnet>/<prefix> next-hop <peer AS router>;
}
}
static {
route <peer AS IPv4 subnet>/<mask> next-hop <peer AS router>;
}

If there are BGP neighbors connecting the remote AS of the alternate gateway service provider, this is a finding.

Check Content Reference

M

Target Key

5479