STIGQter STIGQter: STIG Summary: Juniper Router RTR Security Technical Implementation Guide Version: 1 Release: 3 Benchmark Date: 25 Oct 2019: The Juniper BGP router must be configured to reject outbound route advertisements for any prefixes that do not belong to any customers or the local autonomous system (AS).

DISA Rule

SV-101107r3_rule

Vulnerability Number

V-90897

Group Title

SRG-NET-000018-RTR-000005

Rule Version

JUNI-RT-000510

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Configure the router to filter outbound route advertisements for prefixes that are not allocated to or belong to any customer or the local autonomous system.

Configure a policy-statement to filter BGP route advertisements that will only include the local and customer prefixes.

[edit policy-options]
set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_LOCAL from prefix-list OUR_PREFIXES
set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_LOCAL then accept
set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_CUST1 from prefix-list CUST1_PREFIXES
set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_CUST1 then accept
set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_CUST2 from prefix-list CUST2_PREFIXES
set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_CUST2 then accept
set policy-statement BGP_ADVERTISE_POLICY term REJECT_OTHER then reject

Note: The prefix lists should have already been configured per the previous requirements.

Configure an export statement referencing the advertise policy on all external BGP peer groups as shown in the example below.

[edit protocols bgp group GROUP_AS4]
set export BGP_ADVERTISE_POLICY
[edit protocols bgp group CUST1]
set export BGP_ADVERTISE_POLICY
[edit protocols bgp group CUST2]
set export BGP_ADVERTISE_POLICY

Check Contents

This requirement is not applicable for the DODIN Backbone.”

Review the router configuration to verify that there is a filter defined to only advertise routes for prefixes that belong to any customers or the local AS.

Verify that a policy has been configured to filter prefixes for BGP advertisement as shown in the example below.

}
policy-options {



policy-statement BGP_ADVERTISE_POLICY {
term INCLUDE_LOCAL {
from {
prefix-list OUR_PREFIXES;
}
then accept;
}
term INCLUDE_CUST1 {
from {
prefix-list CUST1_PREFIXES;
}
then accept;
}
term INCLUDE_CUST2 {
from {
prefix-list CUST2_PREFIXES;
}
then accept;
}
term REJECT_OTHER {
then reject;
}
}

Verify that the export statement as shown below references the advertise policy.

protocols {
bgp {
group AS4 {
type external;
import FILTER_ROUTES;
export BGP_ADVERTISE_POLICY;
peer-as 4;
neighbor x.x.x.x;
}
group CUST1 {
type external;
import FILTER_CUST1_ROUTES;
export BGP_ADVERTISE_POLICY;
peer-as 55;
neighbor x.x.x.x;
neighbor x.x.x.x;
}
group CUST2 {
type external;
import FILTER_CUST2_ROUTES;
export BGP_ADVERTISE_POLICY;
peer-as 44;
neighbor x.x.x.x;
neighbor x.x.x.x;
}
}



}

Note: The prefix lists should have already been configured per the previous requirements.

If the router is not configured to reject outbound route advertisements that do not belong to any customers or the local AS, this is a finding.

Vulnerability Number

V-90897

Documentable

False

Rule Version

JUNI-RT-000510

Severity Override Guidance

This requirement is not applicable for the DODIN Backbone.”

Review the router configuration to verify that there is a filter defined to only advertise routes for prefixes that belong to any customers or the local AS.

Verify that a policy has been configured to filter prefixes for BGP advertisement as shown in the example below.

}
policy-options {



policy-statement BGP_ADVERTISE_POLICY {
term INCLUDE_LOCAL {
from {
prefix-list OUR_PREFIXES;
}
then accept;
}
term INCLUDE_CUST1 {
from {
prefix-list CUST1_PREFIXES;
}
then accept;
}
term INCLUDE_CUST2 {
from {
prefix-list CUST2_PREFIXES;
}
then accept;
}
term REJECT_OTHER {
then reject;
}
}

Verify that the export statement as shown below references the advertise policy.

protocols {
bgp {
group AS4 {
type external;
import FILTER_ROUTES;
export BGP_ADVERTISE_POLICY;
peer-as 4;
neighbor x.x.x.x;
}
group CUST1 {
type external;
import FILTER_CUST1_ROUTES;
export BGP_ADVERTISE_POLICY;
peer-as 55;
neighbor x.x.x.x;
neighbor x.x.x.x;
}
group CUST2 {
type external;
import FILTER_CUST2_ROUTES;
export BGP_ADVERTISE_POLICY;
peer-as 44;
neighbor x.x.x.x;
neighbor x.x.x.x;
}
}



}

Note: The prefix lists should have already been configured per the previous requirements.

If the router is not configured to reject outbound route advertisements that do not belong to any customers or the local AS, this is a finding.

Check Content Reference

M

Target Key

3387

Comments