Detections
Analytics

JUEX-RT-000400 - The Juniper perimeter router must be configured to filter traffic destined to the enclave in accordance with the guidelines contained in DoD Instruction 8551.1.

Information

Vulnerability assessments must be reviewed by the System Administrator, and protocols must be approved by the Information Assurance (IA) staff before entering the enclave.

Stateless firewall filters are the first line of defense in a layered security approach. They permit authorized packets and deny unauthorized packets based on port or service type. They enhance the posture of the network by not allowing packets to reach a potential target within the security domain. The lists provided are highly susceptible ports and services that should be blocked or limited as much as possible without adversely affecting customer requirements. Auditing packets attempting to penetrate the network but that are stopped by a firewall filter will allow network administrators to broaden their protective ring and more tightly define the scope of operation.

If the perimeter is in a Deny-by-Default posture and what is allowed through the filter is in accordance with DoD Instruction 8551.1, and if the permit rule is explicitly defined with explicit ports and protocols allowed, then all requirements related to PPS being blocked would be satisfied.

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 use ingress firewall filters to restrict traffic in accordance with the guidelines contained in DOD Instruction 8551.1 for all services and protocols required for operational commitments.

set policy-options prefix-list inside-addresses-ipv4 <IPv4 subnet>/<mask>
<additional subnets as required>
set policy-options prefix-list inside-addresses-ipv6 <IPv6 subnet>/<prefix>
<additional subnets as required>

set firewall family inet filter inbound-ipv4 term 1 from destination-prefix-list inside-addresses-ipv4
set firewall family inet filter inbound-ipv4 term 1 from protocol tcp
set firewall family inet filter inbound-ipv4 term 1 from destination-port 80
set firewall family inet filter inbound-ipv4 term 1 from destination-port 443
set firewall family inet filter inbound-ipv4 term 1 then accept
<additional terms as required>
set firewall family inet filter inbound-ipv4 term default-deny then log
set firewall family inet filter inbound-ipv4 term default-deny then syslog
set firewall family inet filter inbound-ipv4 term default-deny then discard

set firewall family inet6 filter inbound-ipv6 term 1 from destination-prefix-list inside-addresses-ipv6
set firewall family inet6 filter inbound-ipv6 term 1 from next-header tcp
set firewall family inet6 filter inbound-ipv6 term 1 from destination-port 80
set firewall family inet6 filter inbound-ipv6 term 1 from destination-port 443
set firewall family inet6 filter inbound-ipv6 term 1 then accept
set firewall family inet6 filter inbound-ipv6 term default-deny then log
set firewall family inet6 filter inbound-ipv6 term default-deny then syslog
set firewall family inet6 filter inbound-ipv6 term default-deny then discard

See Also

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

Item Details

Category: SYSTEM AND COMMUNICATIONS PROTECTION

References: 800-53|SC-7a., CAT|II, CCI|CCI-001097, Rule-ID|SV-254012r844069_rule, STIG-ID|JUEX-RT-000400, Vuln-ID|V-254012

Plugin: Juniper

Control ID: 48087d53d4825d9ca81311d9d4c1137d236407506c48efe8d5b002fec58e3a8f