OpenControls Logo

STIG Viewer

STIGViewer Support

The Juniper perimeter router must be configured to block all outbound management traffic.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-217043JUNI-RT-000380SV-217043r1050852_ruleCCI-001097medium
Description
For in-band management, the management network must have its own subnet to enforce control and access boundaries provided by Layer 3 network nodes, such as routers and firewalls. Management traffic between the managed network elements and the management network is routed via the same links and nodes as that used for production or operational traffic. Safeguards must be implemented to ensure that the management traffic does not leak past the perimeter of the managed network.
STIGDate
Juniper Router RTR Security Technical Implementation Guide2024-12-05

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (18) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
MON-01Continuous Monitoring
1.00
MON-01.1Intrusion Detection & Prevention Systems (IDS & IPS)
1.00

+8 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (10) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CM-6Configuration Settings
1.00
SC-24Fail in Known State
1.00
SC-47Alternate Communications Paths
1.00
SC-5Denial-of-service Protection
1.00
SC-7Boundary Protection
1.00
SC-7(11)Restrict Incoming Communications Traffic
1.00
SC-7(29)Separate Subnets to Isolate Functions
1.00
SC-7(5)Deny by Default — Allow by Exception
1.00
SI-4System Monitoring
1.00
SI-4(11)Analyze Communications Traffic Anomalies
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.13.1
1.00
3.13.2
1.00
3.13.5
1.00
CCI1 mapping
CCI-001097
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

DE.CM-01
1.00
PR.DS-01
1.00
PR.DS-02
1.00
PR.DS-10
1.00
PR.IR-01
1.00

Who does this work

15 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-217043r1050852_chk)

This requirement is not applicable for the DODIN backbone. The perimeter router of the managed network must be configured with an outbound filter on the egress interface to block all management traffic as shown in the example below. Verify that the router has been configured with an outbound filter as shown in the example below. interfaces { description "NIPRNet"; ge-0/0/0 { unit 0 { family inet { no-redirects; filter { output OUTBOUND_FILTER; } address 10.1.12.2/24; } } } Verify that the outbound filter discards or rejects management traffic as shown in the example below. firewall { family inet { … … … } filter OUTBOUND_FILTER { term BLOCK_TACACS { from { protocol tcp; port tacacs; } then { syslog; discard; } } term BLOCK_SNMP { from { protocol udp; port [ snmp snmptrap ]; } then { syslog; discard; } } term BLOCK_NETFLOW { from { protocol udp; port [ 2055 9995 9996 ]; } then { syslog; discard; } } term ALLOW_OTHER { then accept; } } } If management traffic is not blocked at the perimeter, this is a finding.

Fix Text (F-18270r1050851_fix)

This requirement is not applicable for the DODIN backbone. Configure the perimeter router of the managed network with an outbound filter on the egress interface to block all management traffic. Configure a filter to block egress management traffic. [edit firewall family inet] Set filter OUTBOUND_FILTER term BLOCK_TACACS from protocol tcp port tacacs Set filter OUTBOUND_FILTER term BLOCK_TACACS then syslog discard Set filter OUTBOUND_FILTER term BLOCK_SNMP from protocol udp port [snmp snmptrap] Set filter OUTBOUND_FILTER term BLOCK_SNMP then syslog discard set filter OUTBOUND_FILTER term BLOCK_NETFLOW from protocol udp port [2055 9995 9996] set filter OUTBOUND_FILTER term BLOCK_NETFLOW then syslog discard Configure the external interfaces with the outbound filter. [edit interfaces ge-0/0/0 unit 0 family inet] set filter output OUTBOUND_FILTER