Juniper Router RTR STIG

Juniper Router RTR Security Technical Implementation Guide

The Juniper Router RTR Security Technical Implementation Guide (V3 R2) has 96 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

96STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V3 · R2

CurrentPublished Thu Jan 30 2025

The Juniper perimeter router must be configured to block inbound packets with source Bogon IP address prefixes.

Juniper Router RTR Security Technical Implementation Guide

Assessment Title

Rule Text

The Juniper perimeter router must be configured to block inbound packets with source Bogon IP address prefixes.

Description

Discussion Text

Packets with Bogon IP source addresses should never be allowed to traverse the IP core. Bogon IP networks are RFC1918 addresses or address blocks that have never been assigned by the IANA or have been reserved.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-217032

Rule

SV-217032r855894_rule

Severity

medium

Rule Version

JUNI-RT-000270

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

This requirement is not applicable for the DoDIN Backbone.

Review the router configuration to verify that an ingress filter applied to all external interfaces is blocking packets with Bogon source addresses.

Verify a prefix list has been configured containing the current Bogon prefixes as shown in the example below.

policy-options {
    prefix-list BOGON_PREFIXES {
        0.0.0.0/8;
        10.0.0.0/8;
        100.64.0.0/10;
        127.0.0.0/8;
        169.254.0.0/16;
        172.16.0.0/12;
        192.0.0.0/24;
        192.0.2.0/24;
        192.168.0.0/16;
        198.18.0.0/15;
        198.51.100.0/24;
        203.0.113.0/24;
        224.0.0.0/4;
        240.0.0.0/4;
    }
}

Verify that the inbound filter applied to all external interfaces will block all traffic from Bogon source addresses.

interfaces {
    ge-0/0/0 {
        unit 0 {
            family inet {
                filter {
                    input INBOUND_FILTER;
                }
                address 11.1.12.2/24;
            }
        }
    }
…
…
…
firewall {
    family inet {
        filter INBOUND_FILTER {
            term BLOCK_BOGONS {
                from {
                    source-prefix-list {
                        BOGON_PREFIXES;
                    }
                }
                then {
                    syslog;
                    discard;
                }
            }
            term ALLOW_BGP {
                from {
                    protocol tcp;
                    destination-port bgp;
                }
                then accept;
            }
            term ALLOW_XYZ {
                from {
                    protocol xyz;
                }
                then accept;
            }
            term DENY_ALL_OTHER {
                then {
                    syslog;
                    reject;
                }
            }
        }
}

External Interfaces connected to the NIPRNet or SIPRNet

Review the inbound ACLs on external facing interfaces attached to the NIPRnet or SIPRnet to validate access control lists are configured to block inbound packets with IP sources addresses as documented in RFC5735 and RFC6598. 


External Interfaces connected to a commercial ISP or other non-DoD network
Review the inbound ACLs on external facing interfaces validate access control lists are configured to block inbound packets with IP sources addresses as documented in RFC5735 and RFC6598, as well as address space that has been allocated to the RIRs but not assigned by the RIR to an ISP or other enterprise network. The full list of bogons can be found at the following link: https://www.team-cymru.org/Services/Bogons/fullbogons-ipv4.txt

If the router is not configured to block inbound packets with source Bogon IP address prefixes, this is a finding.

Implementation Procedure

Fix Text

This requirement is not applicable for the DoDIN Backbone.

Configure the perimeter to block inbound packets with Bogon source addresses.

Configure a prefix list containing the current Bogon prefixes as shown below.

[edit policy-options]
set prefix-list BOGON_PREFIXES 0.0.0.0/8
set prefix-list BOGON_PREFIXES 10.0.0.0/8
set prefix-list BOGON_PREFIXES 100.64.0.0/10
set prefix-list BOGON_PREFIXES 127.0.0.0/8
set prefix-list BOGON_PREFIXES 169.254.0.0/16
set prefix-list BOGON_PREFIXES 172.16.0.0/12
set prefix-list BOGON_PREFIXES 192.0.0.0/24
set prefix-list BOGON_PREFIXES 192.0.2.0/24
set prefix-list BOGON_PREFIXES 192.168.0.0/16
set prefix-list BOGON_PREFIXES 198.18.0.0/15
set prefix-list BOGON_PREFIXES 198.51.100.0/24
set prefix-list BOGON_PREFIXES 203.0.113.0/24
set prefix-list BOGON_PREFIXES 224.0.0.0/4
set prefix-list BOGON_PREFIXES 240.0.0.0/4

Add a term to the inbound filter to block the Bogon prefixes.

[edit firewall family inet filter INBOUND_FILTER]
set term BLOCK_BOGONS from source-prefix-list BOGON_PREFIXES
set term BLOCK_BOGONS then syslog discard
insert term BLOCK_BOGONS before term ALLOW_BGP

STIG check 22 of 96 in the Juniper Router RTR STIG checklist

← Previous · V-217031The Juniper perimeter router must be configured to only allow incoming communications from authorized sources to be routed to authorized destinations.Next · V-217033 →The Juniper perimeter router must be configured to protect an enclave connected to an approved gateway by using an inbound filter that only permits packets with destination addresses within the site's address space.