OpenControls Logo

STIG Viewer

STIGViewer Support

The Arista router must be configured to produce audit records containing information to establish where the events occurred.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-256008ARST-RT-000230SV-256008r882366_ruleCCI-000132medium
Description
Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as router components, modules, device identifiers, node names, and functionality. Associating information about where the event occurred within the network provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured router. Satisfies: SRG-NET-000076-RTR-000001, SRG-NET-000077-RTR-000001, SRG-NET-000078-RTR-000001
STIGDate
Arista MLS EOS 4.X Router Security Technical Implementation Guide2025-02-20

Related Frameworks

3 mappings across 5 frameworks
SCF0 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.

MON-01Continuous Monitoring
1.00
MON-01.4System Generated Alerts
1.00
MON-03Content of Event Logs
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (65) 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-16Security and Privacy Attributes
1.00
AC-17(1)Monitoring and Control
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(3)Mandatory Access Control
1.00
AC-4Information Flow Enforcement
1.00

+55 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) 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.3.1
1.00
3.3.2
1.00
CCI3 mappings
CCI-000132
1.00
CCI-000133
1.00
CCI-000134
1.00
NIST CSF 2.00 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.

PR.PS-04
1.00

Who does this work

6 NICE work roles and 5 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-256008r882366_chk)

The Arista router must log all packets that have been dropped via the access control list (ACL). Log output must contain an interface name as to where the packet was filtered. Step 1: To verify the deny ACL is created with the log statement for dropped packets, execute the command "show ip access-list". ip access-list test1 permit ip 10.30.30.0/24 host 10.20.10.1 deny ip 10.30.10.0/24 host 10.20.10.1 log Step 2: To verify the ACL ingress is applied on the appropriate interface, execute the command "show run interface YY". interface ethernet 3 ip access-group test1 in ###### Variables in the syslog messages display the following values: --------------------------------------------------------------- acl Name of ACL. intf Name of interface that received the packet. filter Action triggered by ACL (denied or permitted). protocol IP protocol specified by packet. vlan Number of VLAN receiving packet. ether EtherType protocol specified by packet. src-ip and dst-ip source and destination IP addresses. src-prt and dst-prt source and destination ports. src-mac and dst-mac source and destination MAC addresses. If the logged output does not contain an interface name as to where the packet was filtered, this is a finding. If the Arista router fails to log all packets that have been dropped via the ACL, this is a finding.

Fix Text (F-59627r882365_fix)

Configure the router to record the interface in the log record for packets being dropped. Step 1: Configure the ACL. router(config)#ip access-list test1 router(config-acl-test1)#15 permit ip 10.30.30.0/24 host 10.20.10.1 router(config-acl-test1)#15 deny ip 10.30.10.0/24 host 10.20.10.1 log Step 2: Apply the ACL ingress on the appropriate interface. router(config)#interface ethernet 3 router(config-if-Et3)#ip access-group test1 in