Juniper EX Series Switches Router Security Technical Implementation Guide
- Version/Release: V2R1
- Published: 2024-06-10
- Released: 2024-07-24
-
Expand All:
- Severity:
-
Sort:
Compare
Select any two versions of this STIG to compare the individual requirements
View
Select any old version/release of this STIG to view the previous requirements
- RMF Control
- AC-4
- Severity
- Medium
- CCI
- CCI-001368
- Version
- JUEX-RT-000010
- Vuln IDs
-
- V-253973
- Rule IDs
-
- SV-253973r843952_rule
Checks: C-57425r843950_chk
This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify that stateless firewall filters are configured to allow or deny traffic for specific source and destination addresses as well as ports and protocols. Verify the IP addresses are appropriate for the target environment. IP addresses are configured in lists at [edit policy-options] or are directly embedded into each term. [edit policy-options] prefix-list inside-addresses-ipv4 { <inside IPv4 subnet>/<mask>; <inside IPv4 subnet>/<mask>; } prefix-list inside-addresses-ipv6 { <inside IPv6 subnet>/<prefix>; <inside IPv6 subnet>/<prefix>; } For example: [edit firewall] family inet { filter authorized-outbound-ipv4 { term permitted-http { from { source-prefix-list { inside-addresses-ipv4; } destination-address { <destination IPv4 address>/<mask>; } protocol tcp; destination-port http; } then accept; } : <other terms> : term permitted-source-addresses { from { source-prefix-list { inside-addresses-ipv4; } protocol-except tcp; destination-port-except http; } then accept; } term default-deny { then { log; syslog; discard; } } } } family inet6 { filter authorized-outbound-ipv6 { term permitted-http { from { source-prefix-list { inside-addresses-ipv6; } destination-address { <destination IPv6 address>/<prefix>; } next-header tcp; destination-port http; } then accept; } : <other terms> : term permitted-source-addresses { from { source-prefix-list { inside-addresses-ipv6; } next-header-except tcp; destination-port-except http; } then accept; } term default-deny { then { log; syslog; discard; } } } } Verify filters are applied to the correct interface. For example, the "authorized-outbound" filter, as written, should be applied to the ingress of internal interfaces: [edit interfaces] <internal interface name> { unit <number> { family inet { filter { input authorized-outbound-ipv4; } address <IPv4 address>/<mask>; } family inet6 { filter { input authorized-outbound-ipv6; } address <IPv6 address>/<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" and "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. 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.
Fix: F-57376r843951_fix
This requirement is not applicable for the DODIN Backbone. Configure stateless firewall filters to allow or deny traffic for specific source and destination addresses as well as ports and protocols. Example prefix-lists: set policy-options prefix-list inside-addresses-ipv4 <inside IPv4 subnet> set policy-options prefix-list inside-addresses-ipv6 <inside IPv6 subnet> Example firewall filter: set firewall family inet filter authorized-outbound-ipv4 term permitted-source-addresses from source-prefix-list inside-addresses-ipv4 set firewall family inet filter authorized-outbound-ipv4 term permitted-source-addresses then accept set firewall family inet filter authorized-outbound-ipv4 term 2 then log set firewall family inet filter authorized-outbound-ipv4 term 2 then syslog set firewall family inet filter authorized-outbound-ipv4 term 2 then discard set firewall family inet6 filter authorized-outbound-ipv6 term permitted-source-addresses from source-prefix-list inside-addresses-ipv6 set firewall family inet6 filter authorized-outbound-ipv6 term permitted-source-addresses then accept set firewall family inet6 filter authorized-outbound-ipv6 term 2 then log set firewall family inet6 filter authorized-outbound-ipv6 term 2 then syslog set firewall family inet6 filter authorized-outbound-ipv6 term 2 then discard Example firewall filter applied to ingress of internal interface: set interfaces <interface name> unit <number> family inet filter input authorized-outbound-ipv4 set interfaces <interface name> unit <number> family inet address <IPv4 address>/<mask> set interfaces <interface name> unit <number> family inet6 filter input authorized-outbound-ipv6 set interfaces <interface name> unit <number> family inet6 address <IPv6 address>/<prefix>
- RMF Control
- AC-4
- Severity
- Medium
- CCI
- CCI-001368
- Version
- JUEX-RT-000020
- Vuln IDs
-
- V-253974
- Rule IDs
-
- SV-253974r843955_rule
Checks: C-57426r843953_chk
Review the BGP router configuration to verify that it will reject routes of any currently defined Bogon prefixes. Example route-filter-list of Bogon addresses with corresponding policy-statement referencing the list: [edit policy-options] route-filter-list bogon { /* This host on this network */ 0.0.0.0/8 orlonger; /* CGN Addresses */ 100.64.0.0/10 orlonger; /* Loopback */ 127.0.0.0/8 orlonger; /* IPv4 link-local or APIPA */ 169.254.0.0/16 orlonger; /* IETF Protocol Assignments (/24) and DS-Lite (/29) */ 192.0.0.0/24 orlonger; /* IPv4 documentation addresses: TEST-NET-1 */ 192.0.2.0/24 orlonger; /* 6to4 Relay Anycast descr in RFC3068 */ 192.88.99.0/24 orlonger; /* Benchmark testing descr in RFC2544 */ 198.18.0.0/15 orlonger; /* IPv4 documentation addresses: TEST-NET-2 */ 198.51.100.0/24 orlonger; /* IPv4 documentation addresses: TEST-NET-3 */ 203.0.113.0/24 orlonger; /* Multicast */ 224.0.0.0/24 orlonger; /* Reserved */ 240.0.0.0/4 orlonger; /* RFC1918 Addresses */ 10.0.0.0/8 orlonger; 172.16.0.0/12 orlonger; 192.168.0.0/16 orlonger; <add additional routes as needed> } route-filter-list bogon-ipv6 { /* Includes unspecified (::/128) and loopback (::1/128) */ ::/8 orlonger; /* IPv4-mapped */ ::ffff:0:0/96 orlonger; /* IPv4 Compatible */ ::/96 orlonger; /* 6Bone */ 3ffe::/16 orlonger; /* IPv4-IPv6 Translate */ 64:ff9b::/96 orlonger; /* Reserved - 100::/8 includes Discard-Only (100::/64) */ 100::/8 orlonger; 200::/7 orlonger; 400::/6 orlonger; 800::/5 orlonger; 1000::/4 orlonger; 4000::/3 orlonger; 6000::/3 orlonger; 8000::/3 orlonger; a000::/3 orlonger; c000::/3 orlonger; e000::/4 orlonger; f000::/5 orlonger; f800::/6 orlonger; fe00::/9 orlonger; /* IETF Protocol Assignments */ 2001::/23 orlonger; /* TEREDO */ 2001::/32 orlonger; /* Benchmarking */ 2001:2::/48 orlonger; /* Documentation */ 2001:db8::/32 orlonger; /* ORCHID */ 2001:10::/28 orlonger; /* 6to4 */ 2002::/16 orlonger; /* Unique-Local */ fc00::/7 orlonger; /* Linked-Scoped Unicast */ fe80::/10 orlonger; /* Site local (deprecated) - now reserved */ fec0::/10 orlonger; /* Multicast */ ff00::/8 orlonger; <add additional routes as needed> } Note: The comments (/* comment */) are annotations used to easily identify each list item. Annotations are not required. To add annotations, navigate to the appropriate hierarchy level ("edit policy-options route-filter-list <list name>" in this example) and use the "annotate" command (annotate <list item> "desired comment"). policy-statement bgp-discard { term 1 { from { route-filter-list bogon; route-filter-list bogon-ipv6; } then reject; } <add additional terms as needed> } Note: Using a route-filter-list permits list reuse as well as easing management because the policy-statement only need reference the list once. Other terms within the same policy-statement can be added without affecting the Bogon list. The prefix filter must be referenced inbound on the appropriate BGP neighbor statements. Verify the eBGP import statement prevents Junos from importing routes into the route table. Junos accepts import statements at three hierarchy levels: Global protocol, group, and neighbor (peer). Global is the most general, followed by group, and neighbor is the most restrictive. Junos applies only the most restrictive policy so if a policy is configured at the protocol, group, and neighbor level, only the neighbor policy is applied. [edit protocols bgp] group eBGP { <other group configuration> import bgp-discard; neighbor 192.0.2.2 { <other neighbor configuration> import bgp-discard; } } import bgp-discard; <other BGP configuration> If the router is not configured to reject inbound route advertisements for any Bogon prefixes, this is a finding.
Fix: F-57377r843954_fix
Ensure all eBGP routers are configured to reject inbound route advertisements for any currently defined Bogon prefixes. set policy-options route-filter-list bogon 0.0.0.0/8 orlonger set policy-options route-filter-list bogon 10.0.0.0/8 orlonger set policy-options route-filter-list bogon 100.64.0.0/10 orlonger set policy-options route-filter-list bogon 127.0.0.0/8 orlonger set policy-options route-filter-list bogon 169.254.0.0/16 orlonger set policy-options route-filter-list bogon 172.16.0.0/12 orlonger set policy-options route-filter-list bogon 192.0.0.0/24 orlonger set policy-options route-filter-list bogon 192.0.2.0/24 orlonger set policy-options route-filter-list bogon 192.168.0.0/16 orlonger set policy-options route-filter-list bogon 198.18.0.0/15 orlonger set policy-options route-filter-list bogon 198.51.100.0/24 orlonger set policy-options route-filter-list bogon 203.0.113.0/24 orlonger set policy-options route-filter-list bogon 224.0.0.0/4 orlonger set policy-options route-filter-list bogon 240.0.0.0/4 orlonger set policy-options route-filter-list bogon-ipv6 ::/128 exact set policy-options route-filter-list bogon-ipv6 ::1/128 exact set policy-options route-filter-list bogon-ipv6 ::ffff:0:0/96 orlonger set policy-options route-filter-list bogon-ipv6 ::/96 orlonger set policy-options route-filter-list bogon-ipv6 100::/64 orlonger set policy-options route-filter-list bogon-ipv6 2001:10::/28 orlonger set policy-options route-filter-list bogon-ipv6 2001:db8::/32 orlonger set policy-options route-filter-list bogon-ipv6 fc00::/7 orlonger set policy-options route-filter-list bogon-ipv6 fe80::/10 orlonger set policy-options route-filter-list bogon-ipv6 fec0::/10 orlonger set policy-options route-filter-list bogon-ipv6 ff00::/8 orlonger set policy-options policy-statement bgp-discard term 1 from route-filter-list bogon set policy-options policy-statement bgp-discard term 1 from route-filter-list bogon-ipv6 set policy-options policy-statement bgp-discard term 1 then reject set protocols bgp group eBGP import bgp-discard set protocols bgp group eBGP neighbor 192.0.2.2 import bgp-discard set protocols bgp import bgp-discard
- RMF Control
- AC-4
- Severity
- Medium
- CCI
- CCI-001368
- Version
- JUEX-RT-000030
- Vuln IDs
-
- V-253975
- Rule IDs
-
- SV-253975r843958_rule
Checks: C-57427r843956_chk
Review the BGP router configuration to verify that it will reject routes belonging to the local AS. Example route-filter-list of local AS addresses with corresponding policy-statement referencing the list. Verify the routes are appropriate for the target environment. [edit policy-options] route-filter-list local-routes { 192.0.2.0/24 orlonger; 192.0.3.0/24 orlonger; } route-filter-list local-routes-ipv6 { 2001:db8:2::/64 orlonger; 2001:db8:3::/64 orlonger; } policy-statement bgp-discard { term 1 { from { route-filter-list bogon; route-filter-list bogon-ipv6; } then reject; } term 2 { from { route-filter-list local-routes; route-filter-list local-routes-ipv6; } then reject; } term 3 { from protocol [ ospf direct ]; then reject; } } The example shows using route-filter-lists to ease management. The policy-statement also supports the route directly in the match condition. For example, "route-filter 192.0.2.0/24 orlonger" (in place of route-filter-list local-routes). Note: To reject routes learned via OSPF or directly-connected routes, include a term with a protocol (OSPF and directly-connected routes shown). The policy-statement includes the Bogon term to demonstrate adding terms to a policy without affecting existing terms. The prefix filter must be referenced inbound on the appropriate BGP neighbor statements. Verify the eBGP import statement prevents Junos from importing routes into the route table. Junos accepts import statements at three hierarchy levels: Global protocol, group, and neighbor (peer). Global is the most general, followed by group, and neighbor is the most restrictive. Junos applies only the most restrictive policy so if a policy is configured at the protocol, group, and neighbor level, only the neighbor policy is applied. [edit protocols bgp] group eBGP { <other group configuration> import bgp-discard; neighbor 192.0.2.2 { <other neighbor configuration> import bgp-discard; } } import bgp-discard; <other BGP configuration> If the router is not configured to reject inbound route advertisements belonging to the local AS, this is a finding.
Fix: F-57378r843957_fix
Ensure all eBGP routers are configured to reject inbound route advertisements for any prefixes belonging to the local AS. set policy-options route-filter-list local-routes 192.0.2.0/24 orlonger set policy-options route-filter-list local-routes 192.0.3.0/24 orlonger set policy-options route-filter-list local-routes-ipv6 2001:db8:2::/64 orlonger set policy-options route-filter-list local-routes-ipv6 2001:db8:3::/64 orlonger set policy-options policy-statement bgp-discard term 1 from route-filter-list bogon set policy-options policy-statement bgp-discard term 1 from route-filter-list bogon-ipv6 set policy-options policy-statement bgp-discard term 1 then reject set policy-options policy-statement bgp-discard term 2 from route-filter-list local-routes set policy-options policy-statement bgp-discard term 2 from route-filter-list local-routes-ipv6 set policy-options policy-statement bgp-discard term 2 then reject set policy-options policy-statement bgp-discard term 3 from protocol ospf set policy-options policy-statement bgp-discard term 3 from protocol direct set policy-options policy-statement bgp-discard term 3 then reject set protocols bgp group eBGP import bgp-discard set protocols bgp group eBGP neighbor 192.0.2.2 import bgp-discard set protocols bgp import bgp-discard
- RMF Control
- AC-4
- Severity
- Medium
- CCI
- CCI-001368
- Version
- JUEX-RT-000040
- Vuln IDs
-
- V-253976
- Rule IDs
-
- SV-253976r843961_rule
Checks: C-57428r843959_chk
Review the BGP router configuration to verify there are filters defined to only accept routes for prefixes that belong to specific customers. Example route-filter-list of customer addresses with corresponding policy-statement referencing the list: [edit policy-options] route-filter-list customer1-routes { <customer route 1/mask> orlonger; <customer route 2/mask> orlonger; } route-filter-list customer1-routes-ipv6 { <customer route 1/prefix> orlonger; <customer route 1/prefix> orlonger; } <additional route-filter-list for other customers> policy-statement bgp-accept-cust1-routes { term 1 { from { route-filter-list customer1-routes; route-filter-list customer1-routes-ipv6; } then accept; } term 2 { then reject; } } <additional policies for other customers> Note: The example shows using route-filter-lists to ease management. The policy-statement also supports the route directly in the match condition. For example, "route-filter <customer route 1/mask> orlonger" (in place of route-filter-list customer-routes). Verify the eBGP import statement prevents Junos from importing routes into the route table. Junos accepts import statements at three hierarchy levels: Global protocol, group, and neighbor (peer). Global is the most general, followed by group, and neighbor is the most restrictive. Junos applies only the most restrictive policy so if a policy is configured at the protocol, group, and neighbor level, only the neighbor policy is applied. [edit protocols bgp] group customer1 { <other group configuration> import bgp-accept-cust1-routes; neighbor <address> { <other neighbor configuration> import bgp-accept-cust1-routes; } } import <import policy name>; <other BGP configuration> 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. 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.
Fix: F-57379r843960_fix
Configure all eBGP routers to reject inbound route advertisements from a CE router for prefixes that are not allocated to that customer. set policy-options route-filter-list customer1-routes <customer route 1/mask> orlonger set policy-options route-filter-list customer1-routes <customer route 2/mask> orlonger set policy-options route-filter-list customer1-routes-ipv6 <customer route 1/prefix> orlonger set policy-options route-filter-list customer1-routes-ipv6 <customer route 2/prefix> orlonger <additional route-filter-list for other customers> set policy-options policy-statement bgp-accept-cust1-routes term 1 from route-filter-list customer-routes set policy-options policy-statement bgp-accept-cust1-routes term 1 from route-filter-list customer-routes-ipv6 set policy-options policy-statement bgp-accept-cust1-routes term 1 then accept set policy-options policy-statement bgp-accept-cust1-routes term 2 then reject <additional policies for other customers> set protocols bgp group customer1 import bgp-accept-cust1-routes set protocols bgp group customer1 neighbor <address> import bgp-accept-cust1-routes Note: An import filter is only required at the group, or the neighbor, level but not both unless the specific neighbor requires a different import filter than the group.
- RMF Control
- AC-4
- Severity
- Medium
- CCI
- CCI-001368
- Version
- JUEX-RT-000050
- Vuln IDs
-
- V-253977
- Rule IDs
-
- SV-253977r843964_rule
Checks: C-57429r843962_chk
This requirement is not applicable for the DODIN Backbone. Review the BGP router configuration to verify there is a filter defined to only advertise routes for prefixes belonging to any customer or the local AS. Example route-filter-list of customer addresses with corresponding policy-statement referencing the list: [edit policy-options] route-filter-list customer1-routes { <customer route 1/mask> exact; <customer route 2/mask> exact; } route-filter-list customer1-routes-ipv6 { <customer route 1/prefix> exact; <customer route 2/prefix> exact; } <additional route-filter-lists for other customers> policy-statement bgp-advertise-cust-routes { term 1 { from { route-filter-list customer1-routes; route-filter-list customer1-routes-ipv6; } then accept; } <additional terms for other customers> term default { then reject; } } Note: The example shows using route-filter-lists to ease management. The policy-statement also supports the route directly in the match condition. For example, "route-filter <customer route 1/mask> exact" (in place of route-filter-list customer-routes). The prefix filter must be referenced outbound on the appropriate BGP neighbor statements. Verify the eBGP export statement prevents Junos from exporting routes from the route table into BGP. Junos accepts export statements at three hierarchy levels: Global protocol, group, and neighbor (peer). Global is the most general, followed by group, and neighbor is the most restrictive. Junos applies only the most restrictive policy so if a policy is configured at the protocol, group, and neighbor level, only the neighbor policy is applied. [edit protocols bgp] group eBGP { <other group configuration> export bgp-advertise-cust-routes; neighbor <address> { <other neighbor configuration> export bgp-advertise-cust-routes; } } export bgp-advertise-cust-routes; <other BGP configuration> 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.
Fix: F-57380r843963_fix
Configure all eBGP routers to filter outbound route advertisements for prefixes that are not allocated to or belong to any customer or the local AS. set policy-options route-filter-list customer1-routes <customer route 1/mask> exact set policy-options route-filter-list customer1-routes <customer route 2/mask> exact set policy-options route-filter-list customer1-routes-ipv6 <customer route 1/prefix> exact set policy-options route-filter-list customer1-routes-ipv6 <customer route 2/prefix> exact <additional route-filter-list for other customers> set policy-options policy-statement bgp-advertise-cust-routes term 1 from route-filter-list customer1-routes set policy-options policy-statement bgp-advertise-cust-routes term 1 from route-filter-list customer1-routes-ipv6 set policy-options policy-statement bgp-advertise-cust-routes term 1 then accept <additional terms for other customers> set policy-options policy-statement bgp-advertise-cust-routes term default then reject set protocols bgp group eBGP export bgp-advertise-cust-routes set protocols bgp group eBGP neighbor <address> export bgp-advertise-cust-routes set protocols bgp export bgp-advertise-cust-routes
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-000032
- Version
- JUEX-RT-000060
- Vuln IDs
-
- V-253978
- Rule IDs
-
- SV-253978r945854_rule
Checks: C-57430r843965_chk
Review the BGP 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 the configuration of "enforce-first-as" at either the BGP global or group level. [edit protocols bgp] group eBGP { enforce-first-as; neighbor <address>; } 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.
Fix: F-57381r843966_fix
Configure all ASBRs to deny updates received from eBGP peers that do not list their AS number as the first AS in the AS_PATH attribute. set protocols bgp group eBGP enforce-first-as set protocols bgp group eBGP neighbor <address> set protocols bgp enforce-first-as
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-001368
- Version
- JUEX-RT-000070
- Vuln IDs
-
- V-253979
- Rule IDs
-
- SV-253979r843970_rule
Checks: C-57431r843968_chk
Review the router configuration to determine if there is an import policy to block source-active multicast advertisements for any undesirable multicast groups, as well as any (S, G) states with undesirable source addresses. Verify that an inbound source-active filter is bound to each MSDP peer. [edit protocols msdp] peer <address> { import source-active-filter; } Review the policy-statement referenced by the source-active filter to verify that undesirable multicast groups, auto-RP, single source multicast (SSM) groups, and advertisements from undesirable sources are blocked. [edit policy-options] policy-statement source-active-filter { term unauth-groups { from { route-filter 224.0.1.2/32 exact; route-filter 224.0.2.2/32 exact; } then reject; } term unauth-sources { from { source-address-filter 10.0.0.0/8 orlonger; source-address-filter 127.0.0.0/8 orlonger; } then reject; } } If the router is not configured with an import policy to block undesirable SA multicast advertisements, this is a finding.
Fix: F-57382r843969_fix
Configure the MSDP router to implement an import policy to block multicast advertisements for undesirable multicast groups and sources. set protocols msdp peer <address> import source-active-filter set policy-options policy-statement source-active-filter term unauth-groups from route-filter 224.0.1.2/32 exact set policy-options policy-statement source-active-filter term unauth-groups from route-filter 224.0.2.2/32 exact set policy-options policy-statement source-active-filter term unauth-groups then reject set policy-options policy-statement source-active-filter term unauth-sources from source-address-filter 10.0.0.0/8 orlonger set policy-options policy-statement source-active-filter term unauth-sources from source-address-filter 127.0.0.0/8 orlonger set policy-options policy-statement source-active-filter term unauth-sources then reject
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-001368
- Version
- JUEX-RT-000080
- Vuln IDs
-
- V-253980
- Rule IDs
-
- SV-253980r843973_rule
Checks: C-57432r843971_chk
Review the router configuration to determine if there is export policy to block local source-active multicast advertisements. Verify that an outbound source-active filter is bound to each MSDP peer. [edit protocols msdp] peer <address> { export source-active-filter; } Review the policy-statement referenced by the source-active filters and verify that MSDP source-active messages being sent to MSDP peers do not leak advertisements that are local. [edit policy-options] policy-statement source-active-filter { term unauth-groups { from { route-filter 224.0.1.2/32 exact; route-filter 224.0.2.2/32 exact; } then reject; } term unauth-sources { from { source-address-filter 10.0.0.0/8 orlonger; source-address-filter 127.0.0.0/8 orlonger; } then reject; } } If the router is not configured with an export policy to block local source-active multicast advertisements, this is a finding.
Fix: F-57383r843972_fix
Ensure an export policy is implemented on all MSDP routers to avoid global visibility of local multicast (S, G) states. set protocols msdp peer <address> export source-active-filter set policy-options policy-statement source-active-filter term unauth-groups from route-filter 224.0.1.2/32 exact set policy-options policy-statement source-active-filter term unauth-groups from route-filter 224.0.2.2/32 exact set policy-options policy-statement source-active-filter term unauth-groups then reject set policy-options policy-statement source-active-filter term unauth-sources from source-address-filter 10.0.0.0/8 orlonger set policy-options policy-statement source-active-filter term unauth-sources from source-address-filter 127.0.0.0/8 orlonger set policy-options policy-statement source-active-filter term unauth-sources then reject
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-001368
- Version
- JUEX-RT-000090
- Vuln IDs
-
- V-253981
- Rule IDs
-
- SV-253981r843976_rule
Checks: C-57433r843974_chk
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. [edit protocols] msdp { active-source-limit { maximum <1..1000000>; threshold <1..1000000>; log-warning <percent to log warning>; } local-address <lo0 address>; <additional configuration> peer <address> { active-source-limit { maximum <1..1000000>; threshold <1..1000000>; log-warning <percent to log warning>; } authentication-key "hashed PSK"; ## SECRET-DATA } } Note: Both the global, and the peer limit, are applied to every MSDP peer, and Junos applies the most restrictive limit. The maximum value sets the upper limit for source-active messages and the threshold value determines when Junos begins Random Early Detection (RED) dropping to alleviate congestion. The log-warning value is a percent where Junos begins generating syslog messages. If the router is not configured to limit the source-active messages it accepts, this is a finding.
Fix: F-57384r843975_fix
Configure the MSDP router to limit the amount of source-active messages it accepts from each peer. set protocols msdp active-source-limit maximum <1..1000000> set protocols msdp active-source-limit threshold <1..1000000> set protocols msdp active-source-limit log-warning <percent to log warning> <additional configuration> set protocols msdp peer <address> active-source-limit maximum <1..1000000> set protocols msdp peer <address> active-source-limit threshold <1..1000000> set protocols msdp peer <address> active-source-limit log-warning <percent to log warning>
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-000032
- Version
- JUEX-RT-000100
- Vuln IDs
-
- V-253982
- Rule IDs
-
- SV-253982r945855_rule
Checks: C-57434r843977_chk
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. Review the router configuration and verify that there is an as-path access-list statement defined. Each peer requires a regular expression (REGEX) defining the expected AS_PATH attribute. Each neighbor has an import policy applied to filter updates that do not match the expected path attribute. Assuming AS 65535 is an authorized neighbor's originating AS, verify an as-path REGEX is defined ('.* 65535') and a policy-statement configured to accept that REGEX. [edit policy-options] policy-statement bgp_originate_65535 { term 1 { from as-path orig_65535; then accept; } term 2 { then reject; } } as-path orig_65535 ".* 65535"; Note: The REGEX matches zero or more prepended AS in the AS_PATH beginning with the defined AS number (the originator is the right-most AS in the path). The AS_PATH attribute is a space-delimited list, so a space between the leading AS numbers (.*) and the originating AS (65535) is required. Verify that the as-path access list is referenced by the filter-list inbound for the appropriate BGP neighbors. [edit protocols bgp] group eBGP { neighbor <address> { import bgp_originate_65535; } } 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.
Fix: F-57385r843978_fix
Configure the router to reject updates from CE routers with an originating AS in the AS_PATH attribute that does not belong to that customer. set policy-options policy-statement bgp_originate_65535 term 1 from as-path orig_65535 set policy-options policy-statement bgp_originate_65535 term 1 then accept set policy-options policy-statement bgp_originate_65535 term 2 then reject set policy-options as-path orig_65535 ".* 65535" set protocols bgp group eBGP neighbor <address> import bgp_originate_65535
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-001414
- Version
- JUEX-RT-000110
- Vuln IDs
-
- V-253983
- Rule IDs
-
- SV-253983r843982_rule
Checks: C-57435r843980_chk
Review the configuration and verify that the auxiliary port is disabled unless a secured modem providing encryption and authentication is connected to it. The Junos auxiliary port is disabled by default. Verify the auxiliary port is not configured (there will be no [edit system ports auxiliary] stanza) or that the auxiliary port is explicitly disabled. [edit system ports] auxiliary { disable; } If the auxiliary port is not disabled or is not connected to a secured modem when it is enabled, this is a finding.
Fix: F-57386r843981_fix
Disable the auxiliary port. set system ports auxiliary disable -or- delete system ports auxiliary If used for out-of-band administrative access, the port must be connected to a secured modem providing encryption and authentication.
- RMF Control
- AC-4
- Severity
- Medium
- CCI
- CCI-001414
- Version
- JUEX-RT-000120
- Vuln IDs
-
- V-253984
- Rule IDs
-
- SV-253984r843985_rule
Checks: C-57436r843983_chk
Verify each router enforces approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy. Junos enforces information flow via stateless firewall filters and unicast Reverse Path Forwarding (uRPF). uRPF performs a forwarding table lookup to validate the incoming packet's source address is appropriate for the arriving interface. Verify uRPF is enabled on applicable interfaces. The example shows uRPF and the stateless firewall filter applied. Verify the interface and assigned addresses are appropriate for the target environment. [edit interfaces] <interface name> { unit <logical unit number> { family inet { rpf-check; filter { input deny-prod-to-mgt; } } family inet6 { rpf-check; filter { input deny-prod-to-mgt-v6; } } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. [edit firewall] family inet { filter deny-prod-to-mgt { term 1 { from { source-address { <production IPv4 subnet/mask>; } destination-address { <MGT IPv4 subnet/mask>; } } then { log; syslog; discard; } } term 2 { from { source-address { <production IPv4 subnet/mask>; } } then accept; } } } family inet6 { filter deny-prod-to-mgt-v6 { term 1 { from { source-address { <production IPv6 subnet/prefix>; } destination-address { <MGT IPv6 subnet/prefix>; } } then { log; syslog; discard; } } term 2 { from { source-address { <production IPv6 subnet/prefix>; } } then accept; } } } If the router does not enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy, this is a finding.
Fix: F-57387r843984_fix
Configure the router to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy. set interfaces <interface name> unit <logical unit> family inet rpf-check set interfaces <interface name> unit <logical unit> family inet filter input deny-prod-to-mgt set interfaces <interface name> unit <logical unit> family inet6 rpf-check set interfaces <interface name> unit <logical unit> family inet6 filter input deny-prod-to-mgt-v6 set firewall family inet filter deny-prod-to-mgt term 1 from source-address <production IPv4 subnet/mask> set firewall family inet filter deny-prod-to-mgt term 1 from destination-address <MGT IPv4 subnet/mask> set firewall family inet filter deny-prod-to-mgt term 1 then log set firewall family inet filter deny-prod-to-mgt term 1 then syslog set firewall family inet filter deny-prod-to-mgt term 1 then discard set firewall family inet filter deny-prod-to-mgt term 2 from source-address <production IPv4 subnet/mask> set firewall family inet filter deny-prod-to-mgt term 2 then accept set firewall family inet6 filter deny-prod-to-mgt-v6 term 1 from source-address <production IPv6 subnet/prefix> set firewall family inet6 filter deny-prod-to-mgt-v6 term 1 from destination-address <MGT IPv6 subnet/prefix> set firewall family inet6 filter deny-prod-to-mgt-v6 term 1 then log set firewall family inet6 filter deny-prod-to-mgt-v6 term 1 then syslog set firewall family inet6 filter deny-prod-to-mgt-v6 term 1 then discard set firewall family inet6 filter deny-prod-to-mgt-v6 term 2 from source-address <production IPv6 subnet/prefix> set firewall family inet6 filter deny-prod-to-mgt-v6 term 2 then accept
- RMF Control
- AC-4
- Severity
- Medium
- CCI
- CCI-001414
- Version
- JUEX-RT-000130
- Vuln IDs
-
- V-253985
- Rule IDs
-
- SV-253985r843988_rule
Checks: C-57437r843986_chk
If IPv4 or IPv6 multicast routing is enabled, verify all interfaces enabled for PIM are documented in the network's multicast topology diagram. Review the router configuration to determine if multicast routing is enabled and which interfaces are enabled for PIM. By default, PIM is not enabled on any interface. If not a PIM router, verify there is no PIM stanza at [edit protocols], PIM is disabled globally and/or for all interfaces, or that the stanza is inactive. [edit protocols] inactive: pim { << Stanza is removed or marked inactive disable; << If stanza is present and not inactive, verify globally disabled interface all { << If stanza is present, not inactive, and not globally disabled, disable for all interfaces disable; } } For PIM routers, verify only the required interfaces are configured. For example, the following configuration enables PIM on a specific interface and disables PIM for all others. [edit protocols] pim { interface <name>.<logical unit>; interface all { disable; } } Note: More specific interface configuration statements are preferred. In the example, the interface configuration is more specific than interface "all", so PIM is enabled only on that interface. If an interface is not required to support multicast routing and it is enabled, this is a finding.
Fix: F-57388r843987_fix
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. For non-PIM routers, verify there is no [edit protocols pim] stanza. If the stanza is present, delete or deactivate it. delete protocols pim deactivate protocols pim To disable PIM globally or for all interfaces. set protocols pim disable set protocols pim interface all disable For PIM routers verify only the required interfaces are configured and all others are disabled: set protocols pim interface <name>.<logical unit> set protocols pim interface all disable
- RMF Control
- AC-4
- Severity
- Medium
- CCI
- CCI-001414
- Version
- JUEX-RT-000140
- Vuln IDs
-
- V-253986
- Rule IDs
-
- SV-253986r843991_rule
Checks: C-57438r843989_chk
This requirement is not applicable for the DODIN Backbone. Review the multicast topology diagram and determine if router interfaces are enabled for IPv4 or IPv6 multicast routing. By default, PIM is not enabled on any interface. If not a PIM router, verify there is no PIM stanza at [edit protocols], PIM is disabled globally and/or for all interfaces, or that the stanza is inactive. [edit protocols] inactive: pim { << Stanza is removed or marked inactive disable; << If stanza is present and not inactive, verify globally disabled interface all { << If stanza is present, not inactive, and not globally disabled, disable for all interfaces disable; } } For PIM routers, verify only the required interfaces are configured. For example, the following configuration enables PIM on a specific interface and disables PIM for all others. [edit protocols] pim { interface <name>.<logical unit>; interface all { disable; } } Note: More specific interface configuration statements are preferred. In the example, the interface configuration is more specific than interface "all", so PIM is enabled only on that interface. If the router is enabled for multicast routing, verify all interfaces enabled for PIM have a neighbor filter bound to the interface. The neighbor filter must only accept PIM control plane traffic from the documented PIM neighbors. [edit policy-options] prefix-list PIM-NEIGHBOR-1 { <PIM neighbor address>/32; } <additional PIM neighbor lists> policy-statement PIM-NBR-1 { from { prefix-list PIM-NEIGHBOR-1; } then accept; } <additional policies> [edit protocols pim] interface <interface name>.<logical unit> { mode sparse; neighbor-policy PIM-NBR1; } interface all { disable; } If PIM neighbor filters are not bound to all interfaces that have PIM enabled, this is a finding.
Fix: F-57389r843990_fix
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. set policy-options prefix-list PIM-NEIGHBOR-1 <PIM neighbor address>/32 set policy-options policy-statement PIM-NBR-1 from prefix-list PIM-NEIGHBOR-1 set policy-options policy-statement PIM-NBR-1 then accept set protocols pim interface <interface name>.<logical unit> mode sparse set protocols pim interface <interface name>.<logical unit> neighbor-policy PIM-NBR-1 set protocols pim interface all disable
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-001414
- Version
- JUEX-RT-000150
- Vuln IDs
-
- V-253987
- Rule IDs
-
- SV-253987r843994_rule
Checks: C-57439r843992_chk
Review the router configuration and verify that admin-scope multicast traffic is blocked at the external edge. Verify either a scope is defined for specific interfaces or a scope policy is applied. [edit routing-options multicast] scope <name IPv4> { prefix 239.0.0.0/8; interface [ <external interface 1> <external interface 2> ]; } scope <name IPv6> { prefix ff08::/16; interface [ <external interface 1> <external interface 2> ]; } -or- [edit policy-options] policy-statement <name> { term 1 { from { route-filter 239.0.0.0/8 orlonger; route-filter ff08::/16 orlonger; } then reject; } } [edit routing-options multicast] scope-policy <policy name> If the router is not configured to establish boundaries for administratively scoped multicast traffic, this is a finding.
Fix: F-57390r843993_fix
Configure the policy to deny packets with multicast administratively scoped destination addresses. set routing-options multicast scope <IPv4 scope name> prefix 239.0.0.0/8; set routing-options multicast scope <IPv6 scope name> prefix ff08::/16; -or- set policy-options policy-statement <policy name> term 1 from route-filter 239.0.0.0/8 orlonger set policy-options policy-statement <policy name> term 1 from route-filter ff08::/16 orlonger Apply the multicast boundary at the appropriate interfaces. set routing-options multicast scope <IPv4 scope name> interface [ <external interface 1> <external interface 2> ] set routing-options multicast scope <IPv6 scope name> interface [ <external interface 1> <external interface 2> ] -or- set routing-options multicast scope-policy <policy name>
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-001414
- Version
- JUEX-RT-000160
- Vuln IDs
-
- V-253988
- Rule IDs
-
- SV-253988r843997_rule
Checks: C-57440r843995_chk
Review the router configuration and verify unused interfaces are not configured (implicitly disabled) or are explicitly disabled. If explicitly disabling interfaces, verify multiple interfaces are disabled with the "interface-range" command or separately at each interface declaration. [edit interfaces] interface-range DISABLED_INTERFACES { member <interface name>; member-range <first interface> to <last interface>; disable; } <interface name> { disable; } Note: Individually disabled interfaces should not be included in any "interface-range" stanza. The "member-range" directive assigns the configured parameter(s) to contiguously numbered interfaces. Junos lists interfaces in order so a "missing" interface is not enabled. For instance, if ge-0/0/0 and ge-0/0/2 are configured, but there is no individual ge-0/0/1 stanza and that interface is not a member of an interface-range, then ge-0/0/1 is implicitly disabled. If an interface is not being used but is configured or enabled, this is a finding.
Fix: F-57391r843996_fix
Disable inactive interfaces. delete interfaces <interface name> -or- set interfaces <interface name> disable -or- set interfaces interface-range DISABLED_INTERFACES member <interface name> set interfaces interface-range DISABLED_INTERFACES member-range <first interface name> to <last interface name> set interfaces interface-range DISABLED_INTERFACES disable
- RMF Control
- AC-4
- Severity
- High
- CCI
- CCI-001414
- Version
- JUEX-RT-000170
- Vuln IDs
-
- V-253989
- Rule IDs
-
- SV-253989r997520_rule
Checks: C-57441r843998_chk
This requirement is not applicable for the DODIN Backbone. Review the configuration of each router interface connecting to an alternate gateway. Verify each permit statement of the ingress filter only permits 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. Verify each permit statement "from" stanza (filter match conditions) references either the "destination-address" or "destination-prefix-list" directive. Using prefix lists makes management easier because managing interior addresses must only be configured in one location (the prefix-list) vice many locations (each permitting filter term). For example: [edit policy-options] prefix-list inside_addresses-ipv4 { <IPv4 subnet / mask>; } prefix-list inside_addresses-ipv6 { <IPv6 subnet / prefix>; } [edit firewall] family inet { filter inbound-ipv4 { <deny terms>; permit-term1 { from { <match conditions>; destination-prefix-list inside_addresses-ipv4; } then accept; } <additional permit terms with a destination address definition> } } family inet6 { filter inbound-ipv6 { <deny terms>; permit-term1 { from { <match conditions>; destination-prefix-list inside_addresses-ipv6; } then accept; } <additional permit terms with a destination address definition> } } Verify the filter is applied inbound on exterior-facing interfaces. For example: [edit interfaces] <interface name> { unit <number> { family inet { filter { input inbound-ipv4; } address <IPv4 address / mask>; } family inet6 { filter { input inbound-ipv6; } address <IPv6 address / prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. If the ingress filter 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.
Fix: F-57392r843999_fix
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. For example: set policy-options prefix-list inside_addresses-ipv4 <IPv4 subnet / mask> set policy-options prefix-list inside_addresses-ipv6 <IPv6 subnet / prefix> set firewall family inet filter inbound-ipv4 <deny terms> set firewall family inet filter inbound-ipv4 <permit term> from <match conditions> set firewall family inet filter inbound-ipv4 <permit term> from destination-prefix-list inside_addresses-ipv4 set firewall family inet filter inbound-ipv4 <permit term> then accept set firewall family inet6 filter inbound-ipv6 <deny terms> set firewall family inet6 filter inbound-ipv6 <permit term> from <match conditions> set firewall family inet6 filter inbound-ipv6 <permit term> from destination-prefix-list inside_addresses-ipv6 set firewall family inet6 filter inbound-ipv6 <permit term> then accept
- RMF Control
- AC-4
- Severity
- High
- CCI
- CCI-001414
- Version
- JUEX-RT-000180
- Vuln IDs
-
- V-253990
- Rule IDs
-
- SV-253990r844003_rule
Checks: C-57442r844001_chk
This requirement is not applicable for the DODIN Backbone. Review the configuration of the router connecting to the alternate gateway. Review the [edit protocols bgp] hierarchy and verify there are no BGP neighbors configured to the remote AS that belongs to the alternate gateway service provider. For example: [edit protocols bgp] group eBGP { type external; peer-as 2; neighbor <address-1> { <bgp neighbor configuration>; } neighbor <address-2> { <bgp neighbor configuration>; } } Note: Neither neighbor can belong to a peer AS belonging to the alternate gateway service provider. Verify static routing to the peer AS belonging to the alternate gateway service provider. For example: [edit routing-options] rib inet6.0 { static { route <peer AS IPv6 subnet>/<prefix> next-hop <peer AS router>; } } static { route <peer AS IPv4 subnet>/<mask> next-hop <peer AS router>; } If there are BGP neighbors connecting the remote AS of the alternate gateway service provider, this is a finding.
Fix: F-57393r844002_fix
This requirement is not applicable for the DODIN Backbone. Remove BGP neighbors belonging to the alternate gateway service provider. delete protocols bgp group <name> neighbor <peer AS belonging to alternate gateway service provider> Configure a static route on the perimeter router to reach the AS of a router connecting to an alternate gateway. set routing-options rib inet6.0 static route <IPv6 subnet>/<prefix> next-hop <peer AS router> set routing-options static route <IPv4 subnet>/<mask> next-hop <peer AS router>
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-001414
- Version
- JUEX-RT-000190
- Vuln IDs
-
- V-253991
- Rule IDs
-
- SV-253991r844006_rule
Checks: C-57443r844004_chk
This requirement is not applicable for the DODIN Backbone. Review the configuration of the router connecting to the alternate gateway and verify that redistribution of static routes to the alternate gateway is not occurring. Juniper routers use export policies to limit redistribution of routes. Verify a policy exists to filter route redistribution. [edit policy-options] policy-statement <name> { term 1 { from protocol static; then reject; } } Verify the export policy is applied to the EGP and/or IGP protocol. [edit protocols] bgp { export <policy-name>; group <group name> { type external; export <policy-name>; neighbor <address> { export <policy-name>; } } ospf { export <policy name>; } ospf3 { export <policy name>; } } Note: BGP supports export statements at the protocol level (global), the group level, and the neighbor level. Only the most specific policy is applied. If the static routes to the alternate gateway are being redistributed into BGP or any IGP peering with a NIPRNet gateway or another autonomous system, this is a finding.
Fix: F-57394r844005_fix
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 an Exterior Gateway Protocol or Interior Gateway Protocol to the NIPRNet or to other autonomous systems. set policy-options policy-statement <policy name> term 1 from protocol static set policy-options policy-statement <policy name> term 1 then reject set protocols bgp group <group name> export <policy name> set protocols bgp group <group name> neighbor <address> export <policy name> set protocols bgp export <policy name> set protocols ospf export <policy name> set protocols ospf3 export <policy name>
- RMF Control
- AC-4
- Severity
- Medium
- CCI
- CCI-001414
- Version
- JUEX-RT-000200
- Vuln IDs
-
- V-253992
- Rule IDs
-
- SV-253992r844009_rule
Checks: C-57444r844007_chk
This requirement is not applicable for the DODIN Backbone. Verify that the OOBM interface is an adjacency in the Interior Gateway Protocol routing domain for the management network. Interfaces can only be assigned to one routing instance. [edit protocols ospf] interface <interface name>.<logical unit>; << Cannot be assigned to a virtual routing instance. [edit routing-instances] <name> { instance-type virtual-router; protocols { ospf { area <area number> { interface <interface name>.<logical unit>; << Cannot be assigned to the default routing instance at [edit protocols]. } } } } Note: If the same interface is assigned to the default routing instance and to a virtual routing instance, commit fails. Some platforms support a routing-instance using the reserved name "mgmt_junos". On these platforms, configure the "mgmt_junos" instance and apply at the [edit system] hierarchy. [edit system] management-instance; [edit routing-instances] mgmt_junos { routing-options { static { route 0.0.0.0/0 next-hop <next-hop address>; } } } Note: Not all platforms support routing instances. If the router does not enforce that Interior Gateway Protocol instances configured on the OOBM gateway router peer only with their own routing domain, this is a finding.
Fix: F-57395r844008_fix
This requirement is not applicable for the DODIN Backbone. Configure the router to enforce that Interior Gateway Protocol instances configured on the OOBM gateway router peer only with their own routing domain. set protocols ospf area <number> interface <interface name>.<logical unit> set routing-instances <name> instance-type virtual-router set routing-instances <name> protocols ospf area <number> interface <interface name>.<logical unit>
- RMF Control
- AC-4
- Severity
- Medium
- CCI
- CCI-001414
- Version
- JUEX-RT-000210
- Vuln IDs
-
- V-253993
- Rule IDs
-
- SV-253993r844012_rule
Checks: C-57445r844010_chk
This requirement is not applicable for the DODIN Backbone. Verify the Interior Gateway Protocol instance used for the managed network does not redistribute routes into the Interior Gateway Protocol instance used for the management network, and vice versa. Juniper routers use export policies to limit redistribution of routes. Verify a policy exists to filter route redistribution. Juniper policy-statements support terms, which provides greater granularity within a single policy. [edit policy-options] policy-statement deny-mgt-redist { term 1 { from protocol static; then reject; } term 2 { from { protocol ospf; route-filter <IPv4 subnet>/<mask> orlonger; route-filter <IPv6 subnet>/<prefix> orlonger; } then reject; } <additional terms permitting authorized routes for redistribution> } policy-statement deny-managed-routes { term 1 { from { route-filter <IPv4 subnet>/<mask> orlonger; route-filter <IPv6 subnet>/<prefix> orlonger; } then accept; } term 2 { then reject; } } Verify an export policy is applied to the IGP protocol for each routing instance (default and OOBM). [edit protocols] ospf { area <area number> { interface <NOT OOBM interface>.<logical unit>; } export deny-mgt-redist; } ospf3 { area <area number> { interface <NOT OOBM interface>.<logical unit>; } export deny-mgt-redist; } } [edit routing-instances] OOBM { instance-type virtual-router; protocols { ospf { area <area number> { interface <OOBM interface>.<logical unit>; } export deny-managed-routes; } ospf3 { area <area number> { interface <OOBM interface>.<logical unit>; } export deny-managed-routes; } } } If the Interior Gateway Protocol instance used for the managed network redistributes routes into the Interior Gateway Protocol instance used for the management network, or vice versa, this is a finding.
Fix: F-57396r844011_fix
This requirement is not applicable for the DODIN Backbone. Configure the Interior Gateway Protocol instance used for the managed network to prohibit redistribution of routes into the Interior Gateway Protocol instance used for the management network, and vice versa. set policy-options policy-statement deny-managed-routes term 1 from route-filter <IPv4 subnet>/<mask> orlonger set policy-options policy-statement deny-managed-routes term 1 from route-filter <IPv6 subnet>/<prefix> orlonger set policy-options policy-statement deny-managed-routes term 1 then accept set policy-options policy-statement deny-managed-routes term 2 then reject set policy-options policy-statement deny-mgt-redist term 1 from protocol static set policy-options policy-statement deny-mgt-redist term 1 then reject set policy-options policy-statement deny-mgt-redist term 2 from protocol ospf set policy-options policy-statement deny-mgt-redist term 2 from route-filter <IPv4 subnet>/<mask> orlonger set policy-options policy-statement deny-mgt-redist term 2 from route-filter <IPv6 subnet>/<prefix> orlonger set policy-options policy-statement deny-mgt-redist term 2 then reject <additional terms for permitted redistributable routes> set routing-instances OOBM instance-type virtual-router set routing-instances OOBM protocols ospf area <area number> interface <OOBM interface>.<logical unit> set routing-instances OOBM protocols ospf export test set routing-instances OOBM protocols ospf3 area <area number> interface <OOBM interface>.<logical unit> set routing-instances OOBM protocols ospf3 export test
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-001414
- Version
- JUEX-RT-000220
- Vuln IDs
-
- V-253994
- Rule IDs
-
- SV-253994r844015_rule
Checks: C-57446r844013_chk
Verify that the RP router is configured to filter PIM register messages from unauthorized multicast groups and sources. [edit policy-options] policy-statement <name> { term filter_groups { from { route-filter <multicast address>/<mask> orlonger; route-filter <multicast address>/<mask> exact; <additional groups to filter> } then reject; } term filter_sources { from { source-address-filter <source host address>/32 exact; source-address-filter <source subnet address>/<mask> orlonger; <additional source addresses to filter> } then reject; } term accept_others { then accept; } } [edit protocols pim] rp { rp-register-policy <policy name>; } If the RP router peering with PIM-SM routers is not configured with a PIM import policy to block registration messages for any undesirable multicast groups and sources, this is a finding.
Fix: F-57397r844014_fix
Configure the RP router to filter PIM register messages received from a multicast DR for any undesirable multicast groups or sources. set policy-options policy-statement <name> term filter_groups from route-filter <multicast address>/<mask> <match criterion> set policy-options policy-statement <name> term filter_groups from route-filter <additional multicast address>/<mask> <match criterion> set policy-options policy-statement <name> term filter_groups then reject set policy-options policy-statement <name> term filter_source from source-address-filter <source address>/<mask> <match criterion> set policy-options policy-statement <name> term filter_source from source-address-filter <additional source address>/<mask> <match criterion> set policy-options policy-statement <name> term filter_source then reject set policy-options policy-statement <name> term accept_others then accept set protocols pim rp rp-register-policy <policy name>
- RMF Control
- AC-4
- Severity
- Low
- CCI
- CCI-001414
- Version
- JUEX-RT-000230
- Vuln IDs
-
- V-253995
- Rule IDs
-
- SV-253995r844018_rule
Checks: C-57447r844016_chk
Verify that the RP router is configured to filter PIM register messages. [edit policy-options] policy-statement <name> { term filter_groups { from { route-filter <multicast address>/<mask> orlonger; route-filter <multicast address>/<mask> exact; <additional groups to filter> } then reject; } term filter_sources { from { source-address-filter <source host address>/32 exact; source-address-filter <source subnet address>/<mask> orlonger; <additional source addresses to filter> } then reject; } term accept_others { then accept; } } [edit protocols] pim { mode sparse; import <policy name>; } Note: Alternative is to verify all designated routers are filtering IGMP Membership Report (a.k.a., join) messages received from hosts. If the RP router peering with PIM-SM routers is not configured with a PIM import policy to block registration messages for any undesirable multicast groups and Bogon sources, this is a finding.
Fix: F-57398r844017_fix
RP routers that are peering with customer PIM-SM routers must implement a PIM import policy to block join messages for reserved and any undesirable multicast groups. set policy-options policy-statement <name> term filter_groups from route-filter <multicast address>/<mask> <match criterion> set policy-options policy-statement <name> term filter_groups from route-filter <additional multicast address>/<mask> <match criterion> set policy-options policy-statement <name> term filter_groups then reject set policy-options policy-statement <name> term filter_source from source-address-filter <source address>/<mask> <match criterion> set policy-options policy-statement <name> term filter_source from source-address-filter <additional source address>/<mask> <match criterion> set policy-options policy-statement <name> term filter_source then reject set policy-options policy-statement <name> term accept_others then accept set protocols pim import <policy name>
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000132
- Version
- JUEX-RT-000240
- Vuln IDs
-
- V-253996
- Rule IDs
-
- SV-253996r844021_rule
Checks: C-57448r844019_chk
The router must log all packets that have been dropped via the stateless firewall filter. Verify all discarding firewall filter terms are configured to send events to syslog. Note: Stateless firewall filters support "log" and "syslog" actions. The "log" action maintains a temporary list of events and the "syslog" action generates events for local storage and/or external syslog servers. Verify at least "syslog" is associated with all discarding terms. For example: [edit firewall] family inet { filter <filter name> { term 1 { from { <match conditions>; } then { log; syslog; <<< At a minimum, the 'syslog' action must be enabled for all discarding terms. discard; } } } } family inet6 { filter <filter name> { term 1 { from { <match conditions>; } then { log; syslog; <<< At a minimum, the 'syslog' action must be enabled for all discarding terms. discard; } } } } If the router fails to log all packets that have been dropped via the firewall filter, this is a finding. Verify logging is enabled for local and/or external syslog. To meet this requirement, either the "any" or the "firewall" logging facility must be enabled. Note: To reduce log sizes and to segregate entries, a separate log file for firewall entries is permissible. [edit system syslog] host <external syslog address> { any info; log-prefix <hostname>; explicit-priority; } file messages { any info; } time-format year; Log output must contain an interface name identifying where the packet was filtered. Note: Logged firewall events include the interface and cannot be configured otherwise. There is no provision for changing the log message or for removing the interface name. If the logged output does not contain an interface name identifying where the packet was filtered, this is a finding.
Fix: F-57399r844020_fix
Configure the router to record the interface in the log record for packets being dropped. Example firewall filter with logging enabled: set firewall family inet filter <filter name> term 1 from <match conditions> set firewall family inet filter <filter name> term 1 then log set firewall family inet filter <filter name> term 1 then syslog <<< Must be enabled for all discarding terms set firewall family inet filter <filter name> term 1 then discard set firewall family inet6 filter <filter name> term 1 from <match conditions> set firewall family inet6 filter <filter name> term 1 then log set firewall family inet6 filter <filter name> term 1 then syslog <<< Must be enabled for all discarding terms set firewall family inet6 filter <filter name> term 1 then discard Example consolidated logging: set syslog host <external syslog address> any info set system syslog file messages any info
- RMF Control
- AU-3
- Severity
- Medium
- CCI
- CCI-000133
- Version
- JUEX-RT-000250
- Vuln IDs
-
- V-253997
- Rule IDs
-
- SV-253997r844024_rule
Checks: C-57449r844022_chk
The router must log all packets that have been dropped via the stateless firewall filter. Verify all discarding firewall filter terms are configured to send events to syslog. Note: Stateless firewall filters support "log" and "syslog" actions. The "log" action maintains a temporary list of events and the "syslog" action generates events for local storage and/or external syslog servers. Verify at least "syslog" is associated with all discarding terms. For example: [edit firewall] family inet { filter <filter name> { term 1 { from { <match conditions>; } then { log; syslog; <<< At a minimum, the 'syslog' action must be enabled for all discarding terms. discard; } } } } family inet6 { filter <filter name> { term 1 { from { <match conditions>; } then { log; syslog; <<< At a minimum, the 'syslog' action must be enabled for all discarding terms. discard; } } } } If the router fails to log all packets that have been dropped via the firewall filter, this is a finding. Verify logging is enabled for local and/or external syslog. To meet this requirement, either the "any" or the "firewall" logging facility must be enabled. Note: To reduce log sizes and to segregate entries, a separate log file for firewall entries is permissible. [edit system syslog] host <external syslog address> { any info; log-prefix <hostname>; explicit-priority; } file messages { any info; } time-format year; Log output must contain the source IP address and port of the filtered packets. Note: Logged firewall events include the source, and destination, addresses and cannot be configured otherwise. There is no provision for changing the log message or for removing the source or destination address. If the logged output does not contain source IP address and port of the filtered packets, this is a finding.
Fix: F-57400r844023_fix
Configure the router to record the source address in the log record for packets being dropped. Example firewall filter with logging enabled: set firewall family inet filter <filter name> term 1 from <match conditions> set firewall family inet filter <filter name> term 1 then log set firewall family inet filter <filter name> term 1 then syslog <<< Must be enabled for all discarding terms set firewall family inet filter <filter name> term 1 then discard set firewall family inet6 filter <filter name> term 1 from <match conditions> set firewall family inet6 filter <filter name> term 1 then log set firewall family inet6 filter <filter name> term 1 then syslog <<< Must be enabled for all discarding terms set firewall family inet6 filter <filter name> term 1 then discard set syslog host <external syslog address> any info set system syslog file messages any info
- RMF Control
- AU-3
- Severity
- Low
- CCI
- CCI-000134
- Version
- JUEX-RT-000260
- Vuln IDs
-
- V-253998
- Rule IDs
-
- SV-253998r844027_rule
Checks: C-57450r844025_chk
Review the router interface firewall filters to verify all deny statements are logged. At a minimum, all discarding filter terms must have the "syslog" action enabled. Verify all discarding firewall filter terms are configured with (minimally) the "syslog" action: [edit firewall] family inet { filter <filter name> { term <name> { from { <match conditions>; } then { log; syslog; <<< Must be enabled for local and external syslog. discard; } } } } family inet6 { filter <filter name> { term <name> { from { <match conditions>; } then { log; syslog; <<< Must be enabled for local and external syslog. discard; } } } } If packets being dropped are not logged, this is a finding.
Fix: F-57401r844026_fix
Configure interface firewall filters to log all deny statements. All discarding firewall filter terms: <filter terms and match conditions> set firewall family inet filter <filter name> term <name> then log set firewall family inet filter <filter name> term <name> then syslog <<< Minimally must be configured for all discarding filter terms. set firewall family inet filter <filter name> term <name> then discard <filter terms and match conditions> set firewall family inet6 filter <filter name> term <name> then log set firewall family inet6 filter <filter name> term <name> then syslog <<< Minimally must be configured for all discarding filter terms. set firewall family inet6 filter <filter name> term <name> then discard
- RMF Control
- CM-7
- Severity
- Low
- CCI
- CCI-000381
- Version
- JUEX-RT-000270
- Vuln IDs
-
- V-253999
- Rule IDs
-
- SV-253999r844030_rule
Checks: C-57451r844028_chk
Review the router configuration to determine if services or functions not required for operation, or not related to router functionality (e.g., DNS, email client or server, FTP server, or web server) are enabled. By default, unnecessary services like finger, telnet, TFTP and FTP are not enabled and will not be listed at [edit system services]. For example, the following services should NOT be enabled as shown: [edit system services] finger; ftp; rlogin; telnet; tftp-server; web-management; Note: If the services listed above are marked "inactive", they are not enabled. If unnecessary services and functions are enabled on the router, this is a finding.
Fix: F-57402r844029_fix
Remove unneeded services and functions from the router. For example: delete system services finger delete system services ftp delete system services rlogin delete system services telnet delete system services tftp-server delete system services web-management For processes that support disable: set system processes web-management disable Removal is recommended because the service or function may be inadvertently enabled otherwise. However, if removal is not possible, disable the service or function.
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000280
- Vuln IDs
-
- V-254000
- Rule IDs
-
- SV-254000r844033_rule
Checks: C-57452r844031_chk
Verify the call home service is disabled on the device. Verify [edit system] does NOT contain a phone-home hierarchy as shown: [edit system] host-name <hostname>; : <other system configuration> : phone-home { server https://<applicable URL>; rfc-compliant; } If a call home service is enabled, this is a finding.
Fix: F-57403r844032_fix
Configure the network device to disable the call home service or feature. Delete the phone-home hierarchy under [edit system]. delete system phone-home Note: Because the command is hidden, Junos will not autocomplete and "phone-home" must be explicitly, and correctly, spelled out.
- RMF Control
- IA-7
- Severity
- Medium
- CCI
- CCI-000803
- Version
- JUEX-RT-000290
- Vuln IDs
-
- V-254001
- Rule IDs
-
- SV-254001r844036_rule
Checks: C-57453r844034_chk
Review the router configuration. For every protocol that affects the routing or forwarding tables (where information is exchanged between neighbors), verify that neighbor router authentication is encrypting the authentication key. [edit protocols] ospf { area <area number> { interface <interface name>.<logical unit> { authentication { md5 1 key "$8$aes256-gcm$hmac-sha2-256$100$hvt9Fpk6EEU$I2FKFJNrdKHpp1xesMB0aA$l9BsHxOYO4+B8f7erRj8Hw$A9PYzx53Ius"; ## SECRET-DATA } } interface <interface name>.<logical unit> { ipsec-sa <SA name>; } } } ospf3 { area <area number> { interface <interface name>.<logical unit> { ipsec-sa <SA name>; } } } Note: OSPFv3 only supports IPsec SA authentication; OSPFv2 supports both IPsec SA and MD5 authentication. MD5 authentication is only included to support devices that do not support IPsec SA authentication. Verify the OSPFv3 SA. [edit security ipsec] security-association <SA name> { mode transport; manual { direction bidirectional { protocol (ah | esp | bundle); spi (256..16639); <<< The SPI is an integer value that must match the peer encryption { algorithm (hmac-sha1-96 | hmac-sha-256-128); key hexadecimal "$8$aes256-gcm$hmac-sha2-256$100$QAP67/2oV/s$nz+2A3zRz40fwxMJdbbA0Q$R5A/koX36OvUWBB543QwAA$tQrR3fkCL2oQ3V1O2Tw2lYl7THNuqBQ6hpyi8naLlXMaKQM0SdJYefQU41rB3zpjisVIWBwS+S8+O146luRf3Q"; ## SECRET-DATA } } } } Note: OSPFv3 SA uses manual transport mode encapsulating security payload (ESP) associations. If authentication is not encrypting the authentication key, this is a finding.
Fix: F-57404r844035_fix
Configure routing protocol authentication to encrypt the authentication key. set protocols ospf area <area number> interface <interface name>.<logical unit> authentication md5 <key ID> key "<PSK>" -or- set protocols ospf area <area number> interface <interface name>.<logical unit> ipsec-sa <SA name> set protocols ospf3 area <area number> interface <interface name>.<logical unit> ipsec-sa <SA name> set security ipsec security-association <SA name> mode transport set security ipsec security-association <SA name> manual direction bidirectional protocol (ah | esp | bundle) set security ipsec security-association <SA name> manual direction bidirectional spi <manually configured SPI (256..16639)> set security ipsec security-association <SA name> manual direction bidirectional encryption algorithm (hmac-sha1-96 | hmac-sha-256-128) set security ipsec security-association <SA name> manual direction bidirectional authentication key hexadecimal "<appropriate PSK>" Note: Encryption keys can also be entered as ASCII with the keyword 'ascii-text' replacing 'hexadecimal'. Regardless of key type, the PSK is hashed in the configuration.
- RMF Control
- IA-7
- Severity
- Medium
- CCI
- CCI-000803
- Version
- JUEX-RT-000300
- Vuln IDs
-
- V-254002
- Rule IDs
-
- SV-254002r904444_rule
Checks: C-57454r904443_chk
Verify routing protocol authentication is enabled using a FIPS 198-1 validated hashed message authentication code (HMAC). For protocols supporting IPsec SA: [edit security ipsec] security-association <SA name> { <snip> NOTE: Versions of Junos not supporting RFC5709 must be configured to use MD5 authentication, but this is still a CAT III finding since MD5 is not compliant. For protocols not supporting IPsec SA (OSPFv2 example shown) [edit protocols ospf] area <area number> { interface <name> { authentication { <algorithm> <key number> key “<hashed value>”; } } } If a NIST-validated FIPS 198-1 message authentication code algorithm is not being used to authenticate routing protocols, this is a finding. Routing protocols using authentication with non-NIST-validated FIPS 198-1 algorithms may be downgraded to CAT III.
Fix: F-57405r904414_fix
Configure routing protocol authentication to use a NIST-validated FIPS 198-1 message authentication code algorithm. Configure the IPsec SA: set security ipsec security-association <SA name> mode transport set security ipsec security-association <SA name> manual direction bidirectional protocol (ah | esp | bundle) set security ipsec security-association <SA name> manual direction bidirectional spi <manually configured SPI (256..16639)> set security ipsec security-association <SA name> manual direction bidirectional authentication algorithm (hmac-sha1-96 | hmac-sha-256-128) set security ipsec security-association <SA name> manual direction bidirectional authentication key hexadecimal "<appropriate PSK>" Note: Encryption keys can also be entered as ASCII with the keyword 'ascii-text' replacing 'hexadecimal'. Regardless of key type, the PSK is hashed in the configuration. Configure EGP / IGP to use IPsec SA for authentication: set protocols bgp group <BGP group name> neighbor <IPv4 neighbor address> ipsec-sa <SA name> set protocols bgp group <BGP group name> neighbor <IPv6 neighbor address> ipsec-sa <SA name> set protocols ospf area <OSPFv2 area number> interface <interface name>.<logical unit> ipsec-sa <SA name> set protocols ospf3 area <OSPFv3 area number> interface <interface name>.<logical unit> ipsec-sa <SA name> NOTE: Versions of Junos not supporting RFC5709 must be configured to use MD5 authentication, but this is still a CAT III finding since MD5 is not compliant.
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-001094
- Version
- JUEX-RT-000310
- Vuln IDs
-
- V-254003
- Rule IDs
-
- SV-254003r844042_rule
Checks: C-57455r844040_chk
Review the PE router configuration to determine if a MAC address limit has been set for each bridge domain. Verify the MAC address limit is globally defined for the VPLS protocol or at each interface assigned to the routing instance. [edit routing-instance] <instance name> { protocols { vpls { interface-mac-limit { <value>; } interface <interface name>.<logical unit> { interface-mac-limit { <value>; } } } } } Note: Only EX9200-series devices currently support VPLS. If a limit has not been configured, this is a finding.
Fix: F-57406r844041_fix
Configure a MAC address learning limit for each VPLS bridge domain. set routing-instance <name> protocols vpls interface-mac-limit <value> set routing-instance <name> protocols vpls interface <name>.<logical unit> interface-mac-limit <value>
- RMF Control
- SC-5
- Severity
- Low
- CCI
- CCI-001095
- Version
- JUEX-RT-000320
- Vuln IDs
-
- V-254004
- Rule IDs
-
- SV-254004r844045_rule
Checks: C-57456r844043_chk
Review the router configuration to verify that the router has been configured to enable refresh reduction features. Junos OS controls RSVP refresh reduction features using two commands: aggregate: RSVP message bundling and summary refresh. reliable: RSVP message ID, reliable message delivery, and summary refresh. Starting in Junos 15.2, refresh reduction is enabled by default and the "aggregate" command is deprecated. Configuring the "aggregate" command generates a warning message in the configuration file (## Warning: "aggregate" is deprecated). On Junos earlier than 15.2, verify the "aggregate" command is enabled. On Junos 15.2 and later, no command is required. Junos earlier than 15.2: [edit protocols] rsvp { interface <interface name>.<logical unit> { aggregate; reliable; << If RSVP message ID and reliable message delivery are required. } } Junos 15.2 but pre-16.1R1: [edit protocols] rsvp { interface <interface name>.<logical unit> { reliable; << If RSVP message ID and reliable message delivery are required. } } Starting in Junos 16.1R1, all refresh reduction features are enabled by default. Verify the 'no-reliable' command is configured only if RSVP message ID and reliable message delivery are not required. To enable all refresh reduction features, no commands are necessary. Junos 16.1R1 and later: [edit protocols] rsvp { interface <interface name>.<logical unit> { <other configuration> } } If the router with RSVP-TE enabled does not have message pacing configured based on the link speed and input queue size of adjacent core routers, this is a finding.
Fix: F-57407r844044_fix
Configure RSVP-TE enabled routers with refresh reduction features. Junos earlier than 15.2: set protocols rsvp interface <interface name>.<logical unit> aggregate set protocols rsvp interface <interface name>.<logical unit> reliable Junos 15.2 but pre 16.1R1: set protocols rsvp interface <interface name>.<logical unit> reliable Junos 16.1R1 and later: set protocols rsvp interface <interface name>.<logical unit> <other configuration>
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-001095
- Version
- JUEX-RT-000330
- Vuln IDs
-
- V-254005
- Rule IDs
-
- SV-254005r844048_rule
Checks: C-57457r844046_chk
Review the router configuration to verify that storm control is enabled on CE-facing interfaces deploying VPLS. Verify that a stateless firewall filter has been applied to each VPLS routing instances. [edit] routing-instances { <name> { forwarding-options { family vpls { flood { input <filter name>; } } } } } Verify the filter defines traffic types associated with storm control (i.e., broadcast, multicast, and unknown unicast storms). firewall { family vpls { filter <filter name> { term <term name> { from { traffic-type broadcast; } then { policer <policer name>; accept; } } term <term name> { from { traffic-type multicast; } then { policer <policer name>; accept; } } term <term name> { from { traffic-type unknown-unicast; } then { policer <policer name>; accept; } } } } } Verify that the policer rate limits in accordance with local requirements. firewall { policer <policer name> { if-exceeding { bandwidth-limit <value>; burst-size-limit <value>; } then discard; } } Note: Only EX9200-series devices currently support VPLS. If storm control is not enabled for broadcast traffic, this is a finding.
Fix: F-57408r844047_fix
Configure storm control for each CE-facing interface deploying VPLS bridge domains. Base the suppression threshold on expected traffic rates plus some additional capacity. Configure a policer to rate limit traffic providing storm control in accordance with organizational requirements. set firewall policer <policer name> if-exceeding bandwidth-limit <value> burst-size-limit <value> set firewall policer <policer name> then discard Configure the filter providing storm control to specify traffic types and rate limit broadcast, multicast, and unknown unicast storms. set firewall family vpls filter <filter name> term <term name> from traffic-type broadcast set firewall family vpls filter <filter name> term <term name> then policer <policer name> accept set firewall family vpls filter <filter name> term <term name> from traffic-type multicast set firewall family vpls filter <filter name> term <term name> then policer <policer name> accept set firewall family vpls filter <filter name> term <term name> from traffic-type unknown-unicast set firewall family vpls filter <filter name> term <term name> then policer <policer name> accept Apply the storm control filter to all CE-facing instances deploying VPLS bridge domains. set routing-instances <instance name> forwarding-options family vpls flood input <filter name>
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-001095
- Version
- JUEX-RT-000340
- Vuln IDs
-
- V-254006
- Rule IDs
-
- SV-254006r997521_rule
Checks: C-57458r844049_chk
Review the router configuration and interview the System Administrator to verify that a mechanism for traffic prioritization and bandwidth reservation exists. For example: [edit class-of-service] classifiers { dscp <classifier name> { forwarding-class NC { loss-priority low code-points 110000; } forwarding-class EF { loss-priority high code-points [ 101101 101111 100101 100111 110011 ]; loss-priority low code-points [ 101000 100000 101001 101011 100001 100011 110001 ]; } forwarding-class AF41 { loss-priority high code-points [ 100010 100100 100110 ]; loss-priority low code-points [ 011000 101110 011100 011110 ]; } forwarding-class AF31 { loss-priority high code-points [ 011101 011111 011010 010101 010111 010010 001101 001010 010000 ]; loss-priority low code-points [ 001001 001011 010001 010011 011001 011011 ]; } forwarding-class BE { loss-priority high code-points 000000; } forwarding-class Default { loss-priority high code-points 001000; } forwarding-class dscp15 { loss-priority high code-points 001111; } } } Note: Some platforms apply DSCP values to both IPv4 and IPv6 traffic with a single classifier definition (as shown). Those platforms that support separating classifiers will require a "dscp-ipv6" stanza. host-outbound-traffic { forwarding-class NC; dscp-code-point 110000; } shared-buffer { ingress { percent 50; buffer-partition lossless { percent 5; } buffer-partition lossless-headroom { percent 0; } buffer-partition lossy { percent 95; } } egress { percent 100; buffer-partition lossless { percent 50; } buffer-partition lossy { percent 45; } buffer-partition multicast { percent 5; } } } Note: Some platforms only support shared-buffer percent, and cannot separate between ingress and egress. Not all devices require a shared-buffer stanza. forwarding-classes { class NC queue-num 7; class EF queue-num 6; class AF41 queue-num 5; class AF31 queue-num 4; class BE queue-num 0; class Default queue-num 1; class dscp15 queue-num 6; } traffic-control-profiles { <control profile name 1> { scheduler-map <scheduler map name 1>; shaping-rate percent 100; } <control profile name 2> { scheduler-map <scheduler map name 2>; guaranteed-rate percent 20; } } forwarding-class-sets { <set name 1> { class NC; class EF; class AF41; class AF31; class Default; class dscp15; } <set name 2> { class BE; } } interfaces { <interface name> { forwarding-class-set { <set name 1> { output-traffic-control-profile <control profile name 1>; } <set name 2> { output-traffic-control-profile <control profile name 2>; } } classifiers { dscp <classifier name>; } rewrite-rules { dscp <rewrite rule name>; } } } rewrite-rules { dscp <rewrite rule name> { forwarding-class dscp15 { loss-priority high code-point 101101; } forwarding-class EF { loss-priority low code-point 110001; } forwarding-class AF41 { loss-priority high code-point 100110; } forwarding-class NC { loss-priority low code-point 110000; } forwarding-class AF31 { loss-priority high code-point 010000; } forwarding-class Default { loss-priority high code-point 001000; } } } Note: Some platforms require rewriting all DSCP values if rewriting one (smaller platforms). Most support only rewriting a single DSCP value, which would eliminate all but one rewrite rule. scheduler-maps { <scheduler map name 1> { forwarding-class NC scheduler NC; forwarding-class EF scheduler EF; forwarding-class AF41 scheduler AF41; forwarding-class AF31 scheduler AF31; forwarding-class Default scheduler Default; } <scheduler map name 2> { forwarding-class BE scheduler BE; } } schedulers { NC { buffer-size percent 5; priority strict-high; } EF { shaping-rate percent 20; buffer-size percent 19; priority strict-high; } AF41 { shaping-rate percent 15; buffer-size percent 14; priority strict-high; } AF31 { shaping-rate percent 31; buffer-size percent 29; priority strict-high; } BE { transmit-rate percent 20; buffer-size percent 20; priority low; } Default { shaping-rate percent 10; buffer-size percent 9; priority strict-high; } } This arrangement must ensure that sufficient capacity is available for mission-critical traffic and enforce the traffic priorities specified by the Combatant Commands/Services/Agencies. If no such scheme exists or it is not configured, this is a finding.
Fix: F-57409r844050_fix
Implement a mechanism for traffic prioritization and bandwidth reservation. This mechanism must enforce the traffic priorities specified by the Combatant Commands/Services/Agencies. set class-of-service classifiers dscp <classifier name> forwarding-class NC loss-priority low code-points 110000 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 101101 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 101111 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 100101 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 100111 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 110011 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 101000 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 100000 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 101001 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 101011 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 100001 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 100011 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 110001 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority high code-points 100010 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority high code-points 100100 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority high code-points 100110 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 011000 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 101110 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 011100 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 011110 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 011101 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 011111 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 011010 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010101 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010111 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010010 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 001101 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 001010 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010000 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 001001 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 001011 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 010001 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 010011 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 011001 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 011011 set class-of-service classifiers dscp <classifier name> forwarding-class BE loss-priority high code-points 000000 set class-of-service classifiers dscp <classifier name> forwarding-class Default loss-priority high code-points 001000 set class-of-service classifiers dscp <classifier name> forwarding-class dscp15 loss-priority high code-points 001111 Note: Some platforms apply DSCP values to both IPv4 and IPv6 traffic with a single classifier definition (as shown). Those platforms that support separating classifiers will require a "dscp-ipv6" stanza. set class-of-service host-outbound-traffic forwarding-class NC set class-of-service host-outbound-traffic dscp-code-point 110000 set class-of-service shared-buffer ingress percent 50 set class-of-service shared-buffer ingress buffer-partition lossless percent 5 set class-of-service shared-buffer ingress buffer-partition lossless-headroom percent 0 set class-of-service shared-buffer ingress buffer-partition lossy percent 95 set class-of-service shared-buffer egress percent 100 set class-of-service shared-buffer egress buffer-partition lossless percent 50 set class-of-service shared-buffer egress buffer-partition lossy percent 45 set class-of-service shared-buffer egress buffer-partition multicast percent 5 Note: Some platforms only support shared-buffer percent, and cannot separate between ingress and egress. Not all devices require a shared-buffer stanza. set class-of-service forwarding-classes class NC queue-num 7 set class-of-service forwarding-classes class EF queue-num 6 set class-of-service forwarding-classes class AF41 queue-num 5 set class-of-service forwarding-classes class AF31 queue-num 4 set class-of-service forwarding-classes class BE queue-num 0 set class-of-service forwarding-classes class Default queue-num 1 set class-of-service forwarding-classes class dscp15 queue-num 6 set class-of-service traffic-control-profiles <control profile name 1> scheduler-map <scheduler map name 1> set class-of-service traffic-control-profiles <control profile name 1> shaping-rate percent 100 set class-of-service traffic-control-profiles <control profile name 2> scheduler-map <scheduler map name 2> set class-of-service traffic-control-profiles <control profile name 2> guaranteed-rate percent 20 set class-of-service forwarding-class-sets <set name 1> class NC set class-of-service forwarding-class-sets <set name 1> class EF set class-of-service forwarding-class-sets <set name 1> class AF41 set class-of-service forwarding-class-sets <set name 1> class AF31 set class-of-service forwarding-class-sets <set name 1> class Default set class-of-service forwarding-class-sets <set name 1> class dscp15 set class-of-service forwarding-class-sets <set name 2> class BE set class-of-service interfaces <interface name> forwarding-class-set <set name 1> output-traffic-control-profile <control profile name 1> set class-of-service interfaces <interface name> forwarding-class-set <set name 2> output-traffic-control-profile <control profile name 2> set class-of-service interfaces <interface name> classifiers dscp <classifier name> set class-of-service interfaces <interface name> rewrite-rules dscp <rewrite rule name> set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class dscp15 loss-priority high code-point 101101 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class EF loss-priority low code-point 110001 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class AF41 loss-priority high code-point 100110 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class NC loss-priority low code-point 110000 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class AF31 loss-priority high code-point 010000 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class Default loss-priority high code-point 001000 set class-of-service scheduler-maps <scheduler map name 1> forwarding-class NC scheduler NC set class-of-service scheduler-maps <scheduler map name 1> forwarding-class EF scheduler EF set class-of-service scheduler-maps <scheduler map name 1> forwarding-class AF41 scheduler AF41 set class-of-service scheduler-maps <scheduler map name 1> forwarding-class AF31 scheduler AF31 set class-of-service scheduler-maps <scheduler map name 1> forwarding-class Default scheduler Default set class-of-service scheduler-maps <scheduler map name 2> forwarding-class BE scheduler BE set class-of-service schedulers NC buffer-size percent 5 set class-of-service schedulers NC priority strict-high set class-of-service schedulers EF shaping-rate percent 20 set class-of-service schedulers EF buffer-size percent 19 set class-of-service schedulers EF priority strict-high set class-of-service schedulers AF41 shaping-rate percent 15 set class-of-service schedulers AF41 buffer-size percent 14 set class-of-service schedulers AF41 priority strict-high set class-of-service schedulers AF31 shaping-rate percent 31 set class-of-service schedulers AF31 buffer-size percent 29 set class-of-service schedulers AF31 priority strict-high set class-of-service schedulers BE transmit-rate percent 20 set class-of-service schedulers BE buffer-size percent 20 set class-of-service schedulers BE priority low set class-of-service schedulers Default shaping-rate percent 10 set class-of-service schedulers Default buffer-size percent 9 set class-of-service schedulers Default priority strict-high
- RMF Control
- SC-5
- Severity
- Low
- CCI
- CCI-001095
- Version
- JUEX-RT-000350
- Vuln IDs
-
- V-254007
- Rule IDs
-
- SV-254007r997522_rule
Checks: C-57459r844052_chk
Review the router configuration and verify that a QoS policy has been configured to provide preferred treatment for mission-critical applications in accordance with the QoS GIG Technical Profile. Verify that the classifiers are configured to match on DSCP. Note: Juniper routers also support classifying on MPLS EXP and IEEE 802.1 values. Verify that the schedulers are configured to set DSCP values for the defined classifiers in accordance with the QoS GIG Technical Profile. Verify that forwarding class sets or scheduler maps are applied all interfaces. 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 To classify on L4 ports or protocols, use stateless firewall filters to direct matched traffic into the required forwarding class. [edit class-of-service] classifiers { dscp <classifier name> { forwarding-class NC { loss-priority low code-points 110000; } forwarding-class EF { loss-priority high code-points [ 101101 101111 100101 100111 110011 ]; loss-priority low code-points [ 101000 100000 101001 101011 100001 100011 110001 ]; } forwarding-class AF41 { loss-priority high code-points [ 100010 100100 100110 ]; loss-priority low code-points [ 011000 101110 011100 011110 ]; } forwarding-class AF31 { loss-priority high code-points [ 011101 011111 011010 010101 010111 010010 001101 001010 010000 ]; loss-priority low code-points [ 001001 001011 010001 010011 011001 011011 ]; } forwarding-class BE { loss-priority high code-points 000000; } forwarding-class Default { loss-priority high code-points 001000; } forwarding-class dscp15 { loss-priority high code-points 001111; } } } Note: Some platforms apply DSCP values to both IPv4 and IPv6 traffic with a single classifier definition (as shown). Those platforms that support separating classifiers will require a "dscp-ipv6" stanza. host-outbound-traffic { forwarding-class NC; dscp-code-point 110000; } shared-buffer { ingress { percent 50; buffer-partition lossless { percent 5; } buffer-partition lossless-headroom { percent 0; } buffer-partition lossy { percent 95; } } egress { percent 100; buffer-partition lossless { percent 50; } buffer-partition lossy { percent 45; } buffer-partition multicast { percent 5; } } } Note: Some platforms only support shared-buffer percent, and cannot separate between ingress and egress. Not all devices require a shared-buffer stanza. forwarding-classes { class NC queue-num 7; class EF queue-num 6; class AF41 queue-num 5; class AF31 queue-num 4; class BE queue-num 0; class Default queue-num 1; class dscp15 queue-num 6; } traffic-control-profiles { <control profile name 1> { scheduler-map <scheduler map name 1>; shaping-rate percent 100; } <control profile name 2> { scheduler-map <scheduler map name 2>; guaranteed-rate percent 20; } } forwarding-class-sets { <set name 1> { class NC; class EF; class AF41; class AF31; class Default; class dscp15; } <set name 2> { class BE; } } interfaces { <interface name> { forwarding-class-set { <set name 1> { output-traffic-control-profile <control profile name 1>; } <set name 2> { output-traffic-control-profile <control profile name 2>; } } classifiers { dscp <classifier name>; } rewrite-rules { dscp <rewrite rule name>; } } } rewrite-rules { dscp <rewrite rule name> { forwarding-class dscp15 { loss-priority high code-point 101101; } forwarding-class EF { loss-priority low code-point 110001; } forwarding-class AF41 { loss-priority high code-point 100110; } forwarding-class NC { loss-priority low code-point 110000; } forwarding-class AF31 { loss-priority high code-point 010000; } forwarding-class Default { loss-priority high code-point 001000; } } } Note: Some platforms require rewriting all DSCP values if rewriting one (smaller platforms). Most support only rewriting a single DSCP value, which would eliminate all but one rewrite rule. scheduler-maps { <scheduler map name 1> { forwarding-class NC scheduler NC; forwarding-class EF scheduler EF; forwarding-class AF41 scheduler AF41; forwarding-class AF31 scheduler AF31; forwarding-class Default scheduler Default; } <scheduler map name 2> { forwarding-class BE scheduler BE; } } schedulers { NC { buffer-size percent 5; priority strict-high; } EF { shaping-rate percent 20; buffer-size percent 19; priority strict-high; } AF41 { shaping-rate percent 15; buffer-size percent 14; priority strict-high; } AF31 { shaping-rate percent 31; buffer-size percent 29; priority strict-high; } BE { transmit-rate percent 20; buffer-size percent 20; priority low; } Default { shaping-rate percent 10; buffer-size percent 9; priority strict-high; } } If the router is not configured to implement a QoS policy in accordance with the QoS GIG Technical Profile, this is a finding.
Fix: F-57410r844053_fix
Configure a QoS policy on each router in accordance with the QoS GIG Technical Profile. set class-of-service classifiers dscp <classifier name> forwarding-class NC loss-priority low code-points 110000 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 101101 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 101111 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 100101 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 100111 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 110011 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 101000 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 100000 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 101001 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 101011 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 100001 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 100011 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 110001 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority high code-points 100010 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority high code-points 100100 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority high code-points 100110 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 011000 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 101110 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 011100 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 011110 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 011101 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 011111 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 011010 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010101 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010111 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010010 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 001101 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 001010 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010000 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 001001 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 001011 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 010001 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 010011 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 011001 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 011011 set class-of-service classifiers dscp <classifier name> forwarding-class BE loss-priority high code-points 000000 set class-of-service classifiers dscp <classifier name> forwarding-class Default loss-priority high code-points 001000 set class-of-service classifiers dscp <classifier name> forwarding-class dscp15 loss-priority high code-points 001111 Note: Some platforms apply DSCP values to both IPv4 and IPv6 traffic with a single classifier definition (as shown). Those platforms that support separating classifiers will require a "dscp-ipv6" stanza. set class-of-service host-outbound-traffic forwarding-class NC set class-of-service host-outbound-traffic dscp-code-point 110000 set class-of-service shared-buffer ingress percent 50 set class-of-service shared-buffer ingress buffer-partition lossless percent 5 set class-of-service shared-buffer ingress buffer-partition lossless-headroom percent 0 set class-of-service shared-buffer ingress buffer-partition lossy percent 95 set class-of-service shared-buffer egress percent 100 set class-of-service shared-buffer egress buffer-partition lossless percent 50 set class-of-service shared-buffer egress buffer-partition lossy percent 45 set class-of-service shared-buffer egress buffer-partition multicast percent 5 Note: Some platforms only support shared-buffer percent, and cannot separate between ingress and egress. Not all devices require a shared-buffer stanza. set class-of-service forwarding-classes class NC queue-num 7 set class-of-service forwarding-classes class EF queue-num 6 set class-of-service forwarding-classes class AF41 queue-num 5 set class-of-service forwarding-classes class AF31 queue-num 4 set class-of-service forwarding-classes class BE queue-num 0 set class-of-service forwarding-classes class Default queue-num 1 set class-of-service forwarding-classes class dscp15 queue-num 6 set class-of-service traffic-control-profiles <control profile name 1> scheduler-map <scheduler map name 1> set class-of-service traffic-control-profiles <control profile name 1> shaping-rate percent 100 set class-of-service traffic-control-profiles <control profile name 2> scheduler-map <scheduler map name 2> set class-of-service traffic-control-profiles <control profile name 2> guaranteed-rate percent 20 set class-of-service forwarding-class-sets <set name 1> class NC set class-of-service forwarding-class-sets <set name 1> class EF set class-of-service forwarding-class-sets <set name 1> class AF41 set class-of-service forwarding-class-sets <set name 1> class AF31 set class-of-service forwarding-class-sets <set name 1> class Default set class-of-service forwarding-class-sets <set name 1> class dscp15 set class-of-service forwarding-class-sets <set name 2> class BE set class-of-service interfaces <interface name> forwarding-class-set <set name 1> output-traffic-control-profile <control profile name 1> set class-of-service interfaces <interface name> forwarding-class-set <set name 2> output-traffic-control-profile <control profile name 2> set class-of-service interfaces <interface name> classifiers dscp <classifier name> set class-of-service interfaces <interface name> rewrite-rules dscp <rewrite rule name> set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class dscp15 loss-priority high code-point 101101 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class EF loss-priority low code-point 110001 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class AF41 loss-priority high code-point 100110 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class NC loss-priority low code-point 110000 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class AF31 loss-priority high code-point 010000 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class Default loss-priority high code-point 001000 set class-of-service scheduler-maps <scheduler map name 1> forwarding-class NC scheduler NC set class-of-service scheduler-maps <scheduler map name 1> forwarding-class EF scheduler EF set class-of-service scheduler-maps <scheduler map name 1> forwarding-class AF41 scheduler AF41 set class-of-service scheduler-maps <scheduler map name 1> forwarding-class AF31 scheduler AF31 set class-of-service scheduler-maps <scheduler map name 1> forwarding-class Default scheduler Default set class-of-service scheduler-maps <scheduler map name 2> forwarding-class BE scheduler BE set class-of-service schedulers NC buffer-size percent 5 set class-of-service schedulers NC priority strict-high set class-of-service schedulers EF shaping-rate percent 20 set class-of-service schedulers EF buffer-size percent 19 set class-of-service schedulers EF priority strict-high set class-of-service schedulers AF41 shaping-rate percent 15 set class-of-service schedulers AF41 buffer-size percent 14 set class-of-service schedulers AF41 priority strict-high set class-of-service schedulers AF31 shaping-rate percent 31 set class-of-service schedulers AF31 buffer-size percent 29 set class-of-service schedulers AF31 priority strict-high set class-of-service schedulers BE transmit-rate percent 20 set class-of-service schedulers BE buffer-size percent 20 set class-of-service schedulers BE priority low set class-of-service schedulers Default shaping-rate percent 10 set class-of-service schedulers Default buffer-size percent 9 set class-of-service schedulers Default priority strict-high
- RMF Control
- SC-5
- Severity
- Low
- CCI
- CCI-001095
- Version
- JUEX-RT-000360
- Vuln IDs
-
- V-254008
- Rule IDs
-
- SV-254008r997523_rule
Checks: C-57460r844055_chk
Review the router configuration and verify that a QoS policy has been configured to provide preferred treatment for mission-critical applications in accordance with the QoS GIG Technical Profile. Verify that the classifiers are configured to match on DSCP. Note: Juniper routers also support classifying on MPLS EXP and IEEE 802.1 values. Verify that the schedulers are configured to set DSCP values for the defined classifiers in accordance with the QoS GIG Technical Profile. Verify that classifiers are applied all interfaces. 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 To classify on L4 ports or protocols, use stateless firewall filters to direct matched traffic into the required forwarding class. [edit class-of-service] classifiers { dscp <classifier name> { forwarding-class NC { loss-priority low code-points 110000; } forwarding-class EF { loss-priority high code-points [ 101101 101111 100101 100111 110011 ]; loss-priority low code-points [ 101000 100000 101001 101011 100001 100011 110001 ]; } forwarding-class AF41 { loss-priority high code-points [ 100010 100100 100110 ]; loss-priority low code-points [ 011000 101110 011100 011110 ]; } forwarding-class AF31 { loss-priority high code-points [ 011101 011111 011010 010101 010111 010010 001101 001010 010000 ]; loss-priority low code-points [ 001001 001011 010001 010011 011001 011011 ]; } forwarding-class BE { loss-priority high code-points 000000; } forwarding-class Default { loss-priority high code-points 001000; } forwarding-class dscp15 { loss-priority high code-points 001111; } } } Note: Some platforms apply DSCP values to both IPv4 and IPv6 traffic with a single classifier definition (as shown). Those platforms that support separating classifiers will require a "dscp-ipv6" stanza. host-outbound-traffic { forwarding-class NC; dscp-code-point 110000; } shared-buffer { ingress { percent 50; buffer-partition lossless { percent 5; } buffer-partition lossless-headroom { percent 0; } buffer-partition lossy { percent 95; } } egress { percent 100; buffer-partition lossless { percent 50; } buffer-partition lossy { percent 45; } buffer-partition multicast { percent 5; } } } Note: Some platforms only support shared-buffer percent, and cannot separate between ingress and egress. Not all devices require a shared-buffer stanza. forwarding-classes { class NC queue-num 7; class EF queue-num 6; class AF41 queue-num 5; class AF31 queue-num 4; class BE queue-num 0; class Default queue-num 1; class dscp15 queue-num 6; } traffic-control-profiles { <control profile name 1> { scheduler-map <scheduler map name 1>; shaping-rate percent 100; } <control profile name 2> { scheduler-map <scheduler map name 2>; guaranteed-rate percent 20; } } forwarding-class-sets { <set name 1> { class NC; class EF; class AF41; class AF31; class Default; class dscp15; } <set name 2> { class BE; } } interfaces { <interface name> { forwarding-class-set { <set name 1> { output-traffic-control-profile <control profile name 1>; } <set name 2> { output-traffic-control-profile <control profile name 2>; } } classifiers { dscp <classifier name>; } rewrite-rules { dscp <rewrite rule name>; } } } rewrite-rules { dscp <rewrite rule name> { forwarding-class dscp15 { loss-priority high code-point 101101; } forwarding-class EF { loss-priority low code-point 110001; } forwarding-class AF41 { loss-priority high code-point 100110; } forwarding-class NC { loss-priority low code-point 110000; } forwarding-class AF31 { loss-priority high code-point 010000; } forwarding-class Default { loss-priority high code-point 001000; } } } Note: Some platforms require rewriting all DSCP values if rewriting one (smaller platforms). Most support only rewriting a single DSCP value, which would eliminate all but one rewrite rule. scheduler-maps { <scheduler map name 1> { forwarding-class NC scheduler NC; forwarding-class EF scheduler EF; forwarding-class AF41 scheduler AF41; forwarding-class AF31 scheduler AF31; forwarding-class Default scheduler Default; } <scheduler map name 2> { forwarding-class BE scheduler BE; } } schedulers { NC { buffer-size percent 5; priority strict-high; } EF { shaping-rate percent 20; buffer-size percent 19; priority strict-high; } AF41 { shaping-rate percent 15; buffer-size percent 14; priority strict-high; } AF31 { shaping-rate percent 31; buffer-size percent 29; priority strict-high; } BE { transmit-rate percent 20; buffer-size percent 20; priority low; } Default { shaping-rate percent 10; buffer-size percent 9; priority strict-high; } } If the router is not configured to implement a QoS policy in accordance with the QoS GIG Technical Profile, this is a finding.
Fix: F-57411r844056_fix
Configure a QoS policy on each router in accordance with the QoS GIG Technical Profile. set class-of-service classifiers dscp <classifier name> forwarding-class NC loss-priority low code-points 110000 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 101101 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 101111 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 100101 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 100111 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority high code-points 110011 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 101000 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 100000 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 101001 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 101011 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 100001 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 100011 set class-of-service classifiers dscp <classifier name> forwarding-class EF loss-priority low code-points 110001 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority high code-points 100010 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority high code-points 100100 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority high code-points 100110 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 011000 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 101110 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 011100 set class-of-service classifiers dscp <classifier name> forwarding-class AF41 loss-priority low code-points 011110 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 011101 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 011111 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 011010 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010101 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010111 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010010 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 001101 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 001010 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority high code-points 010000 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 001001 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 001011 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 010001 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 010011 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 011001 set class-of-service classifiers dscp <classifier name> forwarding-class AF31 loss-priority low code-points 011011 set class-of-service classifiers dscp <classifier name> forwarding-class BE loss-priority high code-points 000000 set class-of-service classifiers dscp <classifier name> forwarding-class Default loss-priority high code-points 001000 set class-of-service classifiers dscp <classifier name> forwarding-class dscp15 loss-priority high code-points 001111 Note: Some platforms apply DSCP values to both IPv4 and IPv6 traffic with a single classifier definition (as shown). Those platforms that support separating classifiers will require a "dscp-ipv6" stanza. set class-of-service host-outbound-traffic forwarding-class NC set class-of-service host-outbound-traffic dscp-code-point 110000 set class-of-service shared-buffer ingress percent 50 set class-of-service shared-buffer ingress buffer-partition lossless percent 5 set class-of-service shared-buffer ingress buffer-partition lossless-headroom percent 0 set class-of-service shared-buffer ingress buffer-partition lossy percent 95 set class-of-service shared-buffer egress percent 100 set class-of-service shared-buffer egress buffer-partition lossless percent 50 set class-of-service shared-buffer egress buffer-partition lossy percent 45 set class-of-service shared-buffer egress buffer-partition multicast percent 5 Note: Some platforms only support shared-buffer percent, and cannot separate between ingress and egress. Not all devices require a shared-buffer stanza. set class-of-service forwarding-classes class NC queue-num 7 set class-of-service forwarding-classes class EF queue-num 6 set class-of-service forwarding-classes class AF41 queue-num 5 set class-of-service forwarding-classes class AF31 queue-num 4 set class-of-service forwarding-classes class BE queue-num 0 set class-of-service forwarding-classes class Default queue-num 1 set class-of-service forwarding-classes class dscp15 queue-num 6 set class-of-service traffic-control-profiles <control profile name 1> scheduler-map <scheduler map name 1> set class-of-service traffic-control-profiles <control profile name 1> shaping-rate percent 100 set class-of-service traffic-control-profiles <control profile name 2> scheduler-map <scheduler map name 2> set class-of-service traffic-control-profiles <control profile name 2> guaranteed-rate percent 20 set class-of-service forwarding-class-sets <set name 1> class NC set class-of-service forwarding-class-sets <set name 1> class EF set class-of-service forwarding-class-sets <set name 1> class AF41 set class-of-service forwarding-class-sets <set name 1> class AF31 set class-of-service forwarding-class-sets <set name 1> class Default set class-of-service forwarding-class-sets <set name 1> class dscp15 set class-of-service forwarding-class-sets <set name 2> class BE set class-of-service interfaces <interface name> forwarding-class-set <set name 1> output-traffic-control-profile <control profile name 1> set class-of-service interfaces <interface name> forwarding-class-set <set name 2> output-traffic-control-profile <control profile name 2> set class-of-service interfaces <interface name> classifiers dscp <classifier name> set class-of-service interfaces <interface name> rewrite-rules dscp <rewrite rule name> set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class dscp15 loss-priority high code-point 101101 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class EF loss-priority low code-point 110001 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class AF41 loss-priority high code-point 100110 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class NC loss-priority low code-point 110000 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class AF31 loss-priority high code-point 010000 set class-of-service rewrite-rules dscp <rewrite rule name> forwarding-class Default loss-priority high code-point 001000 set class-of-service scheduler-maps <scheduler map name 1> forwarding-class NC scheduler NC set class-of-service scheduler-maps <scheduler map name 1> forwarding-class EF scheduler EF set class-of-service scheduler-maps <scheduler map name 1> forwarding-class AF41 scheduler AF41 set class-of-service scheduler-maps <scheduler map name 1> forwarding-class AF31 scheduler AF31 set class-of-service scheduler-maps <scheduler map name 1> forwarding-class Default scheduler Default set class-of-service scheduler-maps <scheduler map name 2> forwarding-class BE scheduler BE set class-of-service schedulers NC buffer-size percent 5 set class-of-service schedulers NC priority strict-high set class-of-service schedulers EF shaping-rate percent 20 set class-of-service schedulers EF buffer-size percent 19 set class-of-service schedulers EF priority strict-high set class-of-service schedulers AF41 shaping-rate percent 15 set class-of-service schedulers AF41 buffer-size percent 14 set class-of-service schedulers AF41 priority strict-high set class-of-service schedulers AF31 shaping-rate percent 31 set class-of-service schedulers AF31 buffer-size percent 29 set class-of-service schedulers AF31 priority strict-high set class-of-service schedulers BE transmit-rate percent 20 set class-of-service schedulers BE buffer-size percent 20 set class-of-service schedulers BE priority low set class-of-service schedulers Default shaping-rate percent 10 set class-of-service schedulers Default buffer-size percent 9 set class-of-service schedulers Default priority strict-high
- RMF Control
- SC-7
- Severity
- High
- CCI
- CCI-001109
- Version
- JUEX-RT-000370
- Vuln IDs
-
- V-254009
- Rule IDs
-
- SV-254009r844060_rule
Checks: C-57461r844058_chk
This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify that the firewall filter is configured to allow specific ports and protocols and deny all other traffic. Associating any firewall filter to an interface will create a deny-all, permit-by-exception posture because each filter includes an implicit "deny all" final term. Verify firewall filters applied inbound on external interfaces are configured with terms permitting specific traffic. For example: [edit firewall] family inet { filter permitted_inbound_traffic_ipv4 { term 1 { from { destination-prefix-list { INSIDE_ADDRESSES_IPv4; } protocol tcp; destination-port [ http https ]; } then accept; } term 2 { from { destination-prefix-list { INSIDE_ADDRESSES_IPv4; } protocol udp; destination-port [ domain radius ]; } then accept; } } } family inet6 { filter permitted_inbound_traffic_ipv6 { term 1 { from { destination-prefix-list { INSIDE_ADDRESSES_IPv6; } next-header tcp; destination-port [ http https ]; } then accept; } term 2 { from { destination-prefix-list { INSIDE_ADDRESSES_IPv6; } next-header udp; destination-port [ domain radius ]; } then accept; } } } Note: Although the example filter is sufficient to meet this requirement, an explicit "deny-all" term is required for logging. For example, add the following final term to both filters (IPv4 and IPv6) to enable logging of discarded packets: [edit firewall family (inet|inet6) filter <name>] term default { then { log; syslog; discard; } } The filter must be configured inbound on all external interfaces. [edit interfaces] <external interface> { unit <number> { family inet { filter input permitted_inbound_traffic_ipv4; address <IPv4 address/mask>; } family inet6 { filter input permitted_inbound_traffic_ipv6; address <IPv6 address/prefix>; } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; 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.
Fix: F-57412r844059_fix
This requirement is not applicable for the DODIN Backbone. Configure the perimeter router to deny network traffic by default and allow network traffic by exception. For example: set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-prefix-list INSIDE_ADDRESSES set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from protocol tcp set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-port http set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-port https set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 then accept set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-prefix-list INSIDE_ADDRESSES set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from protocol udp set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-port domain set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-port radius set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 then accept set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-prefix-list INSIDE_ADDRESSES set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from next-header tcp set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-port http set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-port https set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 then accept set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-prefix-list INSIDE_ADDRESSES set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from next-header udp set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-port domain set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-port radius set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 then accept Note: To enable logging, add the following as the final term to each filter: set firewall family [inet|inet6] filter <name> term default then log set firewall family [inet|inet6] filter <name> term default then syslog set firewall family [inet|inet6] filter <name> term default then discard set interfaces <external interface> unit 0 family inet filter input permitted_inbound_traffic_ipv4 set interfaces <external interface> unit 0 family inet address <IPv4 address / mask> set interfaces <external interface> unit 0 family inet6 filter input permitted_inbound_traffic_ipv6 set interfaces <external interface> unit 0 family inet6 address <IPv6 address / prefix>
- RMF Control
- SC-7
- Severity
- High
- CCI
- CCI-001097
- Version
- JUEX-RT-000380
- Vuln IDs
-
- V-254010
- Rule IDs
-
- SV-254010r997524_rule
Checks: C-57462r844061_chk
Review the firewall filter for the router receive path and verify that it will only process specific management plane and control plane traffic from specific sources. For example: [edit policy-options] auth_mgt_networks-ipv4 { <IPv4 subnet / mask>; } auth_mgt_networks-ipv6 { <IPv6 subnet / prefix>; } device_mgt_address-ipv4 { <IPv4 address>/32; } device_mgt_address-ipv6 { <IPv6 address>/128; } [edit firewall] family inet { filter protect_re-ipv4 { term 1 { from { source-prefix-list auth_mgt_networks-ipv4; destination-prefix-list device_mgt_address-ipv4; <additional match criteria>; } } <additional permit terms> term default { then { log; syslog; discard; } } } } family inet6 { filter protect_re-ipv6 { term 1 { from { source-prefix-list auth_mgt_networks-ipv6; destination-prefix-list device_mgt_address-ipv6; <additional match criteria>; } } <additional permit terms> term default { then { log; syslog; discard; } } } } Note: Additional match criteria includes protocol (next-header for IPv6), source and destination ports, ICMP type and code, etc. When applied to the loopback interface, the filter affects identified traffic regardless of ingress interface. Ensure the filter addresses all traffic destined to the RE like routing protocols, ICMP messages, SSH and SCP traffic, SNMP, etc. Verify filters are applied to loopback, all L3 interfaces, or both. For example: [edit interfaces] lo0 { unit 0 { family inet { filter { input protect_re-ipv4; } address <IPv4 address>/32; } family inet6 { filter { input protect_re-ipv6; } address <IPv6 address>/32; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured with a receive-path filter to restrict traffic destined to itself, this is a finding. Note: If the platform does not support the receive path filter, verify that all layer 3 interfaces have an ingress firewall filter to control what packets are allowed to be destined to the router for processing.
Fix: F-57413r844062_fix
Configure all routers with receive path filters to restrict traffic destined to the router. Example prefix lists for management networks and the device management address(es): set prefix-list auth_mgt_networks-ipv4 <IPv4 subnet / mask> set prefix-list auth_mgt_networks-ipv6 <IPv6 subnet / mask> set prefix-list device_mgt_address-ipv4 <IPv4 address>/32 set prefix-list device_mgt_address-ipv6 <IPv6 address>/128 Example firewall filters: set firewall family inet filter protect_re-ipv4 term 1 from source-prefix-list auth_mgt_networks-ipv4 set firewall family inet filter protect_re-ipv4 term 1 from destination-prefix-list device_mgt_address-ipv4 set firewall family inet filter protect_re-ipv4 term 1 from <additional match criteria> set firewall family inet filter protect_re-ipv4 term 1 then accept set firewall family inet filter protect_re-ipv4 term <additional permit terms> set firewall family inet filter protect_re-ipv4 term default then log set firewall family inet filter protect_re-ipv4 term default then syslog set firewall family inet filter protect_re-ipv4 term default then discard set firewall family inet6 filter protect_re-ipv6 term 1 from source-prefix-list auth_mgt_networks-ipv6 set firewall family inet6 filter protect_re-ipv6 term 1 from destination-prefix-list device_mgt_address-ipv6 set firewall family inet6 filter protect_re-ipv6 term 1 from <additional match criteria> set firewall family inet6 filter protect_re-ipv6 term 1 then accept set firewall family inet6 filter protect_re-ipv6 term <additional permit terms> set firewall family inet6 filter protect_re-ipv6 term default then log set firewall family inet filter protect_re-ipv6 term default then syslog set firewall family inet filter protect_re-ipv6 term default then discard Example application on loopback: set interfaces lo0 unit 0 family inet filter input protect_re-ipv4 set interfaces lo0 unit 0 family inet address <IPv4 address>/32 set interfaces lo0 unit 0 family inet6 filter input protect_re-ipv6 set interfaces lo0 unit 0 family inet6 address <IPv6 address>/128
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000390
- Vuln IDs
-
- V-254011
- Rule IDs
-
- SV-254011r997525_rule
Checks: C-57463r844064_chk
Review the firewall filter for the router receive path. Firewall filters applied to the loopback interface affects traffic destined for the Route Engine (RE) regardless of ingress interface. Individual firewall filters are also supported on each ingress interface. Note: Verify the firewall filter applied to the loopback interface addresses all traffic destined for the RE (e.g., BGP, OSPF, etc.). Verify that it will drop all fragmented ICMP packets destined to itself. For example: [edit policy-options] prefix-list router-addresses-ipv4 { <interface IPv4 address>/32; <other router interface addresses>; } [edit firewall family inet] filter protect_re { term 1 { from { destination-prefix-list { router-addresses-ipv4; } is-fragment; protocol icmp; } then { log; syslog; discard; } } <additional terms for RE destined traffic> } [edit interfaces lo0 unit 0] family inet { filter { input protect_re; } address <IPv4 address>/32; } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured with a receive-path filter to drop all fragmented ICMP packets, this is a finding. Note: If the platform does not support the receive path filter, verify that all layer 3 interfaces have an ingress filter to control what packets are allowed to be destined to the router for processing.
Fix: F-57414r844065_fix
Ensure all routers have their receive path filter configured to drop all fragmented ICMP packets. set policy-options prefix-list router-addresses-ipv4 <interface IPv4 address>/32 set firewall family inet filter protect_re term 1 from destination-prefix-list router-addresses-ipv4 set firewall family inet filter protect_re term 1 from protocol icmp set firewall family inet filter protect_re term 1 from is-fragment set firewall family inet filter protect_re term 1 then log set firewall family inet filter protect_re term 1 then syslog set firewall family inet filter protect_re term 1 then discard <additional terms to account for all traffic destined for the RE> set interfaces lo0 unit 0 family inet filter input protect_re
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000400
- Vuln IDs
-
- V-254012
- Rule IDs
-
- SV-254012r844069_rule
Checks: C-57464r844067_chk
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. For example, assuming TCP 80 and 443 are permitted inbound: [edit policy-options] prefix-list inside-addresses-ipv4 { <interior IPv4 subnet / mask>; } prefix-list inside-addresses-ipv4 { <interior IPv6 subnet / prefix>; } [edit firewall] family inet { filter inbound-ipv4 { term 1 { from { destination-prefix-list inside-addresses-ipv4; protocol tcp; destination-port [ 80 443 ]; } then accept; } <other terms as required> term default-deny { then { log; syslog; discard; } } } } family inet6 { filter inbound-ipv6 { term 1 { from { destination-prefix-list inside-addresses-ipv6; next-header tcp; destination-port [ 80 443 ]; } then accept; } <other terms as required> term default-deny { then { log; syslog; discard; } } } } If the router does not filter traffic in accordance with the guidelines contained in DoD 8551, this is a finding.
Fix: F-57415r844068_fix
This requirement is not applicable for the DODIN Backbone. Configure the router to use ingress firewall filters to restrict traffic in accordance with the guidelines contained in DOD Instruction 8551.1 for all services and protocols required for operational commitments. set policy-options prefix-list inside-addresses-ipv4 <IPv4 subnet>/<mask> <additional subnets as required> set policy-options prefix-list inside-addresses-ipv6 <IPv6 subnet>/<prefix> <additional subnets as required> set firewall family inet filter inbound-ipv4 term 1 from destination-prefix-list inside-addresses-ipv4 set firewall family inet filter inbound-ipv4 term 1 from protocol tcp set firewall family inet filter inbound-ipv4 term 1 from destination-port 80 set firewall family inet filter inbound-ipv4 term 1 from destination-port 443 set firewall family inet filter inbound-ipv4 term 1 then accept <additional terms as required> set firewall family inet filter inbound-ipv4 term default-deny then log set firewall family inet filter inbound-ipv4 term default-deny then syslog set firewall family inet filter inbound-ipv4 term default-deny then discard set firewall family inet6 filter inbound-ipv6 term 1 from destination-prefix-list inside-addresses-ipv6 set firewall family inet6 filter inbound-ipv6 term 1 from next-header tcp set firewall family inet6 filter inbound-ipv6 term 1 from destination-port 80 set firewall family inet6 filter inbound-ipv6 term 1 from destination-port 443 set firewall family inet6 filter inbound-ipv6 term 1 then accept set firewall family inet6 filter inbound-ipv6 term default-deny then log set firewall family inet6 filter inbound-ipv6 term default-deny then syslog set firewall family inet6 filter inbound-ipv6 term default-deny then discard
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000410
- Vuln IDs
-
- V-254013
- Rule IDs
-
- SV-254013r844072_rule
Checks: C-57465r844070_chk
This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify that the ingress firewall filter is bound to the external interface in an inbound direction. [edit interfaces] <external interface> { unit <number> { family inet { filter { input inbound-ipv4; } } family inet6 { filter { input inbound-ipv6; } } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured to filter traffic entering the network at the external interface in an inbound direction, this is a finding.
Fix: F-57416r844071_fix
This requirement is not applicable for the DODIN Backbone. Bind the ingress firewall filter to the external interface (inbound). set interfaces <external interface name> unit <number> family inet filter input inbound-ipv4 set interfaces <external interface name> unit <number> family inet6 filter input inbound-ipv6
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000420
- Vuln IDs
-
- V-254014
- Rule IDs
-
- SV-254014r844075_rule
Checks: C-57466r844073_chk
This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify that the egress firewall filter is bound to the internal interface in an inbound direction. [edit interfaces] <internal interface> { unit <number> { family inet { filter { input outbound-ipv4; } } family inet6 { filter { input outbound-ipv6; } } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output' change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured to filter traffic leaving the network at the internal interface in an inbound direction, this is a finding.
Fix: F-57417r844074_fix
This requirement is not applicable for the DODIN Backbone. Configure an egress firewall filter bound to the internal interface in an inbound direction to filter traffic leaving the network. set interfaces <internal interface name> unit <number> family inet filter input outbound-ipv4 set interfaces <internal interface name> unit <number> family inet6 filter input outbound-ipv6
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000430
- Vuln IDs
-
- V-254015
- Rule IDs
-
- SV-254015r844078_rule
Checks: C-57467r844076_chk
Review the BGP router configuration to verify that there is a filter defined to block route advertisements for prefixes that belong to the IP core. Verify an appropriate prefix-list containing the IP core prefixes is referenced in a policy-statement. For example: [edit policy-options] prefix-list ip-core-ipv4 { 192.0.2.0/24; } prefix-list ip-core-ipv6 { 2001:db8:2::/64; } policy-statement advertise-bgp-prefix { term exclude-ipv4-core { from { prefix-list ip-core-ipv4; } then reject; } term exclude-ipv6-core { from { prefix-list ip-core-ipv6; } then reject; } term default { then accept; } } The prefix filter must be referenced outbound on the appropriate BGP neighbor statements. For example: [edit protocols] bgp { group eBGP { type external; export advertise-bgp-prefix; neighbor 192.0.2.11 { export advertise-bgp-prefix; } } export advertise-bgp-prefix; } Note: Juniper routers support global, group, and neighbor export statements with the more specific definition taking precedence. Ensure more specific export policies (e.g., neighbor and group) do not reverse higher level export statements. If the router is not configured to reject outbound route advertisements that belong to the IP core, this is a finding.
Fix: F-57418r844077_fix
Configure all eBGP routers to filter outbound route advertisements belonging to the IP core. For example: set policy-options prefix-list ip-core-ipv4 192.0.2.0/24 set policy-options prefix-list ip-core-ipv6 2001:db8:2::/64 set policy-options policy-statement advertise-bgp-prefix term exclude-ipv4-core from prefix-list ip-core-ipv4 set policy-options policy-statement advertise-bgp-prefix term exclude-ipv4-core then reject set policy-options policy-statement advertise-bgp-prefix term exclude-ipv6-core from prefix-list ip-core-ipv6 set policy-options policy-statement advertise-bgp-prefix term exclude-ipv6-core then reject set policy-options policy-statement advertise-bgp-prefix term default then accept set protocols bgp group eBGP type external set protocols bgp group eBGP export advertise-bgp-prefix set protocols bgp group eBGP neighbor 192.0.2.11 export advertise-bgp-prefix set protocols bgp export advertise-bgp-prefix
- RMF Control
- SC-7
- Severity
- High
- CCI
- CCI-001097
- Version
- JUEX-RT-000440
- Vuln IDs
-
- V-254016
- Rule IDs
-
- SV-254016r997526_rule
Checks: C-57468r844079_chk
Review the PE router configuration to verify that an ingress firewall filter is applied to all CE-facing interfaces. Verify that the ingress firewall filter rejects and logs packets destined to the IP core address block. For example: [edit policy-options] prefix-list ipv4-core { 192.0.2.0/24; } prefix-list ipv6-core { 2001:db8:2::/64; } [edit firewall] family inet { filter deny-core-ipv4 { term 1 { from { destination-prefix-list { ipv4-core; } } then { log; syslog; discard; } } term default { then accept; } } } family inet6 { filter deny-core-ipv6 { term 1 { from { destination-prefix-list { ipv6-core; } } then { log; syslog; discard; } } term default { then accept; } } } Verify the firewall filter is applied to CE-facing interfaces: [edit interfaces] ge-0/0/0 { unit 0 { family inet { filter { input deny-core-ipv4; } address <IPv4 address/mask>; } family inet6 { filter { input deny-core-ipv6; } address <IPv6 address/prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; 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 peers.
Fix: F-57419r844080_fix
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 appropriate prefix lists and firewall filters. For example: set policy-options prefix-list ipv4-core 192.0.2.0/24 set policy-options prefix-list ipv6-core 2001:db8:2::/64 set firewall family inet filter deny-core-ipv4 term 1 from destination-prefix-list ipv4-core set firewall family inet filter deny-core-ipv4 term 1 then log set firewall family inet filter deny-core-ipv4 term 1 then syslog set firewall family inet filter deny-core-ipv4 term 1 then discard set firewall family inet filter deny-core-ipv4 term default then accept set firewall family inet6 filter deny-core-ipv6 term 1 from destination-prefix-list ipv6-core set firewall family inet6 filter deny-core-ipv6 term 1 then log set firewall family inet6 filter deny-core-ipv6 term 1 then syslog set firewall family inet6 filter deny-core-ipv6 term 1 then discard set firewall family inet6 filter deny-core-ipv6 term default then accept Configure the appropriate interfaces with the firewall filter. For example: [edit interfaces] set interfaces ge-0/0/0 unit 0 family inet filter input deny-core-ipv4 set interfaces ge-0/0/0 unit 0 family inet address <IPv4 address/mask> set interfaces ge-0/0/0 unit 0 family inet6 filter input deny-core-ipv6 set interfaces ge-0/0/0 unit 0 family inet6 address <IPv6 address/prefix>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000450
- Vuln IDs
-
- V-254017
- Rule IDs
-
- SV-254017r997527_rule
Checks: C-57469r844082_chk
Review the PE router configuration to determine if uRPF loose mode is enabled on all CE-facing interfaces. [edit interfaces] ge-0/0/12 { unit 0 { family inet { rpf-check { mode loose; } address <IPv4 address>/<mask>; } family inet6 { rpf-check { mode loose; } address <IPv6 address>/<prefix>; } } } For those platforms that do not support uRPF, verify an ingress stateless firewall filter is applied to all CE-facing interfaces. Because the prefixes assigned to each customer is known, verify each customer's prefix list contains only their prefixes and is referenced in an appropriate firewall filter. For example: [edit policy-options] prefix-list cust1-prefixes-ipv4 { 192.0.2.0/24; } prefix-list cust1-prefixes-ipv6 { 2001:db8:2::/64; } [edit firewall] family inet { filter cust1-prefixes-ipv4 { term 1 { from { source-prefix-list { cust1-prefixes-ipv4; } } then accept; } term default { then { log; syslog; discard; } } } } family inet6 { filter cust1-prefixes-ipv6 { term 1 { from { source-prefix-list { cust1-prefixes-ipv6; } } then accept; } term default { then { log; syslog; discard; } } } } Verify the appropriate filter is applied to each CE-facing interface. For example: [edit interfaces] ge-0/0/0 { unit 0 { family inet { filter { input cust1-prefixes-ipv4; } address <IPv4 address>/<mask>; } family inet6 { filter { input cust1-prefixes-ipv6; } address <IPv6 address>/<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If uRPF or an ingress firewall filter is not enabled on all CE-facing interfaces, this is a finding.
Fix: F-57420r844083_fix
Enable uRPF loose mode or apply an ingress filter on all CE-facing interfaces. For example, configure uRPF on CE-facing interfaces: set interfaces ge-0/0/0 unit 0 family inet rpf-check mode loose set interfaces ge-0/0/0 unit 0 family inet6 rpf-check mode loose For example, configure firewall filter and apply to CE-facing interfaces (only for devices that do not support uRPF): set policy-options prefix-list cust1-prefixes-ipv4 192.0.2.0/24 set policy-options prefix-list cust1-prefixes-ipv6 2001:db8:2::/64 set firewall family inet filter cust1-prefixes-ipv4 term 1 from source-prefix-list cust1-prefixes-ipv4 set firewall family inet filter cust1-prefixes-ipv4 term 1 then accept set firewall family inet filter cust1-prefixes-ipv4 term default then log set firewall family inet filter cust1-prefixes-ipv4 term default then syslog set firewall family inet filter cust1-prefixes-ipv4 term default then discard set firewall family inet6 filter cust1-prefixes-ipv6 term 1 from source-prefix-list cust1-prefixes-ipv6 set firewall family inet6 filter cust1-prefixes-ipv6 term 1 then accept set firewall family inet6 filter cust1-prefixes-ipv6 term default then log set firewall family inet6 filter cust1-prefixes-ipv6 term default then syslog set firewall family inet6 filter cust1-prefixes-ipv6 term default then discard set interfaces ge-0/0/0 unit 0 family inet filter input cust1-prefixes-ipv4 set interfaces ge-0/0/0 unit 0 family inet6 filter input cust1-prefixes-ipv6
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000460
- Vuln IDs
-
- V-254018
- Rule IDs
-
- SV-254018r997528_rule
Checks: C-57470r844085_chk
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. MPLS-based VPN (L2 or L3) must have a working provider MPLS network including routing (for reachability) and Label Switched Paths (LSP). Additionally, the PE router will maintain separation for each CE router in individual routing instances. If using a dedicated circuit, verify the interface transporting NOC traffic is properly connected. CE routers will not peer with PE routers when using L2 VPN. Verify the CE router peers with the appropriate CE router, generally with an IGP (e.g., OSPF), and not the PE router. [edit interfaces] <exterior interface> { unit <number> { family inet { address <IPv4 address>/<mask>; } } } lo0 { unit 0 { family inet { address <IPv4 address>/32; } } } [edit protocols ospf] area <number> { interface lo0.0; interface <exterior interface>.<number>; } CE routers will peer with PE routers, generally with eBGP, when using L3 VPN. Verify the CE router advertises the appropriate interior networks to the PE. [edit interfaces] <exterior interface>:0 { unit <number> { family inet { address <IPv4 address>/<mask>; } } } lo0 { family inet { address <IPv4 address>/<mask>; } } [edit routing-options] router-id <ID>; autonomous-system <AS #>; [edit protocols bgp] group PE1 { type external; export <policy name>; peer-as <peer AS #>; neighbor <neighbor address>; << Reachable from the exterior interface } [edit policy-options policy-statement <statement name>] term 1 { from { protocol <protocol>; << Include the appropriate protocol (e.g., 'direct' for directly connected routes) route-filter <subnet>/<mask> <match condition>; << Include only interior routes that must be advertised to the L3 VPN } then accept; } Note: The policy-statement is applied as an export filter, using a route-filter to limit the exported routes. For example, assume 192.0.2.0/24 is the advertised route, and that it is directly connected. Using "protocol direct" will export all directly-connected routes, but no routes learned via an IGP (e.g., OSPF). Using "route-filter 192.0.2.0/24 orlonger then accept" will accept that /24 (or longer mask) and deny all others. Verify the match condition is appropriate for the desired advertisement. 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.
Fix: F-57421r844086_fix
This requirement is not applicable for the DODIN Backbone. CE peering to CE (L2 VPN): set interfaces <exterior interface> unit <number> family inet address <IPv4 address>/<mask> set interfaces lo0 unit 0 family inet address <IPv4 address>/32 set protocols ospf area <number> interface lo0.0 set protocols ospf area <number> interface <exterior interface> CE peering to PE (L3 VPN): set system host-name ce1 set interfaces <exterior interface>:<number> description "Link from CE1 to PE1 for L3vpn" set interfaces <exterior interface>:<number> unit <number> family inet address <IPv4 address>/<mask> set interfaces lo0 unit 0 family inet address <IPv4 address>/32 set routing-options router-id <ID> set routing-options autonomous-system <AS #> set protocols bgp group <name> type external set protocols bgp group <name> export <policy name> set protocols bgp group <name> peer-as <Peer AS #> set protocols bgp group <name> neighbor <neighbor address> set policy-options policy-statement <policy name> term 1 from protocol <protocol> set policy-options policy-statement <policy name> term 1 from route-filter <subnet> <match criterion> set policy-options policy-statement <policy name> term 1 then accept Ensure that a dedicated circuit, MPLS/VPN service, or IPsec tunnel is deployed to transport management traffic between the managed network and the NOC.
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000470
- Vuln IDs
-
- V-254019
- Rule IDs
-
- SV-254019r844090_rule
Checks: C-57471r844088_chk
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. Verify the destination address is configured either via a prefix-list or directly assigned addresses in each firewall filter term match condition. [edit policy-options] prefix-list NOC-ipv4 { <IPv4 address>/<mask>; } prefix-list NOC-ipv6 { <IPv6 address>/<prefix>; } [edit firewall] family inet { filter permit-NOC-ipv4 { term 1 { from { destination-prefix-list { NOC-ipv4; } protocol <protocol>; destination-port [ <port 1> <port 2> ]; } then accept; } <additional permitted traffic terms> term default { then { log; syslog; discard; } } } } family inet6 { filter permit-NOC-ipv6 { term 1 { from { destination-prefix-list { NOC-ipv6; } next-header <protocol>; destination-port [ <port 1> <port 2> ]; } then accept; } <additional permitted traffic terms> term default { then { log; syslog; discard; } } } } [edit interfaces] <OOBM interface> { unit <number> { family inet { filter { output NOC-ipv4; } address <IPv4 address>/<mask>; } family inet6 { filter { output NOC-ipv6; } address <IPv6 address>/<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If using an IPsec tunnel, verify the route with the tunnel interface as the next-hop destination. [edit routing-options] rib inet6.0 { static { route <NOC IPv6 network> next-hop <(tunnel interface | NOC IPv6 tunnel endpoint address)>; } } static { route <NOC IPv4 network> next-hop <(tunnel interface | NOC IPv6 tunnel endpoint address)>; } If traffic other than authorized management traffic is permitted through the OOBM interface or IPsec tunnel, this is a finding.
Fix: F-57422r844089_fix
Configure appropriate prefix lists and firewall filters. For example: set policy-options prefix-list NOC-ipv4 <IPv4 network>/<mask> set policy-options prefix-list NOC-ipv6 <IPv6 network>/<prefix> set firewall family inet filter permit-NOC-ipv4 term 1 from destination-prefix-list NOC-ipv4 set firewall family inet filter permit-NOC-ipv4 term 1 from protocol <protocol> set firewall family inet filter permit-NOC-ipv4 term 1 from destination-port [ <port 1> <port 2> ] set firewall family inet filter permit-NOC-ipv4 term 1 then accept <additional permit terms> set firewall family inet filter permit-NOC-ipv4 term default then log set firewall family inet filter permit-NOC-ipv4 term default then syslog set firewall family inet filter permit-NOC-ipv4 term default then discard set firewall family inet6 filter permit-NOC-ipv6 term 1 from destination-prefix-list NOC-ipv6 set firewall family inet6 filter permit-NOC-ipv6 term 1 from next-header <protocol> set firewall family inet6 filter permit-NOC-ipv6 term 1 from destination-port [ <port 1> <port 2> ] set firewall family inet6 filter permit-NOC-ipv6 term 1 then accept <additional permit terms> set firewall family inet6 filter permit-NOC-ipv6 term default then log set firewall family inet6 filter permit-NOC-ipv6 term default then syslog set firewall family inet6 filter permit-NOC-ipv6 term default then discard Apply firewall filter to OOBM interface: set interfaces <OOBM interface> unit <number> family inet filter output NOC-ipv4 set interfaces <OOBM interface> unit <number> family inet address <IPv4 address>/<mask> set interfaces <OOBM interface> unit <number> family inet6 filter output NOC-ipv6 set interfaces <OOBM interface> unit <number> family inet6 address <IPv6 address>/<prefix> If using IPsec tunnel: set rib inet6.0 static route <NOC IPv6 network> next-hop <(tunnel interface | NOC IPv6 tunnel endpoint address)> set static route <NOC IPv4 network> next-hop <(tunnel interface | NOC IPv4 tunnel endpoint address)>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000480
- Vuln IDs
-
- V-254020
- Rule IDs
-
- SV-254020r844093_rule
Checks: C-57472r844091_chk
This requirement is not applicable for the DODIN Backbone. Review the firewall filter for the router receive path. Verify that only traffic sourced from the OOBM network or the NOC is allowed to access the router. [edit policy-options] prefix-list OOBM-ipv4 { <IPv4 address>/<mask>; } prefix-list OOBM-ipv6 { <IPv6 address>/<prefix>; } prefix-list router-ipv4 { <IPv4 address>/<mask>; } prefix-list router-ipv6 { <IPv6 address>/<prefix>; } [edit firewall] family inet { filter protect-re-ipv4 { term 1 { from { source-prefix-list OOBM-ipv4; destination-prefix-list router-ipv4; } then accept; } <additional terms for authorized traffic like OSPF or BGP> term default { then { log; syslog; discard; } } } } family inet6 { filter protect-re-ipv6 { term 1 { from { source-prefix-list OOBM-ipv6; destination-prefix-list router-ipv6; } then accept { } <additional terms for authorized traffic like OSPF or BGP> term default { then { log; syslog; discard; } } } } Verify the firewall filter is applied to the loopback interface. [edit interfaces] lo0 { unit 0 { family inet { filter { input protect-re-ipv4; } address <IPv4 address/mask>; } family inet6 { filter { input protect-re-ipv6; } address <IPv6 address/prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; 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. Note: If the platform does not support the receive path filter, verify that all non-OOBM interfaces have an ingress firewall filter to restrict access to that interface address or any of the router’s loopback addresses to only traffic sourced from the management network. An exception would be to allow packets destined to these interfaces used for troubleshooting, such as ping and traceroute.
Fix: F-57423r844092_fix
This requirement is not applicable for the DODIN Backbone. Ensure that traffic from the managed network is not able to access the OOBM gateway router using either receive path or interface firewall filters. set policy-options prefix-list OOBM-ipv4 <IPv4 address>/<mask> set policy-options prefix-list OOBM-ipv6 <IPv6 address>/<prefix> set firewall family inet filter protect-re-ipv4 term 1 from source-prefix-list OOBM-ipv4 set firewall family inet filter protect-re-ipv4 term 1 from destination-prefix-list router-ipv4 set firewall family inet filter protect-re-ipv4 term 1 then accept <additional terms for authorized traffic like OSPF or BGP> set firewall family inet filter protect-re-ipv4 term default then log set firewall family inet filter protect-re-ipv4 term default then syslog set firewall family inet filter protect-re-ipv4 term default then discard set firewall family inet filter protect-re-ipv6 term 1 from source-prefix-list OOBM-ipv6 set firewall family inet filter protect-re-ipv6 term 1 from destination-prefix-list router-ipv6 set firewall family inet filter protect-re-ipv6 term 1 then accept <additional terms for authorized traffic like OSPF or BGP> set firewall family inet filter protect-re-ipv6 term default then log set firewall family inet filter protect-re-ipv6 term default then syslog set firewall family inet filter protect-re-ipv6 term default then discard set interfaces lo0 unit 0 family inet filter input protect-re-ipv4 set interfaces lo0 unit 0 family inet address <IPv4 address>/<mask> set interfaces lo0 unit 0 family inet6 filter input protect-re-ipv6 set interfaces lo0 unit 0 family inet6 address <IPv6 address>/<prefix>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000490
- Vuln IDs
-
- V-254021
- Rule IDs
-
- SV-254021r997529_rule
Checks: C-57473r844094_chk
Verify that the managed interface has an inbound and outbound firewall filter configured. In this example, the firewall filter uses prefix-lists rather than directly embedding the addresses in the filter term. Verify that the ingress filter only allows management, IGP, and ICMP traffic. Caveat: If the management interface is a true OOBM interface, this requirement is not applicable. [edit policy-options] prefix-list OOBM-ipv4 { 192.0.2.0/24; } prefix-list OOBM-ipv6 { 2001:db8:2::/64; } [edit firewall] family inet { filter inbound-OOBM-ipv4 { term 1 { from { source-prefix-list { OOBM-ipv4; } protocol [ icmp ospf ]; } then accept; } term 2 { from { source-prefix-list { OOBM-ipv4; } protocol tcp; destination-port ssh; } then accept; } <additional permit terms> term default { then { log; syslog; discard; } } } filter outbound-OOBM-ipv4 { term 1 { from { destination-prefix-list { OOBM-ipv4; } protocol [ icmp ospf ]; } then accept; } term 2 { from { destination-prefix-list { OOBM-ipv4; } protocol tcp; source-port ssh; } then accept; } <additional permit terms> term default { then { log; syslog; discard; } } } } family inet6 { filter inbound-OOBM-ipv6 { term 1 { from { source-prefix-list { OOBM-ipv6; } next-header [ icmp6 ospf ]; } then accept; } term 2 { from { source-prefix-list { OOBM-ipv6; } next-header tcp; destination-port ssh; } then accept; } <additional permit terms> term default { then { log; syslog; discard; } } } filter outbound-OOBM-ipv6 { term 1 { from { destination-prefix-list { OOBM-ipv6; } next-header [ icmp6 ospf ]; } then accept; } term 2 { from { destination-prefix-list { OOBM-ipv6; } next-header tcp; source-port ssh; } then accept; } <additional permit terms> term default { then { log; syslog; discard; } } } } If no true OOBM interface is available, verify the OOBM firewall filter is applied to the revenue interface configured for OOBM use. <revenue OOBM interface> { unit <number> { family inet { filter { input inbound-OOBM-ipv4; output outbound-OOBM-ipv4; } address <IPv4 address>/<mask>; } family inet6 { filter { input inbound-OOBM-ipv6; output outbound-OOBM-ipv6; } address <IPv6 address>/<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router does not restrict traffic that ingresses and egresses the management interface, this is a finding.
Fix: F-57424r844095_fix
If the management interface is a routed interface, it must be configured with both an ingress and egress ACL. set policy-options prefix-list OOBM-ipv4 192.0.2.0/24 set policy-options prefix-list OOBM-ipv6 2001:db8:2::/64 set firewall family inet filter inbound-OOBM-ipv4 term 1 from source-prefix-list OOBM-ipv4 set firewall family inet filter inbound-OOBM-ipv4 term 1 from protocol icmp set firewall family inet filter inbound-OOBM-ipv4 term 1 from protocol ospf set firewall family inet filter inbound-OOBM-ipv4 term 1 then accept set firewall family inet filter inbound-OOBM-ipv4 term 2 from source-prefix-list OOBM-ipv4 set firewall family inet filter inbound-OOBM-ipv4 term 2 from protocol tcp set firewall family inet filter inbound-OOBM-ipv4 term 2 from destination-port ssh set firewall family inet filter inbound-OOBM-ipv4 term 2 then accept <additional accept terms> set firewall family inet filter inbound-OOBM-ipv4 term default then log set firewall family inet filter inbound-OOBM-ipv4 term default then syslog set firewall family inet filter inbound-OOBM-ipv4 term default then discard set firewall family inet filter outbound-OOBM-ipv4 term 1 from destination-prefix-list OOBM-ipv4 set firewall family inet filter outbound-OOBM-ipv4 term 1 from protocol icmp set firewall family inet filter outbound-OOBM-ipv4 term 1 from protocol ospf set firewall family inet filter outbound-OOBM-ipv4 term 1 then accept set firewall family inet filter outbound-OOBM-ipv4 term 2 from destination-prefix-list OOBM-ipv4 set firewall family inet filter outbound-OOBM-ipv4 term 2 from protocol tcp set firewall family inet filter outbound-OOBM-ipv4 term 2 from source-port ssh set firewall family inet filter outbound-OOBM-ipv4 term 2 then accept <additional accept terms> set firewall family inet filter outbound-OOBM-ipv4 term default then log set firewall family inet filter outbound-OOBM-ipv4 term default then syslog set firewall family inet filter outbound-OOBM-ipv4 term default then discard set firewall family inet filter inbound-OOBM-ipv6 term 1 from source-prefix-list OOBM-ipv6 set firewall family inet filter inbound-OOBM-ipv6 term 1 from next-header icmp6 set firewall family inet filter inbound-OOBM-ipv6 term 1 from next-header ospf set firewall family inet filter inbound-OOBM-ipv6 term 1 then accept set firewall family inet filter inbound-OOBM-ipv6 term 2 from source-prefix-list OOBM-ipv6 set firewall family inet filter inbound-OOBM-ipv6 term 2 from next-header tcp set firewall family inet filter inbound-OOBM-ipv6 term 2 from destination-port ssh set firewall family inet filter inbound-OOBM-ipv6 term 2 then accept <additional accept terms> set firewall family inet filter inbound-OOBM-ipv6 term default then log set firewall family inet filter inbound-OOBM-ipv6 term default then syslog set firewall family inet filter inbound-OOBM-ipv6 term default then discard set firewall family inet6 filter outbound-OOBM-ipv6 term 1 from destination-prefix-list OOBM-ipv6 set firewall family inet6 filter outbound-OOBM-ipv6 term 1 from next-header icmp6 set firewall family inet6 filter outbound-OOBM-ipv6 term 1 from next-header ospf set firewall family inet6 filter outbound-OOBM-ipv6 term 1 then accept set firewall family inet6 filter outbound-OOBM-ipv6 term 2 from destination-prefix-list OOBM-ipv6 set firewall family inet6 filter outbound-OOBM-ipv6 term 2 from next-header tcp set firewall family inet6 filter outbound-OOBM-ipv6 term 2 from source-port ssh set firewall family inet6 filter outbound-OOBM-ipv6 term 2 then accept <additional accept terms> set firewall family inet6 filter outbound-OOBM-ipv6 term default then log set firewall family inet6 filter outbound-OOBM-ipv6 term default then syslog set firewall family inet6 filter outbound-OOBM-ipv6 term default then discard set interfaces <revenue OOBM> unit <number> family inet filter input inbound-OOBM-ipv4 set interfaces <revenue OOBM> unit <number> family inet filter output outbound-OOBM-ipv4 set interfaces <revenue OOBM> unit <number> family inet <IPv4 address>/<mask> set interfaces <revenue OOBM> unit <number> family inet6 filter input inbound-OOBM-ipv6 set interfaces <revenue OOBM> unit <number> family inet6 filter output outbound-OOBM-ipv6 set interfaces <revenue OOBM> unit <number> family inet6 <IPv6 address>/<prefix>
- RMF Control
- SC-5
- Severity
- High
- CCI
- CCI-001094
- Version
- JUEX-RT-000500
- Vuln IDs
-
- V-254022
- Rule IDs
-
- SV-254022r997530_rule
Checks: C-57474r844097_chk
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. [edit interfaces] <internal interface name> { unit <number> { family inet { rpf-check; address <IPv4 address>/<mask>; } family inet6 { rpf-check; address <IPv6 address>/<prefix>; } } } For those platforms that do not support uRPF, verify an egress stateless firewall filter is applied to all internal interfaces. In this example, the egress (from the enclave) filter is applied in the input direction of internal interfaces to prevent the router from accepting packets sourced from any address except the internal subnets. For example: [edit policy-options] prefix-list internal-prefixes-ipv4 { 192.0.2.0/24; } prefix-list internal-prefixes-ipv6 { 2001:0:2::/64; } [edit firewall] family inet { filter internal-inbound-ipv4 { term 1 { from { source-prefix-list { internal-prefixes-ipv4; } } then accept; } term default { then { log; syslog; discard; } } } } family inet6 { filter internal-inbound-ipv6 { term 1 { from { source-prefix-list { internal-prefixes-ipv6; } } then accept; } term default { then { log; syslog; discard; } } } } Verify the appropriate filter is applied to each internal interface. For example: [edit interfaces] <internal interface name> { unit <number> { family inet { filter { input internal-inbound-ipv4; } address <IPv4 address>/<mask>; } family inet6 { filter { input internal-inbound-ipv6; } address <IPv6 address>/<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; 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, this is a finding.
Fix: F-57425r844098_fix
This requirement is not applicable for the DODIN Backbone. Configure the router to ensure that an egress filter or uRPF is configured to restrict the router from accepting any outbound IP packet that contains an external IP address in the source field. set interfaces <internal interface name> unit <number> family inet rpf-check set interfaces <internal interface name> unit <number> family inet6 rpf-check For example, configure firewall filter and apply to internal interfaces: set policy-options prefix-list internal-prefixes-ipv4 192.0.2.0/24 set policy-options prefix-list internal-prefixes-ipv6 2001:0:2::/64 set firewall family inet filter internal-inbound-ipv4 term 1 from source-prefix-list internal-prefixes-ipv4 set firewall family inet filter internal-inbound-ipv4 term 1 then accept set firewall family inet filter internal-inbound-ipv4 term default then log set firewall family inet filter internal-inbound-ipv4 term default then syslog set firewall family inet filter internal-inbound-ipv4 term default then discard set firewall family inet6 filter internal-inbound-ipv6 term 1 from source-prefix-list internal-prefixes-ipv6 set firewall family inet6 filter internal-inbound-ipv6 term 1 then accept set firewall family inet6 filter internal-inbound-ipv6 term default then log set firewall family inet6 filter internal-inbound-ipv6 term default then syslog set firewall family inet6 filter internal-inbound-ipv6 term default then discard set interfaces ge-0/0/0 unit 0 family inet filter input internal-inbound-ipv4 set interfaces ge-0/0/0 unit 0 family inet6 filter input internal-inbound-ipv6
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000510
- Vuln IDs
-
- V-254023
- Rule IDs
-
- SV-254023r997531_rule
Checks: C-57475r844100_chk
This requirement is not applicable for the DODIN Backbone. Review the router configuration to determine if it will block all packets with IP options. [edit firewall family inet] filter <name> { term 1 { from { ip-options any; } then { log; syslog; discard; } } <additional accept terms> term default { then { log; syslog; discard; } } } [edit interfaces] <interface name> { unit <number> { family inet { filter input <filter name>; address <IPv4 address>/<mask>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured to drop all packets with IP options, this is a finding.
Fix: F-57426r844101_fix
This requirement is not applicable for the DODIN Backbone. Configure the router to drop all packets with IP options. set firewall family inet filter <filter name> term 1 from ip-options any set firewall family inet filter <filter name> term 1 then log set firewall family inet filter <filter name> term 1 then syslog set firewall family inet filter <filter name> term 1 then discard <additional accept terms> set firewall family inet filter default term 1 then log set firewall family inet filter default term 1 then syslog set firewall family inet filter default term 1 then discard set interfaces <interface name> unit <number> family inet filter input <filter name> set interfaces <interface name> unit <number> family inet address <IPv4 address>/<mask>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000520
- Vuln IDs
-
- V-254024
- Rule IDs
-
- SV-254024r997532_rule
Checks: C-57476r844103_chk
Review the router configuration to determine if it will block all packets with IP options. [edit firewall family inet] filter <name> { term 1 { from { ip-options any; } then { log; syslog; discard; } } <additional accept terms> term default { then { log; syslog; discard; } } } [edit interfaces] <interface name> { unit <number> { family inet { filter input <filter name>; address <IPv4 address>/<mask>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured to drop all packets with IP options, this is a finding.
Fix: F-57427r844104_fix
Configure the router to drop all packets with IP options. set firewall family inet filter <filter name> term 1 from ip-options any set firewall family inet filter <filter name> term 1 then log set firewall family inet filter <filter name> term 1 then syslog set firewall family inet filter <filter name> term 1 then discard <additional accept terms> set firewall family inet filter default term 1 then log set firewall family inet filter default term 1 then syslog set firewall family inet filter default term 1 then discard set interfaces <interface name> unit <number> family inet filter input <filter name> set interfaces <interface name> unit <number> family inet address <IPv4 address>/<mask>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- JUEX-RT-000530
- Vuln IDs
-
- V-254025
- Rule IDs
-
- SV-254025r945861_rule
Checks: C-57477r844106_chk
Review the router configuration. For every protocol that affects the routing or forwarding tables (where information is exchanged between neighbors), verify that neighbor router authentication is enabled. [edit security ipsec] security-association <sa name> { manual { direction bidirectional { protocol esp; spi <SPI value>; authentication { algorithm hmac-sha-256-128; key ascii-text "$8$aes256-gcm$hmac-sha2-256$100$SpJ/ERRFEsc$y1Wqf1zM3d3xI+ZVB9WzTw$lgM06LJZN3FcVbTaSkDz4g$bZVi57MkUWg"; ## SECRET-DATA } } } } [edit protocols] bgp { group <group name> { type external; local-as <local AS number>; neighbor <neighbor 1 address> { authentication-key "$8$aes256-gcm$hmac-sha2-256$100$cFQ99Gy83Og$SCMVXvnfna7/cZqH9fCECQ$bCVokm+es94xFJONmbKFNA$4561Uc/r"; ## SECRET-DATA } neighbor <neighbor 2 address> { ipsec-sa <SA name>; } } } Note: Juniper BGP routers support either an MD5 key, rotating MD5 keys, or an IPsec security association (SA). Verify the PSK for each MD5 and SA is different between all neighbors. ospf { area <area number> { interface <interface name>.<logical unit> { authentication { md5 1 key "$8$aes256-gcm$hmac-sha2-256$100$hvt9Fpk6EEU$I2FKFJNrdKHpp1xesMB0aA$l9BsHxOYO4+B8f7erRj8Hw$A9PYzx53Ius"; ## SECRET-DATA } } interface <interface name>.<logical unit> { interface-type p2p; ipsec-sa <SA name>; } } } Note: Juniper OSPF routers support either an MD5 key or an IPsec SA. ospf3 { area <area number> { interface <interface name>.<logical unit> { ipsec-sa <SA name>; } } } Note: Juniper OSPFv3 routers only support IPsec SA. If authentication is not enabled, this is a finding.
Fix: F-57428r844107_fix
Configure authentication to be enabled for every protocol that affects the routing or forwarding tables. set security ipsec security-association <sa name> manual direction bidirectional protocol esp set security ipsec security-association <sa name> manual direction bidirectional spi <SPI value> set security ipsec security-association <sa name> manual direction bidirectional authentication algorithm hmac-sha-256-128 set security ipsec security-association <sa name> manual direction bidirectional authentication key ascii-text <PSK value> set protocols bgp group <group name> type external set protocols bgp group <group name> local-as <local AS number> set protocols bgp group <group name> neighbor <neighbor 1 address> authentication-key <PSK value> set protocols bgp group <group name> neighbor <neighbor 1 address> ipsec-sa <SA name> set protocols ospf area 0.0.0.1 interface <interface name>.<logical unit> authentication md5 1 key <PSK value> set protocols ospf area 0.0.0.1 interface <interface name>.<logical unit> interface-type p2p set protocols ospf area 0.0.0.1 interface <interface name>.<logical unit> ipsec-sa <SA name>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- JUEX-RT-000540
- Vuln IDs
-
- V-254026
- Rule IDs
-
- SV-254026r945862_rule
Checks: C-57478r844109_chk
Interview the ISSM and router administrator to determine if unique keys are being used. [edit security ipsec] security-association <sa name> { manual { direction bidirectional { protocol esp; spi <SPI value>; authentication { algorithm hmac-sha-256-128; key ascii-text "$8$aes256-gcm$hmac-sha2-256$100$SpJ/ERRFEsc$y1Wqf1zM3d3xI+ZVB9WzTw$lgM06LJZN3FcVbTaSkDz4g$bZVi57MkUWg"; ## SECRET-DATA } } } } [edit protocols bgp] group <group name> { type external; local-as <local AS number>; neighbor <neighbor 1 address> { authentication-key "$8$aes256-gcm$hmac-sha2-256$100$cFQ99Gy83Og$SCMVXvnfna7/cZqH9fCECQ$bCVokm+es94xFJONmbKFNA$4561Uc/r"; ## SECRET-DATA } neighbor <neighbor 2 address> { ipsec-sa <sa name>; } } Note: Juniper BGP routers support either an MD5 key, rotating MD5 keys, or an IPsec security association (SA). Verify the PSK for each MD5 and SA is different between all neighbors. If unique keys are not being used, this is a finding.
Fix: F-57429r844110_fix
Configure all eBGP routers with unique keys for each eBGP neighbor that it peers with. set security ipsec security-association <sa name> manual direction bidirectional protocol esp set security ipsec security-association <sa name> manual direction bidirectional spi <SPI value> set security ipsec security-association <sa name> manual direction bidirectional authentication algorithm hmac-sha-256-128 set security ipsec security-association <sa name> manual direction bidirectional authentication key ascii-text <PSK value> set protocols bgp group <group name> type external set protocols bgp group <group name> local-as <local AS number> set protocols bgp group <group name> neighbor <neighbor 1 address> authentication-key <PSK value> set protocols bgp group <group name> neighbor <neighbor 2 address> ipsec-sa test
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- JUEX-RT-000550
- Vuln IDs
-
- V-254027
- Rule IDs
-
- SV-254027r945863_rule
Checks: C-57479r844112_chk
This requirement is not applicable for the DODIN Backbone. For each authenticated routing protocol session, review the configured key expiration dates. [edit security] authentication-key-chains { key-chain <name> { key 1 { secret "$9$vNbM7Vg4ZjkPJGn/AtOB7-d"; ## SECRET-DATA start-time "2021-1-1.00:00:00 -0700"; algorithm md5; } key 2 { secret "$9$MAQL7VgoGqmTwYmTz3tpWLxNwY4aZjk."; ## SECRET-DATA start-time "2021-5-31.00:00:00 -0700"; algorithm md5; } } } [edit protocols] bgp { group eBGP { authentication-key-chain <name>; neighbor 1.2.3.4 { authentication-key-chain <name>; } } authentication-key-chain <name>; } Note: BGP supports authentication globally, at the group level, and individually for each neighbor. The most specific authentication configuration is applied. ospf { area 0.0.0.2 { interface ge-0/0/0.0 { authentication { md5 0 key "$9$vG08xd24Zk.5bs.5QFAtM8X7bsgoJDHq" start-time "2021-1-1.00:00:00 -0700"; ## SECRET-DATA md5 1 key "$9$m5z6p0IreW9AeWLxwsP5QF9AuO1hyl" start-time "2021-5-31.00:00:00 -0700"; ## SECRET-DATA } } } } If any key has a lifetime of more than 180 days, this is a finding.
Fix: F-57430r844113_fix
This requirement is not applicable for the DODIN Backbone. For each authenticated routing protocol session, configure each key to have a lifetime of no more than 180 days. set security authentication-key-chains key-chain <name> key <number-1> secret <key value> set security authentication-key-chains key-chain <name> key <number-1> start-time <YYYY-MM-DD.HH:MM> set security authentication-key-chains key-chain <name> key <number-1> algorithm md5 set security authentication-key-chains key-chain <name> key <number-2> secret <key value> set security authentication-key-chains key-chain <name> key <number-2> start-time <YYYY-MM-DD.HH:MM> set security authentication-key-chains key-chain <name> key <number-2> algorithm md5 set protocols bgp group <name> authentication-key-chain <name> set protocols bgp group <name> neighbor <neighbor address> authentication-key-chain <name> set protocols bgp authentication-key-chain <name> set protocols ospf area <area number> interface <interface name>.<logical unit> authentication md5 <number> key <key value> set protocols ospf area <area number> interface <interface name>.<logical unit> authentication md5 <number> start-time <YYYY-MM-DD.HH:MM> set protocols ospf area <area number> interface <interface name>.<logical unit> authentication md5 <number> key <key value> set protocols ospf area <area number> interface <interface name>.<logical unit> authentication md5 <number> start-time <YYYY-MM-DD.HH:MM>
- RMF Control
- IA-3
- Severity
- Medium
- CCI
- CCI-001958
- Version
- JUEX-RT-000560
- Vuln IDs
-
- V-254028
- Rule IDs
-
- SV-254028r844260_rule
Checks: C-57480r844115_chk
Review the router configuration to determine if LDP messages are being authenticated for the targeted LDP sessions. [edit protocols] ldp { interface <interface 1 name>.<logical unit>; interface <interface 2 name>.<logical unit>; session <Session destination address> { authentication-algorithm <aes-128-cmac-96|hmac-sha-1-96>; authentication-key-chain <name>; } } If authentication is not being used for the LDP sessions using a FIPS-approved message authentication code algorithm, this is a finding.
Fix: F-57431r844116_fix
Implement authentication for all targeted LDP sessions using a FIPS-approved message authentication code algorithm. set protocols ldp interface <interface 1 name>.<logical unit> set protocols ldp interface <interface 2 name>.<logical unit> set protocols ldp session <Session destination address> authentication-algorithm <aes-128-cmac-96|hmac-sha-1-96> set protocols ldp session <Session destination address> authentication-key-chain <name>
- RMF Control
- IA-3
- Severity
- Medium
- CCI
- CCI-001958
- Version
- JUEX-RT-000570
- Vuln IDs
-
- V-254029
- Rule IDs
-
- SV-254029r844120_rule
Checks: C-57481r844118_chk
Review the router configuration to determine if received MSDP packets are authenticated. [edit protocols] msdp { active-source-limit { maximum <1..1000000>; threshold <1..1000000>; log-warning <percent to log warning>; } <additional configuration> peer <address> { authentication-key "hashed PSK"; ## SECRET-DATA } } If the router does not require MSDP authentication, this is a finding.
Fix: F-57432r844119_fix
Ensure all MSDP packets received by an MSDP router are authenticated. set protocols msdp active-source-limit maximum <1..1000000> set protocols msdp active-source-limit threshold <1..1000000> set protocols msdp active-source-limit log-warning <percent to log warning> <additional configuration> set protocols msdp peer <address> authentication-key <PSK>
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- JUEX-RT-000580
- Vuln IDs
-
- V-254030
- Rule IDs
-
- SV-254030r844123_rule
Checks: C-57482r844121_chk
Review the device configuration to determine if a configuration auto-loading or zero-touch deployment feature is enabled. Verify the Juniper router is not configured with the factory default configuration. The Zero Touch Provisioning (ZTP) feature requires the factory default configuration. Juniper ZTP leverages Dynamic Host Configuration Protocol (DHCP) options to provide not only the interface address, but also the location of the upgrade image and configuration file. Interfaces configured for DHCP will not attempt to establish a ZTP session simply because DHCP is enabled but, instead, also require a factory default configuration. Therefore, if DHCP is authorized, removing the following [edit system] options, setting a root password, and committing will prevent the device from attempting ZTP. Verify the following are removed. [edit system] : : auto-configuration; << Delete this command. phone-home { << Delete this stanza. server <server URL>; rfc-compliant; } If a configuration auto-loading feature or zero-touch deployment feature is enabled, this is a finding. Note: Auto-configuration or zero-touch deployment features can be enabled when the router is offline for the purpose of image loading or building out the configuration. In addition, this would not be applicable to the provisioning of virtual routers via a software-defined network (SDN) orchestration system.
Fix: F-57433r844122_fix
Disable all configuration auto-loading or zero-touch deployment features. delete system auto-configuration delete system phone-home Note: The "phone-home" command is hidden and must be fully typed into the CLI (autocomplete will not work). Configure the router with a nondefault configuration and commit.
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- JUEX-RT-000590
- Vuln IDs
-
- V-254031
- Rule IDs
-
- SV-254031r997533_rule
Checks: C-57483r844124_chk
Determine whether control plane protection has been implemented on the device by verifying traffic types have been classified based on importance levels and a policy has been configured to filter and rate limit the traffic according to each class. Verify firewall filters include policers (rate limiting) based upon importance levels. Although the policer names shown in the example are the bandwidth limit, any legal name can be used. [edit firewall] family inet { filter <name> { term accept-tcp-initial { from { source-prefix-list { management-networks-ipv4; } destination-prefix-list { router-addresses-ipv4; } protocol tcp; destination-port ssh; tcp-initial; } then { policer policer-32k; << Lower rate for connection attempts to help prevent SYN flood attacks. accept; } } term accept-ssh { from { source-prefix-list { management-networks-ipv4; } destination-prefix-list { router-addresses-ipv4; } protocol tcp; destination-port ssh; } then { policer policer-1g; << Higher rate after connection establishment for remote management and/or secure file transfer. accept; } } term accept-snmp { from { source-prefix-list { snmp-servers-ipv4; } destination-prefix-list { router-addresses-ipv4; } protocol udp; destination-port snmp; } then { policer policer-1m; accept; } } <additional terms> term default-deny { then { log; syslog; discard; } } } } family inet6 { filter <name> { term accept-tcp-initial { from { source-prefix-list { management-networks-ipv6; } destination-prefix-list { router-addresses-ipv6; } next-header tcp; destination-port ssh; tcp-initial; } then { policer policer-32k; << Lower rate for connection attempts to help prevent SYN flood attacks. accept; } } term accept-ssh { from { source-prefix-list { management-networks-ipv6; } destination-prefix-list { router-addresses-ipv6; } next-header tcp; destination-port ssh; } then { policer policer-1g; << Higher rate after connection establishment for remote management. accept; } } term accept-snmp { from { source-prefix-list { snmp-servers-ipv6; } destination-prefix-list { router-addresses-ipv6; } next-header udp; destination-port snmp; } then { policer policer-1m; accept; } } <additional terms> term default-deny { then { log; syslog; discard; } } } } Note: Verify the applied filter has terms for all permitted traffic (e.g., OSPF, BGP, etc.). policer policer-1g { if-exceeding { bandwidth-limit 1g; burst-size-limit 100k; } then discard; } policer policer-1m { if-exceeding { bandwidth-limit 1m; burst-size-limit 15k; } then discard; } policer policer-32k { if-exceeding { bandwidth-limit 32k; burst-size-limit 1500; } then discard; } [edit interfaces] lo0 { unit <number> { family inet { filter { input <filter name>; } address <IPv4 address>/32; } family inet6 { filter { input <filter name>; } address <IPv6 address>/128/ } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router does not have control plane protection implemented, this is a finding.
Fix: F-57434r844125_fix
Implement control plane protection by classifying traffic types based on importance and configure filters to restrict and rate limit the traffic directed to and processed by the RE according to each class. set firewall family inet filter <name> term accept-tcp-initial from source-prefix-list management-networks-ipv4 set firewall family inet filter <name> term accept-tcp-initial from destination-prefix-list router-addresses-ipv4 set firewall family inet filter <name> term accept-tcp-initial from protocol tcp set firewall family inet filter <name> term accept-tcp-initial from destination-port ssh set firewall family inet filter <name> term accept-tcp-initial from tcp-initial set firewall family inet filter <name> term accept-tcp-initial then policer policer-32k set firewall family inet filter <name> term accept-tcp-initial then accept set firewall family inet filter <name> term accept-ssh from source-prefix-list management-networks-ipv4 set firewall family inet filter <name> term accept-ssh from destination-prefix-list router-addresses-ipv4 set firewall family inet filter <name> term accept-ssh from protocol tcp set firewall family inet filter <name> term accept-ssh from destination-port ssh set firewall family inet filter <name> term accept-ssh then policer policer-1g set firewall family inet filter <name> term accept-ssh then count accept-ssh set firewall family inet filter <name> term accept-ssh then accept set firewall family inet filter <name> term accept-snmp from source-prefix-list snmp-servers-ipv4 set firewall family inet filter <name> term accept-snmp from destination-prefix-list router-addresses-ipv4 set firewall family inet filter <name> term accept-snmp from protocol udp set firewall family inet filter <name> term accept-snmp from destination-port snmp set firewall family inet filter <name> term accept-snmp then policer policer-1m set firewall family inet filter <name> term accept-snmp then count accept-snmp set firewall family inet filter <name> term accept-snmp then accept <additional terms> set firewall family inet filter <name> term default-deny then log set firewall family inet filter <name> term default-deny then syslog set firewall family inet filter <name> term default-deny then discard set firewall policer policer-1g if-exceeding bandwidth-limit 1g set firewall policer policer-1g burst-size-limit 100k set firewall policer policer-1g then discard set firewall policer policer-1m if-exceeding bandwidth-limit 1m set firewall policer policer-1m burst-size-limit 15k set firewall policer policer-1m then discard set firewall policer policer-32k if-exceeding bandwidth-limit 132k set firewall policer policer-32k burst-size-limit 1500 set firewall policer policer-32k then discard set interfaces lo0 unit <number> family inet filter <name> set interfaces lo0 unit <number> family inet address <IPv4 address>/32 set interfaces lo0 unit <number> family inet6 filter <name> set interfaces lo0 unit <number> family inet6 address <IPv6 address>/128
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- JUEX-RT-000600
- Vuln IDs
-
- V-254032
- Rule IDs
-
- SV-254032r844129_rule
Checks: C-57484r844127_chk
Review the configuration to determine if gratuitous ARP is disabled on all external interfaces. [edit interfaces] <external interface> { no-gratuitous-arp-reply; no-gratuitous-arp-request; unit <number> { family inet { address <IPv4 address>/<mask>; } family inet6 { address <IPv6 address>/<mask>; } } } If gratuitous ARP is enabled on any external interface, this is a finding.
Fix: F-57435r844128_fix
Disable gratuitous ARP on all external interfaces. set interfaces <external interface> no-gratuitous-arp-reply set interfaces <external interface> no-gratuitous-arp-request set interfaces <external interface> unit <number> family inet address <IPv4 address>/<mask> set interfaces <external interface> unit <number> family inet6 address <IPv6 address>/<prefix>
- RMF Control
- SC-5
- Severity
- Low
- CCI
- CCI-002385
- Version
- JUEX-RT-000610
- Vuln IDs
-
- V-254033
- Rule IDs
-
- SV-254033r997534_rule
Checks: C-57485r844130_chk
Review the router configuration to determine if IP directed broadcast is enabled. By default, IP directed broadcast is disabled on all L3 interfaces, including Integrated Routing and Bridging (IRB) interfaces. Verify "targeted-broadcast" is not enabled as shown. [edit interfaces] <L3 interface> { unit <number> { family inet { targeted-broadcast; << Must not be present. address <IPv4 address>/<mask>; } } } irb { unit <number> { family inet { targeted-broadcast; << Must not be present. address <IPv4 address>/<mask>; } } } If IP directed broadcast is enabled on layer 3 interfaces, this is a finding.
Fix: F-57436r844131_fix
Disable IP directed broadcasts on all layer 3 interfaces. delete interfaces <L3 interface> unit <number> family inet targeted-broadcast delete interfaces irb unit <L3 IRB interface> family inet targeted-broadcast
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- JUEX-RT-000620
- Vuln IDs
-
- V-254034
- Rule IDs
-
- SV-254034r844135_rule
Checks: C-57486r844133_chk
Review the device configuration to determine if controls have been defined to ensure the router does not send ICMP unreachable notifications out to any external interfaces. [edit policy-options] prefix-list router-address-ipv4 { <external interface address>/32; <internal subnet>/<mask>; } [edit firewall family inet] filter <name> { term 1 { from { source-prefix-list { router-address-ipv4; } protocol icmp; icmp-type unreachable; } then { log; syslog; discard; } } <additional terms> term default { then { log; syslog; discard; } } } [edit interfaces] <external interface> { unit <number> { family inet { filter { output <filter name>; } address <IPv4 address>/<mask>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If ICMP unreachable notifications are enabled on any external interfaces, this is a finding.
Fix: F-57437r844134_fix
Disable ICMP unreachable notifications on all external interfaces. set policy-options prefix-list router-addresses-ipv4 <external interface address>/32 set policy-options prefix-list router-addresses-ipv4 <internal subnet>/<mask> set firewall family inet filter <name> term 1 from source-prefix-list router-address-ipv4 set firewall family inet filter <name> term 1 from protocol icmp set firewall family inet filter <name> term 1 from icmp-type unreachable set firewall family inet filter <name> term 1 then log set firewall family inet filter <name> term 1 then syslog set firewall family inet filter <name> term 1 then discard <additional terms> set firewall family inet filter <name> term default then log set firewall family inet filter <name> term default then syslog set firewall family inet filter <name> term default then discard set interfaces <interface name> unit <number> family inet filter output <filter name> set interfaces <interface name> unit <number> family inet address <IPv4 address>.<mask>
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- JUEX-RT-000630
- Vuln IDs
-
- V-254035
- Rule IDs
-
- SV-254035r844138_rule
Checks: C-57487r844136_chk
Review the device configuration to determine if controls have been defined to ensure the router does not send ICMP Mask Reply messages out to any external interfaces. [edit policy-options] prefix-list router-address-ipv4 { <external interface address>/32; <internal subnet>/<mask>; } [edit firewall family inet] filter <name> { term 1 { from { source-prefix-list { router-address-ipv4; } protocol icmp; icmp-type mask-reply; } then { log; syslog; discard; } } <additional terms> term default { then { log; syslog; discard; } } } [edit interfaces] <external interface> { unit <number> { family inet { filter { output <filter name>; } address <IPv4 address>/<mask>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If ICMP Mask Reply messages are enabled on any external interfaces, this is a finding.
Fix: F-57438r844137_fix
Disable ICMP mask replies on all external interfaces. set policy-options prefix-list router-addresses-ipv4 <external interface address>/32 set policy-options prefix-list router-addresses-ipv4 <internal subnet>/<mask> set firewall family inet filter <name> term 1 from source-prefix-list router-address-ipv4 set firewall family inet filter <name> term 1 from protocol icmp set firewall family inet filter <name> term 1 from icmp-type mask-reply set firewall family inet filter <name> term 1 then log set firewall family inet filter <name> term 1 then syslog set firewall family inet filter <name> term 1 then discard <additional terms> set firewall family inet filter <name> term default then log set firewall family inet filter <name> term default then syslog set firewall family inet filter <name> term default then discard set interfaces <interface name> unit <number> family inet filter output <filter name> set interfaces <interface name> unit <number> family inet address <IPv4 address>.<mask>
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- JUEX-RT-000640
- Vuln IDs
-
- V-254036
- Rule IDs
-
- SV-254036r844141_rule
Checks: C-57488r844139_chk
Review the device configuration to determine if controls have been defined to ensure the router does not send ICMP Redirect messages out to any external interfaces. Verify the global "no-redirects" statement is enabled under [edit system] or that individual interface "no-redirects" statements are configured on external interfaces. [edit system] no-redirects; [edit interfaces] <external interface name> { unit <number> { family inet { no-redirects; address <IPv4 address>.<mask>; } family inet6 { no-redirects; address <IPv6 address>.<prefix>; } } } If ICMP Redirect messages are enabled on any external interfaces, this is a finding.
Fix: F-57439r844140_fix
Disable ICMP redirects on all external interfaces. set system no-redirects set interfaces <external interface name> unit <number> family inet no-redirects set interfaces <external interface name> unit <number> family inet6 no-redirects
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- JUEX-RT-000650
- Vuln IDs
-
- V-254037
- Rule IDs
-
- SV-254037r844144_rule
Checks: C-57489r844142_chk
Review the router configuration to verify that the number of received prefixes from each eBGP neighbor is controlled. [edit protocols] bgp { group <group name> { type external; local-as <local AS number>; neighbor <neighbor 1 address> { family inet { unicast { prefix-limit { maximum 10; teardown; } } } family inet6 { unicast { prefix-limit { maximum 10; teardown; } } } authentication-key "$8$aes256-gcm$hmac-sha2-256$100$cFQ99Gy83Og$SCMVXvnfna7/cZqH9fCECQ$bCVokm+es94xFJONmbKFNA$4561Uc/r"; ## SECRET-DATA } neighbor <neighbor 2 address> { family inet { unicast { prefix-limit { maximum 10; teardown; } } } family inet6 { unicast { prefix-limit { maximum 10; teardown; } } } ipsec-sa <SA name>; } } } If the router is not configured to control the number of prefixes received from each peer to protect against route table flooding and prefix deaggregation attacks, this is a finding.
Fix: F-57440r844143_fix
Configure all eBGP routers to use the prefix limit feature to protect against route table flooding and prefix deaggregation attacks. set protocols bgp group <group name> type external set protocols bgp group <group name> local-as <local AS number> set protocols bgp group <group name> neighbor <neighbor 1 address> family inet unicast prefix-limit maximum 10 set protocols bgp group <group name> neighbor <neighbor 1 address> family inet unicast prefix-limit teardown set protocols bgp group <group name> neighbor <neighbor 1 address> family inet6 unicast prefix-limit maximum 10 set protocols bgp group <group name> neighbor <neighbor 1 address> family inet6 unicast prefix-limit teardown set protocols bgp group <group name> neighbor <neighbor 1 address> authentication-key <PSK value> set protocols bgp group <group name> neighbor <neighbor 2 address> family inet unicast prefix-limit maximum 10 set protocols bgp group <group name> neighbor <neighbor 2 address> family inet unicast prefix-limit teardown set protocols bgp group <group name> neighbor <neighbor 2 address> family inet6 unicast prefix-limit maximum 10 set protocols bgp group <group name> neighbor <neighbor 2 address> family inet6 unicast prefix-limit teardown set protocols bgp group <group name> neighbor <neighbor 2 address> ipsec-sa <SA name>
- RMF Control
- SC-5
- Severity
- Low
- CCI
- CCI-002385
- Version
- JUEX-RT-000660
- Vuln IDs
-
- V-254038
- Rule IDs
-
- SV-254038r844147_rule
Checks: C-57490r844145_chk
This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify that there is a filter to reject inbound route advertisements that are greater than /24, or the least significant prefixes issued to the customer, whichever is larger. Verify each BGP neighbor implements an import policy. BGP import policies are supported in three locations: Global (at [edit protocols bgp]), group (at [edit protocols bgp group <name>]), and for each neighbor (at [edit protocols bgp group <name> neighbor <neighbor address>]) with the most specific import statement being applied. Multiple policy statements may be necessary to address each customer's requirements. [edit policy-options] policy-statement reject-long-prefixes { term 1 { from { route-filter 0.0.0.0/0 prefix-length-range /25-/32; } then reject; } <additional terms> } [edit protocols] bgp { group <group name> { type external; import <policy statement name>; << Applied instead of global BGP policy unless a more specific neighbor import filter exists. Excludes all terms in the global filter. local-as <local AS number>; neighbor <neighbor 1 address> { import <policy statement name>; << Most specific import filter. If configured, only this filter applies to this neighbor (all other terms in all other filters ignored). authentication-key "$8$aes256-gcm$hmac-sha2-256$100$cFQ99Gy83Og$SCMVXvnfna7/cZqH9fCECQ$bCVokm+es94xFJONmbKFNA$4561Uc/r"; ## SECRET-DATA } neighbor <neighbor 2 address> { import <policy statement name>; << Most specific import filter. If configured, only this filter applies to this neighbor (all other terms in all other filters ignored). ipsec-sa <SA name>; } } import <policy statement name>; << Least specific import filter. } 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.
Fix: F-57441r844146_fix
Configure all eBGP routers to use the prefix limit feature to protect against route table flooding and prefix deaggregation attacks. set policy-options policy-statement <statement name> term 1 from route-filter 0.0.0.0/0 prefix-length-range /25-/32 set policy-options policy-statement <statement name> term 1 then reject set protocols bgp group <group name> type external set protocols bgp group <group name> import <statement name> set protocols bgp group <group name> local-as <local AS number> set protocols bgp group <group name> neighbor <neighbor 1 address> import <statement name> set protocols bgp group <group name> neighbor <neighbor 1 address> authentication-key <PSK value> set protocols bgp group <group name> neighbor <neighbor 2 address> import <statement name> set protocols bgp group <group name> neighbor <neighbor 2 address> ipsec-sa <SA name> set protocols bgp import <statement name>
- RMF Control
- SC-5
- Severity
- Low
- CCI
- CCI-002385
- Version
- JUEX-RT-000670
- Vuln IDs
-
- V-254039
- Rule IDs
-
- SV-254039r844150_rule
Checks: C-57491r844148_chk
Review the router configuration to verify that IGMP or MLD snooping has been configured for IPv4 and IPv6 multicast traffic respectively for each VPLS bridge domain (VFI instance). [edit routing-instances <name>] protocols { igmp-snooping { vlan <VLAN name>; } mld-snooping { vlan <VLAN name>; } } Note: Only EX9200-series devices currently support VPLS. If the router is not configured to implement IGMP or MLD snooping for each VPLS bridge domain, this is a finding.
Fix: F-57442r844149_fix
Configure IGMP or MLD snooping for IPv4 and IPv6 multicast traffic respectively for each VPLS bridge domain. set routing-instances <name> protocols igmp-snooping vlan <vlan ID> set routing-instances <name> protocols mld-snooping vlan <vlan ID>
- RMF Control
- SC-5
- Severity
- Low
- CCI
- CCI-002385
- Version
- JUEX-RT-000680
- Vuln IDs
-
- V-254040
- Rule IDs
-
- SV-254040r997535_rule
Checks: C-57492r844151_chk
Review the router configuration to determine if forwarding cache thresholds are defined. [edit routing-options] multicast { forwarding-cache { threshold { suppress <1..200000>; reuse <1..200000>; log-warning <percent to generate warning>; } } } 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.
Fix: F-57443r844152_fix
Configure MSDP-enabled RP routers to limit the multicast forwarding cache for source-active entries. set routing-options multicast forwarding-cache threshold suppress <1..200000> set routing-options multicast forwarding-cache threshold reuse <1..200000> set routing-options multicast forwarding-cache threshold log-warning <percent to generate warning>
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- JUEX-RT-000690
- Vuln IDs
-
- V-254041
- Rule IDs
-
- SV-254041r844156_rule
Checks: C-57493r844154_chk
Review the configuration of the RP to verify that it is rate limiting the number of multicast register messages. [edit protocols pim] rp { register-limit { maximum <1..65535>; } <additional configuration> } If the RP is not limiting multicast register messages, this is a finding.
Fix: F-57444r844155_fix
Configure the RP to rate limit the number of multicast register messages. set protocols pim rp register-limit maximum <1..65535>
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- JUEX-RT-000700
- Vuln IDs
-
- V-254042
- Rule IDs
-
- SV-254042r844159_rule
Checks: C-57494r844157_chk
Review the DR configuration to verify that it is limiting the number of mroute states via IGMP or MLD. Verify the group-limit parameter is appropriate for the target network. [edit protocols] igmp { interface <name>.<logical unit> { group-limit <1..32767>; } } mld { interface <name>.<logical unit> { group-limit <1..32767>; } } If the DR is not limiting multicast join requests via IGMP or MLD, this is a finding.
Fix: F-57445r844158_fix
Configure the DR on a global or interface basis to limit the number of mroute states resulting from IGMP or MLD membership reports. set protocols igmp interface <name>.<logical unit> group-limit <1..32767> set protocols mld interface <name>.<logical unit> group-limit <1..32767>
- RMF Control
- SC-5
- Severity
- Medium
- CCI
- CCI-002385
- Version
- JUEX-RT-000710
- Vuln IDs
-
- V-254043
- Rule IDs
-
- SV-254043r945856_rule
Checks: C-57495r844160_chk
Review the multicast last-hop router configuration to verify that the SPT switchover threshold is increased (default is "0") or set to infinity (never switch over). Verify the policy statement includes specific multicast groups or all groups (as shown). [edit policy-options] policy-statement <name> { term 1 { from { route-filter 234.0.0.0/8 orlonger; } then accept; } } Verify the infinity policy is applied. [edit protocols pim] spt-threshold { infinity <policy name>; } If any multicast router is not configured to increase the SPT threshold or set to infinity to minimalize (S, G) state, this is a finding.
Fix: F-57446r844161_fix
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. set policy-options policy-statement <name> term 1 from route-filter 239.0.0.0/8 orlonger set policy-options policy-statement <name> term 1 then accept set protocols pim spt-threshold infinity <policy name>
- RMF Control
- SC-5
- Severity
- Low
- CCI
- CCI-002385
- Version
- JUEX-RT-000720
- Vuln IDs
-
- V-254044
- Rule IDs
-
- SV-254044r997536_rule
Checks: C-57496r844163_chk
Review the router configuration. Verify a firewall filter term discards BGP packets with a TTL less than 255. [edit firewall family inet] filter gtsm { term 1 { from { protocol tcp; ttl 255; destination-port bgp; } then accept; } term 2 { from { protocol tcp; destination-port bgp; } then { log; syslog; discard; } } <additional accept terms> term default { then { log; syslog; discard; } } } Some routers support the "ttl-except" directive that can replace the two term filter shown above. For example: [edit firewall family inet] filter gtsm { term 1 { from { protocol tcp; ttl-except 255; destination-port bgp; } then { log; syslog; discard; } } <additional accept terms> term default { then { log; syslog; discard; } } } Verify the filter is applied to BGP neighbor interfaces. [edit interfaces] <bgp interface> { unit <number> { family inet { filter input gtsm; } address <IPv4 address>.<mask>; } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured to use GTSM for all Exterior Border Gateway Protocol peering sessions, this is a finding.
Fix: F-57447r844164_fix
Configure all Exterior Border Gateway Protocol peering sessions to use GTSM. set firewall family inet filter gtsm term 1 from protocol tcp set firewall family inet filter gtsm term 1 from ttl 255 set firewall family inet filter gtsm term 1 from destination-port bgp set firewall family inet filter gtsm term 1 then accept set firewall family inet filter gtsm term 2 from protocol tcp set firewall family inet filter gtsm term 2 from destination-port bgp set firewall family inet filter gtsm term 2 then log set firewall family inet filter gtsm term 2 then syslog set firewall family inet filter gtsm term 2 then discard <additional accept terms> set firewall family inet filter gtsm term default then log set firewall family inet filter gtsm term default then syslog set firewall family inet filter gtsm term default then discard For those platforms that support 'ttl-except': set firewall family inet filter gtsm term 1 from protocol tcp set firewall family inet filter gtsm term 1 from ttl-except 255 set firewall family inet filter gtsm term 1 from destination-port bgp set firewall family inet filter gtsm term 1 then log set firewall family inet filter gtsm term 1 then syslog set firewall family inet filter gtsm term 1 then discard <additional accept terms> set firewall family inet filter gtsm term default then log set firewall family inet filter gtsm term default then syslog set firewall family inet filter gtsm term default then discard set interfaces <BGP interface> unit <number> family inet filter input gtsm set interfaces <BGP interface> unit <number> family inet address <IPv4 address>.<mask>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000730
- Vuln IDs
-
- V-254045
- Rule IDs
-
- SV-254045r844168_rule
Checks: C-57497r844166_chk
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. [edit policy-options] prefix-list inside-addresses-ipv4 { 192.0.2.0/25; 192.0.2.130/32; } prefix-list inside-addresses-ipv6 { 2001:db8:1::/64; 2001:db8:a1::/64; } [edit firewall] family inet { filter authorized-outbound-ipv4 { <additional terms> term permitted-source-addresses { from { source-prefix-list { inside-addresses-ipv4; } } then accept; } term default-deny { then { log; syslog; discard; } } } filter authorized-inbound-ipv4 { <additional terms> term permitted-destination-addresses { from { destination-prefix-list { inside-addresses-ipv4; } } then accept; } term default-deny { then { log; syslog; discard; } } } } family inet6 { filter authorized-outbound-ipv6 { <additional terms> term permitted-source-addresses { from { source-prefix-list { inside-addresses-ipv6; } } then accept; } term default-deny { then { log; syslog; discard; } } } filter authorized-inbound-ipv6 { <additional terms> term permitted-destination-addresses { from { destination-prefix-list { inside-addresses-ipv6; } } then accept; } term default-deny { then { log; syslog; discard; } } } } Note: The same firewall filtering process can be configured to control traffic destined to the router, or between internal subnets. Verify the firewall filters are applied to the correct interface in the appropriate direction. [edit interfaces] <external interface> { unit <number> { family inet { filter { input authorized-inbound-ipv4; } address <IPv4 address>.<mask>; } family inet6 { filter { input authorized-inbound-ipv6; } address <IPv6 address>.<prefix>; } } } <internal interface> { unit <number> { family inet { filter { input authorized-outbound-ipv4; } address <IPv4 address>.<mask>; } family inet6 { filter { input authorized-outbound-ipv6; } address <IPv6 address>.<prefix>; } } } If the router does not restrict incoming communications to allow only authorized sources and destinations, this is a finding.
Fix: F-57448r844167_fix
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. set policy-options prefix-list inside-addresses-ipv4 192.0.2.0/25 set policy-options prefix-list inside-addresses-ipv4 192.0.2.130/32 set policy-options prefix-list inside-addresses-ipv6 2001:db8:1::/64 set policy-options prefix-list inside-addresses-ipv6 2001:db8:a1::/64 set firewall family inet filter authorized-outbound-ipv4 <additional terms> set firewall family inet filter authorized-outbound-ipv4 term permitted-source-addresses from source-prefix-list inside-addresses-ipv4 set firewall family inet filter authorized-outbound-ipv4 term permitted-source-addresses then accept set firewall family inet filter authorized-outbound-ipv4 term default-deny then log set firewall family inet filter authorized-outbound-ipv4 term default-deny then syslog set firewall family inet filter authorized-outbound-ipv4 term default-deny then discard set firewall family inet filter authorized-inbound-ipv4 <additional terms> set firewall family inet filter authorized-inbound-ipv4 term permitted-destination-addresses from destination-prefix-list inside-addresses-ipv4 set firewall family inet filter authorized-inbound-ipv4 term permitted-destination-addresses then accept set firewall family inet filter authorized-inbound-ipv4 term default-deny then log set firewall family inet filter authorized-inbound-ipv4 term default-deny then syslog set firewall family inet filter authorized-inbound-ipv4 term default-deny then discard set firewall family inet6 filter authorized-outbound-ipv6 <additional terms> set firewall family inet6 filter authorized-outbound-ipv6 term permitted-source-addresses from source-prefix-list inside-addresses-ipv6 set firewall family inet6 filter authorized-outbound-ipv6 term permitted-source-addresses then accept set firewall family inet6 filter authorized-outbound-ipv6 term default-deny then log set firewall family inet6 filter authorized-outbound-ipv6 term default-deny then syslog set firewall family inet6 filter authorized-outbound-ipv6 term default-deny then discard set firewall family inet6 filter authorized-inbound-ipv6 <additional terms> set firewall family inet6 filter authorized-inbound-ipv6 term permitted-destination-addresses from destination-prefix-list inside-addresses-ipv6 set firewall family inet6 filter authorized-inbound-ipv6 term permitted-destination-addresses then accept set firewall family inet6 filter authorized-inbound-ipv6 term default-deny then log set firewall family inet6 filter authorized-inbound-ipv6 term default-deny then syslog set firewall family inet6 filter authorized-inbound-ipv6 term default-deny then discard set interfaces <external interface> unit <number> family inet filter input authorized-inbound-ipv4 set interfaces <external interface> unit <number> family inet6 filter input authorized-inbound-ipv6 set interfaces <internal interface> unit <number> family inet filter input authorized-outbound-ipv4 set interfaces <internal interface> unit <number> family inet6 filter input authorized-outbound-ipv6
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000740
- Vuln IDs
-
- V-254046
- Rule IDs
-
- SV-254046r844171_rule
Checks: C-57498r844169_chk
This requirement is not applicable for the DODIN Backbone. Verify that the ingress filter is blocking packets with Bogon source addresses. Bogon addresses are added to prefix lists to ease management, and prefix lists are associated with firewall filters. Verify appropriate prefix lists for IPv4 and IPv6 Bogon addresses. For example: [edit policy-options] prefix-list bogon-addresses-ipv4 { /* This host on this network */ 0.0.0.0/8; /* CGN Addresses */ 100.64.0.0/10; /* Loopback */ 127.0.0.0/8; /* IPv4 link-local or APIPA */ 169.254.0.0/16; /* IETF Protocol Assignments */ 192.0.0.0/24; /* IPv4 documentation addresses: TEST-NET-1 */ 192.0.2.0/24; /* 6to4 Relay Anycast descr in RFC3068 */ 192.88.99.0/24; /* Benchmark testing descr in RFC2544 */ 198.18.0.0/15; /* IPv4 documentation addresses: TEST-NET-2 */ 198.51.100.0/24; /* IPv4 documentation addresses: TEST-NET-3 */ 203.0.113.0/24; /* Multicast */ 224.0.0.0/24; /* Reserved */ 240.0.0.0/4; /* RFC1918 Addresses */ 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16; <add additional routes as needed> } route-filter-list bogon-ipv6 { /* Unspecified */ ::/128; /* Loopback */ ::1/128; /* IPv4 Compatible */ 0::/96; /* IPv4-mapped */ ::ffff:0:0/96; /* 6Bone */ 3ffe::/16; /* IPv4-IPv6 Translate */ 64:ff9b::/96; /* Discard-Only */ 100::/64; /* ORCHID */ 2001:10::/28; /* Documentation */ 2001:db8::/32; /* Benchmarking */ 2001:2::/48; /* TEREDO */ 2001::/32; /* IETF Protocol Assignments */ 2001::/23; /* 6to4 */ 2002::/16; /* Unique-Local */ fc00::/7; /* Site local (deprecated) - now reserved */ fec0::/10; /* Multicast */ ff00::/8; <add additional routes as needed> } Note: The comments associated with addresses is configured with the "annotate" command. Annotations will appear in the standard hierarchical configuration display but do not appear when using "display set". The annotations are not required but added to this check to show what each address represents. Verify IPv4 and IPv6 firewall filters incorporate Bogon address restrictions. [edit firewall] family inet { filter inbound-ipv4 { term 1 { from { source-prefix-list bogon-ipv4; } then { log; syslog; discard; } } <permitted traffic terms> } } family inet6 { filter inbound-ipv6 { term 1 { from { source-prefix-list bogon-ipv6; } then { log; syslog; discard; } } <permitted traffic terms> } } Review the router configuration to verify that it is configured to block IP packets with a Bogon source address. Verify the firewall filter enforcing Bogon restrictions is applied inbound on exterior-facing interfaces. For example: [edit interfaces] <interface name> { unit <number> { family inet { filter { input inbound-ipv4; } address <IPv4 address>/<mask>; } family inet6 { filter { input inbound-ipv6; } address <IPv6 address>/<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; Reference minimum IPv4 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.88.99.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 Reference minimum IPv6 Bogon Prefixes ::/128 ::1/128 0::/96 ::ffff:0:0/96 3ffe::/16 64:ff9b::/96 100::/64 2001:10::/28 2001:db8::/32 2001:2::/48 2001::/32 2001::/23 2002::/16 fc00::/7 fe80::/10 fec0::/10 ff00::/8 If the router is not configured to block inbound IP packets containing a Bogon source address, this is a finding. Note: At a minimum, IP packets containing a source address from the special purpose address space as defined in RFC 6890 must be blocked. The 6Bone prefix (3ffe::/16) is also be considered a Bogon address. Perimeter routers connected to commercial ISPs for internet or other non-DoD network sources will need to be reviewed for a full Bogon list. The IPv4 full Bogon list contains prefixes that have been allocated to RIRs but not assigned by those RIRs. Reference the following link: http://www.team-cymru.org/Services/Bogons/fullbogons-ipv4.txt The IPv6 full Bogon list contains prefixes that have not been allocated to RIRs, or those that have been allocated to RIRs but have not been assigned by those RIRs. Reference the following link: https://www.team-cymru.org/Services/Bogons/fullbogons-ipv6.txt
Fix: F-57449r844170_fix
This requirement is not applicable for the DODIN Backbone. Configure the router to block inbound packets with Bogon source addresses. Example Bogon prefix lists: set policy-options prefix-list bogon-ipv4 0.0.0.0/8 set policy-options prefix-list bogon-ipv4 10.0.0.0/8 set policy-options prefix-list bogon-ipv4 100.64.0.0/10 set policy-options prefix-list bogon-ipv4 127.0.0.0/8 set policy-options prefix-list bogon-ipv4 169.254.0.0/16 set policy-options prefix-list bogon-ipv4 172.16.0.0/12 set policy-options prefix-list bogon-ipv4 192.0.0.0/24 set policy-options prefix-list bogon-ipv4 192.0.2.0/24 set policy-options prefix-list bogon-ipv4 192.88.99.0/24 set policy-options prefix-list bogon-ipv4 192.168.0.0/16 set policy-options prefix-list bogon-ipv4 198.18.0.0/15 set policy-options prefix-list bogon-ipv4 198.51.100.0/24 set policy-options prefix-list bogon-ipv4 203.0.113.0/24 set policy-options prefix-list bogon-ipv4 224.0.0.0/24 set policy-options prefix-list bogon-ipv4 240.0.0.0/4 set policy-options prefix-list bogon-ipv6 ::/128 set policy-options prefix-list bogon-ipv6 ::1/128 set policy-options prefix-list bogon-ipv6 0::/96 set policy-options prefix-list bogon-ipv6 ::ffff:0:0/96 set policy-options prefix-list bogon-ipv6 3ffe::/16 set policy-options prefix-list bogon-ipv6 64:ff9b::/96 set policy-options prefix-list bogon-ipv6 100::/64 set policy-options prefix-list bogon-ipv6 2001:10::/28 set policy-options prefix-list bogon-ipv6 2001:db8::/32 set policy-options prefix-list bogon-ipv6 2001:2::/48 set policy-options prefix-list bogon-ipv6 2001::/32 set policy-options prefix-list bogon-ipv6 2001::/23 set policy-options prefix-list bogon-ipv6 2002::/16 set policy-options prefix-list bogon-ipv6 fc00::/7 set policy-options prefix-list bogon-ipv6 fec0::/10 set policy-options prefix-list bogon-ipv6 ff00::/8 Example firewall filters: set firewall family inet filter inbound-ipv4 term 1 from source-prefix-list bogon-ipv4 set firewall family inet filter inbound-ipv4 term 1 then log set firewall family inet filter inbound-ipv4 term 1 then syslog set firewall family inet filter inbound-ipv4 term 1 then discard set firewall family inet filter inbound-ipv4 term <permitted traffic terms> set firewall family inet6 filter inbound-ipv6 term 1 from source-prefix-list bogon-ipv6 set firewall family inet6 filter inbound-ipv6 term 1 then log set firewall family inet6 filter inbound-ipv6 term 1 then syslog set firewall family inet6 filter inbound-ipv6 term 1 then discard set firewall family inet6 filter inbound-ipv6 term <permitted traffic terms> Example application on external interfaces: set interfaces <interface name> unit <number> family inet filter input inbound-ipv4 set interfaces <interface name> unit <number> family inet address <IPv4 address / mask> set interfaces <interface name> unit <number> family inet6 filter input inbound-ipv6 set interfaces <interface name> unit <number> family inet6 address <IPv6 address / prefix>
- RMF Control
- SC-7
- Severity
- Low
- CCI
- CCI-002403
- Version
- JUEX-RT-000750
- Vuln IDs
-
- V-254047
- Rule IDs
-
- SV-254047r844174_rule
Checks: C-57499r844172_chk
This requirement is not applicable for the DODIN Backbone. Review all router configurations to ensure LLDPs are not included in the global configuration or LLDPs are not included for each active external interface. Examples of LLDPs are Cisco Discovery Protocol (CDP), Link Layer Discovery Protocol (LLDP), and Link Layer Discovery Protocol - Media Endpoint Discovery (LLDP-MED). Junos does not support CDP, but supports both LLDP and LLDP-MED, configured at [edit protocols]. Verify external interfaces are either not configured or explicitly disabled. For example: To globally disable LLDP and LLDP-MED: [edit protocols] <no LLDP or LLDP-MED hierarchy> -or- lldp { interface all { disable; } } lldp-med { interface all { disable; } } If LLDP or LLDP-MED is authorized, verify external interfaces are not configured or are explicitly disabled. For example: [edit protocols] lldp { interface all { disable; } interface ge-0/0/0; <<< Verify ge-0/0/0 is not an external interface. interface ge-0/0/1 { disable; <<< Assuming ge-0/0/1 is an external interface, it is disabled globally (interface all disable) or explicitly disabled as shown. } } lldp-med { interface all { disable; interface ge-0/0/0; <<< Verify ge-0/0/0 is not an external interface. interface ge-0/0/1 { disable; <<< Assuming ge-0/0/1 is an external interface, it is disabled globally (interface all disable) or explicitly disabled as shown. } } Note: Both LLDP and LLDP-MED are globally disabled on all interfaces but Junos will apply the most specific configuration. Therefore, both LLDP and LLDP-MED are enabled only on ge-0/0/0 and disabled on all other interfaces as configured in the example. If LLDPs are configured globally or on any external interface, this is a finding.
Fix: F-57450r844173_fix
This requirement is not applicable for the DODIN Backbone. Disable LLDPs on all external interfaces. set protocols lldp interface all disable set protocols lldp interface <interior interface> set protocols lldp interface <exterior interface> disable set protocols lldp-med interface all disable set protocols lldp-med interface <interior interface> set protocols lldp-med interface <exterior interface> disable Note: The <exterior interface> disable command is not required if LLDP and LLDP-MED are globally disabled. However, the configured protocol status may be more apparent if each exterior interface is explicitly disabled.
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000760
- Vuln IDs
-
- V-254048
- Rule IDs
-
- SV-254048r844177_rule
Checks: C-57500r844175_chk
This requirement is not applicable for the DODIN Backbone. Review the router configuration to determine if Proxy ARP is disabled on all external interfaces. By default, Proxy ARP is disabled on all interfaces. Verify "proxy-arp" has not been enabled on external interfaces as shown in the example: [edit interfaces] <external interface> { unit 0 { proxy-arp [restricted|unrestricted]; << Must not be configured on external interfaces. <additional configuration> } } If Proxy ARP is enabled on any external interface, this is a finding.
Fix: F-57451r844176_fix
This requirement is not applicable for the DODIN Backbone. Disable IP Proxy ARP on all external interfaces. delete interfaces <external interface> unit 0 proxy-arp
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-001097
- Version
- JUEX-RT-000770
- Vuln IDs
-
- V-254049
- Rule IDs
-
- SV-254049r945857_rule
Checks: C-57501r844178_chk
This requirement is not applicable for the DODIN Backbone. The perimeter router of the managed network must be configured with a firewall filter on the egress interface to block all management traffic. [edit firewall] family inet { filter <name> { term block-UDP-MGT-SRC { from { protocol udp; source-port [ snmp snmptrap 2055 9995 9996 ]; } then { syslog; discard; } } term block-TCP-MGT-SRC { from { protocol tcp; source-port [ ssh tacacs ]; } then { syslog; discard; } } term block-UDP-MGT-DST { from { protocol udp; destination-port [ snmp snmptrap 2055 9995 9996 ]; } then { syslog; discard; } } term block-TCP-MGT-DST { from { protocol tcp; destination-port [ ssh tacacs ]; } then { syslog; discard; } } <additional terms> term accept-other { then accept; } } } family inet6 { filter <name> { term block-UDP-MGT-SRC { from { next-header udp; source-port [ snmp snmptrap 2055 9995 9996 ]; } then { syslog; discard; } } term block-TCP-MGT-SRC { from { next-header tcp; source-port [ ssh tacacs ]; } then { syslog; discard; } } term block-UDP-MGT-DST { from { next-header udp; destination-port [ snmp snmptrap 2055 9995 9996 ]; } then { syslog; discard; } } term block-TCP-MGT-DST { from { next-header tcp; destination-port [ ssh tacacs ]; } then { syslog; discard; } } <additional terms> term accept-other { then accept; } } } Note: Some platforms support the "port" match criterion. For those platforms, only a single term is required to flag on both source- and destination-port. For example: [edit firewall] family [inet|inet6] { filter <name> { term <name> { from { : port [ port1 port2... ]; } then { syslog; discard; } } <additional terms> } } Verify the filter is applied to external interfaces. [edit interfaces] <external interface> { unit <number> { family inet { filter { output <name>; } address <IPv4 address>/<mask>; } family inet6 { filter { output <name>; } address <IPv6 address>/<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If management traffic is not blocked at the perimeter, this is a finding.
Fix: F-57452r844179_fix
This requirement is not applicable for the DODIN Backbone. Configure the perimeter router of the managed network with a firewall filter on the egress interface to block all outbound management traffic. set firewall family inet filter <name> term block-UDP-MGT-SRC from protocol udp set firewall family inet filter <name> term block-UDP-MGT-SRC from source-port [ snmp snmptrap 2055 9995 9996 ] set firewall family inet filter <name> term block-UDP-MGT-SRC then syslog set firewall family inet filter <name> term block-UDP-MGT-SRC then discard set firewall family inet filter <name> term block-TCP-MGT-SRC from protocol tcp set firewall family inet filter <name> term block-TCP-MGT-SRC from source-port [ ssh tacacs ] set firewall family inet filter <name> term block-TCP-MGT-SRC then syslog set firewall family inet filter <name> term block-TCP-MGT-SRC then discard set firewall family inet filter <name> term block-UDP-MGT-DST from protocol udp set firewall family inet filter <name> term block-UDP-MGT-DST from destination-port [ snmp snmptrap 2055 9995 9996 ] set firewall family inet filter <name> term block-UDP-MGT-DST then syslog set firewall family inet filter <name> term block-UDP-MGT-DST then discard set firewall family inet filter <name> term block-TCP-MGT-DST from protocol tcp set firewall family inet filter <name> term block-TCP-MGT-DST from destination-port [ ssh tacacs ] set firewall family inet filter <name> term block-TCP-MGT-DST then syslog set firewall family inet filter <name> term block-TCP-MGT-DST then discard <additional terms> set firewall family inet filter <name> term accept-others then accept set firewall family inet6 filter <name> term block-UDP-MGT-SRC from next-header udp set firewall family inet6 filter <name> term block-UDP-MGT-SRC from source-port [ snmp snmptrap 2055 9995 9996 ] set firewall family inet6 filter <name> term block-UDP-MGT-SRC then syslog set firewall family inet6 filter <name> term block-UDP-MGT-SRC then discard set firewall family inet6 filter <name> term block-TCP-MGT-SRC from next-header tcp set firewall family inet6 filter <name> term block-TCP-MGT-SRC from source-port [ ssh tacacs ] set firewall family inet6 filter <name> term block-TCP-MGT-SRC then syslog set firewall family inet6 filter <name> term block-TCP-MGT-SRC then discard set firewall family inet6 filter <name> term block-UDP-MGT-DST from next-header udp set firewall family inet6 filter <name> term block-UDP-MGT-DST from destination-port [ snmp snmptrap 2055 9995 9996 ] set firewall family inet6 filter <name> term block-UDP-MGT-DST then syslog set firewall family inet6 filter <name> term block-UDP-MGT-DST then discard set firewall family inet6 filter <name> term block-TCP-MGT-DST from next-header tcp set firewall family inet6 filter <name> term block-TCP-MGT-DST from destination-port [ ssh tacacs ] set firewall family inet6 filter <name> term block-TCP-MGT-DST then syslog set firewall family inet6 filter <name> term block-TCP-MGT-DST then discard <additional terms> set firewall family inet6 filter <name> term accept-others then accept set interfaces <external interface> unit <number> family inet filter output <name> set interfaces <external interface> unit <number> family inet address <IPv4 address>/<mask> set interfaces <external interface> unit <number> family inet6 filter output <name> set interfaces <external interface> unit <number> family inet6 address <IPv6 address>/<prefix>
- RMF Control
- SC-7
- Severity
- Low
- CCI
- CCI-002403
- Version
- JUEX-RT-000780
- Vuln IDs
-
- V-254050
- Rule IDs
-
- SV-254050r844262_rule
Checks: C-57502r844181_chk
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. 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. [edit policy-options] policy-statement <name> { term unauth-groups { from { route-filter 224.0.1.2/32 exact; route-filter 224.0.2.2/32 exact; } then reject; } term allow-others { then accept; } } policy-statement <name IPv6> { term unauth-groups { from { route-filter fec0:1:1:4::/64 exact; } then reject; } term allow-others { then accept; } } [edit protocols] igmp { interface <name>.<logical unit> { group-policy <policy name>; } } mld { interface <name>.<logical unit> { group-policy <policy name IPv6>; } } If the DR is not filtering IGMP or MLD report messages, this is a finding.
Fix: F-57453r844182_fix
Configure the DR to filter the IGMP and MLD report messages to allow hosts to join only those multicast groups that have been approved. set policy-options policy-statement <name> term unauth-groups from route-filter 224.0.1.2/32 exact set policy-options policy-statement <name> term unauth-groups from route-filter 224.0.2.2/32 exact set policy-options policy-statement <name> term unauth-groups then reject set policy-options policy-statement <name> term accept-others then accept set policy-options policy-statement <name IPv6> term unauth-groups from route-filter fec0:1:1:4::/64 exact set policy-options policy-statement <name IPv6> term unauth-groups then reject set policy-options policy-statement <name IPv6> term accept-others then accept set protocols igmp interface <name>.<logical unit> group-policy <policy name> set protocols mld interface <name>.<logical unit> group-policy <policy name IPv6>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000790
- Vuln IDs
-
- V-254051
- Rule IDs
-
- SV-254051r844263_rule
Checks: C-57503r844184_chk
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. Note: This requirement is only applicable to Source Specific Multicast (SSM) implementation. [edit policy-options] policy-statement <name> { term unauth-sources { from { source-address-filter <IPv4 address>/<mask> orlonger; } then reject; } term allow-others { then accept; } } policy-statement <name IPv6> { term unauth-sources { from { source-address-filter <IPv6 address>/<prefix> orlonger; } then reject; } term allow-others { then accept; } } [edit protocols] igmp { interface <name>/<logical unit> { group-policy <policy name>; } } mld { interface <name>/<logical unit> { group-policy <policy name IPv6>; } } If the DR is not filtering IGMP or MLD report messages, this is a finding.
Fix: F-57454r844185_fix
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. set policy-options policy-statement <name> term unauth-sources from source-address-filter <IPv4 address>/<mask> orlonger set policy-options policy-statement <name> term unauth-sources then reject set policy-options policy-statement <name> term accept-others then accept set policy-options policy-statement <name IPv6> term unauth-sources from source-address-filter <IPv6 address>/<prefix> orlonger set policy-options policy-statement <name IPv6> term unauth-sources then reject set policy-options policy-statement <name IPv6> term accept-others then accept set protocols igmp interface <name>.<logical unit> group-policy <policy name> set protocols mld interface <name>.<logical unit> group-policy <policy name IPv6>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000800
- Vuln IDs
-
- V-254052
- Rule IDs
-
- SV-254052r844189_rule
Checks: C-57504r844187_chk
Review the router configuration to determine if there is a receive path or interface filter to only accept MSDP packets from known MSDP peers. [edit firewall] family inet { filter <name> { term 1 { from { source-prefix-list { msdp-peers; } protocol tcp; destination-port msdp; } then accept; } term 2 { from { source-prefix-list { msdp-peers; } protocol tcp; source-port msdp; } then accept; } <additional terms> term default { then { syslog; discard; } } } } family inet6 { filter <name> { term 1 { from { source-prefix-list { msdp-peers-ipv6; } next-header tcp; destination-port msdp; } then accept; } term 2 { from { source-prefix-list { msdp-peers-ipv6; } next-header tcp; source-port msdp; } then accept; } <additional terms> term default { then { syslog; discard; } } } } Note: Some platforms support the "port" keyword that filters on both source- and destination-port, which eliminates the need for separate terms. For instance: filter <name> { term 1 { from { source-prefix-list { <prefix list name>; } [protocol|next-header] tcp; port msdp; } then accept; } <additional terms> term default { then { syslog; discard; } } } Verify the filter is applied to external interfaces or loopback. [edit interfaces] <external interface> { unit <number> { family inet { filter { input <IPv4 filter name>; } address <IPv4 address>/<mask>; } family inet6 { filter { input <IPv6 filter name>; } address <IPv6 address>/<prefix>; } } } lo0 { unit <number> { family inet { filter { input <IPv4 filter name>; } address <IPv4 address>/32; } family inet6 { filter { input <IPv6 filter name>; } address <IPv6 address>/128; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured to only accept MSDP packets from known MSDP peers, this is a finding.
Fix: F-57455r844188_fix
Ensure the receive path or interface filter for all MSDP routers only accepts MSDP packets from known MSDP peers. set firewall family inet filter <name> term 1 from source-prefix-list msdp-peers set firewall family inet filter <name> term 1 from protocol tcp set firewall family inet filter <name> term 1 from destination-port msdp set firewall family inet filter <name> term 1 then accept set firewall family inet filter <name> term 2 from source-prefix-list msdp-peers set firewall family inet filter <name> term 2 from protocol tcp set firewall family inet filter <name> term 2 from source-port msdp set firewall family inet filter <name> term 2 then accept <additional terms> set firewall family inet filter <name> term default then syslog set firewall family inet filter <name> term default then discard set firewall family inet6 filter <name> term 1 from source-prefix-list msdp-peers-ipv6 set firewall family inet6 filter <name> term 1 from next-header tcp set firewall family inet6 filter <name> term 1 from destination-port msdp set firewall family inet6 filter <name> term 1 then accept set firewall family inet6 filter <name> term 2 from source-prefix-list msdp-peers-ipv6 set firewall family inet6 filter <name> term 2 from next-header tcp set firewall family inet6 filter <name> term 2 from source-port msdp set firewall family inet6 filter <name> term 2 then accept <additional terms> set firewall family inet6 filter <name> term default then syslog set firewall family inet6 filter <name> term default then discard set interfaces <external interface> unit <number> family inet filter input <IPv4 filter name> set interfaces <external interface> unit <number> family inet address <IPv4 address>/<mask> set interfaces <external interface> unit <number> family inet6 filter input <IPv6 filter name> set interfaces <external interface> unit <number> family inet6 address <IPv6 address>/<prefix> set interfaces lo0 unit <number> family inet filter input <IPv4 filter name> set interfaces lo0 unit <number> family inet address <IPv4 address>/32 set interfaces lo0 unit <number> family inet6 filter input <IPv6 filter name> set interfaces lo0 unit <number> family inet6 address <IPv6 address>/128
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000810
- Vuln IDs
-
- V-254053
- Rule IDs
-
- SV-254053r950991_rule
Checks: C-57505r844190_chk
This requirement is not applicable for the DODIN Backbone. There is no check for dropping RFC 7112 nonconformant fragmented IPv6 packets because Juniper EX switches drop these packets without offering or requiring a configurable option in the CLI. Review the router configuration to determine if it is configured to drop fragmented transit IPv6 traffic. [edit firewall family inet6] filter <filter name> { term <name> { from { next-header fragment; } then { syslog; discard; } } } Note: Some platforms also support "is-fragment" or "fragment-flags is-fragment" in addition to "next-header fragment" as shown in the example. If the router is not configured to drop first-fragment IPv6 packets without the entire header chain, this is a finding.
Fix: F-57456r844191_fix
Configure the router to drop first-fragment IPv6 packets without the entire header chain. There is no configurable CLI option to prevent EX devices from dropping nonconformant fragmented IPv6 packets destined to the device. Configure the router to drop fragmented transit IPv6 packets. set firewall family inet6 filter <name> term <name> from next-header fragment set firewall family inet6 filter <name> term <name> then syslog set firewall family inet6 filter <name> term <name> then discard
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000820
- Vuln IDs
-
- V-254054
- Rule IDs
-
- SV-254054r844195_rule
Checks: C-57506r844193_chk
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. [edit firewall family inet6] filter <name> { term 1 { from { next-header routing; } then { log; syslog; discard; } } <additional terms> term default { then { log; syslog; discard; } } } Note: Juniper routers do not support configuring option types for Routing extension headers. Therefore, all packets with the Routing extension header are dropped. Verify the filter is applied to applicable interfaces. [edit interfaces] <interface name> { unit <number> { family inet6 { filter { input <filter name>; } address <IPv6 address>.<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; 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.
Fix: F-57457r844194_fix
Configure the router to drop IPv6 packets with Routing Header of type 0, 1, or 3–255. set firewall family inet6 filter <name> term 1 from next-header routing set firewall family inet6 filter <name> term 1 then log set firewall family inet6 filter <name> term 1 then syslog set firewall family inet6 filter <name> term 1 then discard <additional terms> set firewall family inet6 filter <name> term default then log set firewall family inet6 filter <name> term default then syslog set firewall family inet6 filter <name> term default then discard set interfaces <interface name> unit <number> family inet6 filter input <filter name> set interfaces <interface name> unit <number> family inet6 address <IPv6 address>.<prefix>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000830
- Vuln IDs
-
- V-254055
- Rule IDs
-
- SV-254055r844198_rule
Checks: C-57507r844196_chk
This requirement is not applicable for the DODIN Backbone. Review the router configuration to determine if filters 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). [edit firewall family inet6] filter <name> { term 1 { from { next-header [ hop-by-hop dstopts ]; } then { log; syslog; discard; } } <additional terms> term default { then { log; syslog; discard; } } } Note: Juniper routers do not support configuring option types for Hop-by-Hop or Destination Options extension headers. Therefore, all packets with the Hop-by-Hop or Destination Options extension header are dropped. Verify the filter is applied to applicable interfaces. [edit interfaces] <interface name> { unit <number> { family inet6 { filter { input <filter name>; } address <IPv6 address>.<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; 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.
Fix: F-57458r844197_fix
Configure the router 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). set firewall family inet6 filter <name> term 1 from next-header hop-by-hop set firewall family inet6 filter <name> term 1 from next-header dstopts set firewall family inet6 filter <name> term 1 then log set firewall family inet6 filter <name> term 1 then syslog set firewall family inet6 filter <name> term 1 then discard <additional terms> set firewall family inet6 filter <name> term default then log set firewall family inet6 filter <name> term default then syslog set firewall family inet6 filter <name> term default then discard set interfaces <interface name> unit <number> family inet6 filter input <filter name> set interfaces <interface name> unit <number> family inet6 address <IPv6 address>.<prefix>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000840
- Vuln IDs
-
- V-254056
- Rule IDs
-
- SV-254056r844201_rule
Checks: C-57508r844199_chk
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 IPv6 packets containing a Destination Option header with option type values of 0x05 (Router Alert) or 0xC2 (Jumbo Payload). [edit firewall family inet6] filter <name> { term 1 { from { next-header [ hop-by-hop dstopts ]; } then { log; syslog; discard; } } <additional terms> term default { then { log; syslog; discard; } } } Note: Juniper routers do not support configuring option types for Hop-by-Hop or Destination Options extension headers. Therefore, all packets with the Hop-by-Hop or Destination Options extension header are dropped. Verify the filter is applied to applicable interfaces. [edit interfaces] <interface name> { unit <number> { family inet6 { filter { input <filter name>; } address <IPv6 address>.<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured to drop IPv6 packets containing a Destination Option header with invalid option type values, this is a finding.
Fix: F-57459r844200_fix
Configure the router to drop IPv6 packets containing a Destination Option header with option type values of 0x05 (Router Alert) or 0xC2 (Jumbo Payload). set firewall family inet6 filter <name> term 1 from next-header hop-by-hop set firewall family inet6 filter <name> term 1 from next-header dstopts set firewall family inet6 filter <name> term 1 then log set firewall family inet6 filter <name> term 1 then syslog set firewall family inet6 filter <name> term 1 then discard <additional terms> set firewall family inet6 filter <name> term default then log set firewall family inet6 filter <name> term default then syslog set firewall family inet6 filter <name> term default then discard set interfaces <interface name> unit <number> family inet6 filter input <filter name> set interfaces <interface name> unit <number> family inet6 address <IPv6 address>.<prefix>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000850
- Vuln IDs
-
- V-254057
- Rule IDs
-
- SV-254057r844204_rule
Checks: C-57509r844202_chk
This requirement is not applicable for the DODIN Backbone. Review the router switch configuration and determine if filters are bound to the applicable interfaces to drop 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. [edit firewall family inet6] filter <name> { term 1 { from { next-header [ hop-by-hop dstopts ]; } then { log; syslog; discard; } } <additional terms> term default { then { log; syslog; discard; } } } Note: Juniper routers do not support configuring option types for Hop-by-Hop or Destination Options extension headers. Therefore, all packets with the Hop-by-Hop or Destination Options extension header are dropped. Verify the filter is applied to applicable interfaces. [edit interfaces] <interface name> { unit <number> { family inet6 { filter { input <filter name>; } address <IPv6 address>.<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured to drop IPv6 packets containing an extension header with the Endpoint Identification option, this is a finding.
Fix: F-57460r844203_fix
Configure the router to drop 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. set firewall family inet6 filter <name> term 1 from next-header hop-by-hop set firewall family inet6 filter <name> term 1 from next-header dstopts set firewall family inet6 filter <name> term 1 then log set firewall family inet6 filter <name> term 1 then syslog set firewall family inet6 filter <name> term 1 then discard <additional terms> set firewall family inet6 filter <name> term default then log set firewall family inet6 filter <name> term default then syslog set firewall family inet6 filter <name> term default then discard set interfaces <interface name> unit <number> family inet6 filter input <filter name> set interfaces <interface name> unit <number> family inet6 address <IPv6 address>.<prefix>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000860
- Vuln IDs
-
- V-254058
- Rule IDs
-
- SV-254058r844207_rule
Checks: C-57510r844205_chk
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). Verify the router drops all destination-options extension headers. [edit firewall family inet6] filter <name> { term 1 { from { next-header dstopts; } then { log; syslog; discard; } } <additional terms> term default { then { log; syslog; discard; } } } Note: Juniper routers do not support configuring option types for Destination Options extension headers. Therefore, all packets with the Destination Options extension header are dropped. Verify the filter is applied to applicable interfaces. [edit interfaces] <interface name> { unit <number> { family inet6 { filter { input <filter name>; } address <IPv6 address>.<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured to drop IPv6 packets containing the NSAP address option within Destination Option header, this is a finding.
Fix: F-57461r844206_fix
Configure the router to drop IPv6 packets containing a Destination Option header with option type value of 0xC3 (NSAP address). set firewall family inet6 filter <name> term 1 from next-header dstopts set firewall family inet6 filter <name> term 1 then log set firewall family inet6 filter <name> term 1 then syslog set firewall family inet6 filter <name> term 1 then discard <additional terms> set firewall family inet6 filter <name> term default then log set firewall family inet6 filter <name> term default then syslog set firewall family inet6 filter <name> term default then discard set interfaces <interface name> unit <number> family inet6 filter input <filter name> set interfaces <interface name> unit <number> family inet6 address <IPv6 address>.<prefix>
- RMF Control
- SC-7
- Severity
- Medium
- CCI
- CCI-002403
- Version
- JUEX-RT-000870
- Vuln IDs
-
- V-254059
- Rule IDs
-
- SV-254059r844210_rule
Checks: C-57511r844208_chk
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. Verify the router drops all hop-by-hop and destination-options extension headers. [edit firewall family inet6] filter <name> { term 1 { from { next-header [ hop-by-hop dstopts ]; } then { log; syslog; discard; } } <additional terms> term default { then { log; syslog; discard; } } } Note: Juniper routers do not support configuring option types for either the Hop-by-Hop or Destination Options extension headers. Therefore, all packets with the Hop-by-Hop or Destination Options extension header are dropped. Verify the filter is applied to applicable interfaces. [edit interfaces] <interface name> { unit <number> { family inet6 { filter { input <filter name>; } address <IPv6 address>.<prefix>; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the router is not configured to drop IPv6 packets containing a Hop-by-Hop or Destination Option extension header, this is a finding.
Fix: F-57462r844209_fix
Configure the router to drop all inbound IPv6 packets containing an undefined option type value regardless of whether or not they appear in a Hop-by-Hop or Destination Option header. set firewall family inet6 filter <name> term 1 from next-header hop-by-hop set firewall family inet6 filter <name> term 1 from next-header dstopts set firewall family inet6 filter <name> term 1 then log set firewall family inet6 filter <name> term 1 then syslog set firewall family inet6 filter <name> term 1 then discard <additional terms> set firewall family inet6 filter <name> term default then log set firewall family inet6 filter <name> term default then syslog set firewall family inet6 filter <name> term default then discard set interfaces <interface name> unit <number> family inet6 filter input <filter name> set interfaces <interface name> unit <number> family inet6 address <IPv6 address>.<prefix>
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- JUEX-RT-000880
- Vuln IDs
-
- V-254060
- Rule IDs
-
- SV-254060r844213_rule
Checks: C-57512r844211_chk
Review the router configuration to verify that a loopback address has been configured. Verify that a loopback interface is used as the source address for all iBGP sessions. bgp { group iBGP { type internal; local-interface lo0.0; : } } If the router does not use its loopback address as the source address for all iBGP sessions, this is a finding.
Fix: F-57463r844212_fix
Ensure that the router’s loopback address is used as the source address when originating traffic. set protocols bgp group <group name> type internal set protocols bgp group <group name> local-interface lo0.0
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- JUEX-RT-000890
- Vuln IDs
-
- V-254061
- Rule IDs
-
- SV-254061r844216_rule
Checks: C-57513r844214_chk
Review the router configuration to determine if it uses its loopback address as the source address for LDP peering sessions. Verify that a loopback address has been configured as shown in the following example: [edit interfaces] lo0 { unit 0 { family inet { address <IPv4 address>/32; } family inet6 { address <IPv6 address>/128; } } } An MPLS router will use the LDP router ID as the source address for LDP hellos and when establishing TCP sessions with LDP peers; hence, it is necessary to verify that the LDP router ID is the same as the loopback address. By default, routers will assign the LDP router ID using the highest IP address on the router, with preference given to loopback addresses. If the router-id command is specified that overrides this default behavior, verify that it is the IP address of the designated loopback interface. [edit routing-options] router-id <lo0 address>; If the router is not configured do use its loopback address for LDP peering, this is a finding.
Fix: F-57464r844215_fix
Configure MPLS routers to use their loopback address as the source address for LDP peering sessions. set interfaces lo0 unit 0 family inet <IPv4 address>/32 set interfaces lo0 unit 0 family inet6 <IPv6 address>/128 set routing-options router-id <lo0 address>
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- JUEX-RT-000900
- Vuln IDs
-
- V-254062
- Rule IDs
-
- SV-254062r844219_rule
Checks: C-57514r844217_chk
Review the router OSPF or IS-IS configuration. Verify that LDP will synchronize with the link-state routing protocol. [edit protocols] ospf { area <number> { interface <name>.<logical unit> { authentication { md5 <key number> key "$8$aes256-gcm$hmac-sha2-256$100$LfJ7NdAYx/0$+4wGg1QJKLzkaAmVCGxBUQ$n0XxNofUtXE8aoJBhFNDDQ$uIDW/H+VY6U"; ## SECRET-DATA } ldp-synchronization { hold-time 10; } } interface <name>.<logical unit> { ipsec-sa <name>; ldp-synchronization { hold-time 10; } } } } ldp { interface <name>.<logical unit>; } -OR- isis { interface <name>.<logical unit> { ldp-synchronization { hold-time 10; } } level 1 authentication-key-chain <name>; level 2 authentication-key-chain <name>; } mpls { interface <name>.<logical unit>; } If the router is not configured to synchronize IGP and LDP, this is a finding.
Fix: F-57465r844218_fix
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. set protocols ospf area <number> interface <name>.<logical unit> authentication md5 <key number> <PSK> set protocols ospf area <number> interface <name>.<logical unit> ldp-synchronize hold-time 10 set protocols ldp interface <name>.<logical unit> -OR- set protocols isis level 1 authentication-key-chain <name> set protocols isis level 2 authentication-key-chain <name> set protocols isis interface <name>.<logical unit> ldp-synchronize hold-time 10 set protocols mpls interface <name>.<logical unit>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- JUEX-RT-000910
- Vuln IDs
-
- V-254063
- Rule IDs
-
- SV-254063r844222_rule
Checks: C-57515r844220_chk
Review the router configuration to verify that TTL propagation is disabled. [edit protocols mpls] no-propagate-ttl; If the router is not configured to disable TTL propagation, this is a finding.
Fix: F-57466r844221_fix
Configure LERs to disable TTL propagation. set protocols mpls no-propagate-ttl
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- JUEX-RT-000920
- Vuln IDs
-
- V-254064
- Rule IDs
-
- SV-254064r997537_rule
Checks: C-57516r844223_chk
Review the design plan for deploying L3VPN and VRF-lite. Review all CE-facing interfaces and verify that the proper VRF is defined. [edit interfaces] <ce-facing interface> { description "To customer 1"; unit <number> { family inet { address <IPv4 address>/<mask>; } family inet6 { address <IPv6 address>/<prefix>; } } } [edit routing-instances] <instance name> { description "To customer 1"; instance-type vrf; interface <ce-facing interface>.<logical unit>; route-distinguisher <Number in (16 bit:32 bit) or (32 bit 'L':16 bit) or (IP address:16 bit) format>; vrf-target <Target community to use in import and export>; vrf-table-label; protocols { ospf { area <number> { interface <ce-facing interface>.<logical unit>; } } } } Note: In L3 VPN, the CE router forms an adjacency with the PE router (OSPF in the example). If any VRFs are not bound to the appropriate physical or logical interface, this is a finding.
Fix: F-57467r844224_fix
Configure the PE router to have each VRF bound to the appropriate physical or logical interfaces to maintain traffic separation between all MPLS L3VPNs. set interfaces <ce facing interface> description <"appropriate description"> set interfaces <ce facing interface> unit <number> family inet address <IPv4 address>/<mask> set interfaces <ce facing interface> unit <number> family inet6 address <IPv6 address>/<prefix> set routing-instances <name> description <"appropriate description"> set routing-instances <name> instance-type vrf set routing-instances <name> interface <ce-facing interface>.<logical unit> set routing-instances <name> route-distinguisher <Number in (16 bit:32 bit) or (32 bit 'L':16 bit) or (IP address:16 bit) format> set routing-instances <name> vrf-target <Target community to use in import and export> set routing-instances <name> vrf-table-label set routing-instances <name> protocols ospf area <number> interface <ce-facing interface>.<logical unit>
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- JUEX-RT-000930
- Vuln IDs
-
- V-254065
- Rule IDs
-
- SV-254065r997538_rule
Checks: C-57517r844226_chk
Verify that the correct RT is configured for each VRF. Review the design plan for MPLS/L3VPN and VRF-lite to determine what RTs have been assigned for each VRF. Review the route-distinguisher and vrf-target statements under each configured VRF and verify that the correct RTs have been defined for each VRF. Assuming the assigned RT for "customer 1" is "cust1:33:33", verify vrf-target matches. [edit routing-instances] <instance name> { description "To customer 1"; instance-type vrf; interface <ce-facing interface>.<logical unit>; route-distinguisher 33:33; << Must match the design plan for "customer 1". vrf-target cust1:33:33; << Must match the design plan for "customer 1". vrf-table-label; protocols { ospf { area <number> { interface <ce-facing interface>.<logical unit>; } } } } Note: In L3 VPN, the CE router forms an adjacency with the PE router (OSPF in the example). If there are VRFs configured with the wrong RT, this is a finding.
Fix: F-57468r844227_fix
Configure all J-PE routers to have the correct VRF defined with the appropriate RT. set routing-instances <name> description <"appropriate description"> set routing-instances <name> instance-type vrf set routing-instances <name> interface <ce-facing interface>.<logical unit> set routing-instances <name> route-distinguisher 33:33 << Must match the design plan for "customer 1". set routing-instances <name> vrf-target cust1:33:33 << Must match the design plan for "customer 1". set routing-instances <name> vrf-table-label set routing-instances <name> protocols ospf area <number> interface <ce-facing interface>.<logical unit>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- JUEX-RT-000940
- Vuln IDs
-
- V-254066
- Rule IDs
-
- SV-254066r844231_rule
Checks: C-57518r844229_chk
Review the RDs that have been assigned for each VRF according to the plan provided by the ISSM. Review all VRFs configured on CE-facing interfaces and verify that the proper RD has been configured for each. Assuming the assigned RD for "customer 1" is "33:33", verify the route-distinguisher matches. [edit routing-instances] <instance name> { description "To customer 1"; instance-type vrf; interface <ce-facing interface>.<logical unit>; route-distinguisher 33:33; << Must match the design plan for "customer 1". vrf-target cust1:33:33; << Must match the design plan for "customer 1". vrf-table-label; protocols { ospf { area <number> { interface <ce-facing interface>.<logical unit>; } } } } Note: In L3 VPN, the CE router forms an adjacency with the PE router (OSPF in the example). If the wrong RD has been configured for any VRF, this is a finding.
Fix: F-57469r844230_fix
Configure the correct RD for each VRF. set routing-instances <name> description <"appropriate description"> set routing-instances <name> instance-type vrf set routing-instances <name> interface <ce-facing interface>.<logical unit> set routing-instances <name> route-distinguisher 33:33 << Must match the design plan for "customer 1". set routing-instances <name> vrf-target cust1:33:33 << Must match the design plan for "customer 1". set routing-instances <name> vrf-table-label set routing-instances <name> protocols ospf area <number> interface <ce-facing interface>.<logical unit>
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- JUEX-RT-000950
- Vuln IDs
-
- V-254067
- Rule IDs
-
- SV-254067r844234_rule
Checks: C-57519r844232_chk
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. [edit interfaces] <interface name> { encapsulation ethernet-ccc; unit <number> { <additional configuration> } } [edit protocols] l2circuit { neighbor 1.1.1.1 { interface <interface name>.<logical unit> { virtual-circuit-id <1..4294967295>; } } } 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.
Fix: F-57470r844233_fix
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. set interfaces <interface name> unit <number> encapsulation vlan-ccc set protocols l2circuit neighbor <neighbor> interface <interface>.<logical unit> virtual-circuit-id <1..4294967295>
- RMF Control
- CM-6
- Severity
- High
- CCI
- CCI-000366
- Version
- JUEX-RT-000960
- Vuln IDs
-
- V-254068
- Rule IDs
-
- SV-254068r997539_rule
Checks: C-57520r844235_chk
Review the implementation plan and the VPN IDs assigned to customer VLANs for the VPLS deployment. Review the PE router configuration to verify that customer attachment circuits (i.e., VLANs) are associated to the appropriate VPLS ID. 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. [edit] routing-instances { <instance name> { interface <interface name>.<logical unit>; protocols { vpls { vpls-id <VPLS ID>; neighbor <neighbor address>; } } } } } Note: Only EX9200-series devices currently support VPLS. If the attachment circuits have not been bound to the appropriate routing-instance with the assigned VPN ID for each associated VLAN, this is a finding.
Fix: F-57471r844236_fix
Assign globally unique VPN IDs for each customer VLAN using VPLS for carrier Ethernet services between multiple sites, and configure the attachment circuits to the appropriate VFI. set routing-instances <instance name> protocols vpls vpls-id <VPLS ID> neighbor <neighbor address>
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- JUEX-RT-000970
- Vuln IDs
-
- V-254069
- Rule IDs
-
- SV-254069r844240_rule
Checks: C-57521r844238_chk
Review the PE router configuration to verify that split horizon is enabled. By default, Juniper devices configured as PE routers and VPLS enforce split horizon operation. Except for H-VPLS, Juniper devices do not support disabling split horizon operation. LDP signaled VPLS requires a full mesh topology, which can lead to scaling issues. Hierarchical VPLS (H-VPLS) partitions the VPLS domains into mesh groups, reducing the required number of pseudo wires. However, the inner VPLS domain may require split horizon be disabled. Juniper devices support these scenarios with the "local-switching" command. Ensure mesh groups supporting H-VPLS do not have the "local-switching" directive enabled, unless required, as shown in the following example. Generally, only inner mesh groups (that is, a group "nested" within another) may require split horizon be disabled. [edit routing-instances <name> protocols vpls] mesh-group <name> { : local-switching; : } Note: Only EX9200-series devices currently support VPLS. If split horizon is disabled but not required to be, this is a finding. Note: In a ring VPLS, split horizon is disabled so that a PE router can forward a packet received from one pseudowire to another pseudowire. To prevent the consequential loop, at least one span in the ring would not have a pseudowire for any given VPLS instance.
Fix: F-57472r844239_fix
Enable split horizon on all PE routers deploying VPLS in a full-mesh configuration. There is no fix for full mesh VPLS because Juniper PE devices with VPLS do not support or require a CLI command to enable/disabled split horizon. Split horizon operation cannot be disabled. For H-VPLS, delete the "local-switching" directive for all inner mesh groups that do not require split horizon be disabled. delete routing-instances <name> protocols vpls mesh-group <name> local-switching
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- JUEX-RT-000980
- Vuln IDs
-
- V-254070
- Rule IDs
-
- SV-254070r844243_rule
Checks: C-57522r844241_chk
Review the router configuration to verify that a loopback address has been configured. Verify that a loopback interface is used as the source address for all MSDP packets generated by the router. [edit protocols] msdp { active-source-limit { maximum <1..1000000>; threshold <1..1000000>; log-warning <percent to log warning>; } local-address <lo0 address>; <additional configuration> peer <address> { active-source-limit { maximum <1..1000000>; threshold <1..1000000>; log-warning <percent to log warning>; } authentication-key "hashed PSK"; ## SECRET-DATA } } Note: Both the global, and the peer limit, are applied to every MSDP peer, and Junos applies the most restrictive limit. The maximum value sets the upper limit for source-active messages and the threshold value determines when Junos begins Random Early Detection (RED) dropping to alleviate congestion. The log-warning value is a percent where Junos begins generating syslog messages. If the router does not use its loopback address as the source address when originating MSDP traffic, this is a finding.
Fix: F-57473r844242_fix
Ensure that the router’s loopback address is used as the source address when originating traffic. set protocols msdp active-source-limit maximum <1..1000000> set protocols msdp active-source-limit threshold <1..1000000> set protocols msdp active-source-limit log-warning <percent to log warning> set protocols msdp local-address <lo0 address> <additional configuration> set protocols msdp peer <address> active-source-limit maximum <1..1000000> set protocols msdp peer <address> active-source-limit threshold <1..1000000> set protocols msdp peer <address> active-source-limit log-warning <percent to log warning> set protocols msdp peer <address> authentication-key <PSK>
- RMF Control
- CM-6
- Severity
- Low
- CCI
- CCI-000366
- Version
- JUEX-RT-000990
- Vuln IDs
-
- V-254071
- Rule IDs
-
- SV-254071r844246_rule
Checks: C-57523r844244_chk
This requirement is not applicable for the DODIN Backbone. Review the router configuration to determine if the hop limit has been configured for Router Advertisement messages. Verify each interface configured for router advertisements contains a hop limit of at least 32. [edit protocols] router-advertisement { interface ge-0/0/0.0 { : current-hop-limit 32; <<< Supported values: 0 - 255 : } } If it has been configured and has not been set to at least 32, it is a finding.
Fix: F-57474r844245_fix
Configure the router to advertise a hop limit of at least 32 in Router Advertisement messages. set protocols router-advertisement interface <internal interface> current-hop-limit <32 or greater>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- JUEX-RT-001000
- Vuln IDs
-
- V-254072
- Rule IDs
-
- SV-254072r844249_rule
Checks: C-57524r844247_chk
Review the router configuration to ensure FEC0::/10 IP addresses are not defined. Show the interface configuration using "show configuration interfaces" (from operational mode) or "show interfaces" (configuration mode at the top of the hierarchy). When showing the configuration, piping (|) to match or find (similar to *nix 'grep') will limit the search. For example, to limit the search to lines that include "FEC0": (operational mode) show configuration interfaces | match fec0 Returns the lines with 'fec0' but no surrounding context There should be no returned lines (operational mode) show configuration interfaces | find fec0 Returns the configuration with the first line containing 'fec0' Returns context (meaning can scroll up / down in the configuration) There should be no returned configuration If IPv6 Site Local Unicast addresses are defined, this is a finding.
Fix: F-57475r844248_fix
Configure the router using authorized IPv6 addresses. Delete unauthorized addresses: delete interfaces <interface name> unit <logical unit number> family inet6 address <unauth address>/<prefix> Configure authorized addresses: set interfaces <interface name> unit <logical unit number> family inet6 address <auth address>/<prefix>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- JUEX-RT-001010
- Vuln IDs
-
- V-254073
- Rule IDs
-
- SV-254073r844252_rule
Checks: C-57525r844250_chk
This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify Router Advertisements are suppressed on all external IPv6-enabled interfaces. By default, IPv6 router advertisements are disabled. Verify all configured interfaces are not external facing. [edit protocols] router-advertisement { interface <internal interface>.<logical unit> { managed-configuration; : : prefix <internal IPv6 prefix>; } } If the router is not configured to suppress Router Advertisements on all external IPv6-enabled interfaces, this is a finding.
Fix: F-57476r844251_fix
Configure the router to suppress Router Advertisements on all external IPv6-enabled interfaces. If IPv6 router advertisements are not used, even for internal interfaces, delete or deactivate the [edit protocols router-advertisement] stanza. [delete|deactivate] protocols router-advertisement Delete or deactivate router advertisements on external interfaces. [delete|deactivate] protocols router-advertisement interface <external interface>
- RMF Control
- CM-6
- Severity
- Medium
- CCI
- CCI-000366
- Version
- JUEX-RT-001020
- Vuln IDs
-
- V-254074
- Rule IDs
-
- SV-254074r844255_rule
Checks: C-57526r844253_chk
Determine if the router is configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. If it is not configured in accordance with the designated security configuration settings, this is a finding.
Fix: F-57477r844254_fix
Configure the router to be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.