STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Juniper Router RTR Security Technical Implementation Guide

V-217048

CAT II (Medium)

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.

Rule ID

SV-217048r604135_rule

STIG

Juniper Router RTR Security Technical Implementation Guide

Version

V3R2

CCIs

CCI-001097

Discussion

If the gateway router is not a dedicated device for the OOBM network, several safeguards must be implemented for containment of management and production traffic boundaries. It is imperative that hosts from the managed network are not able to access the OOBM gateway router.

Check Content

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.

Fix Text

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