From Juniper Router RTR Security Technical Implementation Guide
Part of SRG-NET-000019-RTR-000002
Associated with: CCI-001414
Information flow control regulates authorized information to travel within a network and between interconnected networks. Controlling the flow of network traffic is critical so it does not introduce any unacceptable risk to the network infrastructure or data. An example of a flow control restriction is blocking outside traffic claiming to be from within the organization. For most routers, internal information flow control is a product of system design.
Review the router configuration to verify that firewall filters are configured to allow or deny traffic for specific source and destination addresses as well as ports and protocols. For example, the configuration below will allow only printer traffic into subnet 11.1.23.0/24 and SQL traffic into subnet 11.1.24.0/24. ICMP is allowed for troubleshooting and OSPF is the routing protocol used within the network. interfaces { ge-0/0/0 { unit 0 { family inet { filter { input FILTER_SERVER_TRAFFIC; } address 11.1.12.2/24; } } } … … … firewall { family inet { filter FILTER_SERVER_TRAFFIC { term PRINT_FILTER { from { destination-address { 11.1.23.0/24; } protocol tcp; destination-port [ 515 631 9100 ]; } then accept; } term SQL_FILTER { from { destination-address { 11.1.24.0/24; } protocol tcp; destination-port [ 1433 1434 4022 ]; } then accept; } term ALLOW_BGP { from { protocol tcp; destination-port bgp; } then accept; } term ALLOW_OSPF { from { protocol ospf; } then accept; } term ALLOW_ICMP { from { protocol icmp; } then accept; } term DENY_ALL_OTHER { then { syslog; reject; } } } If the router is not configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies, this is a finding.
This requirement is not applicable for the DoDIN Backbone. Configure firewall filters to allow or deny traffic for specific source and destination addresses as well as ports and protocols between various subnets as required. The commands used below were used to create the configuration as shown in the check content. [edit firewall family inet] set filter FILTER_SERVER_TRAFFIC term PRINT_FILTER from destination-address 11.1.23.0/24 set filter FILTER_SERVER_TRAFFIC term PRINT_FILTER from protocol tcp destination-port [515 631 9100] set filter FILTER_SERVER_TRAFFIC term PRINT_FILTER then accept set filter FILTER_SERVER_TRAFFIC term SQL_FILTER from destination-address 11.1.24.0/24 set filter FILTER_SERVER_TRAFFIC term SQL_FILTER from protocol tcp destination-port [1433 1434 4022] set filter FILTER_SERVER_TRAFFIC term SQL_FILTER then accept set filter FILTER_SERVER_TRAFFIC term ALLOW_OSPF from protocol ospf set filter FILTER_SERVER_TRAFFIC term ALLOW_OSPF then accept set filter FILTER_SERVER_TRAFFIC term ALLOW_ICMP from protocol icmp set filter FILTER_SERVER_TRAFFIC term ALLOW_ICMP then accept set filter FILTER_SERVER_TRAFFIC term DENY_ALL_OTHER then syslog reject Apply the filter inbound on all applicable interfaces. [edit interfaces ge-0/0/0 unit 0 family inet] set filter input FILTER_SERVER_TRAFFIC
Lavender hyperlinks in small type off to the right (of CSS
class id, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle or
Accept: application/rdf+xml.
Powered by sagemincer