Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
This requirement is not applicable for the DoDIN Backbone. Review the router configuration to verify that firewall filters are configured to allow or deny traffic for specific source and destination addresses as well as ports and protocols. For example, the configuration below will allow only printer traffic into subnet 11.1.23.0/24 and SQL traffic into subnet 11.1.24.0/24. ICMP is allowed for troubleshooting and OSPF is the routing protocol used within the network. interfaces { ge-0/0/0 { unit 0 { family inet { filter { input FILTER_SERVER_TRAFFIC; } address 11.1.12.2/24; } } } … … … firewall { family inet { filter FILTER_SERVER_TRAFFIC { term PRINT_FILTER { from { destination-address { 11.1.23.0/24; } protocol tcp; destination-port [ 515 631 9100 ]; } then accept; } term SQL_FILTER { from { destination-address { 11.1.24.0/24; } protocol tcp; destination-port [ 1433 1434 4022 ]; } then accept; } term ALLOW_OSPF { from { protocol ospf; } then accept; } term ALLOW_ICMP { from { protocol icmp; } then accept; } term DENY_ALL_OTHER { then { log; syslog; reject; } } } If the router is not configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure firewall filters to allow or deny traffic for specific source and destination addresses as well as ports and protocols between various subnets as required. The commands used below were used to create the configuration as shown in the check content. [edit firewall family inet] set filter FILTER_SERVER_TRAFFIC term PRINT_FILTER from destination-address 11.1.23.0/24 set filter FILTER_SERVER_TRAFFIC term PRINT_FILTER from protocol tcp destination-port [515 631 9100] set filter FILTER_SERVER_TRAFFIC term PRINT_FILTER then accept set filter FILTER_SERVER_TRAFFIC term SQL_FILTER from destination-address 11.1.24.0/24 set filter FILTER_SERVER_TRAFFIC term SQL_FILTER from protocol tcp destination-port [1433 1434 4022] set filter FILTER_SERVER_TRAFFIC term SQL_FILTER then accept set filter FILTER_SERVER_TRAFFIC term ALLOW_OSPF from protocol ospf set filter FILTER_SERVER_TRAFFIC term ALLOW_OSPF then accept set filter FILTER_SERVER_TRAFFIC term ALLOW_ICMP from protocol icmp set filter FILTER_SERVER_TRAFFIC term ALLOW_ICMP then accept set filter FILTER_SERVER_TRAFFIC term DENY_ALL_OTHER then log reject [edit interfaces ge-0/0/0 unit 0 family inet] set filter input FILTER_SERVER_TRAFFIC
Review the router configuration. Verify that neighbor router authentication is enabled for all routing protocols as shown in the example configuration below. protocols { bgp { group AS_5 { type external; peer-as 5; neighbor x.x.x.x { authentication-key "$8$tBga0ORx7VsYoIEgJ"; ## SECRET-DATA } } } ospf { area 0.0.0.0 { interface ge-0/0/0.0 { authentication { simple-password "$8$NHVb2mPQ3nCYg/t"; ## SECRET-DATA } } interface ge-0/1/0.0 { authentication { simple-password "$8$Lgb7NbHkPTQnVwF/"; ## SECRET-DATA } } interface lo0.0; interface ge-0/2/0.0 { authentication { simple-password "$8$7DdVY.mTF39s26A"; ## SECRET-DATA } } } } isis { level 1 { authentication-key "$8$n2OT9CuvMXN-wp0VY"; ## SECRET-DATA authentication-type md5; } level 2 { authentication-key "$8$8G9x7ViHm5T3dbz6"; ## SECRET-DATA authentication-type md5; } interface ge-0/0/0.0; interface ge-0/0/1.0; } ldp { interface ge-0/0/0.0; interface ge-0/0/1.0; session 10.3.3.3 { authentication-key "$8$3hus/u1ylMNVYX7qf"; ## SECRET-DATA } session 10.1.2.2 { authentication-key "$8$Qq0I3nCrlMLX-9A7V"; ## SECRET-DATA } } rip { authentication-type md5; authentication-key "$8$34fM/u1ylMNVYX7qf"; ## SECRET-DATA group RIP_GROUP { neighbor ge-1/0/1.0; } } } If authentication is not enabled for all control plane protocols, this is a finding.
Configure authentication to be enabled for all control plane protocols as shown in the example below. [edit protocols ospf area 0.0.0.0] set interface ge-0/0/0 authentication simple-password xxxxxxxxxxxx set interface ge-0/1/0 authentication simple-password xxxxxxxxxxxx set interface ge-0/2/0 authentication simple-password xxxxxxxxxxxx [edit protocols isis] set level 1 authentication-type md5 set level 1 authentication-key xxxxxxxx set level 2 authentication-type md5 set level 2 authentication-key xxxxxxxx [edit protocols rip] set authentication-type md5 set authentication-key xxxxxxxx [edit protocols bgp group AS_2 neighbor x.x.x.x] set authentication-key xxxxxxxxxxxxxxx [edit protocols ldp] set session 10.1.2.2 authentication-key xxxxxxxxxx
This requirement is not applicable for the DoDIN Backbone. Review the start times for each key within the configured key chains used for routing protocol authentication as shown in the examples below. security { … … … authentication-key-chains { key-chain BGP_KEY { key 1 { secret "$8$PTQnhclvMX3687"; ## SECRET-DATA start-time "2018-5-1.12:00:00 +0000"; } key 2 { secret "$8$iq.5OBESyKfTlM"; ## SECRET-DATA start-time "2018-9-1.12:00:00 +0000"; } key 3 { secret "$8$ZADjqAtOIRSk.hr"; ## SECRET-DATA start-time "2019-1-1.12:00:00 +0000"; } } } } ospf { area 0.0.0.0 { interface ge-0/0/0.0 { authentication { md5 1 key "$8$P5T36/t0ORDi.5F3tp" start-time "2018-1-1.01:01:00 +0000"; ## SECRET-DATA md5 2 key "$8$S.oevLbwg4aUvWxn" start-time "2018-4-1.01:01:00 +0000"; ## SECRET-DATA md5 3 key "$8$SInrWxbO1hcYg4ajH" start-time "2018-8-1.01:01:00 +0000"; ## SECRET-DATA } } } } If each key used for routing protocol authentication does not have a lifetime of no more than 180 days, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure each key used for routing protocol authentication to have a lifetime of no more than 180 days as shown in the example below. [edit security authentication-key-chains] set key-chain BGP_KEY key 1 start-time 2018-05-01.12:00 secret xxxxxxxxxxxxx set key-chain BGP_KEY key 2 start-time 2018-09-01.12:00 secret xxxxxxxxxxxxx set key-chain BGP_KEY key 3 start-time 2019-01-01.12:00 secret xxxxxxxxxxxxx } [edit protocols ospf area 0.0.0.0 interface ge-0/0/0.0] set authentication md5 1 key xxxxxxxx start-time 2018-01-01.01:01 set authentication md5 2 key xxxxxxxx start-time 2018-04-01.01:01 set authentication md5 3 key xxxxxxxx start-time 2018-08-01.01:01 Note: Currently Junos does not support key chains for RIP.
Review the router configuration. For every routing protocol that affects the routing or forwarding tables, verify that neighbor router authentication is encrypting the authentication key as shown in the examples below. OSPF Example: protocols { … … … ospf { area 0.0.0.0 { interface ge-0/0/0 { authentication { md5 1 key "$8$NHVb2mPQ3nCYg/t"; ## SECRET-DATA } } interface ge-0/1/0 { authentication { md5 1 key "$8$Lgb7NbHkPTQnVwF/"; ## SECRET-DATA } } interface lo0.0; interface ge-0/2/0 { authentication { md5 1 key "$8$7DdVY.mTF39s26A"; ## SECRET-DATA } } } } } IS-IS Example: security { … … … } authentication-key-chains { key-chain ISIS_KEY { key 1 { secret "$8$W8oXxdji.f5F-VQn"; ## SECRET-DATA start-time "2018-5-1.12:00:00 +0000"; algorithm hmac-sha-1; options isis-enhanced; } key 2 { secret "$8$Q4953nCrlMLX-9A7V"; ## SECRET-DATA start-time "2018-9-1.12:00:00 +0000"; algorithm hmac-sha-1; options isis-enhanced; } key 3 { secret "$8$UeiHmpu1Ehr.PSe"; ## SECRET-DATA start-time "2019-1-1.12:00:00 +0000"; algorithm hmac-sha-1; options isis-enhanced; } } } } protocols { … … … isis { level 1 authentication-key-chain ISIS_KEY; level 2 authentication-key-chain ISIS_KEY; interface ge-0/0/0 { level 1 hello-authentication-key-chain ISIS_KEY; level 2 hello-authentication-key-chain ISIS_KEY; } interface lo0.0; } BGP Example: security { … … … } authentication-key-chains { key-chain BGP_KEY { key 1 { secret "$8$PTQnhclvMX3687"; ## SECRET-DATA start-time "2018-5-1.12:00:00 +0000"; } key 2 { secret "$8$iq.5OBESyKfTlM"; ## SECRET-DATA start-time "2018-9-1.12:00:00 +0000"; } key 3 { secret "$8$ZADjqAtOIRSk.hr"; ## SECRET-DATA start-time "2019-1-1.12:00:00 +0000"; } } protocols { bgp { group AS_2 { type external; peer-as 2; neighbor 11.1.25.2 { authentication-algorithm md5; authentication-key-chain BGP_KEY; } neighbor 11.1.1.1 { authentication-algorithm hmac-sha-1-96; authentication-key-chain BGP_KEY; } } } If the routing protocol is not encrypting the authentication key, this is a finding.
Configure all routing protocol authentications to encrypt the authentication key. OSPF Example: [edit protocols ospf area 0.0.0.0] set interface ge-0/0/0 authentication md5 1 key xxxxxxxxxxxx set interface ge-0/1/0 authentication md5 1 key xxxxxxxxxxxx set interface ge-0/2/0 authentication md5 1 key xxxxxxxxxxxx IS-IS Example: [edit security authentication-key-chains] set key-chain ISIS_KEY key 1 options isis-enhanced set key-chain ISIS_KEY key 2 options isis-enhanced set key-chain ISIS_KEY key 3 options isis-enhanced set key-chain ISIS_KEY key 1 start-time 2018-05-01.12:00 algorithm hmac-sha-1 secret xxxxxxxxxxxxx set key-chain ISIS_KEY key 2 start-time 2018-09-01.12:00 algorithm hmac-sha-1 secret xxxxxxxxxxxxx set key-chain ISIS_KEY key 3 start-time 2019-01-01.12:00 algorithm hmac-sha-1 secret xxxxxxxxxxxxx [edit protocols] set isis level 1 authentication-key-chain ISIS_KEY set isis interface ge-0/0/0 level 1 hello-authentication-key-chain ISIS_KEY set isis interface ge-0/0/0 level 2 hello-authentication-key-chain ISIS_KEY BGP Example: [edit security authentication-key-chains] set key-chain BGP_KEY key 1 start-time 2018-05-01.12:00 secret xxxxxxxxxxxxx set key-chain BGP_KEY key 2 start-time 2018-09-01.12:00 secret xxxxxxxxxxxxx set key-chain BGP_KEY key 3 start-time 2019-01-01.12:00 secret xxxxxxxxxxxxx [edit protocols bgp group AS_5] set neighbor 11.1.25.5 authentication-algorithm hmac-sha-1-96 set neighbor 11.1.25.5 authentication-key-chain BGP_KEY set neighbor 11.1.1.1 authentication-algorithm hmac-sha-1-96 set neighbor 11.1.1.1 authentication-key-chain BGP_KEY
Review the router configuration to verify it is using a NIST-validated FIPS 140-2 message authentication code algorithm to authenticate routing protocol messages. IS-IS Example: security { … … … } authentication-key-chains { key-chain ISIS_KEY { key 1 { secret "$8$W8oXxdji.f5F-VQn"; ## SECRET-DATA start-time "2018-5-1.12:00:00 +0000"; algorithm hmac-sha-1; options isis-enhanced; } key 2 { secret "$8$Q4953nCrlMLX-9A7V"; ## SECRET-DATA start-time "2018-9-1.12:00:00 +0000"; algorithm hmac-sha-1; options isis-enhanced; } key 3 { secret "$8$UeiHmpu1Ehr.PSe"; ## SECRET-DATA start-time "2019-1-1.12:00:00 +0000"; algorithm hmac-sha-1; options isis-enhanced; } } } } protocols { … … … isis { level 1 authentication-key-chain ISIS_KEY; level 2 authentication-key-chain ISIS_KEY; interface ge-0/0/0 { level 1 hello-authentication-key-chain ISIS_KEY; level 2 hello-authentication-key-chain ISIS_KEY; } interface lo0.0; } BGP Example: } security { … … … } authentication-key-chains { key-chain BGP_KEY { key 1 { secret "$8$PTQnhclvMX3687"; ## SECRET-DATA start-time "2018-5-1.12:00:00 +0000"; } key 2 { secret "$8$iq.5OBESyKfTlM"; ## SECRET-DATA start-time "2018-9-1.12:00:00 +0000"; } key 3 { secret "$8$ZADjqAtOIRSk.hr"; ## SECRET-DATA start-time "2019-1-1.12:00:00 +0000"; } } protocols { bgp { group AS_2 { type external; peer-as 2; neighbor 11.1.25.2 { authentication-algorithm hmac-sha-1-96; authentication-key-chain BGP_KEY; } neighbor 11.1.1.1 { authentication-algorithm hmac-sha-1-96; authentication-key-chain BGP_KEY; } } } OSPF Example: IPsec authentication must be used to authenticate OSPF messages with a FIPS 140-2 message authentication code algorithm. Step 1: Verify the authentication algorithm in the IPsec security association as shown in the example below. security { … … … ipsec { security-association IPSEC-SA1 { mode transport; manual { direction bidirectional { protocol ah; spi 256; authentication { algorithm hmac-sha1-96; key ascii-text "$8$u6M6OEcrevL7-YaZUjHmF39B1hP5CuBRle"; ## SECRET-DATA } } } } } Step 2: Verify that an IPsec security association has been configured on the interfaces as shown in the following example: protocols { … … … ospf { area 0.0.0.0 { interface ge-0/0/0 { ipsec-sa IPSEC-SA1; } interface ge-0/1/0 { ipsec-sa IPSEC-SA1; } interface lo0.0; interface ge-0/2/0 { ipsec-sa IPSEC-SA1; } } } ospf3 { area 0.0.0.0 { interface ge-1/2/0 { ipsec-sa IPSEC-SA1; } } } } If a NIST-validated FIPS 140-2 message authentication code algorithm is not being used to authenticate routing protocol messages, this is a finding. Note: Juniper does not support FIPS 140-2 message authentication code algorithm for RIP.
Configure routing protocol authentication to use a NIST-validated FIPS 140-2 message authentication code algorithm. IS-IS Example: [edit security authentication-key-chains] set key-chain ISIS_KEY key 1 options isis-enhanced set key-chain ISIS_KEY key 2 options isis-enhanced set key-chain ISIS_KEY key 3 options isis-enhanced set key-chain ISIS_KEY key 1 start-time 2018-05-01.12:00 algorithm hmac-sha-1 secret xxxxxxxxxxxxx set key-chain ISIS_KEY key 2 start-time 2018-09-01.12:00 algorithm hmac-sha-1 secret xxxxxxxxxxxxx set key-chain ISIS_KEY key 3 start-time 2019-01-01.12:00 algorithm hmac-sha-1 secret xxxxxxxxxxxxx [edit protocols] set isis level 1 authentication-key-chain ISIS_KEY set isis interface ge-0/0/0 level 1 hello-authentication-key-chain ISIS_KEY set isis interface ge-0/0/0 level 2 hello-authentication-key-chain ISIS_KEY BGP Example: [edit security authentication-key-chains] set key-chain BGP_KEY key 1 start-time 2018-05-01.12:00 secret xxxxxxxxxxxxx set key-chain BGP_KEY key 2 start-time 2018-09-01.12:00 secret xxxxxxxxxxxxx set key-chain BGP_KEY key 3 start-time 2019-01-01.12:00 secret xxxxxxxxxxxxx [edit protocols bgp group AS_5] set neighbor 11.1.25.5 authentication-algorithm hmac-sha-1-96 set neighbor 11.1.25.5 authentication-key-chain BGP_KEY set neighbor 11.1.1.1 authentication-algorithm hmac-sha-1-96 set neighbor 11.1.1.1 authentication-key-chain BGP_KEY OSPF Example: Configure IPsec Security Association [edit security ipsec] set security-association IPSEC-SA1 set security-association IPSEC-SA1 mode transport set security-association IPSEC-SA1 manual direction bidirectional set security-association IPSEC-SA1 manual direction bidirectional protocol ah set security-association IPSEC-SA1 manual direction bidirectional spi 256 set security-association IPSEC-SA1 manual direction bidirectional authentication algorithm hmac-sha1-96 key ascii-text 1234567890abcdefghij [edit protocols ospf area 0.0.0.0] set interface ge-0/0/0 ipsec-sa IPSEC-SA1 set interface ge-0/1/0 ipsec-sa IPSEC-SA1 set interface ge-0/2/0 ipsec-sa IPSEC-SA1 [edit protocols ospf area 0.0.0.0] set interface ge-1/2/0 ipsec-sa IPSEC-SA1
Review the router configuration and verify that inactive interfaces have been disabled as shown below. interfaces { ge-1/1/0 { disable; unit 0 { } } If an interface is not being used but is configured or enabled, this is a finding.
Disable all inactive interfaces as shown below. [edit interfaces] set ge-1/1/0 disable
Review the router configuration to determine if services not required for operation are enabled. Services such as finger, ftp, telnet must never be enabled; hence, they should not be shown under the system services hierarchy. If J-web is not used for administrative access, the web-management services must not be configured as shown below. If DHCP server is not being deployed on the router, the command dhcp-local-server must not be configured as shown below. system { … … … services { web-management { https { interface ge-0/0/0.0; } } finger; ftp; ssh { protocol-version v2; macs [ hmac-sha1-96 hmac-sha2-256 hmac-sha2-512 ]; } telnet; netconf { ssh; } dhcp-local-server { group DHCP_GROUP { interface ge-0/1/0.0; } } } If unnecessary services and functions are enabled on the router, this is a finding.
Remove unneeded services and functions from the router as shown below. [edit system services] delete telnet [edit system services] delete finger [edit system services] delete ftp
Determine whether control plane protection has been implemented on the router. Verify that a CoPP policy has been configured that classifies traffic types into levels of importance. firewall { family inet { … … … } filter CoPP_Policy { term CRITICAL { from { protocol [ ospf pim tcp ]; source-port bgp; destination-port bgp; } then policer CRITICAL_POLICER; } term IMPORTANT { from { protocol [ tcp udp ]; destination-port [ ssh tacacs snmp ntp ]; } then { policer IMPORTANT_POLICER; } } term NORMAL { from { protocol icmp; icmp-type [ echo-reply echo-request ]; icmp-code [ port-unreachable ttl-eq-zero-during-transit ]; } then policer NORMAL_POLICER; } term UNDESIRABLE { from { protocol udp; } then policer UNDESIRABLE_POLICER; } term ALL-OTHER { from { address { 0.0.0.0/0; } } then policer ALL-OTHER_POLICER; } } } Verify that policers have been configured to rate limit traffic types. firewall { family inet { … … … } policer CRITICAL_POLICER { filter-specific; if-exceeding { bandwidth-limit 3m; burst-size-limit 4k; } then discard; } policer IMPORTANT_POLICER { filter-specific; if-exceeding { bandwidth-limit 400k; burst-size-limit 1500; } then discard; } policer NORMAL_POLICER { filter-specific; if-exceeding { bandwidth-limit 55k; burst-size-limit 1500; } then discard; } policer UNDESIRABLE_POLICER { filter-specific; if-exceeding { bandwidth-limit 32k; burst-size-limit 1500; } then discard; } policer ALL-OTHER_POLICER { filter-specific; if-exceeding { bandwidth-limit 40k; burst-size-limit 1500; } then discard; } Verify that the CoPP policy has been applied to the loopback interface as shown in the example below. interfaces { … … … lo0 { unit 0 { family inet { filter { input CoPP_Policy; } address 2.2.2.2/32; } } } } Note: Several Juniper router platforms provide a DDoS Protection feature that is configured at the system hierarchy via set ddos-protection commands. If the router does not have control plane protection implemented, this is a finding.
Implement control plane protection by classifying traffic types based on importance and rate limit the traffic accordingly as shown in the example below. Create filters for critical, important, normal, and undesirable traffic. set firewall filter CoPP_Policy term CRITICAL from protocol ospf set firewall filter CoPP_Policy term CRITICAL from protocol pim set firewall filter CoPP_Policy term CRITICAL from protocol tcp destination-port bgp set firewall filter CoPP_Policy term CRITICAL from protocol tcp source-port bgp set firewall filter CoPP_Policy term CRITICAL then policer CRITICAL_POLICER set firewall filter CoPP_Policy term IMPORTANT from protocol tcp destination-port ssh set firewall filter CoPP_Policy term IMPORTANT from protocol tcp destination-port tacacs set firewall filter CoPP_Policy term IMPORTANT from protocol tcp destination-port snmp set firewall filter CoPP_Policy term IMPORTANT from protocol tcp destination-port ntp set firewall filter CoPP_Policy term IMPORTANT then policer IMPORTANT_POLICER set firewall filter CoPP_Policy term NORMAL from protocol icmp icmp-code ttl-eq-zero-during-transit set firewall filter CoPP_Policy term NORMAL from protocol icmp icmp-code port-unreachable set firewall filter CoPP_Policy term NORMAL from protocol icmp icmp-type echo-reply set firewall filter CoPP_Policy term NORMAL from protocol icmp icmp-type echo-request set firewall filter CoPP_Policy term NORMAL then policer NORMAL_POLICER set firewall filter CoPP_Policy term UNDESIRABLE from protocol udp set firewall filter CoPP_Policy term UNDESIRABLE then policer UNDESIRABLE_POLICER set firewall filter CoPP_Policy term ALL-OTHER from address 0.0.0.0/0 set firewall filter CoPP_Policy term ALL-OTHER then policer ALL-OTHER_POLICER Create policers for each traffic type to limit bandwidth. set firewall policer CRITICAL_POLICER filter-specific set firewall policer CRITICAL_POLICER if-exceeding bandwidth-limit 3000000 burst-size-limit 4000 set firewall policer CRITICAL_POLICER then discard set firewall policer IMPORTANT_POLICER filter-specific set firewall policer IMPORTANT_POLICER if-exceeding bandwidth-limit 400000 burst-size-limit 1500 set firewall policer IMPORTANT_POLICER then discard set firewall policer NORMAL_POLICER filter-specific set firewall policer NORMAL_POLICER if-exceeding bandwidth-limit 55000 burst-size-limit 150000 set firewall policer NORMAL_POLICER then discard set firewall policer UNDESIRABLE_POLICER filter-specific set firewall policer UNDESIRABLE_POLICER if-exceeding bandwidth-limit 32000 burst-size-limit 1500 set firewall policer UNDESIRABLE_POLICER then discard set firewall policer ALL-OTHER_POLICER filter-specific set firewall policer ALL-OTHER_POLICER if-exceeding bandwidth-limit 40000 burst-size-limit 1500 set firewall policer ALL-OTHER_POLICER then discard Apply the CoPP policy to the loopback interface. set interface lo0 unit 0 family inet filter input CoPP_Policy Note: Several Juniper router platforms provide a DDoS Protection feature that is configured at the system hierarchy via set ddos-protection commands.
Review the filter for the router’s receive path and verify that it will only allow specific management plane traffic from specific sources. Verify filter has been configured as shown in the example below. firewall { family inet { … … … } filter DESTINED_TO_RE { term ALLOW_OSPF { from { protocol ospf; } then accept; } term ALLOW_BGP { from { source-address { 11.1.12.1/32; 11.1.23.3/32; 11.1.25.5/32; } protocol tcp; port bgp; } } term FILTER_TCP { from { destination-address { 11.1.12.0/24; } protocol tcp; destination-port [ ssh tacacs telnet ]; } then accept; } term FILTER_UDP { from { destination-address { 11.1.12.0/24; } protocol udp; destination-port [ntp snmp ]; } then accept; } term ICMP_ANY { from { protocol icmp; } then accept; } term DENY_BY_DEFAULT { then { log; discard; } } } } Verify that the input filter has been applied to loopback interface as shown in the example below. interfaces { … … … lo0 { unit 0 { family inet { filter { input-list [ DESTINED_TO_RE CoPP_Policy ]; } address 2.2.2.2/32; } } } } If the router is not configured with a receive-path filter to restrict traffic destined to itself, this is a finding
Configure the router’s receive path filters to restrict traffic destined to the router. Configure a filter to define what traffic should be received by the Routing Engine. [edit firewall family inet] set filter DESTINED_TO_RP term FILTER_TCP from destination-address 11.1.12.0/24 set filter DESTINED_TO_RP term FILTER_TCP from protocol tcp destination-port ssh set filter DESTINED_TO_RP term FILTER_TCP from protocol tcp destination-port tacacs set filter DESTINED_TO_RP term FILTER_TCP then accept set filter DESTINED_TO_RP term FILTER_UDP from destination-address 11.1.12.0/24 set filter DESTINED_TO_RP term FILTER_UDP from protocol udp destination-port ntp set filter DESTINED_TO_RP term FILTER_UDP from protocol udp destination-port snmp set filter DESTINED_TO_RP term FILTER_UDP then accept set filter DESTINED_TO_RP term ICMP_ANY from protocol icmp set filter DESTINED_TO_RP term ICMP_ANY from protocol icmp then accept set filter DESTINED_TO_RP term DENY_BY_DEFAULT then log discard Apply the filter to the loopback interface. [edit interfaces lo0 unit 0 family inet] set filter input-list DESTINED_TO_RP.
Review the filter that is applied inbound to the loopback interface and verify that it discards fragmented ICMP packets as shown in the example below. firewall { family inet { … … … } filter DESTINED_TO_RE { … … … } term BLOCK_ICMP_FRAG { from { is-fragment; protocol icmp; } then { discard; } } term ICMP_ANY { from { protocol icmp; } then accept; } term DENY_BY_DEFAULT { then { log; discard; } } } } If the router is not configured to filter to drop all fragmented ICMP packets destined to itself, this is a finding.
Configure the filter that is applied inbound to the loopback interface to drop all fragmented ICMP packets as shown in the example below. [edit firewall family inet filter DESTINED_TO_RP] set term BLOCK_ICMP_FRAG from protocol icmp is-fragment set term BLOCK_ICMP_FRAG then discard insert term BLOCK_ICMP_FRAG before term DENY_BY_DEFAULT
Review the configuration to determine if gratuitous ARP is disabled on all external interfaces. The following command should not be set to any interface: gratuitous-arp-reply If gratuitous ARP is enabled on any external interface, this is a finding.
Disable gratuitous ARP on all external interfaces using the following command. [edit interfaces ge-1/1/0 ] delete gratuitous-arp-reply
Review the firewall hierarchy configuration to verify that all packets that are not permitted are silently dropped using the discard parameter as shown in the configuration example below. firewall { family inet { … … … } filter FILTER_INBOUND { term ALLOW_XYZ { from { protocol xyz; } then accept; } … … … } term DENY_BY_DEFAULT { then { log; discard; } } } } If ICMP unreachable notifications are sent for packets that are dropped, this is a finding.
[edit firewall family inet] set filter FILTER_INBOUND term DENY_BY_DEFAULT then log discard
JUNOS has no interface command to not reply to an ICMP Mask Request message destined to the router. Consequently, to ensure that the router does not send any ICMP Mask Reply message in response to an ICMP Mask Request, include a term statement in the routing engine filter to silently drop any ICMP Masks Requests sent to it as shown in the example below. firewall { family inet { … … … } filter DESTINED_TO_RE { term ALLOW_XYZ { from { protocol xyz; } then accept; } … … … } term DENY_MASK_REQUEST { from { protocol icmp; icmp-type mask-request; } then { discard; } } term ICMP_ANY { from { protocol icmp; } then accept; } term DENY_BY_DEFAULT { then { log; discard; } } } } If the router is not configured to silently drop all ICMP Mask Reply messages destined to the router, this is a finding.
Configure the filter protecting the routing engine to silently drop all ICMP Mask Request messages destined to the router. [edit firewall family inet filter DESTINED_TO_RP] set term DENY_MASK_REQUEST from protocol icmp icmp-type mask-request insert term DENY_MASK_REQUEST before term ALLOW_ICMP
Review the device configuration to determine if it has been configured to ensure the router does not send ICMP Redirect messages out to any external interface. interfaces { ge-1/0/0 { unit 0 { family inet { no-redirects; address 11.1.12.2/24; } } } ge-1/1/0 { unit 0 { family inet { no-redirects; address 11.1.23.2/24; } } } If ICMP Redirect messages are enabled on any external interfaces, this is a finding.
Disable ICMP redirects on all external interfaces as shown in the example below. [edit interfaces] set ge-1/0/0 unit 0 family inet no-redirects set ge-1/1/0 unit 0 family inet no-redirects
Review all filters to verify that packets that are discarded or rejected are logged as shown in the configuration below. firewall { family inet { filter XYZ … … … } term DENY_BY_DEFAULT { then { syslog; discard; } } } } Verify that logging is enabled to capture packets that are dropped as shown in the configuration below. system { host-name XYZ; … … … } syslog { file LOG_FILE { firewall any; } } } Note: The “any” parameter can be configured in lieu of the “firewall” parameter. If packets being dropped are not logged, this is a finding.
Configure the firewall terms that discards or rejects packets to log the action as shown in the example below. [edit firewall family inet] set filter FILTER_INBOUND term DENY_BY_DEFAULT then syslog discard Configure logging to record packets being dropped by firewall filters as shown in the example below. [edit system syslog] set file LOG_FILE firewall any Note: The “any” parameter can be configured in lieu of the “firewall” parameter.
Review the router configuration to verify that events are logged containing information to establish where the events occurred as shown in the example below. system { host-name XYZ; … … … } syslog { file LOG_FILE { any any; } } } If the router is not configured to produce audit records containing information to establish to establish where the events occurred, this is a finding.
Configure the router to log events containing information to establish where the events occurred as shown in the example below. [edit system syslog] set file LOG_FILE any any
Review the router configuration to verify that events are logged containing information to establish where the events occurred as shown in the example below. system { host-name XYZ; … … … } syslog { file LOG_FILE { any any; } } } If the router is not configured to produce audit records containing information to establish the source of the events, this is a finding.
Configure the router to log events containing information to establish where the events occurred as shown in the example below. [edit system syslog] set file LOG_FILE any any
Review the configuration and verify that the auxiliary port is disabled unless a secured modem providing encryption and authentication is connected to it. If the auxiliary port has never been configured or has been removed from the configuration this is Not Applicable. system { host-name XYZ; … … … ports { auxiliary { disable; type xterm; } } If the auxiliary port is not disabled or is not connected to a secured modem when it is enabled, this is a finding.
Disable the auxiliary port. [edit system ports] set auxiliary disable Note: If used for out-of-band administrative access, the port must be connected to a secured modem providing encryption and authentication.
This requirement is not applicable for the DoDIN Backbone. Review the router configuration to verify that the inbound filter applied to all external interfaces is configured to allow specific ports and protocols and deny all other traffic. Verify that an inbound filter is applied to all external interfaces as shown in the example below. interfaces { ge-0/0/0 { unit 0 { family inet { filter { input FILTER_INBOUND_TRAFFIC; } address 11.1.12.2/24; } } } Review inbound filters to verify that the ending term is configured to deny all other traffic that is not explicitly allowed. firewall { family inet { filter FILTER_INBOUND_TRAFFIC { term ALLOW_BGP { from { destination-address { 11.1.24.0/24; } protocol tcp; destination-port bgp; } then accept; } … … … term ALLOW_XYZ { from { protocol xyz; } then accept; } term DENY_ALL_OTHER { then { syslog; discard; } } } If the 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.
This requirement is not applicable for the DoDIN Backbone. Configure a term at the end of the inbound filter to deny all other traffic by default as shown in the example below. [edit firewall family inet] set filter FILTER_INBOUND_TRAFFIC term DENY_ALL_OTHER then syslog discard
This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify that filters are configured to allow or deny traffic for specific source and destination addresses as well as ports and protocols. In the example below, the router is peering BGP with DISN. ICMP echo and echo-reply packets are allowed for troubleshooting connectivity. WWW traffic is permitted inbound to the NIPRnet host-facing web server (x.12.1.22). Step 1: Verify that external interface has an inbound filter configured as shown in the example below: interfaces { ge-0/0/0 { unit 0 { family inet { filter { input FILTER_INBOUND_TRAFFIC; } address x.1.12.2/30; } } } Step 2: Verify that the inbound filter allows only traffic that is to be permitted into the network as shown in the example below: firewall { family inet { filter FILTER_INBOUND_TRAFFIC { term TCP_ESTABLISHED { from { tcp-established; } then accept; } term ALLOW_BGP { from { source-address { x.1.12.1/32; } protocol tcp; destination-port bgp; } then accept; } term ALLOW_PING { from { protocol icmp; icmp-type [ echo-reply echo-request ]; } then accept; } term ALLOW_WWW { from { destination-address { x.12.1.22/32; } protocol tcp; destination-port http; } then accept; } term DENY_ALL_OTHER { then { syslog; reject; } } } } } If the router is not configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies, this is a finding.
This requirement is not applicable for the DODIN Backbone. [edit firewall family inet] set filter FILTER_INBOUND_TRAFFIC term TCP_ESTABLISHED from tcp-established set filter FILTER_INBOUND_TRAFFIC term TCP_ESTABLISHED then accept set filter FILTER_INBOUND_TRAFFIC term ALLOW_BGP from source-address x.1.12.1/32 set filter FILTER_INBOUND_TRAFFIC term ALLOW_BGP from protocol tcp set filter FILTER_INBOUND_TRAFFIC term ALLOW_BGP from destination-port bgp set filter FILTER_INBOUND_TRAFFIC term ALLOW_BGP then accept set filter FILTER_INBOUND_TRAFFIC term ALLOW_PING from protocol icmp set filter FILTER_INBOUND_TRAFFIC term ALLOW_PING from icmp-type echo-reply set filter FILTER_INBOUND_TRAFFIC term ALLOW_PING from icmp-type echo-request set filter FILTER_INBOUND_TRAFFIC term ALLOW_PING then accept set filter FILTER_INBOUND_TRAFFIC term ALLOW_WWW from destination-address x.12.1.22/32 set filter FILTER_INBOUND_TRAFFIC term ALLOW_WWW from protocol tcp set filter FILTER_INBOUND_TRAFFIC term ALLOW_WWW from destination-port http set filter FILTER_INBOUND_TRAFFIC term ALLOW_WWW then accept set filter FILTER_INBOUND_TRAFFIC term DENY_ALL_OTHER then syslog set filter FILTER_INBOUND_TRAFFIC term DENY_ALL_OTHER then reject Step 2: Apply the filter inbound on all applicable interfaces. [edit interfaces ge-0/0/0 unit 0 family inet] set filter input FILTER_INBOUND_TRAFFIC
This requirement is not applicable for the DoDIN Backbone. Review the router configuration to determine if the router allows only incoming communications from authorized sources to be routed to authorized destinations. The hypothetical example below allows inbound NTP from host x.3.12.33 only to host x.1.22.4. filter INBOUND_FILTER { term ALLOW_NTP { from { source-address { x.3.12.33/32; } destination-address { x.1.22.4/32; <<< change to global address } protocol udp; destination-port ntp; } } } If the router does not restrict incoming communications to allow only authorized sources and destinations, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the router to allow only incoming communications from authorized sources to be routed to authorized destinations.
This requirement is not applicable for the DoDIN Backbone. Review the router configuration to verify that an ingress filter applied to all external interfaces is blocking packets with Bogon source addresses. Verify a prefix list has been configured containing the current Bogon prefixes as shown in the example below. policy-options { prefix-list BOGON_PREFIXES { 0.0.0.0/8; 10.0.0.0/8; 100.64.0.0/10; 127.0.0.0/8; 169.254.0.0/16; 172.16.0.0/12; 192.0.0.0/24; 192.0.2.0/24; 192.168.0.0/16; 198.18.0.0/15; 198.51.100.0/24; 203.0.113.0/24; 224.0.0.0/4; 240.0.0.0/4; } } Verify that the inbound filter applied to all external interfaces will block all traffic from Bogon source addresses. interfaces { ge-0/0/0 { unit 0 { family inet { filter { input INBOUND_FILTER; } address 11.1.12.2/24; } } } … … … firewall { family inet { filter INBOUND_FILTER { term BLOCK_BOGONS { from { source-prefix-list { BOGON_PREFIXES; } } then { syslog; discard; } } term ALLOW_BGP { from { protocol tcp; destination-port bgp; } then accept; } term ALLOW_XYZ { from { protocol xyz; } then accept; } term DENY_ALL_OTHER { then { syslog; reject; } } } } External Interfaces connected to the NIPRNet or SIPRNet Review the inbound ACLs on external facing interfaces attached to the NIPRnet or SIPRnet to validate access control lists are configured to block inbound packets with IP sources addresses as documented in RFC5735 and RFC6598. External Interfaces connected to a commercial ISP or other non-DoD network Review the inbound ACLs on external facing interfaces validate access control lists are configured to block inbound packets with IP sources addresses as documented in RFC5735 and RFC6598, as well as address space that has been allocated to the RIRs but not assigned by the RIR to an ISP or other enterprise network. The full list of bogons can be found at the following link: https://www.team-cymru.org/Services/Bogons/fullbogons-ipv4.txt If the router is not configured to block inbound packets with source Bogon IP address prefixes, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the perimeter to block inbound packets with Bogon source addresses. Configure a prefix list containing the current Bogon prefixes as shown below. [edit policy-options] set prefix-list BOGON_PREFIXES 0.0.0.0/8 set prefix-list BOGON_PREFIXES 10.0.0.0/8 set prefix-list BOGON_PREFIXES 100.64.0.0/10 set prefix-list BOGON_PREFIXES 127.0.0.0/8 set prefix-list BOGON_PREFIXES 169.254.0.0/16 set prefix-list BOGON_PREFIXES 172.16.0.0/12 set prefix-list BOGON_PREFIXES 192.0.0.0/24 set prefix-list BOGON_PREFIXES 192.0.2.0/24 set prefix-list BOGON_PREFIXES 192.168.0.0/16 set prefix-list BOGON_PREFIXES 198.18.0.0/15 set prefix-list BOGON_PREFIXES 198.51.100.0/24 set prefix-list BOGON_PREFIXES 203.0.113.0/24 set prefix-list BOGON_PREFIXES 224.0.0.0/4 set prefix-list BOGON_PREFIXES 240.0.0.0/4 Add a term to the inbound filter to block the Bogon prefixes. [edit firewall family inet filter INBOUND_FILTER] set term BLOCK_BOGONS from source-prefix-list BOGON_PREFIXES set term BLOCK_BOGONS then syslog discard insert term BLOCK_BOGONS before term ALLOW_BGP
This requirement is not applicable for the DoDIN Backbone. Verify the interface connecting to ISP has an inbound filter as shown in the example below. interfaces { ge-0/0/0 { description "Verizon ISP link"; unit 0 { family inet { filter { input ISP_FILTER; } address 11.1.12.2/24; } } } Verify that the filter only allows traffic to specific destination addresses (i.e. enclave’s NIPRNet address space) as shown in the example below. firewall { family inet { filter ISP_FILTER { term RESTRICT_DESTINATION { from { destination-address { 0.0.0.0/0; 11.1.0.0/16 except; } } then { syslog; discard; } } term ALLOW_XYZ { from { protocol xyz; } then accept; } … … … term DENY_ALL_OTHER { then { syslog; reject; } } } If the ingress filter bound to the interface connecting to an alternate gateway permits packets with addresses other than those specified, such as destination addresses of the site's NIPRNet address space or a destination address belonging to the address block assigned by the alternate gateway network service provider, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the ingress filter of the perimeter router connected to an alternate gateway to only permit packets with destination addresses of the site's NIPRNet address space or a destination address belonging to the address block assigned by the alternate gateway network service provider as shown in the example below. [edit firewall family inet filter ISP_FILTER] set term RESTRICT_DESTINATION from destination-address 0.0.0.0/0 set term RESTRICT_DESTINATION from destination-address 11.1.0.0/16 except set term RESTRICT_DESTINATION then syslog discard insert term RESTRICT_DESTINATION before term ALLOW_XYZ
This requirement is not applicable for the DoDIN Backbone. Review the protocols hierarchy in the router configuration (see example below) and verify there are no BGP neighbors configured to a peer AS that belongs to the alternate gateway service provider. protocols { bgp { group AS_2 { type external; peer-as 2; neighbor x.x.x.x { authentication-algorithm hmac-sha-1-96; authentication-key-chain BGP_KEY; } neighbor x.x.x.x { authentication-algorithm hmac-sha-1-96; authentication-key-chain BGP_KEY; } } } If there are BGP neighbors connecting to a peer AS of the alternate gateway service provider, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure a static route on the perimeter router to reach the AS of a router connecting to an alternate gateway as shown in the example below. [edit routing-options] set static route 0.0.0.0/0 next-hop x.x.x.x
This requirement is not applicable for the DoDIN Backbone. Review the configurations under the protocols hierarchy. If the export statement is configured as shown in the example below proceed to step 2. } protocols { bgp { group AS_5 { type external; export REDISTRIBUTE; peer-as 5; … … … } } } ospf { export REDISTRIBUTE; area 0.0.0.0 { interface ge-0/0/0 { … … … } } } } Review the export policy referenced above to determine if static routes are being exported as shown in the example below. policy-options { … … … } policy-statement REDISTRIBUTE { term EXPORT_STATIC { from protocol static; then accept; } } } Review the static routes that have been configured to determine if there routes with the next hop address that of the alternate gateway. routing-options { static { route 10.1.16.0/24 next-hop 10.1.12.1; route 0.0.0.0/0 next-hop 144.22.1.3; } If the static routes to the alternate gateway are being redistributed into BGP or any IGP peering to a NIPRNet gateway or any other autonomous system, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the router so that static routes are not redistributed to an alternate gateway into either a BGP or any IGP peering with the NIPRNet or to any other autonomous systems. This can be done by excluding that route in the export policy as shown in the example below. [edit policy-options policy-statement REDISTRIBUTE] set term NOT_ISP_DEFAULT from protocol static route-filter 0.0.0.0/0 exact set term NOT_ISP_DEFAULT then reject insert term set term NOT_ISP_DEFAULT before term EXPORT_STATIC
This requirement is not applicable for the DoDIN Backbone. Review the router configuration to verify uRPF or an egress filter has been configured on all internal interfaces to restrict the router from accepting outbound IP packets that contain an illegitimate address in the source address field. interfaces { ge-0/1/0 { description "LAN link"; unit 0 { family inet { rpf-check; If uRPF or an egress filter to restrict the router from accepting outbound IP packets that contain an illegitimate address in the source address field has not been configured on all internal interfaces in an enclave, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the router to ensure that an egress filter or uRPF is configured on internal interfaces to restrict the router from accepting any outbound IP packet that contains an illegitimate address in the source field. The example below enables uRPF. [edit interfaces ge-0/1/0 unit 0 family inet] set rpf-check
This requirement is not applicable for the DoDIN Backbone. Review the router configuration to verify that the ingress filter is in accordance with DoD 8551. Verify that an inbound filter is configured on all external interfaces. interfaces { ge-0/0/0 { unit 0 { family inet { filter { input INBOUND_FILTER; } address 11.1.12.2/24; } } } Review the inbound filter to verify that it is filtering traffic in accordance with DoD 8551. firewall { family inet { filter INBOUND_FILTER { term ALLOW_ABC { from { protocol tcp; destination-port abc; } then accept; } term ALLOW_XYZ { from { protocol xyz; } then accept; } term DENY_ALL_OTHER { then { syslog; reject; } } } } If the router does not filter traffic in accordance with the guidelines contained in DoD 8551, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the router to use an inbound filter on all external interfaces as shown in the example below to restrict traffic in accordance with the guidelines contained in DOD Instruction 8551.1. set filter INBOUND_FILTER term ALLOW_ABC from protocol tcp destination-port abc set filter INBOUND_FILTER term ALLOW_ABC then accept set filter INBOUND_FILTER term ALLOW_XYZ from protocol tcp destination-port xyz set filter INBOUND_FILTER term ALLOW_XYZ then accept set filter INBOUND_FILTER term DENY_ALL_OTHER then syslog reject [edit interfaces ge-0/0/0 unit 0 family inet] set filter input INBOUND_FILTER
This requirement is not applicable for the DoDIN Backbone. Review the router configuration to verify that an inbound filter is configured on all external interfaces as shown in the example below. interfaces { description "NIPRNet"; ge-0/0/0 { unit 0 { family inet { filter { input INBOUND_FILTER; } address x.x.x.x/24; } } } If the router is not configured to filter traffic entering the network at all external interfaces in an inbound direction, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the router to use an inbound filter on all external interfaces as shown in the example below. [edit interfaces ge-0/0/0 unit 0 family inet] set filter input INBOUND_FILTER
This requirement is not applicable for the DoDIN Backbone. Review the router configuration to verify that the egress ACL is bound to the internal interface in an inbound direction. interfaces { ge-0/1/0 { description "LAN link"; unit 0 { family inet { filter { input OUTBOUND_FILTER; } address x.x.x.x/24; } } } If the router is not configured to filter traffic leaving the network at the internal interface in an inbound direction, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the router to use an inbound filter on all internal interfaces as shown in the example below. [edit interfaces ge-0/1/0 unit 0 family inet] set filter input OUTBOUND_FILTER
This requirement is not applicable for the DoDIN Backbone. Review the router configuration to determine if it will block all packets with IP options. firewall { family inet { filter INBOUND_FILTER { term DROP_IPOPTIONS { from { ip-options any; } then { syslog; discard; } } term BLOCK_BOGONS { from { source-prefix-list { BOGON_PREFIXES; } } then { syslog; discard; } } term ALLOW_ABC { … … … term DENY_ALL_OTHER { then { log; syslog; reject; } } } If the router is not configured to drop all packets with IP options, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the router to drop all packets with IP options. [edit firewall family inet filter INBOUND_FILTER] set term DROP_IPOPTIONS from ip-options any set term DROP_IPOPTIONS then discard insert term DROP_IPOPTIONS before term BLOCK_BOGONS
This requirement is not applicable for the DoDIN Backbone. Review all router configurations to ensure LLDP is not enabled external interface. protocols { … … … lldp { advertisement-interval 30; interface all; } } If LLDP is configured globally or on any external interface, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Disable LLDP on all external interfaces. If necessary, remove the interface all parameter and define all internal interfaces as shown in the example below. [edit protocols lldp] delete interface all set interface ge-0/1/0 set interface ge-0/1/1
Review the router configuration to determine if IP Proxy ARP is disabled on all external interfaces. interfaces { description "NIPRNet"; ge-0/0/0 { unit 0 { proxy-arp restricted; family inet { If IP Proxy ARP is enabled on any external interface, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Disable Proxy ARP on all external interfaces as shown in the example below. [edit interfaces em0 unit 0] delete proxy-arp restricted
This requirement is not applicable for the DoDIN Backbone. The perimeter router of the managed network must be configured with an outbound filter on the egress interface to block all management traffic as shown in the example below. Verify that the router has been configured with an outbound filter as shown in the example below. interfaces { description "NIPRNet"; ge-0/0/0 { unit 0 { family inet { no-redirects; filter { output OUTBOUND_FILTER; } address 10.1.12.2/24; } } } Verify that the outbound filter discard or rejects management traffic as shown in the example below. firewall { family inet { … … … } filter OUTBOUND_FILTER { term BLOCK_TACACS { from { protocol tcp; port tacacs; } then { syslog; discard; } } term BLOCK_SNMP { from { protocol udp; port [ snmp snmptrap ]; } then { syslog; discard; } } term BLOCK_NETFLOW { from { protocol udp; port [ 2055 9995 9996 ]; } } term ALLOW_OTHER { then accept; } } } If management traffic is not blocked at the perimeter, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the perimeter router of the managed network with an outbound filter on the egress interface to block all management traffic. Configure a filter to block egress management traffic. [edit firewall family inet] Set filter OUTBOUND_FILTER term BLOCK_TACACS from protocol tcp port tacacs Set filter OUTBOUND_FILTER term BLOCK_TACACS then syslog discard Set filter OUTBOUND_FILTER term BLOCK_SNMP from protocol udp port [snmp snmptrap] Set filter OUTBOUND_FILTER term BLOCK_SNMP then syslog discard set filter OUTBOUND_FILTER term BLOCK_NETFLOW from protocol udp port [2055 9995 9996] set filter OUTBOUND_FILTER term BLOCK_NETFLOW then syslog discard Configure the external interfaces with the outbound filter. [edit interfaces ge-0/0/0 unit 0 family inet] set filter output OUTBOUND_FILTER
This requirement is not applicable for the DoDIN Backbone. Review the network topology diagram to determine connectivity between the managed network and the NOC. Review the OOBM gateway router configuration to validate the path and interface that the management traffic traverses. If an IPsec tunnel is used to transport the management traffic between the NOC and the managed network, review the configuration following the steps below. Review the security association within the IPsec configuration to be used for encapsulating the management traffic and verify that it is in tunnel mode. Also note the security association to be used. security { ipsec { proposal IPSEC_PHASE2_PROPOSAL { protocol esp; authentication-algorithm hmac-sha1-96; encryption-algorithm aes-128-cbc; } policy IPSEC_POLICY { perfect-forward-secrecy { keys group14; } proposals IPSEC_PHASE2_PROPOSAL; } security-association IPSEC-SA_XYZ { description "For XYZ"; mode transport; manual { direction bidirectional { protocol ah; spi 256; authentication { algorithm hmac-sha1-96; key ascii-text "$8$oPJjH.P5F69mSHqPQn6u0RhSreW-dsZGi8XYoZDmP"; ## SECRET-DATA } } } } security-association IPSEC_SA_MGMT { description "IPsec Tunnel for Mgmt Traffic"; mode tunnel; dynamic { ipsec-policy IPSEC_POLICY; } } } ike { proposal IKE_PHASE1_PROPOSAL { authentication-method pre-shared-keys; dh-group group14; authentication-algorithm sha-256; encryption-algorithm aes-128-cbc; } policy 10.1.25.2 { mode main; proposals IKE_PHASE1_PROPOSAL; pre-shared-key ascii-text "$8$J4UDkCA01IcHqEy"; ## SECRET-DATA } } Verify there is a filter to direct the management traffic to the IPsec tunnel by verifying the name of the IPsec SA referenced in the then statement as shown in the example below. firewall { family inet { … … … filter MGMT_TRAFFIC { term ALLOW_SNMP { from { protocol udp; port [ snmp snmptrap ]; } then ipsec-sa IPSEC_SA_MGMT; } term ALLOW_TACACS { from { protocol tcp; port tacacs; } then ipsec-sa IPSEC_SA_MGMT; } term ALLOW_NETFLOW { from { protocol udp; port [ 2055 9995 9996 ]; } then ipsec-sa IPSEC_SA_MGMT; } term OTHER { then accept; } } } If management traffic is not transported between the managed network and the NOC via dedicated circuit, MPLS/VPN service, or IPsec tunnel, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Ensure that a dedicated circuit, MPLS/VPN service, or IPsec tunnel is deployed to transport management traffic between the managed network and the NOC. If an IPsec tunnel is to be used, the steps below can be used as a guideline. Configure an IPsec tunnel using commands similar to the example below. [edit security] set ike proposal IKE_PHASE1_PROPOSAL authentication-method pre-shared-keys set ike proposal IKE_PHASE1_PROPOSAL authentication-algorithm sha-256 set ike proposal IKE_PHASE1_PROPOSAL dh-group group14 set ike proposal IKE_PHASE1_PROPOSAL encryption-algorithm aes-128-cbc set ike policy 10.1.25.2 proposals IKE_PHASE1_PROPOSAL set ike policy 10.1.25.2 mode main set ike policy 10.1.25.2 pre-shared-key ascii-text xxxxxxxxx set ipsec proposal IPSEC_PHASE2_PROPOSAL protocol esp set ipsec proposal IPSEC_PHASE2_PROPOSAL authentication-algorithm hmac-sha1-96 set ipsec proposal IPSEC_PHASE2_PROPOSAL encryption-algorithm aes-128-cbc set ipsec security-association IPSEC_SA_MGMT mode tunnel set ipsec security-association IPSEC_SA_MGMT dynamic ipsec-policy IPSEC_POLICY Configure a filter to define the management traffic to be forwarded into the IPsec tunnel. [edit firewall family inet] set filter MGMT_TRAFFIC term ALLOW_SNMP from protocol udp port [snmp snmptrap] set filter MGMT_TRAFFIC term ALLOW_SNMP then ipsec-sa IPSEC_SA_MGMT set filter MGMT_TRAFFIC term ALLOW_TACACS from protocol tcp port tacacs set filter MGMT_TRAFFIC term ALLOW_TACACS then ipsec-sa IPSEC_SA_MGMT set filter MGMT_TRAFFIC term ALLOW_NETFLOW from protocol udp port [2055 9995 9996] set filter MGMT_TRAFFIC term ALLOW_NETFLOW then ipsec-sa IPSEC_SA_MGMT set filter MGMT_TRAFFIC term OTHER then accept
This requirement is not applicable for the DoDIN Backbone. Review the network topology diagram to determine connectivity between the managed network and the NOC. Review the OOBM gateway router configuration to validate the path that the management traffic traverses. Verify that only management traffic is forwarded through the OOBM interface or IPsec tunnel. If an OOBM link is used, verify that the only authorized management traffic is transported to the NOC by reviewing the outbound filter applied to the OOBM interface as shown in the example below. interfaces { description "OOBM Net"; ge-1/1/0 { unit 0 { family inet { filter { output MGMT_TRAFFIC; } address 10.2.22.2/24; } } } … … … firewall { family inet { … … … filter MGMT_TRAFFIC { term ALLOW_SNMP { from { protocol udp; port [ snmp snmptrap ]; } then accept; } term ALLOW_TACACS { from { protocol tcp; port tacacs; } then accept; } term ALLOW_NETFLOW { from { protocol udp; port [ 2055 9995 9996 ]; } then accept; } term DENY_OTHER { then { syslog; discard; } } } } If an IPsec tunnel is used, verify that the only authorized management traffic is transported to the NOC by reviewing the filter referencing the applicable security association as shown int example below. firewall { family inet { … … … filter MGMT_TRAFFIC { term ALLOW_SNMP { from { protocol udp; port [ snmp snmptrap ]; } then ipsec-sa IPSEC_SA_MGMT; } term ALLOW_TACACS { from { protocol tcp; port tacacs; } then ipsec-sa IPSEC_SA_MGMT; } term ALLOW_NETFLOW { from { protocol udp; port [ 2055 9995 9996 ]; } then ipsec-sa IPSEC_SA_MGMT; } term OTHER { then accept; } } } If traffic other than authorized management traffic is permitted through the OOBM interface or IPsec tunnel, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure filters to permit only authorized management traffic into IPsec tunnels or the OOBM interface used for forwarding management data as shown in the examples below. OOBM Link [edit firewall family inet] set filter MGMT_TRAFFIC term ALLOW_SNMP from protocol udp port [snmp snmptrap] set filter MGMT_TRAFFIC term ALLOW_SNMP then accept set filter MGMT_TRAFFIC term ALLOW_TACACS from protocol tcp port tacacs set filter MGMT_TRAFFIC term ALLOW_TACACS then accept set filter MGMT_TRAFFIC term ALLOW_NETFLOW from protocol udp port [2055 9995 9996] set filter MGMT_TRAFFIC term ALLOW_NETFLOW then accept set filter MGMT_TRAFFIC term DENY_OTHER then syslog discard [edit interfaces ge-1/1/0 unit 0 family inet] set filter output MGMT_TRAFFIC IPsec Tunnel [edit firewall family inet] set filter MGMT_TRAFFIC term ALLOW_SNMP from protocol udp port [snmp snmptrap] set filter MGMT_TRAFFIC term ALLOW_SNMP then ipsec-sa IPSEC_SA_MGMT set filter MGMT_TRAFFIC term ALLOW_TACACS from protocol tcp port tacacs set filter MGMT_TRAFFIC term ALLOW_TACACS then ipsec-sa IPSEC_SA_MGMT set filter MGMT_TRAFFIC term ALLOW_NETFLOW from protocol udp port [2055 9995 9996] set filter MGMT_TRAFFIC term ALLOW_NETFLOW then ipsec-sa IPSEC_SA_MGMT set filter MGMT_TRAFFIC term OTHER then accept
This requirement is not applicable for the DoDIN Backbone. Verify that the OOBM interface is an adjacency in the IGP domain for the management network via separate VRF as shown in the example below. } protocols { ospf { area 0.0.0.0 { interface ge-2/0/0; interface ge-2/1/0; } } } routing-instances { VRF_MGMT { instance-type vrf; interface ge-1/0/0; interface ge-1/1/0; route-distinguisher 10.1.12.0:12; vrf-target { import target:1234:4567; export target:1234:4567; } routing-options { router-id 11.11.11.11; } protocols { ospf { area 0.0.0.0 { interface ge-1/0/0; interface ge-1/1/0; } } } } } If the router is not configured to have separate IGP instances for the managed network and management network, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the router to have a separate IGP instance for the management network as shown in the example below. [edit routing-instances] set VRF_MGMT instance-type vrf set VRF_MGMT route-distinguisher 10.1.12.0:12 set VRF_MGMT vrf-target import target:1234:4567 set VRF_MGMT vrf-target export target:1234:4567 set VRF_MGMT interface ge-1/0/0 set VRF_MGMT interface ge-1/1/0 set VRF_MGMT protocols ospf area 0.0.0.0 interface ge-1/0/0 set VRF_MGMT protocols ospf area 0.0.0.0 interface ge-1/1/0 set VRF_MGMT routing-options router-id 11.11.11.11
This requirement is not applicable for the DoDIN Backbone. Verify the Interior Gateway Protocol (IGP) instance used for the managed network does not redistribute routes into the IGP instance used for the management network, and vice versa. The example below imports routes from the global route table (inet.0) in the route table for the management VRF. } routing-options { interface-routes { rib-group inet INET0_GROUP; } rib-groups { INET0_GROUP { import-rib [ VRF_MGMT.inet.0 inet.0 ]; } } } If the IGP instance used for the managed network redistributes routes into the IGP instance used for the management network, or vice versa, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Remove the configuration that imports routes from the management network into the managed network or vice versa as shown in the example below. [edit routing-options] delete rib-groups INET0_GROUP delete interface-routes rib-group inet INET0_GROUP
This requirement is not applicable for the DoDIN Backbone. Review the firewall filter applied to the routers loopback interface to verify that only traffic sourced from the OOBM network or the NOC is allowed to access the router as shown in the example below. interfaces { … … … lo0 { unit 0 { family inet { filter { input PROTECT_RE; } address 1.1.1.1/32; } } } } … … … firewall { family inet { filter PROTECT_RE { term RESTRICT_ADDRESS { from { source-address { 0.0.0.0/0; 10.2.14.0/24 except; } } then { syslog; discard; } } term ALLOW_OTHER { then accept; } } } } If the router does not block any traffic destined to itself that is not sourced from the OOBM network or the NOC, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure the router to only allow traffic to the Routing Engine from the OOBM network. [edit firewall family inet] set filter PROTECT_RP term RESTRICT_ADDRESS from source-address 0.0.0.0/0 set filter PROTECT_RP term RESTRICT_ADDRESS from source-address 10.2.14.0/24 except set filter PROTECT_RP term RESTRICT_ADDRESS then syslog discard set filter PROTECT_RP term ALLOW_OTHER then accept [edit interfaces lo0 unit 0 family inet] set filter input PROTECT_RP
Verify that the managed interface has an inbound and outbound filter configured. interfaces { … … … ge-0/0/0 { description "OOBM Network"; unit 0 { family inet { filter { input OOBM_INBOUND; output OOBM_OUTBOUND; } address 10.2.14.1/24; } } } Verify that the ingress filter only allows management and ICMP traffic. firewall { family inet { … … … filter OOBM_INBOUND { term ALLOW_SNMP { from { protocol udp; port snmp; } then accept; } term ALLOW_TACACS { from { protocol tcp; port tacacs; } then accept; } term ALLOW_ICMP { from { protocol icmp; } then accept; } term ALLOW_SSH { from { protocol tcp; port ssh; } then accept; } term ALLOW_NTP { from { protocol tcp; port ntp; } then accept; } term DENY_OTHER { then { syslog; discard; } } } } } Verify that the ingress filter only allows management and ICMP traffic. firewall { family inet { … … … filter OOBM_OUTBOUND { term ALLOW_SNMP { from { protocol udp; port [ snmp snmptrap ]; } then accept; } term ALLOW_TACACS { from { protocol tcp; port tacacs; } then accept; } term ALLOW_SSH { from { protocol tcp; port ssh; } then accept; } term ALLOW_NTP { from { protocol udp; port ntp; } then accept; } term ALLOW_SYSLOG { from { protocol udp; port syslog; } then accept; } term ALLOW_NETFLOW { from { protocol udp; port [ 2055 9995 9996 ]; } then accept; } term DENY_OTHER { then { syslog; discard; } } } } } Caveat: If the management interface is a true OOBM interface, this requirement is not applicable. If the router does not restrict traffic that ingresses and egresses the management interface, this is a finding.
If the management interface is not a dedicated OOBM interface, it must be configured with both an ingress and egress filter. Configure an inbound filter a shown in the example below. [edit firewall family inet] set filter OOBM_INBOUND term ALLOW_SNMP from protocol udp port snmp set filter OOBM_INBOUND term ALLOW_SNMP then accept set filter OOBM_INBOUND term ALLOW_TACACS from protocol tcp port tacacs set filter OOBM_INBOUND term ALLOW_TACACS then accept set filter OOBM_INBOUND term ALLOW_SSH from protocol tcp port ssh set filter OOBM_INBOUND term ALLOW_SSH then accept set filter OOBM_INBOUND term ALLOW_NTP from protocol udp port ntp set filter OOBM_INBOUND term ALLOW_NTP then accept set filter OOBM_INBOUND term ALLOW_ICMP from protocol icmp set filter OOBM_INBOUND term ALLOW_ICMP then accept set filter OOBM_INBOUND term DENY_OTHER then syslog discard Configure an outbound filter a shown in the example below. set filter OOBM_OUTBOUND term ALLOW_SNMP from protocol udp port [snmp snmptrap] set filter OOBM_OUTBOUND term ALLOW_SNMP then accept set filter OOBM_OUTBOUND term ALLOW_TACACS from protocol tcp port tacacs set filter OOBM_OUTBOUND term ALLOW_TACACS then accept set filter OOBM_OUTBOUND term ALLOW_SSH from protocol tcp port ssh set filter OOBM_OUTBOUND term ALLOW_SSH then accept set filter OOBM_OUTBOUND term ALLOW_NTP from protocol udp port ntp set filter OOBM_OUTBOUND term ALLOW_NTP then accept set filter OOBM_OUTBOUND term ALLOW_SYSLOG from protocol udp port set filter OOBM_OUTBOUND term ALLOW_SYSLOG then accept set filter OOBM_OUTBOUND term ALLOW_NETFLOW from protocol udp port [2055 9995 9996] set filter OOBM_OUTBOUND term ALLOW_NETFLOW then accept set filter OOBM_OUTBOUND term DENY_OTHER then syslog discard Apply the filters to the OOBM interfaces. [edit interfaces ge-0/0/0 unit 0 family inet] set filter input OOBM_INBOUND set filter output OOBM_OUTBOUND
This requirement is not applicable for the DoDIN Backbone. Verify that all traffic from the managed network to the management network and vice-versa is secured via IPsec tunnel. Review the security association within the IPsec configuration to be used for encapsulating the management traffic and verify that it is in tunnel mode. Also note the security association to be used. security { ipsec { proposal IPSEC_PHASE2_PROPOSAL { protocol esp; authentication-algorithm hmac-sha1-96; encryption-algorithm aes-128-cbc; } policy IPSEC_POLICY { perfect-forward-secrecy { keys group14; } proposals IPSEC_PHASE2_PROPOSAL; } security-association IPSEC-SA_XYZ { description "For XYZ"; mode transport; manual { direction bidirectional { protocol ah; spi 256; authentication { algorithm hmac-sha1-96; key ascii-text "$8$oPJjH.P5F69mSHqPQn6u0RhSreW-dsZGi8XYoZDmP"; ## SECRET-DATA } } } } security-association IPSEC_SA_MGMT { description "IPsec Tunnel for Mgmt Traffic"; mode tunnel; dynamic { ipsec-policy IPSEC_POLICY; } } } ike { proposal IKE_PHASE1_PROPOSAL { authentication-method pre-shared-keys; dh-group group14; authentication-algorithm sha-256; encryption-algorithm aes-128-cbc; } policy 10.1.25.2 { mode main; proposals IKE_PHASE1_PROPOSAL; pre-shared-key ascii-text "$8$J4UDkCA01IcHqEy"; ## SECRET-DATA } } Verify there is a filter to direct the management traffic to the IPsec tunnel by verifying the name of the IPsec SA referenced in the then statement as shown in the example below. firewall { family inet { … … … filter MGMT_TRAFFIC { term ALLOW_SNMP { from { protocol udp; port [ snmp snmptrap ]; } then ipsec-sa IPSEC_SA_MGMT; } term ALLOW_TACACS { from { protocol tcp; port tacacs; } then ipsec-sa IPSEC_SA_MGMT; } term ALLOW_NETFLOW { from { protocol udp; port [ 2055 9995 9996 ]; } then ipsec-sa IPSEC_SA_MGMT; } term OTHER { then accept; } } } If the management traffic is not secured via IPsec tunnel, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Ensure that all traffic from the managed network to the management network is secured via IPsec tunnel as shown in the configuration examples below. Configure an IPsec tunnel to be used to transport the management traffic. [edit security] set ike proposal IKE_PHASE1_PROPOSAL authentication-method pre-shared-keys set ike proposal IKE_PHASE1_PROPOSAL authentication-algorithm sha-256 set ike proposal IKE_PHASE1_PROPOSAL dh-group group14 set ike proposal IKE_PHASE1_PROPOSAL encryption-algorithm aes-128-cbc set ike policy 10.1.25.2 proposals IKE_PHASE1_PROPOSAL set ike policy 10.1.25.2 mode main set ike policy 10.1.25.2 pre-shared-key ascii-text xxxxxxxxx set ipsec proposal IPSEC_PHASE2_PROPOSAL protocol esp set ipsec proposal IPSEC_PHASE2_PROPOSAL authentication-algorithm hmac-sha1-96 set ipsec proposal IPSEC_PHASE2_PROPOSAL encryption-algorithm aes-128-cbc set policy IPSEC_POLICY perfect-forward-secrecy keys group14 set policy IPSEC_POLICY proposals xxxxx set ipsec security-association IPSEC_SA_MGMT mode tunnel set ipsec security-association IPSEC_SA_MGMT dynamic ipsec-policy IPSEC_POLICY Configure a filter that will select which traffic to be forwarded via the IPsec tunnel by specifying the security association bound to the tunnel. [edit firewall family inet] set filter MGMT_TRAFFIC term ALLOW_SNMP from protocol udp port [snmp snmptrap] set filter MGMT_TRAFFIC term ALLOW_SNMP then ipsec-sa IPSEC_SA_MGMT set filter MGMT_TRAFFIC term ALLOW_TACACS from protocol tcp port tacacs set filter MGMT_TRAFFIC term ALLOW_TACACS then ipsec-sa IPSEC_SA_MGMT set filter MGMT_TRAFFIC term ALLOW_NETFLOW from protocol udp port [2055 9995 9996] set filter MGMT_TRAFFIC term ALLOW_NETFLOW then ipsec-sa IPSEC_SA_MGMT set filter MGMT_TRAFFIC term OTHER then accept
Verify that a filter has been configured to only allow BGP packets with a TTL of 255 as shown in the example below. firewall { … … … filter GTSM_FILTER { term TTL_SECURITY { from { protocol tcp; ttl-except 255; port bgp; } then { syslog; discard; } } term ELSE_ACCEPT { then accept; } } } Verify that the filter is applied to all interfaces connecting to eBGP peers. interfaces { … … … ge-0/0/0 { unit 0 { family inet { filter { input-list [INBOUND_FILTER GTSM_FILTER]; } address x.x.x.x/30; } } } } Configure the router to send all BGP packets with a TTL of 255 as shown in the example below. If the router is not configured to use GTSM for all Exterior Border Gateway Protocol peering sessions, this is a finding.
Configure a filter to only accept bgp packets with a TTL of 255 as shown in the example below. [edit firewall] set filter GTSM_FILTER term TTL_SECURITY from protocol tcp port bgp ttl-except 255 set filter GTSM_FILTER term TTL_SECURITY then syslog discard set filter GTSM_FILTER term ELSE_ACCEPT then accept Apply the firewall filter to the inbound interface for all eBGP single-hop peer as shown in the example below. [edit interfaces ge-0/0/0 unit 0 family inet] set filter input-list INBOUND_FILTER set filter input-list GTSM_FILTER
Review the BGP configuration to determine if it is peering with multiple autonomous systems. Interview the ISSM and router administrator to determine if unique keys are being used. protocols { bgp { group AS44 { type external; peer-as 44; neighbor x.x.x.x { authentication-key "$8$tBga0ORx7VsYoIEgJ"; ## SECRET-DATA } } group AS66 { type external; peer-as 66; neighbor x.x.x.x { authentication-key "$8$Q4953nCrlMLX-9A7V"; ## SECRET-DATA } } } If unique keys are not being used, this is a finding.
Configure the router to use unique keys for each AS that it peers with as shown in the example below. [edit protocols bgp] set group GROUP_AS66 authentication-key abc123 set group GROUP_AS44 authentication-key xyz123
Review the router configuration to verify that it will reject BGP routes for any Bogon prefixes. Verify a prefix list has been configured containing the current Bogon prefixes as shown in the example below. policy-options { prefix-list BOGON_PREFIXES { 0.0.0.0/8; 10.0.0.0/8; 100.64.0.0/10; 127.0.0.0/8; 169.254.0.0/16; 172.16.0.0/12; 192.0.0.0/24; 192.0.2.0/24; 192.168.0.0/16; 198.18.0.0/15; 198.51.100.0/24; 203.0.113.0/24; 224.0.0.0/4; 240.0.0.0/4; } } Verify that a policy has been configured to reject the Bogon prefixes. policy-options { … … … policy-statement FILTER_ROUTES { term REJECT_BOGONS { from { prefix-list BOGON_PREFIXES; } then reject; } term ACCEPT_OTHERS { then accept; } } } Verify that the configured policy to filter Bogons has been applied to external BGP peers as shown in the example below. protocols { bgp { group GROUP_AS4 { type external; import FILTER_ROUTES; peer-as 4; neighbor x.x.x.x; } } If the router is not configured to reject inbound route advertisements for any Bogon prefixes, this is a finding.
Configure the router to reject inbound route advertisements for any Bogon prefixes. Configure a prefix list containing the current Bogon prefixes as shown below. [edit policy-options] set prefix-list BOGON_PREFIXES 0.0.0.0/8 set prefix-list BOGON_PREFIXES 10.0.0.0/8 set prefix-list BOGON_PREFIXES 100.64.0.0/10 set prefix-list BOGON_PREFIXES 127.0.0.0/8 set prefix-list BOGON_PREFIXES 169.254.0.0/16 set prefix-list BOGON_PREFIXES 172.16.0.0/12 set prefix-list BOGON_PREFIXES 192.0.0.0/24 set prefix-list BOGON_PREFIXES 192.0.2.0/24 set prefix-list BOGON_PREFIXES 192.168.0.0/16 set prefix-list BOGON_PREFIXES 198.18.0.0/15 set prefix-list BOGON_PREFIXES 198.51.100.0/24 set prefix-list BOGON_PREFIXES 203.0.113.0/24 set prefix-list BOGON_PREFIXES 224.0.0.0/4 set prefix-list BOGON_PREFIXES 240.0.0.0/4 Configure a policy-statement to reject Bogon prefixes. set policy-statement FILTER_ROUTES term REJECT_BOGONS from prefix-list BOGON_PREFIXES set policy-statement FILTER_ROUTES term REJECT_BOGONS then reject set policy-statement FILTER_ROUTES term ACCEPT_OTHER then accept Configure an import statement referencing the policy to reject Bogons on all external BGP peers. [edit protocols bgp group GROUP_AS4] set import FILTER_ROUTES
Review the router configuration to verify that it will reject routes belonging to the local AS. Verify a prefix list has been configured containing prefixes belonging to the local autonomous system as shown in the example below. policy-options { … … … prefix-list OUR_PREFIXES { x.x.x.x/16; } Verify that a policy has been configured to reject the local prefixes. policy-options { … … … policy-statement FILTER_ROUTES { term REJECT_BOGONS { from { prefix-list BOGON_PREFIXES; } then reject; } term REJECT_OUR_PREFIXES { from { prefix-list OUR_PREFIXES; } then reject; } term ACCEPT_OTHER { then accept; } } } Verify that the configured policy to filter local prefixes has been applied to external BGP peers as shown in the example below. protocols { bgp { group GROUP_AS4 { type external; import FILTER_ROUTES; peer-as 4; neighbor x.x.x.x; } } If the router is not configured to reject inbound route advertisements belonging to the local AS, this is a finding.
Configure the router to reject inbound route advertisements for any prefixes belonging to the local AS. Configure a prefix list containing prefixes belonging to the local autonomous system. [edit policy-options] set prefix-list OUR_PREFIXES x.x.x.x/16 Configure a policy-statement to reject prefixes belonging to the local autonomous system. This can be done by adding a term to the existing policy to filter Bogons as shown in the example below. [edit policy-options policy-statement FILTER_ROUTES] set term REJECT_OUR_PREFIXES from prefix-list OUR_PREFIXES set term REJECT_OUR_PREFIXES then reject insert term REJECT_OUR_PREFIXES before term ACCEPT_OTHER Note: There is no need change the BGP configuration assuming the import statement is already configured for all external neighbors.
Review the router configuration to verify that there are filters defined to only accept routes for prefixes that belong to specific customers. Verify prefix list has been configured containing prefixes belonging to each customer as shown in the example below. policy-options { … … … prefix-list CUST1_PREFIXES { x.x.x.x/24; x.x.x.x/24; } prefix-list CUST2_PREFIXES { x.x.x.x/24; } Verify that a policy has been configured to only accept routes belonging to the customer. policy-options { … … … policy-statement FILTER_CUST1_ROUTES { term ACCEPT-ROUTES { from { prefix-list CUST1_PREFIXES; } then accept; } term REJECT_OTHER { then reject; } } policy-statement FILTER_CUST2_ROUTES { term ACCEPT_ROUTES { from { prefix-list CUST2_PREFIXES; } then accept; } term REJECT_OTHER { then reject; } } } Verify that the configured policy to filter customer prefixes has been applied to customer BGP peers as shown in the example below. protocols { bgp { … … … } group CUST1 { type external; import FILTER_CUST1_ROUTES; peer-as 55; neighbor x.x.x.x; neighbor x.x.x.x; } group CUST2 { type external; import FILTER_CUST2_ROUTES; peer-as 44; neighbor x.x.x.x; neighbor x.x.x.x; } } … … … } Note: Routes to PE-CE links within a VPN are needed for troubleshooting end-to-end connectivity across the MPLS/IP backbone. Hence, these prefixes are an exception to this requirement. If the router is not configured to reject inbound route advertisements from each CE router for prefixes that are not allocated to that customer, this is a finding.
Configure the router to reject inbound route advertisements from a CE router for prefixes that are not allocated to that customer. Configure a prefix list containing prefixes belonging to the customers. [edit policy-options] set prefix-list CUST1_PREFIXES x.x.x.x/24 set prefix-list CUST1_PREFIXES x.x.x.x/24 set prefix-list CUST2_PREFIXES x.x.x.x/24 set prefix-list CUST2_PREFIXES x.x.x.x/24 Configure a policy-statement to filter customer routes. set policy-statement FILTER_CUST1_ROUTES term ACCEPT_ROUTES from prefix-list CUST1_PREFIXES set policy-statement FILTER_CUST1_ROUTES term then accept set policy-statement FILTER_CUST1_ROUTES term REJECT_OTHER then reject set policy-statement FILTER_CUST2_ROUTES term ACCEPT_ROUTES from prefix-list CUST2_PREFIXES set policy-statement FILTER_CUST2_ROUTES term then accept set policy-statement FILTER_CUST2_ROUTES term REJECT_OTHER then reject Apply the import policy to filter received routes for each customer group. [edit protocols bgp group CUST1] set import FILTER_CUST1_ROUTES [edit protocols bgp group CUST2] set import FILTER_CUST2_ROUTES
This requirement is not applicable for the DODIN Backbone.” Review the router configuration to verify that there is a filter defined to only advertise routes for prefixes that belong to any customers or the local AS. Verify that a policy has been configured to filter prefixes for BGP advertisement as shown in the example below. } policy-options { … … … policy-statement BGP_ADVERTISE_POLICY { term INCLUDE_LOCAL { from { prefix-list OUR_PREFIXES; } then accept; } term INCLUDE_CUST1 { from { prefix-list CUST1_PREFIXES; } then accept; } term INCLUDE_CUST2 { from { prefix-list CUST2_PREFIXES; } then accept; } term REJECT_OTHER { then reject; } } Verify that the export statement as shown below references the advertise policy. protocols { bgp { group AS4 { type external; import FILTER_ROUTES; export BGP_ADVERTISE_POLICY; peer-as 4; neighbor x.x.x.x; } group CUST1 { type external; import FILTER_CUST1_ROUTES; export BGP_ADVERTISE_POLICY; peer-as 55; neighbor x.x.x.x; neighbor x.x.x.x; } group CUST2 { type external; import FILTER_CUST2_ROUTES; export BGP_ADVERTISE_POLICY; peer-as 44; neighbor x.x.x.x; neighbor x.x.x.x; } } … … … } Note: The prefix lists should have already been configured per the previous requirements. If the router is not configured to reject outbound route advertisements that do not belong to any customers or the local AS, this is a finding.
Configure the router to filter outbound route advertisements for prefixes that are not allocated to or belong to any customer or the local autonomous system. Configure a policy-statement to filter BGP route advertisements that will only include the local and customer prefixes. [edit policy-options] set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_LOCAL from prefix-list OUR_PREFIXES set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_LOCAL then accept set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_CUST1 from prefix-list CUST1_PREFIXES set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_CUST1 then accept set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_CUST2 from prefix-list CUST2_PREFIXES set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_CUST2 then accept set policy-statement BGP_ADVERTISE_POLICY term REJECT_OTHER then reject Note: The prefix lists should have already been configured per the previous requirements. Configure an export statement referencing the advertise policy on all external BGP peer groups as shown in the example below. [edit protocols bgp group GROUP_AS4] set export BGP_ADVERTISE_POLICY [edit protocols bgp group CUST1] set export BGP_ADVERTISE_POLICY [edit protocols bgp group CUST2] set export BGP_ADVERTISE_POLICY
Review the router configuration to verify that there is a filter defined to block route advertisements for prefixes that belong to the IP core. Verify a prefix list has been configured containing prefixes belonging to the local autonomous system as shown in the example below. policy-options { … … … prefix-list CORE_PREFIX { x.x.x.x/16; } Verify that a policy has been configured to not advertise prefixes belong to the core as shown in the example below. policy-options { … … … policy-statement BGP_ADVERTISE_POLICY { term EXCLUDE_CORE { from { prefix-list CORE_PREFIX; } then reject; } term INCLUDE_OTHER { then accept; } } Verify that the export statement as shown below references the advertise policy. protocols { bgp { group AS4 { type external; export BGP_ADVERTISE_POLICY; peer-as 4; neighbor x.x.x.x; } If the router is not configured to reject outbound route advertisements that belong to the IP core, this is a finding.
Configure the router to filter outbound route advertisements belonging to the IP core. Configure a prefix list containing prefixes belonging to the IP core. [edit policy-options] set prefix-list CORE_PREFIX x.x.x.x/16 Configure a policy-statement to filter BGP route advertisements that will exclude core prefixes. [edit policy-options] set policy-statement BGP_ADVERTISE_POLICY term EXCLUDE_CORE from prefix-list CORE_PREFIX set policy-statement BGP_ADVERTISE_POLICY term EXCLUDE_CORE then reject set policy-statement BGP_ADVERTISE_POLICY term INCLUDE_OTHER then accept Configure an export statement referencing the advertise policy on all external BGP peer groups as shown in the example below. [edit protocols bgp group GROUP_AS4] set export BGP_ADVERTISE_POLICY
Review the router configuration to verify the router is configured to deny updates received from eBGP peers that do not list their AS number as the first AS in the AS_PATH attribute. Verify that the enforce-first-as command has been configured at the BGP or group hierarchy as shown in the example below: protocols { … … … bgp { enforce-first-as; If the router is not configured to reject updates from peers that do not list their AS number as the first AS in the AS_PATH attribute, this is a finding.
Configure the router to deny updates received from eBGP peers that do not list their AS number as the first AS in the AS_PATH attribute using the enforce-first-as command as shown in the example below: [edit protocols bgp group] set enforce-first-as
This requirement is not applicable for the DODIN Backbone.” Review the router configuration to verify the router is configured to deny updates received from CE routers with an originating AS in the AS_PATH attribute that does not belong to that customer. Step 1: Verify a policy has been configured to filter AS_PATH attribute for received BGP advertisements as shown in the example below: policy-options { … … … policy-statement FILTER_ASx { term ALLOW_ASx { from as-path PEER_ASx; then accept; } term ELSE_REJECT { then reject; } } … … … as-path PEER_ASx "^x$"; } Note: the characters “^” and “$” representing the beginning and the end of the expression respectively are optional and are implicitly defined if omitted. Step 2: Verify that the import policy has been applied to all external BGP peers as shown in the example below: protocols { bgp { group GROUP_ASx { type external; import [ FILTER_ASx FILTER_ROUTES ]; peer-as x; neighbor x.x.x.x; } If the router is not configured to reject updates from CE routers with an originating AS in the AS_PATH attribute that does not belong to that customer, this is a finding.
Step 1: Configure a policy to filter the AS_PATH as shown in the example below: [edit policy-options] set as-path PEER_ASx "^x$" set policy-statement FILTER_ASx term ALLOW_ASx from as-path PEER_ASx set policy-statement FILTER_ASx term ALLOW_ASx then accept set policy-statement FILTER_ASx term ELSE_REJECT then reject Step 2: Apply the import policy as shown in the example below: [edit protocols bgp group GROUP_ASx] set import [FILTER_AS4 FILTER_ROUTES]
Review the router configuration to verify that the number of received prefixes from each eBGP neighbor is controlled. protocols { bgp { group GROUP_AS4 { type external; family inet { unicast { prefix-limit { maximum 10; teardown; } } } peer-as 4; neighbor x.x.x.x; } If the router is not configured to control the number of prefixes received from each peer to protect against route table flooding and prefix de-aggregation attacks, this is a finding.
Configure the router to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks as shown in the example below. [edit protocols bgp group GROUP_AS4] set family inet unicast prefix-limit maximum nnnnn teardown
This requirement is not applicable for the DODIN Backbone. Review the router configuration to determine if it is compliant with this requirement. Verify that a policy statement has been configured to reject prefixes longer than /24 or the least significant prefixes issued to the customers as shown in the example below. policy-options { … … … } policy-statement NO_LONG_PREFIXES { from { route-filter 0.0.0.0/0 prefix-length-range /25-/32 reject; } } Note: It may be necessary to configure separate policy statements depending on the address space issued to each customer. Verify that there is an import statement referencing the policy statement to filter prefix length. protocols { bgp { … … … } group CUST1 { type external; import [ FILTER_CUST1_ROUTES NO_LONG_PREFIXES ]; peer-as 55; neighbor x.x.x.x; neighbor x.x.x.x; } group CUST2 { type external; import [ FILTER_CUST1_ROUTES NO_LONG_PREFIXES ]; peer-as 44; neighbor x.x.x.x; neighbor x.x.x.x; } If the router is not configured to limit the prefix size on any inbound route advertisement to /24 or the least significant prefixes issued to the customer, this is a finding.
Configure the router to limit the prefix size on any route advertisement to /24 or the least significant prefixes issued to the customer. Configure a route filter to reject any prefix that is longer than /24. [edit policy-options] set policy-statement NO_LONG_PREFIXES from route-filter 0.0.0.0/0 prefix-length-range /25-/32 reject Apply the policy statement to the BGP customer groups. [edit protocols bgp group CUST1] set import NO_LONG_PREFIXES [edit protocols bgp group CUST2] set import NO_LONG_PREFIXES
Review the router configuration to verify that a loopback address has been configured. interfaces { … … … } lo0 { unit 0 { family inet { address 2.2.2.2/32; } } } } Verify that the loopback interface is used as the source address for all iBGP sessions. protocols { bgp { … … … } group IBGP_PEERS { type internal; local-address 2.2.2.2; neighbor x.x.x.x; } If the router does not use its loopback address as the source address for all iBGP sessions, this is a finding.
Configure the router to use its loopback address as the source address for all iBGP peering. [edit protocols bgp group IBGP_PEERS] set local-address 2.2.2.2
Review the router configuration to determine if it is compliant with this requirement. Verify that a loopback address has been configured as shown in the following example: } interfaces { … … … } lo0 { unit 0 { family inet { address 2.2.2.2/32; } } } } By default, routers will use its loopback address for LDP peering. If an address has not be configured on the loopback interface, it will use its physical interface connecting to the LDP peer. If the router-id command is specified that overrides this default behavior, verify that it is the IP address of the designated loopback interface as shown in the example below. } routing-options { router-id 2.2.2.2; autonomous-system 5; } If the router is not configured do use its loopback address for LDP peering, this is a finding.
Configure the router to use their loopback address as the source address for LDP peering sessions. As noted in the check content, the default behavior is to use its loopback address. However, if a router ID is configured, ensure it matches the address of the loopback address as shown in the example below. [edit routing-options] set router-id 2.2.2.2
Review the router OSPF or IS-IS configuration and verify that LDP will synchronize with the link-state routing protocol as shown in the example below. OSPF Example: protocols { mpls { interface ge-0/0/0.0; } … … … ospf { export REDISTRIBUTE; area 0.0.0.0 { interface ge-0/0/0.0 { ldp-synchronization { hold-time 10; } … … … } } ldp { interface ge-0/0/0.0; } } IS-IS Example: protocols { mpls { interface ge-0/0/0.0; } … … … isis { level 1 authentication-key-chain ISIS_KEY; level 2 authentication-key-chain ISIS_KEY; interface ge-0/0/0.0 { ldp-synchronization { hold-time 10; } … … … } } ldp { interface ge-0/0/0.0; } } If the router is not configured to synchronize IGP and LDP, this is a finding.
Configure the MPLS router to synchronize IGP and LDP, minimizing packet loss when an IGP adjacency is established prior to LDP peers completing label exchange. [edit protocols ospf area 0.0.0.0] set interface ge-0/0/0.0 ldp-synchronization hold-time 10 [edit protocols isis] set interface ge-0/0/0.0 ldp-synchronization hold-time 10 Note: The hold-time is the amount of time (in seconds) the routing device advertises the maximum cost metric for a link that is not fully operational. Default is infinity.
Review the router configuration to determine if it is compliant with this requirement. The aggregate reliable commands in the example below will enable the following RSVP refresh reduction features: message bundling, Message ID, reliable message delivery, and summary refresh. protocols { rsvp { interface ge-0/0/0.0 { aggregate; reliable; } } If the router configured with RSVP-TE does not have refresh reduction features enabled, this is a finding.
Configure the router to enable all refresh reduction features as shown in the example. [edit protocols rsvp] set interface ge-0/0/0.0 aggregate reliable Note: The aggregate reliable commands will enable the following RSVP refresh reduction features: message bundling, reliable message delivery, and summary refresh.
Review the router configuration to verify that TTL propagation is disabled. protocols { mpls { no-propagate-ttl; } If the MPLS router is not configured to disable TTL propagation, this is a finding.
Configure the MPLS router to disable TTL propagation. [edit protocols mpls] set no-propagate-ttl
Review the design plan for deploying L3VPN and VRF-lite. Review all CE-facing interfaces and verify that the proper VRF is defined. The example below depicts the CE-facing interface ge-0/1/0 bound to VRF titled L3VPN_CUST1. Notice that the PE router is peering OSPF with the CE router. interfaces { … … … } ge-0/1/0 { description "link to Customer 1"; unit 0 { family inet { address 101.3.44.6/30; } } } … … … } routing-instances { L3VPN_CUST1 { description "Between PE1 & PE2"; instance-type vrf; interface ge-0/1/0.0; route-distinguisher 33:33; vrf-target target:33:33; vrf-table-label; protocols { ospf { area 0.0.0.1 { interface ge-0/1/0.0; } } } } } If any VRFs are not bound to the appropriate physical or logical interface, this is a finding.
Configure the PE router to have each VRF bound to the appropriate physical or logical interfaces to maintain traffic separation between all MPLS L3VPNs as shown in the example below. [edit] set routing-instances L3VPN_CUST1 instance-type vrf set routing-instances L3VPN_CUST1 description "Between PE1 & PE2" set routing-instances L3VPN_CUST1 interface ge-0/1/0.0 set routing-instances L3VPN_CUST1 protocols ospf interface area 1 ge-0/1/0.0 set routing-instances L3VPN_CUST1 route-distinguisher 33:33 set routing-instances L3VPN_CUST1 vrf-target target:33:33 set routing-instances L3VPN_CUST1 vrf-table-label
Review the design plan for MPLS/L3VPN and VRF-lite to determine what RTs have been assigned for each VRF. Review the router configuration and verify that the correct RT is configured for each VRF. In the example below, route target 33:33 has been configured for customer 1. routing-instances { L3VPN_CUST1 { description "Between PE1 & PE2"; instance-type vrf; interface ge-0/1/0.0; route-distinguisher 33:33; vrf-target target:33:33; vrf-table-label; protocols { ospf { area 0.0.0.1 { interface ge-0/1/0.0; } } } } If there are VRFs configured with the wrong RT, this is a finding.
Configure the router to have each VRF instance defined with the correct RT. [edit] set routing-instances L3VPN_CUST1 vrf-target target:33:33
Review the RDs that have been assigned for each VRF according to the plan provided by the ISSM. Review the router configuration and verify that the correct RD is configured for each VRF. In the example below, route distinguisher 33:33 has been configured for customer 1. routing-instances { L3VPN_CUST1 { description "Between PE1 & PE2"; instance-type vrf; interface ge-0/1/0.0; route-distinguisher 33:33; vrf-target target:33:33; vrf-table-label; protocols { ospf { area 0.0.0.1 { interface ge-0/1/0.0; } } } } If the wrong RD has been configured for any VRF, this is a finding.
Configure the correct RD for each VRF. [edit] set routing-instances L3VPN_CUST1 route-distinguisher 33:33
Review the router configuration to determine if LDP messages are being authenticated for the targeted LDP sessions. In the example below, the PE router is LDP peering with remote PE 8.8.8.8. ldp { interface ge-0/1/0.0; interface ge-0/1/1.0; session 8.8.8.8 { authentication-algorithm hmac-sha-1-96; authentication-key-chain LDP_KEY; } } If authentication is not being used for the LDP targeted sessions using a FIPS-approved message authentication code algorithm, this is a finding.
Implement authentication for all targeted LDP sessions using a FIPS-approved message authentication code algorithm. [edit security authentication-key-chains] set key-chain LDP_KEY key 1 start-time 2018-05-01.12:00 secret xxxxxxxxxxxxx set key-chain LDP_KEY key 2 start-time 2018-09-01.12:00 secret xxxxxxxxxxxxx set key-chain LDP_KEY key 3 start-time 2019-01-01.12:00 secret xxxxxxxxxxxxx [edit protocols ldp] set session 8.8.8.8 authentication-algorithm hmac-sha-1-96 authentication-key-chain LDP_KEY
Review the ingress and egress PE router configuration for each virtual circuit that has been provisioned. Verify that the correct and unique VCID has been configured for the appropriate attachment circuit. In the example below ge-0/1/0 is the CE-facing interface that is configured for VPWS (aka pseudowire). interfaces { ge-0/1/0.0 { encapsulation ethernet-ccc; unit 0 { } } … … … protocols { … … … } l2circuit { neighbor 8.8.8.8 { interface ge-0/1/0.0{ virtual-circuit-id 13; } } } If the correct VC ID has not been configured on both routers, this is a finding. Note: Ethernet over MPLS in VLAN mode transports Ethernet traffic from a source 802.1Q VLAN to a destination 802.1Q VLAN over a core MPLS network. The VC ID must be unique and the same on each end as it is used to connect the endpoints of the VC.
Assign globally unique VC IDs for each virtual circuit and configure the attachment circuits with the appropriate VC ID. Configure the same VC ID on both ends of the VC. [edit protocols l2circuit] set neighbor 8.8.8.8 interface em0 virtual-circuit-id 13
Review the implementation plan and the VPLS IDs assigned to customer VLANs for the VPLS deployment. Review the PE router configuration to verify that customer attachment circuits are associated to the appropriate routing instance configured for the customers VPLS ID. interfaces { ge-0/1/0.0 { encapsulation ethernet-vpls; unit 0 { } } … … … routing-instances { VPLS_CUST2 { instance-type vpls; interface ge-0/1/0.0; route-distinguisher 22:22; vrf-target target:22:22; protocols { vpls { site-range 9; no-tunnel-services; site R8 { site-identifier 8; interface ge-0/1/0.0; } vpls-id 102; neighbor 8.8.8.8; } } } } If the attachment circuits have not been bound to appropriate routing instance configured with the assigned VPLS ID for each customer VLAN, this is a finding.
Assign globally unique VPLS ID to each VPLS routing instance as shown in the example. [edit routing-instances VPLS_CUST2 protocols vpls] set vpls-id 102 neighbor 8.8.8.8
Review the router configuration to verify that storm control is enabled on CE-facing interfaces deploying VPLS. Verify that a flood filter has been configured for each VPLS routing instances as shown in the example below. routing-instances { VPLS_CUST2 { instance-type vpls; interface ge-0/1/0.0; route-distinguisher 22:22; vrf-target target:22:22; forwarding-options { family vpls { flood { input VPLS_FLOOD_FILTER; } } } protocols { vpls { site-range 9; no-tunnel-services; site R8 { site-identifier 8; interface ge-0/1/0.0; } vpls-id 102; neighbor 8.8.8.8; } } } } Review the filter configured for the VPLS routing instances to verify it defines traffic types associated with storm control (i.e. broadcast, multicast, and unknown unicast storms). firewall { … … … family vpls { filter VPLS_FLOOD_FILTER { term BROADCAST_TRAFFIC { from { traffic-type broadcast; } then { policer STORM_POLICER; accept; } } term MULTICAST_TRAFFIC { from { traffic-type multicast; } then { policer STORM_POLICER; accept; } } term UNKNOWN_UNICAST_TRAFFIC { from { traffic-type unknown-unicast; } then { policer STORM_POLICER; accept; } } } } Verify that the policer rates limits storm traffic. firewall { … … … policer STORM_POLICER { if-exceeding { bandwidth-limit 10m; burst-size-limit 5m; } then discard; } If storm control is not enabled, this is a finding.
Configure storm control for each VPLS bridge domain. Base the rate limiting on expected traffic rates plus some additional capacity. Configure a policer to rate limit traffic to provide storm control for all VPLS implementations as shown in the example. [edit firewall] set policer STORM_POLICER if-exceeding bandwidth-limit 10m burst-size-limit 5m set policer STORM_POLICER then discard Configure the filter to specify traffic types to rate limit broadcast, multicast, and unknown unicast storms as shown in the example. [edit firewall family vpls filter VPLS_FLOOD_FILTER] set term BROADCAST_TRAFFIC from traffic-type broadcast set term BROADCAST_TRAFFIC then policer STORM_POLICER accept set term MULTICAST_TRAFFIC from traffic-type multicast set term MULTICAST_TRAFFIC then policer STORM_POLICER accept set term UNKNOWN_UNICAST_TRAFFIC from traffic-type unknown-unicast set term UNKNOWN_UNICAST_TRAFFIC then policer STORM_POLICER accept Apply the storm control filter to all VPLS routing instances as shown in the example. [edit routing-instances VPLS_CUST2] set forwarding-options family vpls flood input VPLS_FLOOD_FILTER
Review the router configuration to verify that PIM snooping has been configured under the routing instance protocols hierarchy for each VPLS bridge domain as shown in the example. routing-instances { VPLS_CUST2 { instance-type vpls; interface ge-0/1/0.0; route-distinguisher 22:22; vrf-target target:22:22; } protocols { vpls { site-range 9; no-tunnel-services; site R8 { site-identifier 8; interface ge-0/1/0.0; } vpls-id 102; neighbor 8.8.8.8; } pim-snooping; } } } } If the router is not configured to implement PIM snooping for each VPLS bridge domain, this is a finding.
Configure PIM snooping for each VPLS bridge domain as shown in the example below. [edit routing-instances VPLS_CUST2] set routing-instances VPLS_CUST2 protocols pim-snooping
Review the PE router configuration to determine if a MAC address limit has been set for each VPLS bridge domain. routing-instances { VPLS_CUST2 { instance-type vpls; interface ge-0/1/0.0; route-distinguisher 22:22; vrf-target target:22:22; protocols { vpls { site-range 9; mac-table-size { nnnn; } no-tunnel-services; site R8 { site-identifier 8; interface ge-0/1/0.0; } vpls-id 102; neighbor 8.8.8.8; } } } } If a limit has not been configured, this is a finding.
Configure a MAC address learning limit for each VPLS bridge domain. [edit routing-instances VPLS_CUST2 protocols vpls] set mac-table-size nnnn
Review the router configuration to verify that an ingress filter is applied to all CE-facing interfaces. interfaces { ge-0/1/0 { description "link to Customer 2"; unit 0 { family inet { filter { input INGRESS_FILTER; } address x.x.x.x/30; } } } Verify that the ingress filter discards and logs packets destined to the IP core address space. firewall { family inet { filter INGRESS_FILTER { term BLOCK_TO_CORE { from { destination-address { x.x.x.x/8; } } then { log; discard; } } term ALLOW_TRANSIT_TRAFFIC { then accept; } } } If the PE router is not configured to block any traffic with a destination address assigned to the IP core infrastructure, this is a finding. Note: Internet Control Message Protocol (ICMP) echo requests and traceroutes will be allowed to the edge from external adjacent neighbors.
Configure protection for the IP core to be implemented at the edges by blocking any traffic with a destination address assigned to the IP core infrastructure. Configure an ingress filter to discard and log packets destined to the IP core address space. [edit firewall family inet] set filter INGRESS_FILTER term BLOCK_TO_CORE from destination-address x.x.x.x/8 set filter INGRESS_FILTER term BLOCK_TO_CORE then log discard set filter INGRESS_FILTER term ALLOW_TRANSIT_TRAFFIC then accept Apply the filter inbound to all CE-facing interfaces. [edit interfaces ge-0/1/0 unit 0] set family inet filter input INGRESS_FILTER
Review the router configuration to determine if uRPF loose mode is enabled on all CE-facing interfaces. interfaces { ge-0/1/0 { description "link to Customer 2"; unit 0 { family inet { rpf-check { mode loose; } address x.x.x.x/30; } } } If uRPF loose mode is not enabled on all CE-facing interfaces, this is a finding.
Configure uRPF loose mode on all CE-facing interfaces as shown in the example. [edit interfaces ge-0/1/0 unit 0 family inet] set rpf-check mode loose
Review the router configuration to determine if it will block all packets with IP options. firewall { family inet { filter INGRESS_FILTER { term BLOCK_TO_CORE { from { destination-address { x.x.x.x/8; } } then { log; discard; } } term BLOCK_IP_OPTIONS { from { ip-options any; } then { discard; } } term ALLOW_TRANSIT_TRAFFIC { then accept; } } } If the router is not configured to drop all packets with IP options, this is a finding.
Configure the router to drop all packets with IP options. [edit firewall family inet filter INGRESS_FILTER] set term BLOCK_IP_OPTIONS from ip-options any set term BLOCK_IP_OPTIONS then discard insert term BLOCK_IP_OPTIONS before term ALLOW_TRANSIT_TRAFFIC
Review the router configuration and verify that it has been configured to enforce a QoS policy in accordance with the QoS GIG Technical Profile (GTP-0009). The router must be configured to use either configured or default Behavior Aggregate (BA) classifier on all interfaces as shown in the example below: class-of-service { … … … } interfaces { ge-0/0/1 { unit 0 { classifiers { dscp default; } } } ge-0/1/0 { unit 0 { classifiers { dscp default; } } } ge-1/0/1 { unit 0 { classifiers { dscp default; } } } ge-1/1/0 { unit 0 { classifiers { dscp default; } } } Note: The GTP QOS document (GTP-0009) can be downloaded via the following link: https://intellipedia.intelink.gov/wiki/Portal:GIG_Technical_Guidance/GTG_GTPs/GTP_Development_List If the router is not configured to enforce a QoS policy in accordance with the QoS DODIN Technical Profile, this is a finding.
Configure all interfaces to use a configured or the default BA classifier as shown in the example below: [edit class-of-service interfaces] set ge-0/0/1 unit 0 classifiers dscp default set ge-0/1/0 unit 0 classifiers dscp default set ge-1/0/1 unit 0 classifiers dscp default set ge-1/1/0 unit 0 classifiers dscp default Note: The GTP QOS document (GTP-0009) can be downloaded via the following link: https://intellipedia.intelink.gov/wiki/Portal:GIG_Technical_Guidance/GTG_GTPs/GTP_Development_List
Review the router configuration and verify that it has been configured to enforce a QoS policy in accordance with the QoS GIG Technical Profile (GTP-0009). The router must be configured to use either configured or default Behavior Aggregate (BA) classifier on all interfaces as shown in the example below: class-of-service { … … … } interfaces { ge-0/0/1 { unit 0 { classifiers { dscp default; } } } ge-0/1/0 { unit 0 { classifiers { dscp default; } } } ge-1/0/1 { unit 0 { classifiers { dscp default; } } } ge-1/1/0 { unit 0 { classifiers { dscp default; } } } Note: The GTP QOS document (GTP-0009) can be downloaded via the following link: https://intellipedia.intelink.gov/wiki/Portal:GIG_Technical_Guidance/GTG_GTPs/GTP_Development_List If the router is not configured to enforce a QoS policy in accordance with the QoS GIG Technical Profile, this is a finding.
Configure all P router interfaces and PE core-facing interfaces to use a configured or the default BA classifier as shown in the example below. [edit class-of-service interfaces] set ge-0/0/1 unit 0 classifiers dscp default set ge-0/1/0 unit 0 classifiers dscp default set ge-1/0/1 unit 0 classifiers dscp default set ge-1/1/0 unit 0 classifiers dscp default Note: The GTP QOS document (GTP-0009) can be downloaded via the following link: https://intellipedia.intelink.gov/wiki/Portal:GIG_Technical_Guidance/GTG_GTPs/GTP_Development_List
Verify that a forwarding class has been configured for the Scavenger class. CS1 has been adopted as the forwarding class; hence, the example below will define class CS1 to be used. class-of-service { … … … } forwarding-classes { class CS1 queue-num 7 priority low; } The Scavenger class is marked at the access layer with DSCP CS1. Hence, the router must maintain the marking and assign the packet to the configured forwarding class CS1. PE Router only - Verify that the Multifield (MF) classifier has provisioned for this class as shown in the example below. firewall { family inet { filter CLASSIFY_TRAFFIC { … … … } term SCAVENGER { from { dscp cs1; } then { forwarding-class CS1; accept; } } term ACCEPT_OTHER { then { forwarding-class best-effort; accept; } } } } } PE and P router - Verify that a Behavior aggregate (BA) classifier has been configured to match the Scavenger class (CS1) as shown in the example below. class-of-service { classifiers { dscp CLASSIFIER { import default; forwarding-class CS1 { loss-priority high code-points 001000; } } } Note: A proactive approach to mitigating DoS and worm flooding attacks within the base/camp/agency enclaves is to respond immediately to out-of-profile network behavior indicative of a DoS or worm attack via access-Layer policers. Such policers can meter traffic rates received from endpoint devices. When these traffic flows exceed specified rates, they no longer are considered normal flows and henceforth can be set to the Scavenger class marking (DSCP CS1). P router – Verify that the BA classifier has been applied to all interfaces as shown in the example below. class-of-service { … … … } interfaces { ge-0/0/1 { unit 0 { classifiers { dscp CLASSIFIER; } } } ge-0/1/1 { unit 0 { classifiers { dscp CLASSIFIER; } } } } } Remaining steps only apply to the PE router. Verify that a scheduler has been configured for the Scavenger class as shown in the example below. class-of-service { … … … } schedulers { … … … } SCAVENGER_SCHED { transmit-rate percent 5; buffer-size percent 5; priority low; } } } Verify that the scheduler has been added to the scheduler map. class-of-service { … … … } scheduler-maps { QOS_SCHED_MAP { forwarding-class expedited-forwarding scheduler VOIP_SCHED; forwarding-class network-control scheduler CONTROL_PLANE_SCHED; forwarding-class assured-forwarding scheduler MGMT_SCHED; forwarding-class best-effort scheduler BEST_EFFORT_SCHED; forwarding-class CS1 scheduler SCAVENGER_SCHED; } } Verify that rewrite rules have been created to mark DSCP CS1 for those packets assigned to the Scavenger class with the appropriate code points. class-of-service { … … … } rewrite-rules { dscp REWRITE_DSCP { import default; forwarding-class CS1 { loss-priority high code-point 001000; } } } Verify that the scheduler map, rewrite rules, and the BA classifier has been applied to all core-facing interfaces. class-of-service { … … … } interfaces { ge-2/1/1 { scheduler-map QOS_SCHED_MAP; unit 0 { classifiers { dscp CLASSIFIER; } rewrite-rules { dscp REWRITE_DSCP; } } } ge-2/0/1 { scheduler-map QOS_SCHED_MAP; unit 0 { rewrite-rules { dscp REWRITE_DSCP; } } } } If QoS policy to limit the effects of packet flooding denial-of-service (DoS) attacks has not been configured, this is a finding.
Configure a forwarding class has been configured for the Scavenger class as shown in the example below. [edit class-of-service forwarding-classes] set class CS1 queue-num 7 priority low The Scavenger class is marked at the access layer with DSCP CS1. Hence, the router must maintain the marking and assign the packet to the configured forwarding class CS1. PE Router only – Configure a Multifield (MF) classifier to provision for the Scavenger class as shown in the example below. [edit firewall family inet filter CLASSIFY_TRAFFIC] set term SCAVENGER from dscp cs1 set term SCAVENGER then forwarding-class CS1 accept insert term SCAVENGER before term ACCEPT_OTHER PE and P Router – Configure a Behavior aggregate (BA) classifier to match on the packets marked with DSCP CS1. [edit class-of-service classifiers] set dscp CLASSIFIER import default forwarding-class CS1 loss-priority high code-points 001000 P router only – Apply the BA classifier to all interfaces. [edit class-of-service interfaces] set ge-0/0/1 unit 0 classifiers dscp CLASSIFIER set ge-0/1/1 unit 0 classifiers dscp CLASSIFIER Remaining steps are only applicable to the PE router. Configure a scheduler for the Scavenger class. [edit class-of-service schedulers] set SCAVENGER_SCHED transmit-rate percent 5 set SCAVENGER_SCHED buffer-size percent 5 set SCAVENGER_SCHED priority low set BEST_EFFORT_SCHED transmit-rate percent 55 Add the Scavenger scheduler to the scheduler map. [edit class-of-service scheduler-maps QOS_SCHED_MAP] set forwarding-class CS1 scheduler SCAVENGER_SCHED Apply the scheduler map to all core-facing interfaces. [edit class-of-service interfaces] set ge-2/1/1 scheduler-map QOS_SCHED_MAP set ge-1/0/1 scheduler-map QOS_SCHED_MAP Note: The above step should already have been completed. Configure rewrite rules to ensure egress Scavenger packets will continue to be marked with DSCP CS1. [edit class-of-service rewrite-rules] set dscp REWRITE_DSCP import default forwarding-class CS1 loss-priority high code-point 001000 Apply the configured rewrite rules to all core-facing interfaces. [edit class-of-service interfaces] set ge-2/1/1 unit 0 rewrite-rules dscp REWRITE_DSCP set ge-1/0/1 unit 0 rewrite-rules dscp REWRITE_DSCP
Review the network's multicast topology diagram. Review the router configuration to verify that only the PIM interfaces as shown in the multicast topology diagram are enabled for PIM. protocols { … … … pim { interface ge-1/0/1.0 { mode sparse; } interface ge-1/1/1.0 { mode sparse; } interface ge-2/1/0.0 { mode sparse; } interface ge-2/1/1.0 { mode sparse; } } If an interface is not required to support multicast routing and it is enabled, this is a finding.
Document all enabled interfaces for PIM in the network's multicast topology diagram. Disable support for PIM on interfaces that are not required to support it. [edit protocols pim] delete interface ge-2/1/1.0
This requirement is not applicable for the DoDIN Backbone. Verify all interfaces enabled for PIM have a neighbor filter bound to the interface as shown in the example below. protocols { … … … pim { interface ge-1/0/1.0 { mode sparse; neighbor-policy PIM_NBR1_POLICY; } interface ge-1/1/1.0 { mode sparse; neighbor-policy PIM_NBR2_POLICY; } interface ge-2/1/0.0 { mode sparse; neighbor-policy PIM_NBR3_POLICY; } } Review the prefix list and policy statements configured for filtering PIM neighbors as shown in the example below. policy-options { prefix-list PIM_NBR1 { x.x.x.x/32; } prefix-list PIM_NBR2 { x.x.x.x/32; } prefix-list PIM_NBR3 { x.x.x.x/32; } policy-statement PIM_NBR1_POLICY { from { prefix-list PIM_NBR1; } then accept; } policy-statement PIM_NBR2_POLICY { from { prefix-list PIM_NBR2; } then accept; } policy-statement PIM_NBR3_POLICY { from { prefix-list PIM_NBR3; } then accept; } If PIM neighbor filters are not bound to all interfaces that have PIM enabled, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure neighbor filters to only accept PIM control plane traffic from documented PIM neighbors. Bind neighbor filters to all PIM enabled interfaces. Configure prefix list for each neighbor. [edit policy-options] set prefix-list PIM_NBR1 x.x.x.x/32 set prefix-list PIM_NBR2 x.x.x.x/32 set prefix-list PIM_NBR3 x.x.x.x/32 Configure policy statements for each PIM neighbor. [edit policy-options] set policy-statement PIM_NBR1_POLICY from prefix-list PIM_NBR1 set policy-statement PIM_NBR1_POLICY then accept set policy-statement PIM_NBR2_POLICY from prefix-list PIM_NBR1 set policy-statement PIM_NBR2_POLICY then accept set policy-statement PIM_NBR3_POLICY from prefix-list PIM_NBR1 set policy-statement PIM_NBR3_POLICY then accept Apply the neighbor policy to all interfaces enabled for PIM. [edit protocols pim] set interface ge-1/0/1.0 neighbor-policy PIM_NBR1_POLICY set interface ge-1/1/1.0 neighbor-policy PIM_NBR1_POLICY set interface ge-2/1/0.0 neighbor-policy PIM_NBR1_POLICY
Review the router configuration to verify it is blocking admin-scope multicast traffic (239.0.0.0/8) at the multicast domain edge as shown in the example below: routing-options { … … … multicast { scope ADMIN_SCOPE { prefix 239.0.0.0/8; interface [ ge-1/0/1.0 ge-1/1/1.0 ]; } } } If the router is not configured to block admin-scoped multicast traffic at the multicast domain edge, this is a finding.
Configure the router to block admin-scoped multicast traffic at the multicast domain edge as shown in the example below: [edit routing-options] set multicast scope ADMINL_SCOPE interface ge-1/0/1.0 prefix 239.0.0.0/8 set multicast scope ADMINL_SCOPE interface ge-1/1/1.0 prefix 239.0.0.0/8
Review the router configuration to determine if forwarding cache thresholds are defined as shown in the example below. routing-options { multicast { … … … } forwarding-cache { threshold { suppress 5000; reuse 4000; } } } } If the RP router is not configured to limit the multicast forwarding cache to ensure that its resources are not saturated, this is a finding.
Configure the router to limit the multicast forwarding cache for source-active entries. [edit routing-options multicast] set forwarding-cache threshold suppress 5000 reuse 4000
Verify that the RP router is configured to filter PIM register messages. Verify that the RP has a register policy enabled as shown in the example below. protocols { … … … } pim { rp { rp-register-policy MULTICAST_REGISTER_POLICY; local { address 2.2.2.2; } } Verify that the register policy has defined both bad multicast groups and sources as shown in the example below. policy-options { … … … } policy-statement MULTICAST_REGISTER_POLICY { term BAD_SOURCES { from { source-address-filter x.x.x.x/32 exact; source-address-filter x.x.x.x/24 orlonger; } then reject; } term BAD_GROUPS { from { route-filter 224.1.1.0/24 orlonger; route-filter 225.1.2.3/32 exact; route-filter 239.0.0.0/8 orlonger; … … … route-filter 232.0.0.0/8 orlonger; } then reject; } term ALLOW_OTHER { then accept; } } If the RP router peering with PIM-SM routers is not configured with a policy to block registration messages for any undesirable multicast groups and sources, this is a finding.
Configure the router to filter PIM register messages received from a multicast DR for any undesirable multicast groups and sources. [edit policy-options policy-statement MULTICAST_REGISTER_POLICY] set term BAD_SOURCES from source-address-filter x.x.x.x/32 exact set term BAD_SOURCES from source-address-filter x.x.x.x/24 orlonger set term BAD_GROUPS from route-filter 224.1.1.0/24 orlonger set term BAD_GROUPS from route-filter 225.1.2.3/32 exact set term BAD_GROUPS from route-filter 239.0.0.0/8 orlonger set term BAD_GROUPS then reject set term ALLOW_OTHER then accept [edit protocols pim rp] set rp-register-policy MULTICAST_REGISTER_POLICY
Review the RP router configuration to determine if it filters PIM join messages for any reserved multicast groups. Step 1: Verify that a PIM import statement has been configured as shown in the example below: protocols { … … … } pim { import MULTICAST_JOIN_POLICY; Step 2: Verify that the join policy has defined both bad multicast groups and sources as shown in the example below: policy-options { … … … } policy-statement MULTICAST_JOIN_POLICY { term BAD_GROUPS { from { route-filter 224.1.1.0/24 orlonger; route-filter 225.1.2.3/32 exact; … … … route-filter 232.0.0.0/8 orlonger; } then reject; } term ALLOW_OTHER { then accept; } } If the RP router peering with PIM-SM routers is not configured with a PIM import policy to block join messages for any undesirable multicast groups, this is a finding.
RP routers that are peering with customer PIM-SM routers must implement a PIM import policy to block join messages for any undesirable multicast groups. Step 1: Configure a multicast join policy to filter bad groups and sources as shown in the example below: [edit policy-options policy-statement MULTICAST_JOIN_POLICY] set term BAD_GROUPS from route-filter 224.1.1.0/24 orlonger set term BAD_GROUPS from route-filter 225.1.2.3/32 exact … … … set term BAD_GROUPS then reject set term ALLOW_OTHER then accept Step 2: Configure PIM to enable the join policy as shown in the example below: [edit protocols pim] set import MULTICAST_JOIN_POLICY
Review the configuration of the RP to verify that it is rate limiting the number of multicast register messages. protocols { … … … } pim { rp { register-limit maximum nnnnn; local { address 2.2.2.2; } } Note: Each any-source group (*,G) counts as one group toward the limit. Each source-specific group (S,G) counts as one group toward the limit. If the RP is not limiting multicast register messages, this is a finding.
Configure the RP to rate limit the number of multicast register messages it will allow for each (S, G) entry. [edit protocols pim rp] set register-limit maximum nnnnn
Review the configuration of the DR to verify that it is filtering IGMP or MLD report messages, allowing hosts to join only those groups that have been approved. Verify that a group policy has been configured to filter IGMP join requests as shown in the example below. protocols { igmp { interface ge-1/0/1.0 { group-policy MULTICAST_JOIN_POLICY; } } Verify that the group policy only allows join requests for those groups that have been approved. policy-options { … … … } policy-statement MULTICAST_JOIN_POLICY { … … … } term BAD_GROUPS { from { route-filter 224.1.1.0/24 orlonger; route-filter 225.1.2.3/32 exact; route-filter 239.0.0.0/8 orlonger; … … … route-filter 232.0.0.0/8 orlonger; } then reject; } term ALLOW_APPROVED { then accept; } } Note: This requirement is only applicable to Source Specific Multicast (SSM) implementation. This requirement is not applicable to Any Source Multicast (ASM) since the filtering is being performed by the Rendezvous Point router. If the DR is not filtering IGMP or MLD report messages to only allow joins for approved groups, this is a finding.
Configure the DR to filter the IGMP and MLD report messages to allow hosts to join only those multicast groups that have been approved. Configure a multicast join policy to filter groups that have not been approved as shown in the example below. [edit policy-options policy-statement MULTICAST_JOIN_POLICY] set term BAD_GROUPS from route-filter 224.1.1.0/24 orlonger set term BAD_GROUPS from route-filter 225.1.2.3/32 exact set term BAD_GROUPS from route-filter 239.0.0.0/8 orlonger set term BAD_GROUPS then reject set term ALLOW_APPROVED then accept Apply the policy to all interfaces enabled for IGMP. [edit protocols igmp] set interface ge-1/0/1.0 group-policy MULTICAST_JOIN_POLICY
Review the configuration of the DR to verify that it is filtering IGMP or MLD report messages, allowing hosts to only join multicast groups from sources that have been approved. Verify that a group policy has been configured to filter IGMP join requests as shown in the example below. protocols { igmp { interface ge-1/0/1.0 { group-policy MULTICAST_JOIN_POLICY; } } Verify that the policy only allows join requests for those sources that have been approved. policy-options { … … … } policy-statement MULTICAST_JOIN_POLICY { term BAD_SOURCES { from { source-address-filter x.x.x.x/32 exact; source-address-filter x.x.x.x/24 orlonger; } then reject; } … … … } term ALLOW_APPROVED { then accept; } } Note: This requirement is only applicable to Source Specific Multicast (SSM) implementation. If the DR is not filtering IGMP or MLD report messages to only allow joins for approved sources, this is a finding.
Configure the DR to filter the IGMP and MLD report messages to allow hosts to join only those multicast groups from sources that have been approved. Configure a multicast join policy to filter unauthorized multicast sources. [edit policy-options policy-statement MULTICAST_JOIN_POLICY] set term BAD_SOURCES from source-address-filter x.x.x.x/32 exact set term BAD_SOURCES from source-address-filter x.x.x.x/24 orlonger set term BAD_SOURCES then reject set term ALLOW_APPROVED then accept Apply the policy to all interfaces enabled for IGMP. [edit protocols igmp] set interface ge-1/0/1.0 group-policy MULTICAST_JOIN_POLICY
Review the DR configuration to verify that it is limiting the number of mroute states via IGMP or MLD. protocols { igmp { interface ge-1/0/1.0 { group-limit nnn; } } If the DR is not limiting multicast join requests via IGMP or MLD, this is a finding.
Configure the DR on a global or interface basis to limit the number of mroute states resulting from IGMP or MLD membership reports. [edit protocols igmp] set interface ge-1/0/1.0 group-limit nnn
Review the multicast last-hop router configuration to verify that the SPT switchover threshold is set to infinity for all or specific multicast groups and sources. Verify that an infinity policy has been enabled for PIM. protocols { … … … } pim { spt-threshold { infinity SPT_INFINITY; } } } Verify that the infinity policy defines specific multicast groups and sources or all multicast groups and sources as shown in the example below. policy-options { … … … } policy-statement SPT_INFINITY { term ALL_GROUPS { from { route-filter 234.0.0.0/8 orlonger; } then accept; } } } If any multicast router is not configured to set the SPT threshold to infinity to minimalize (S, G) state, this is a finding.
Configure the multicast router to increase the SPT threshold or set it to infinity to minimalize (S, G) state within the multicast topology where ASM is deployed. Configure a policy statement to set SPT threshold to infinity for all multicast groups or only specific groups and sources. [edit policy-options] set policy-statement SPT_INFINITY term ALL_GROUPS from route-filter 234.0.0.0/8 orlonger set policy-statement SPT_INFINITY term ALL_GROUPS then accept Apply the SPT infinity policy. [edit protocols pim] set spt-threshold infinity SPT_INFINITY
Review the router configuration to determine if there is a receive path or interface filter to only accept MSDP packets from known MSDP peers. Verify that the loopback has been configured to filter packets destined to the routing engine as shown in the example below. interfaces { … … … } lo0 { unit 0 { family inet { filter { input PROTECT_RE; } address 2.2.2.2/32; } } } } Verify that the filter is configured to only accept MSDP packets from known MSDP peers as shown in the example below. firewall { family inet { filter PROTECT_RE { term MSDP_PEERS { from { source-address { 0.0.0.0/0; 1.1.1.1/32 except; 5.5.5.5/32 except; } protocol tcp; port msdp; } then { discard; } } term ALLOW_OTHER { then accept; } } } } If the router is not configured to only accept MSDP packets from known MSDP peers, this is a finding.
Configure the receive path filter to only accept MSDP packets from known MSDP peers as shown in the following example: [edit firewall family inet filter PROTECT_RE] set term MSDP_PEERS from protocol tcp port msdp set term MSDP_PEERS from source-address 0.0.0.0/0 set term MSDP_PEERS from source-address 1.1.1.1/32 except set term MSDP_PEERS from source-address 5.5.5.5/32 except set term MSDP_PEERS then discard set term ALLOW_OTHER then accept Apply the filter to the loopback interface. [edit interfaces lo0 unit 0 family inet] set filter input PROTECT_RE
Review the router configuration to determine if received MSDP packets are authenticated. protocols { msdp { group AS25 { peer 5.5.5.5 { authentication-key "$8$KspW87GUH.mTxNfz"; ## SECRET-DATA} } } If the router does not require MSDP authentication, this is a finding.
Configure the router to authenticate MSDP messages as shown in the following example: [edit protocols msdp group AS25 peer 5.5.5.5] set authentication-key xxxxxxxx
Review the router configuration to determine if there is import policy to block source-active multicast advertisements for undesirable multicast groups and sources. policy-options { … … … } policy-statement SA_IMPORT { term BAD_GROUPS { from { route-filter 224.0.1.2/32 exact; route-filter 224.77.0.0/16 orlonger; } then reject; } term BAD_SOURCES { from { source-address-filter x.x.x.x /8 orlonger; source-address-filter x.x.x.x /8 orlonger; } then reject; } term ACCEPT_OTHERS { then accept; } } Verify that an import source-active filter has been applied to MSDP. protocols { … … … } msdp { import SA_IMPORT; If the router is not configured with an import policy to block undesirable SA multicast advertisements, this is a finding.
Configure the MSDP to implement an import policy to block multicast advertisements for undesirable multicast groups and sources. Configure the source-active filter to reject undesirable multicast groups and sources as shown in the example below. [edit policy-options] set policy-statement SA_IMPORT term BAD_GROUPS from route-filter 224.0.1.2/32 exact set policy-statement SA_IMPORT term BAD_GROUPS from route-filter 224.77.0.0/16 orlonger set policy-statement SA_IMPORT term BAD_GROUPS then reject set policy-statement SA_IMPORT term BAD_SOURCES from source-address-filter x.x.x.x/8 orlonger set policy-statement SA_IMPORT term BAD_SOURCES from source-address-filter x.x.x.x/16 orlonger set policy-statement SA_IMPORT term BAD_SOURCES then reject set policy-statement SA_IMPORT term ACCEPT_OTHERS then accept Configure the source-active filter to be an import filter. [edit protocols msdp] set import SA_IMPORT
Review the router configuration to determine if there is export policy to block local source-active multicast advertisements. Verify that the router is configured with an export policy to filter multicast source-active advertisements. policy-options { … … … } policy-statement SA_EXPORT { term INTERNAL_GROUP { from { route-filter 239.0.0.0/8 orlonger; } then reject; } term INTERNAL_ADDR { from { source-address-filter 10.0.0.0/8 orlonger; } then reject; } term ACCEPT_OTHERS { then accept; } } Verify that an export source-active filter has been applied to MSDP. protocols { … … … } msdp { export SA_EXPORT; If the router is not configured with an export policy to block local source-active multicast advertisements, this is a finding.
Configure the router with an export policy avoid global visibility of local multicast (S, G) states. The example below will avoid exporting multicast active sources belonging to the private network. [edit policy-options] set policy-statement SA_EXPORT term INTERNAL_GROUP from route-filter 239.0.0.0/8 orlonger set policy-statement SA_EXPORT term INTERNAL_GROUP then reject set policy-statement SA_EXPORT term INTERNAL_ADDR from source-address-filter 10.0.0.0/8 orlonger set policy-statement SA_EXPORT term INTERNAL_ADDR then reject set policy-statement SA_EXPORT term ACCEPT_OTHERS then accept [edit protocols msdp] set export SA_EXPORT
Review the router configuration to determine if it is configured to limit the amount of source-active messages it accepts on a per-peer basis. protocols { … … … } msdp { export SA_EXPORT; import SA_IMPORT; group AS25 { peer x.x.x.x { active-source-limit { maximum nnn; } If the router is not configured to limit the source-active messages it accepts, this is a finding.
Configure the router to limit the amount of source-active messages it accepts from each peer. [edit protocols msdp group AS25 peer x.x.x.x] set active-source-limit maximum nnn
Review the router configuration to verify that a loopback address has been configured. interfaces { … … … lo0 { unit 0 { family inet { address 2.2.2.2/32; } } } } Verify that the loopback interface is used as the source address for all MSDP packets generated by the router. protocols { msdp { group AS25 { peer 5.5.5.5 { local-address 2.2.2.2; } } } If the router does not use its loopback address as the source address when originating MSDP traffic, this is a finding.
Configure the router to use its loopback address is used as the source address when sending MSDP packets. [edit protocols msdp] set group AS_5 peer 5.5.5.5 local-address 2.2.2.2
This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify that Router Advertisements are suppressed on all external IPv6-enabled interfaces as shown in the example below. By default, router advertisements are disabled by Junos. Verify that there are no external-facing interfaces defined under the protocols router-advertisement hierarchy as shown in the example below. protocols { router-advertisement { interface fe-0/1/0.0 { prefix 2001:1:123::/64; } } } If the router is not configured to suppress Router Advertisements on all external IPv6-enabled interfaces, this is a finding.
Remove any external IPv6-enabled interfaces from the protocols router-advertisement hierarchy.
Review the router configuration to ensure FEC0::/10 IP addresses are not defined. If FEC0::/10 IP addresses are defined, this is a finding.
Configure the device using authorized IPv6 addresses.
This requirement is not applicable for the DODIN Backbone. Review the router configuration to determine if it is configured to drop IPv6 packets containing a Routing Header of type 0, 1, or 3-255. Step 1: Verify that all external IPv6-enabled interfaces have an IPv6 filter as shown in the example below. interfaces { ge-0/0/0 { unit 0 { family inet6 { filter { input IPV6-INGRESS-FILTER; } address 2001:1:0:146::1/64; } } } } Step 2: Verify that the IPV6 filter blocks all packets with a routing header as shown in the example below. firewall { family inet6 { filter IPV6-INGRESS-FILTER { term ROUTING_HEADER { from { next-header routing; } then { syslog; discard; } } term ALLOW_TCP_ESTABLISHED { from { next-header tcp; tcp-established; } then accept; } term DENY_BY_DEFAULT { then { syslog; discard; } } } } } Note: Currently JUNOS has no method to filter option type within a routing header. Hence, all packets with a routing header must be dropped. If the router is not configured to drop IPv6 packets containing a Routing Header of type 0, 1, or 3-255, this is a finding.
Step 1: Configure a filter to block packets with a routing header as shown in the example. user@R1# edit firewall family inet6 user@R1# edit filter IPV6-INGRESS-FILTER user@R1# set term ROUTING_HEADER from next-header routing user@R1# set term ROUTING_HEADER then discard syslog user@R1# top Step 2: Apply the filter inbound on all external IPv6-enabled interfaces. user@R1# edit interfaces ge-0/0/0 unit 0 family inet6 user@R1# set filter input IPV6-INGRESS-FILTER user@R1# commit
This requirement is not applicable for the DODIN Backbone. Review the router configuration to determine if ACLs are bound to the applicable interfaces to drop IPv6 packets containing a Hop-by-Hop header with option type values of 0x04 (Tunnel Encapsulation Limit), 0xC9 (Home Address Destination), or 0xC3 (NSAP Address). Step 1: Verify that all external IPv6-enabled interfaces have an IPv6 filter as shown in the example below. interfaces { ge-0/0/0 { unit 0 { family inet6 { filter { input IPV6-INGRESS-FILTER; } address 2001:1:0:146::1/64; } } } } Step 2: Verify that the IPV6 filter blocks all packets with a Hop-by-Hop header as shown in the example below. firewall { family inet6 { filter IPV6-INGRESS-FILTER { term HOP_BY_HOP_HEADER { from { next-header hop-by-hop; } then { syslog; discard; } } term ALLOW_TCP_ESTABLISHED { from { next-header tcp; tcp-established; } then accept; } term DENY_BY_DEFAULT { then { syslog; discard; } } } } } Note: Currently JUNOS has no method to filter option type within Hop-by-Hop header. Hence, all packets with the Hop-by-Hop header must be dropped. If the router is not configured to drop IPv6 packets containing a Hop-by-Hop header with invalid option type values, this is a finding.
Configure the router to drop IPv6 packets containing a Hop-by-Hop header as shown in the example below. Step 1: Configure a filter to block packets with a Hop-by-Hop header as shown in the example. user@R1# edit firewall family inet6 user@R1# edit filter IPV6-INGRESS-FILTER user@R1# set term HOP_BY_HOP_HEADER from next-header hop-by-hop user@R1# set term HOP_BY_HOP_HEADER then discard syslog user@R1# top Step 2: Apply the filter inbound on all external IPv6-enabled interfaces. user@R1# edit interfaces ge-0/0/0 unit 0 family inet6 user@R1# set filter input IPV6-INGRESS-FILTER user@R1# commit
This requirement is not applicable for the DODIN Backbone. Review the router configuration and determine if filters are bound to the external interfaces to drop all IPv6 packets containing a Destination Option header with option type values of 0x05 (Router Alert) or 0xC2 (Jumbo Payload). The following example will block any inbound IPv6 packet containing a Destination Option header with option type values of with option type values of 0x05 (Router Alert) or 0xC2 (Jumbo Payload): Step 1: Verify that all external IPv6-enabled interfaces have an IPv6 filter as shown in the example below. interfaces { ge-0/0/0 { unit 0 { family inet6 { filter { input IPV6-INGRESS-FILTER; } address 2001:1:0:146::1/64; } } } } Step 2: Verify that the IPV6 filter blocks all packets with a Destination Option header as shown in the example below. firewall { family inet6 { filter IPV6-INGRESS-FILTER { term DEST_ OPT_HEADER { from { next-header dstops; } then { syslog; discard; } } term ALLOW_TCP_ESTABLISHED { from { next-header tcp; tcp-established; } then accept; } term DENY_BY_DEFAULT { then { syslog; discard; } } } } } Note: Currently JUNOS has no method to filter option type within Destination Option header. Hence, all packets with the Destination Option header must be dropped. If the router is not configured to drop IPv6 packets containing a Destination Option header with invalid option type values, this is a finding.
Step 1: Configure a filter to block packets with a Destination Option header as shown in the example. user@R1# edit firewall family inet6 user@R1# edit filter IPV6-INGRESS-FILTER user@R1# set term DEST_ OPT_HEADER from next-header dstops user@R1# set term DEST_ OPT_HEADER then discard syslog user@R1# top Step 2: Apply the filter inbound on all external IPv6-enabled interfaces. user@R1# edit interfaces ge-0/0/0 unit 0 family inet6 user@R1# set filter input IPV6-INGRESS-FILTER user@R1# commit
This requirement is not applicable for the DODIN Backbone. Review the router configuration and determine if filters are bound to the applicable interfaces to drop all inbound IPv6 packets containing an option type values of 0x8A (Endpoint Identification) regardless of whether it appears in a Hop-by-Hop or Destination Option header. The following example will block IPv6 packet containing either a Hop-by-Hop or Destination Option header: family inet6 { filter IPV6-INGRESS-FILTER { term HOP_BY_HOP_HEADER { from { next-header hop-by-hop; } then { syslog; discard; } } term DEST_ OPT_HEADER { from { next-header dstops; } then { syslog; discard; } } term ALLOW_TCP_ESTABLISHED { from { next-header tcp; tcp-established; } then accept; } term DENY_BY_DEFAULT { then { syslog; discard; } } } } } Note: Currently JUNOS has no method to filter option type within either Hop-by-Hop or Destination Option header. Hence, all packets with a Hop-by-Hop or Destination Option headers must be dropped. If the router is not configured to drop IPv6 packets containing an extension header with the Endpoint Identification option, this is a finding.
Step 1: Configure a filter to block packets with either a Hop-by-Hop or Destination Option header as shown in the example. user@R1# edit firewall family inet6 user@R1# edit filter IPV6-INGRESS-FILTER user@R1# set term HOP_BY_HOP_HEADER from next-header hop-by-hop user@R1# set term HOP_BY_HOP_HEADER then discard syslog user@R1# set term DEST_ OPT_HEADER from next-header dstops user@R1# set term DEST_ OPT_HEADER then discard syslog user@R1# top Step 2: Apply the filter inbound on all external IPv6-enabled interfaces. user@R1# edit interfaces ge-0/0/0 unit 0 family inet6 user@R1# set filter input IPV6-INGRESS-FILTER user@R1# commit
This requirement is not applicable for the DODIN Backbone. Review the router configuration and determine if filters are bound to the applicable interfaces to drop IPv6 packets containing a Destination Option header with option type value of 0xC3 (NSAP address). The following example will block any inbound IPv6 packet containing a Destination Option header: Step 1: Verify that all external IPv6-enabled interfaces have an IPv6 filter as shown in the example below. interfaces { ge-0/0/0 { unit 0 { family inet6 { filter { input IPV6-INGRESS-FILTER; } address 2001:1:0:146::1/64; } } } } Step 2: Verify that the IPV6 filter blocks all packets with a Destination Option header as shown in the example below. firewall { family inet6 { filter IPV6-INGRESS-FILTER { term DEST_ OPT_HEADER { from { next-header dstops; } then { syslog; discard; } } term ALLOW_TCP_ESTABLISHED { from { next-header tcp; tcp-established; } then accept; } term DENY_BY_DEFAULT { then { syslog; discard; } } } } } Note: Currently JUNOS has no method to filter option type within Destination Option header. Hence, all packets with the Destination Option header must be dropped. If the router is not configured to drop IPv6 packets containing the NSAP address option within Destination Option header, this is a finding.
Step 1: Configure a filter to block packets with a Destination Option header as shown in the example. user@R1# edit firewall family inet6 user@R1# edit filter IPV6-INGRESS-FILTER user@R1# set term DEST_ OPT_HEADER from next-header dstops user@R1# set term DEST_ OPT_HEADER then discard syslog user@R1# top Step 2: Apply the filter inbound on all external IPv6-enabled interfaces. user@R1# edit interfaces ge-0/0/0 unit 0 family inet6 user@R1# set filter input IPV6-INGRESS-FILTER user@R1# commit
This requirement is not applicable for the DODIN Backbone. Review the router configuration and determine if filters are bound to the applicable interfaces to drop all inbound IPv6 packets containing an undefined option type value regardless of whether they appear in a Hop-by-Hop or Destination Option header. Undefined values are 0x02, 0x03, 0x06, 0x9 – 0xE, 0x10 – 0x22, 0x24, 0x25, 0x27 – 0x2F, and 0x31 – 0xFF. The following example will block any inbound IPv6 packet containing either a Hop-by-Hop or Destination Option header: family inet6 { filter IPV6-INGRESS-FILTER { term HOP_BY_HOP_HEADER { from { next-header hop-by-hop; } then { syslog; discard; } } term DEST_ OPT_HEADER { from { next-header dstops; } then { syslog; discard; } } term ALLOW_TCP_ESTABLISHED { from { next-header tcp; tcp-established; } then accept; } term DENY_BY_DEFAULT { then { syslog; discard; } } } } } Note: Currently JUNOS has no method to filter option type within either Hop-by-Hop or Destination Option header. Hence, all packets with a Hop-by-Hop or Destination Option headers must be dropped. If the router is not configured to drop IPv6 packets containing a Hop-by-Hop or Destination Option extension header with an undefined option type, this is a finding.
Step 1: Configure a filter to block packets with either a Hop-by-Hop or Destination Option header as shown in the example. user@R1# edit firewall family inet6 user@R1# edit filter IPV6-INGRESS-FILTER user@R1# set term HOP_BY_HOP_HEADER from next-header hop-by-hop user@R1# set term HOP_BY_HOP_HEADER then discard syslog user@R1# set term DEST_ OPT_HEADER from next-header dstops user@R1# set term DEST_ OPT_HEADER then discard syslog user@R1# top Step 2: Apply the filter inbound on all external IPv6-enabled interfaces. user@R1# edit interfaces ge-0/0/0 unit 0 family inet6 user@R1# set filter input IPV6-INGRESS-FILTER user@R1# commit