JUNI-RT-000430 - 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.

Information

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.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

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

Item Details

Audit Name: DISA STIG Juniper Router RTR v3r2

Category: SYSTEM AND COMMUNICATIONS PROTECTION

Plugin: Juniper

Control ID: 85913e8a2a3a0fe3c46d27e1d25394e1f7b1829619857dccd0e594bee4b2710b

Detections

Analytics

JUNI-RT-000430 - 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.

Information

Solution

See Also

Item Details