| Checked | Name | Title |
|---|
| ☐ | SV-207097r1137893_rule | The 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-207098r1137894_rule | The BGP router must be configured to reject inbound route advertisements for any Bogon prefixes. |
| ☐ | SV-207099r1137895_rule | The BGP router must be configured to reject inbound route advertisements for any prefixes belonging to the local autonomous system (AS). |
| ☐ | SV-207100r1137896_rule | The 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-207101r1137897_rule | The 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-207102r1137898_rule | The 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-207103r1137900_rule | The Multicast Source Discovery Protocol (MSDP) router must be configured to filter received source-active multicast advertisements for any undesirable multicast groups and sources. |
| ☐ | SV-207104r1137902_rule | The 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-207105r1137903_rule | The MSDP router must be configured to limit the amount of source-active messages it accepts on per-peer basis. |
| ☐ | SV-207106r1137905_rule | The 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-207107r1137906_rule | The router must be configured to disable the auxiliary port unless it is connected to a secured modem providing encryption and authentication. |
| ☐ | SV-207108r1137907_rule | The perimeter router must be configured to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy. |
| ☐ | SV-207109r1137908_rule | The multicast router must be configured to disable Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing. |
| ☐ | SV-207110r1137911_rule | The multicast router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled. |
| ☐ | SV-207111r1137912_rule | The multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic. |
| ☐ | SV-207112r1137913_rule | The router must be configured to have all inactive interfaces disabled. |
| ☐ | SV-207113r1137916_rule | The 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 site's address space. |
| ☐ | SV-207114r1137919_rule | The perimeter router must be configured to not be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider. |
| ☐ | SV-207115r1137922_rule | The perimeter router must be configured to not redistribute static routes to an alternate gateway service provider into Border Gateway Protocol (BGP) or an Interior Gateway Protocol (IGP) peering with the NIPRNet or to other autonomous systems. |
| ☐ | SV-207116r1137925_rule | The out-of-band management (OOBM) gateway router must be configured to have separate Interior Gateway Protocol (IGP) instances for the managed network and management network. |
| ☐ | SV-207117r1137928_rule | The out-of-band management (OOBM) gateway router must be configured to not redistribute routes between the management network routing domain and the managed network routing domain. |
| ☐ | SV-207118r1137930_rule | The multicast Rendezvous Point (RP) router must be configured to filter Protocol Independent Multicast (PIM) Register messages received from the Designated Router (DR) for any undesirable multicast groups and sources. |
| ☐ | SV-207119r1137932_rule | The multicast Rendezvous Point (RP) router must be configured to filter Protocol Independent Multicast (PIM) Join messages received from the Designated Router (DR) for any undesirable multicast groups. |
| ☐ | SV-207120r604135_rule | The router must be configured to produce audit records containing information to establish where the events occurred. |
| ☐ | SV-207121r604135_rule | The router must be configured to produce audit records containing information to establish the source of the events. |
| ☐ | SV-207122r604135_rule | The router must be configured to log all packets that have been dropped. |
| ☐ | SV-207123r604135_rule | The router must be configured to have all non-essential capabilities disabled. |
| ☐ | SV-207124r604135_rule | The router must be configured to use encryption for routing protocol authentication. |
| ☐ | SV-207125r604135_rule | The router must be configured to authenticate all routing protocol messages using NIST-validated FIPS 198-1 message authentication code algorithm. |
| ☐ | SV-207126r604135_rule | The PE router must be configured to limit the number of MAC addresses it can learn for each Virtual Private LAN Services (VPLS) bridge domain. |
| ☐ | SV-207127r604135_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-207128r604135_rule | The PE router providing Virtual Private LAN Services (VPLS) must be configured to have traffic storm control thresholds on CE-facing interfaces. |
| ☐ | SV-207129r604135_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-207130r604135_rule | The PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS DoDIN Technical Profile. |
| ☐ | SV-207131r604135_rule | The P router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile. |
| ☐ | SV-207132r1137935_rule | The perimeter router must be configured to deny network traffic by default and allow network traffic by exception. |
| ☐ | SV-207133r604135_rule | The router must be configured to restrict traffic destined to itself. |
| ☐ | SV-207134r604135_rule | The router must be configured to drop all fragmented Internet Control Message Protocol (ICMP) packets destined to itself. |
| ☐ | SV-207135r604135_rule | The perimeter router must be configured to filter traffic destined to the enclave in accordance with the guidelines contained in DoD Instruction 8551.1. |
| ☐ | SV-207136r604135_rule | The perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction. |
| ☐ | SV-207137r604135_rule | The perimeter router must be configured to filter egress traffic at the internal interface on an inbound direction. |
| ☐ | SV-207138r604135_rule | The BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core. |
| ☐ | SV-207139r604135_rule | The PE router must be configured to block any traffic that is destined to IP core infrastructure. |
| ☐ | SV-207140r604135_rule | The PE router must be configured with Unicast Reverse Path Forwarding (uRPF) loose mode enabled on all CE-facing interfaces.. |
| ☐ | SV-207141r604135_rule | The out-of-band management (OOBM) gateway must be configured to transport management traffic to the Network Operations Center (NOC) via dedicated circuit, MPLS/VPN service, or IPsec tunnel. |
| ☐ | SV-207142r604135_rule | The out-of-band management (OOBM) gateway router must be configured to forward only authorized management traffic to the Network Operations Center (NOC). |
| ☐ | SV-207143r604135_rule | The out-of-band management (OOBM) gateway router must be configured to block any traffic destined to itself that is not sourced from the OOBM network or the NOC. |
| ☐ | SV-207144r604135_rule | The router must be configured to only permit management traffic that ingresses and egresses the OOBM interface. |
| ☐ | SV-207145r604135_rule | The router providing connectivity to the NOC must be configured to forward all in-band management traffic via an IPsec tunnel. |
| ☐ | SV-207146r604135_rule | The router must be configured to stop forwarding traffic upon the failure of the following actions: system initialization, shutdown, or system abort. |
| ☐ | SV-207147r856631_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-207148r856632_rule | The Multicast Source Discovery Protocol (MSDP) router must be configured to authenticate all received MSDP packets. |
| ☐ | SV-207149r856633_rule | The router must not be configured to have any zero-touch deployment feature enabled when connected to an operational network. |
| ☐ | SV-207150r856634_rule | The router must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection. |
| ☐ | SV-207151r856635_rule | The router must be configured to have Gratuitous ARP disabled on all external interfaces. |
| ☐ | SV-207152r856636_rule | The router must be configured to have IP directed broadcast disabled on all interfaces. |
| ☐ | SV-207153r856637_rule | The router must be configured to have Internet Control Message Protocol (ICMP) unreachable notifications disabled on all external interfaces. |
| ☐ | SV-207154r856638_rule | The router must be configured to have Internet Control Message Protocol (ICMP) mask replies disabled on all external interfaces. |
| ☐ | SV-207155r856639_rule | The router must be configured to have Internet Control Message Protocol (ICMP) redirects disabled on all external interfaces. |
| ☐ | SV-207156r856640_rule | The BGP router must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks. |
| ☐ | SV-207157r856641_rule | The 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-207158r856642_rule | The PE router must be configured to implement Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) snooping for each Virtual Private LAN Services (VPLS) bridge domain. |
| ☐ | SV-207159r856643_rule | The multicast Rendezvous Point (RP) 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-207160r856644_rule | The multicast Rendezvous Point (RP) must be configured to rate limit the number of Protocol Independent Multicast (PIM) Register messages. |
| ☐ | SV-207161r856645_rule | The multicast Designated Router (DR) must be configured to limit the number of mroute states resulting from Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Host Membership Reports. |
| ☐ | SV-207162r945856_rule | The 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-207163r856646_rule | The perimeter router must be configured to only allow incoming communications from authorized sources to be routed to authorized destinations. |
| ☐ | SV-207164r856649_rule | The perimeter router must be configured to block inbound packets with source Bogon IP address prefixes. |
| ☐ | SV-207165r856650_rule | The perimeter router must be configured to have Link Layer Discovery Protocols (LLDPs) disabled on all external interfaces. |
| ☐ | SV-207166r856651_rule | The perimeter router must be configured to have Proxy ARP disabled on all external interfaces. |
| ☐ | SV-207167r945857_rule | The perimeter router must be configured to block all outbound management traffic. |
| ☐ | SV-207168r856652_rule | The 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-207169r856653_rule | The 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-207170r856654_rule | The Multicast Source Discovery Protocol (MSDP) router must be configured to only accept MSDP packets from known MSDP peers. |
| ☐ | SV-207171r1137965_rule | The router must be configured to fail securely in the event of an operational failure. |
| ☐ | SV-207172r604135_rule | The BGP router must be configured to use its loopback address as the source address for iBGP peering sessions. |
| ☐ | SV-207173r604135_rule | The MPLS router must be configured to use its loopback address as the source address for LDP peering sessions. |
| ☐ | SV-207174r604135_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-207175r604135_rule | The MPLS router must be configured to have TTL Propagation disabled. |
| ☐ | SV-207176r604135_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-207177r604135_rule | The PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Target (RT). |
| ☐ | SV-207178r604135_rule | The PE router must be configured to have each VRF with the appropriate Route Distinguisher (RD). |
| ☐ | SV-207179r604135_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-207180r604135_rule | The PE router providing Virtual Private LAN Services (VPLS) must be configured to have all attachment circuits defined to the virtual forwarding instance (VFI) with the globally unique VPN ID assigned for each customer VLAN. |
| ☐ | SV-207181r604135_rule | The PE router must be configured to enforce the split-horizon rule for all pseudowires within a Virtual Private LAN Services (VPLS) bridge domain. |
| ☐ | SV-207182r604135_rule | The Multicast Source Discovery Protocol (MSDP) router must be configured to use its loopback address as the source address when originating MSDP traffic. |
| ☐ | SV-216506r604135_rule | The router must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
| ☐ | SV-216978r856655_rule | The router must not be configured to have any feature enabled that calls home to the vendor. |
| ☐ | SV-216979r945858_rule | The 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-216980r945859_rule | The perimeter router must be configured to block all packets with any IP options. |
| ☐ | SV-216981r945860_rule | The PE router must be configured to ignore or block all packets with any IP options. |
| ☐ | SV-216982r945861_rule | The router must be configured to implement message authentication for all control plane protocols. |
| ☐ | SV-216983r945862_rule | The BGP router must be configured to use a unique key for each autonomous system (AS) that it peers with. |
| ☐ | SV-216984r945863_rule | The router must be configured to use keys with a duration not exceeding 180 days for authenticating routing protocol messages. |
| ☐ | SV-216985r856661_rule | The BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM). |
| ☐ | SV-220144r604135_rule | The router must be configured to advertise a hop limit of at least 32 in Router Advertisement messages for IPv6 stateless auto-configuration deployments. |
| ☐ | SV-220145r604135_rule | The router must not be configured to use IPv6 Site Local Unicast addresses. |
| ☐ | SV-220146r604135_rule | The perimeter router must be configured to suppress Router Advertisements on all external IPv6-enabled interfaces. |
| ☐ | SV-220147r950991_rule | The perimeter router must be configured to drop IPv6 undetermined transport packets. |
| ☐ | SV-220148r856665_rule | The perimeter router must be configured drop IPv6 packets with a Routing Header type 0, 1, or 3255. |
| ☐ | SV-220149r856667_rule | The perimeter router must be configured to drop IPv6 packets containing a Hop-by-Hop header with invalid option type values. |
| ☐ | SV-220150r856669_rule | The perimeter router must be configured to drop IPv6 packets containing a Destination Option header with invalid option type values. |
| ☐ | SV-220151r856671_rule | The perimeter router must be configured to drop IPv6 packets containing an extension header with the Endpoint Identification option. |
| ☐ | SV-220152r856673_rule | The perimeter router must be configured to drop IPv6 packets containing the NSAP address option within Destination Option header. |
| ☐ | SV-220153r856675_rule | The perimeter router must be configured to drop IPv6 packets containing a Hop-by-Hop or Destination Option extension header with an undefined option type. |
| ☐ | SV-264309r984168_rule | The router must employ organization-defined controls by type of denial of service (DoS) to achieve the DoS objective. |
| ☐ | SV-264310r1137936_rule | The router must implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions. |
| ☐ | SV-264311r984174_rule | The router must establish organization-defined alternate communications paths for system operations organizational command and control. |
| ☐ | SV-278997r1137939_rule | The router must dynamically associate security attributes with organization-defined subjects in accordance with organization-defined security policies as information is created and combined. |
| ☐ | SV-278998r1137942_rule | The router must validate the integrity of transmitted security attributes. |
| ☐ | SV-278999r1137945_rule | The router must enforce information flow control based on organization-defined metadata. |
| ☐ | SV-279000r1137948_rule | The router must use organization-defined security attributes associated with organization-defined information, source, and destination objects to enforce organization-defined information flow control policies as a basis for flow control decisions. |
| ☐ | SV-279001r1137951_rule | When transferring information between different security domains, the router must use organization-defined data type identifiers to validate data essential for information flow decisions. |
| ☐ | SV-279002r1137954_rule | The router must uniquely identify and authenticate source by organization, system, application, and/or individual for information transfer. |
| ☐ | SV-279003r1137957_rule | The router must uniquely identify and authenticate destination by organization, system, application, and/or individual for information transfer. |
| ☐ | SV-279004r1137960_rule | When transferring information between different security domains, the router must apply the same security policy filtering to metadata as it applies to data payloads. |
| ☐ | SV-279005r1137963_rule | The router must use cryptographic algorithms approved by NSA to protect NSS when transporting classified traffic across an unclassified network. |
| ☐ | SV-279006r1137968_rule | The router must implement cryptographic mechanisms to prevent unauthorized disclosure of information and/or detect changes to information during transmission. |
| ☐ | SV-279007r1137971_rule | The router must use a FIPS-validated cryptographic module to generate cryptographic hashes. |
| ☐ | SV-279008r1137974_rule | The router must dynamically associate security attributes with organization-defined objects in accordance with organization-defined security policies as information is created and combined. |
| ☐ | SV-279009r1137977_rule | The router must be configured to use cryptographic algorithms approved by NSA to protect NSS for remote access to a classified network. |
| ☐ | SV-279010r1137980_rule | The router must use a FIPS-validated cryptographic module to provision digital signatures. |
| ☐ | SV-279011r1137983_rule | The router must use a FIPS-validated cryptographic module to implement encryption services for unclassified information requiring confidentiality. |
STIGQter: STIG Summary: