| Checked | Name | Title |
|---|
| ☐ | SV-255987r882303_rule | The Arista router must be configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies. |
| ☐ | SV-255988r882306_rule | The Arista BGP router must be configured to reject inbound route advertisements for any Bogon prefixes. |
| ☐ | SV-255989r882309_rule | The Arista BGP router must be configured to reject inbound route advertisements for any prefixes belonging to the local autonomous system (AS). |
| ☐ | SV-255990r882312_rule | The Arista BGP router must be configured to reject inbound route advertisements from a customer edge (CE) router for prefixes that are not allocated to that customer. |
| ☐ | SV-255991r882315_rule | The Arista BGP router must be configured to reject outbound route advertisements for any prefixes that do not belong to any customers or the local autonomous system (AS). |
| ☐ | SV-255992r945854_rule | The Arista BGP router must be configured to reject route advertisements from BGP peers that do not list their autonomous system (AS) number as the first AS in the AS_PATH attribute. |
| ☐ | SV-255993r882321_rule | The Arista Multicast Source Discovery Protocol (MSDP) router must be configured to filter received source-active multicast advertisements for any undesirable multicast groups and sources. |
| ☐ | SV-255994r882324_rule | The Arista Multicast Source Discovery Protocol (MSDP) router must be configured to filter source-active multicast advertisements to external MSDP peers to avoid global visibility of local-only multicast sources and groups. |
| ☐ | SV-255995r882327_rule | The Arista MSDP router must be configured to limit the amount of source-active messages it accepts on per-peer basis. |
| ☐ | SV-255996r945855_rule | The Arista BGP router must be configured to reject route advertisements from CE routers with an originating AS in the AS_PATH attribute that does not belong to that customer. |
| ☐ | SV-255997r882333_rule | The Arista perimeter router must be configured to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy. |
| ☐ | SV-255998r882336_rule | The Arista multicast router must be configured to disable Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing. |
| ☐ | SV-255999r882339_rule | The Arista multicast router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled. |
| ☐ | SV-256000r882342_rule | The Arista multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic. |
| ☐ | SV-256001r882345_rule | The Arista router must be configured to have all inactive interfaces disabled. |
| ☐ | SV-256002r882348_rule | The Arista perimeter router must be configured to protect an enclave connected to an alternate gateway by using an inbound filter that only permits packets with destination addresses within the sites address space. |
| ☐ | SV-256003r882351_rule | The Arista perimeter router must be configured to not be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider. |
| ☐ | SV-256004r882354_rule | The Arista perimeter router must be configured to not redistribute static routes to an alternate gateway service provider into BGP or an IGP peering with the NIPRNet or to other autonomous systems. |
| ☐ | SV-256005r882357_rule | The out-of-band management (OOBM) Arista gateway router must be configured to have separate IGP instances for the managed network and management network. |
| ☐ | SV-256006r882360_rule | The out-of-band management (OOBM) Arista gateway router must be configured to not redistribute routes between the management network routing domain and the managed network routing domain. |
| ☐ | SV-256007r882363_rule | The multicast Rendezvous Point (RP) Arista router must be configured to filter Protocol Independent Multicast (PIM) Register and Join messages received from the Designated Router (DR) for any undesirable multicast groups and sources. |
| ☐ | SV-256008r882366_rule | The Arista router must be configured to produce audit records containing information to establish where the events occurred. |
| ☐ | SV-256009r882369_rule | The Arista router must be configured to have all non-essential capabilities disabled. |
| ☐ | SV-256010r882372_rule | The Arista router must be configured to authenticate all routing protocol messages using NIST-validated FIPS 198-1 message authentication code algorithm. |
| ☐ | SV-256011r882375_rule | The MPLS router with RSVP-TE enabled must be configured with message pacing or refresh reduction to adjust maximum number of RSVP messages to an output queue based on the link speed and input queue size of adjacent core routers. |
| ☐ | SV-256012r882378_rule | The PE router must be configured to enforce a Quality-of-Service (QoS) policy to limit the effects of packet flooding denial-of-service (DoS) attacks. |
| ☐ | SV-256013r882381_rule | The PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS DODIN Technical Profile. |
| ☐ | SV-256014r882384_rule | The PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile. |
| ☐ | SV-256015r882387_rule | The Arista perimeter router must be configured to deny network traffic by default and allow network traffic by exception. |
| ☐ | SV-256016r882390_rule | The Arista router must be configured to restrict traffic destined to itself. |
| ☐ | SV-256017r882393_rule | The Arista router must be configured to drop all fragmented Internet Control Message Protocol (ICMP) packets destined to itself. |
| ☐ | SV-256018r882396_rule | The Arista perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction. |
| ☐ | SV-256019r882399_rule | The Arista perimeter router must be configured to filter egress traffic at the internal interface on an inbound direction. |
| ☐ | SV-256020r882402_rule | The Arista BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core. |
| ☐ | SV-256021r882405_rule | The Arista router must be configured to block any traffic that is destined to IP core infrastructure. |
| ☐ | SV-256022r882408_rule | The Arista router must be configured with Unicast Reverse Path Forwarding (uRPF) loose mode enabled on all CE-facing interfaces. |
| ☐ | SV-256023r991786_rule | The out-of-band management (OOBM) Arista gateway router must be configured to forward only authorized management traffic to the Network Operations Center (NOC). |
| ☐ | SV-256024r991787_rule | The out-of-band management (OOBM) Arista gateway router must be configured to block any traffic destined to itself that is not sourced from the OOBM network or the NOC. |
| ☐ | SV-256025r991788_rule | The Arista router must be configured to only permit management traffic that ingresses and egresses the out-of-band management (OOBM) interface. |
| ☐ | SV-256026r945858_rule | The Arista perimeter router must be configured to restrict it from accepting outbound IP packets that contain an illegitimate address in the source address field via egress filter or by enabling Unicast Reverse Path Forwarding (uRPF). |
| ☐ | SV-256027r945862_rule | The Arista BGP router must be configured to use a unique key for each autonomous system (AS) that it peers with. |
| ☐ | SV-256028r882426_rule | The PE router providing MPLS Layer 2 Virtual Private Network (L2VPN) services must be configured to authenticate targeted Label Distribution Protocol (LDP) sessions used to exchange virtual circuit (VC) information using a FIPS-approved message authentication code algorithm. |
| ☐ | SV-256029r882429_rule | The Arista router must not be configured to have any zero-touch deployment feature enabled when connected to an operational network. |
| ☐ | SV-256030r882432_rule | The Arista router must be configured to have gratuitous ARP disabled on all external interfaces. |
| ☐ | SV-256031r884234_rule | The Arista router must be configured to have IP directed broadcast disabled on all interfaces. |
| ☐ | SV-256032r882438_rule | The Arista router must be configured to have Internet Control Message Protocol (ICMP) unreachable notifications disabled on all external interfaces. |
| ☐ | SV-256033r882441_rule | The Arista router must be configured to have Internet Control Message Protocol (ICMP) mask replies disabled on all external interfaces. |
| ☐ | SV-256034r882444_rule | The Arista router must be configured to have Internet Control Message Protocol (ICMP) redirects disabled on all external interfaces. |
| ☐ | SV-256035r882447_rule | The Arista BGP router must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks. |
| ☐ | SV-256036r882450_rule | The Arista BGP router must be configured to limit the prefix size on any inbound route advertisement to /24 or the least significant prefixes issued to the customer. |
| ☐ | SV-256037r882453_rule | The multicast Rendezvous Point (RP) Arista router must be configured to limit the multicast forwarding cache so that its resources are not saturated by managing an overwhelming number of Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) source-active entries. |
| ☐ | SV-256038r945856_rule | The Arista multicast Designated Router (DR) must be configured to increase the shortest-path tree (SPT) threshold or set it to infinity to minimalize source-group (S, G) state within the multicast topology where Any Source Multicast (ASM) is deployed. |
| ☐ | SV-256039r882459_rule | The Arista BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM). |
| ☐ | SV-256040r882462_rule | The Arista perimeter router must be configured to only allow incoming communications from authorized sources to be routed to authorized destinations. |
| ☐ | SV-256041r882465_rule | The Arista perimeter router must be configured to block inbound packets with source Bogon IP address prefixes. |
| ☐ | SV-256042r882468_rule | The Arista perimeter router must be configured to have Link Layer Discovery Protocols (LLDPs) disabled on all external interfaces. |
| ☐ | SV-256043r882471_rule | The Arista perimeter router must be configured to have Proxy ARP disabled on all external interfaces. |
| ☐ | SV-256044r945857_rule | The Arista perimeter router must be configured to block all outbound management traffic. |
| ☐ | SV-256045r882477_rule | The Arista multicast Designated Router (DR) must be configured to filter the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Report messages to allow hosts to join only multicast groups that have been approved by the organization. |
| ☐ | SV-256046r882480_rule | The Arista multicast Designated Router (DR) must be configured to filter the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Report messages to allow hosts to join a multicast group only from sources that have been approved by the organization. |
| ☐ | SV-256047r882483_rule | The Arista Multicast Source Discovery Protocol (MSDP) router must be configured to only accept MSDP packets from known MSDP peers. |
| ☐ | SV-256048r991789_rule | The Arista BGP router must be configured to use its loopback address as the source address for iBGP peering sessions. |
| ☐ | SV-256049r991790_rule | The MPLS router must be configured to use its loopback address as the source address for LDP peering sessions. |
| ☐ | SV-256050r882492_rule | The MPLS router must be configured to synchronize IGP and LDP to minimize packet loss when an IGP adjacency is established prior to LDP peers completing label exchange. |
| ☐ | SV-256051r882495_rule | The MPLS router must be configured to have TTL propagation disabled. |
| ☐ | SV-256052r991791_rule | The PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance bound to the appropriate physical or logical interfaces to maintain traffic separation between all MPLS L3VPNs. |
| ☐ | SV-256053r991792_rule | The PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Target (RT). |
| ☐ | SV-256054r991793_rule | The PE router must be configured to have each VRF with the appropriate Route Distinguisher (RD). |
| ☐ | SV-256055r991794_rule | The PE router providing MPLS Virtual Private Wire Service (VPWS) must be configured to have the appropriate virtual circuit identification (VC ID) for each attachment circuit. |
| ☐ | SV-256056r991795_rule | The Arista Multicast Source Discovery Protocol (MSDP) router must be configured to use its loopback address as the source address when originating MSDP traffic. |
| ☐ | SV-256057r882513_rule | The Arista router must be configured to advertise a hop limit of at least 32 in Router Advertisement messages for IPv6 stateless auto-configuration deployments. |
| ☐ | SV-256058r882516_rule | The Arista router must not be configured to use IPv6 Site Local Unicast addresses. |
| ☐ | SV-256059r882519_rule | The Arista perimeter router must be configured to suppress Router Advertisements on all external IPv6-enabled interfaces. |
| ☐ | SV-256060r945859_rule | The perimeter router must be configured to block all packets with any IP options. |
| ☐ | SV-256061r945860_rule | The PE router must be configured to ignore or block all packets with any IP options. |
STIGQter: STIG Summary: