Detections
Analytics

JUEX-RT-000370 - The Juniper perimeter router must be configured to deny network traffic by default and allow network traffic by exception.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

A deny-all, permit-by-exception network communications traffic policy ensures that only connections that are essential and approved are allowed.

This requirement applies to both inbound and outbound network communications traffic. All inbound and outbound traffic must be denied by default. Firewalls and perimeter routers should only allow traffic through that is explicitly permitted. The initial defense for the internal network is to block any traffic at the perimeter that is attempting to make a connection to a host residing on the internal network. In addition, allowing unknown or undesirable outbound traffic by the firewall or router will establish a state that will permit the return of this undesirable traffic inbound.

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 perimeter router to deny network traffic by default and allow network traffic by exception. For example:

set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-prefix-list INSIDE_ADDRESSES
set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from protocol tcp
set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-port http
set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-port https
set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 then accept
set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-prefix-list INSIDE_ADDRESSES
set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from protocol udp
set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-port domain
set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-port radius
set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 then accept

set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-prefix-list INSIDE_ADDRESSES
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from next-header tcp
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-port http
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-port https
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 then accept
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-prefix-list INSIDE_ADDRESSES
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from next-header udp
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-port domain
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-port radius
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 then accept

Note: To enable logging, add the following as the final term to each filter:
set firewall family [inet|inet6] filter <name> term default then log
set firewall family [inet|inet6] filter <name> term default then syslog
set firewall family [inet|inet6] filter <name> term default then discard

set interfaces <external interface> unit 0 family inet filter input permitted_inbound_traffic_ipv4
set interfaces <external interface> unit 0 family inet address <IPv4 address / mask>
set interfaces <external interface> unit 0 family inet6 filter input permitted_inbound_traffic_ipv6
set interfaces <external interface> unit 0 family inet6 address <IPv6 address / prefix>

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Juniper_EX_Switches_Y24M01_STIG.zip

Item Details

References: CAT|I, CCI|CCI-001109, Rule-ID|SV-254009r844060_rule, STIG-ID|JUEX-RT-000370, Vuln-ID|V-254009

Plugin: Juniper

Control ID: fd030fcb81028937fe049489da4b778f929923cdfe0e33629bc1c70ce92854c7