OpenControls Logo

STIG Viewer

STIGViewer Support

The Arista perimeter router must be configured to deny network traffic by default and allow network traffic by exception.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-256015ARST-RT-000330SV-256015r882387_ruleCCI-001109high
Description
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.
STIGDate
Arista MLS EOS 4.X Router Security Technical Implementation Guide2025-02-20

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) 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.

NET-04.1Deny Traffic by Default & Allow Traffic by Exception
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (6) 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.

AC-4Information Flow Enforcement
1.00
SC-24Fail in Known State
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(5)Deny by Default — Allow by Exception
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) 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.6
1.00
CCI1 mapping
CCI-001109
1.00

Details

Check Text (C-256015r882387_chk)

This requirement is not applicable for the DODIN backbone. Review the Arista router configuration to verify the access control list (ACL) or filter is configured to allow specific ports and protocols and deny all other traffic. The filter must be configured inbound on all external interfaces. Step 1: Verify the ACL is configured to allow traffic per the requirement and deny all by default. Execute the command "sh ip access-list". ip access-list INBOUND 10 permit tcp 10.10.10.0/24 host 10.20.10.1 eq ssh telnet 20 permit tcp 10.10.10.0/24 any eq www https 30 permit udp 10.20.20.0/24 any eq bootps snmp Step 2: Verify the ACL is applied inbound on all external interfaces. Execute the command "sh run int Eth YY". interface ethernet 13 ip access-group INBOUND in If the ACL or filter is not configured to allow specific ports and protocols and deny all other traffic, this is a finding. If the filter is not configured inbound on all external interfaces, this is a finding.

Fix Text (F-59634r882386_fix)

This requirement is not applicable for the DODIN backbone. Configure the Arista perimeter router to deny network traffic by default and allow network traffic by exception. Step 1: Configure an ACL inbound to allow traffic per the requirement and deny all by default. ip access-list INBOUND 10 permit tcp 10.10.10.0/24 host 10.20.10.1 eq ssh telnet 20 permit tcp 10.10.10.0/24 any eq www https 30 permit udp 10.20.20.0/24 any eq bootps snmp Step 2: Apply the ACL inbound on all external interfaces. router(config)#interface ethernet 13 router(config-if-Et13)#ip access-group INBOUND in