DOCSLIB.ORG

Guidelines on Firewalls and Firewall Policy (Draft)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Guidelines on Firewalls and Firewall Policy (Draft) Special Publication 800-41 Revision 1 (Draft) Guidelines on Firewalls and Firewall Policy (Draft) Recommendations of the National Institute of Standards and Technology Karen Scarfone Paul Hoffman NIST Special Publication 800-41 Guidelines on Firewalls and Firewall Revision 1 (Draft) Policy (Draft) Recommendations of the National Institute of Standards and Technology Karen Scarfone Paul Hoffman C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 July 2008 U.S. Department of Commerce Carlos M. Gutierrez, Secretary National Institute of Standards and Technology James M. Turner, Deputy Director GUIDELINES ON FIREWALLS AND FIREWALL POLICY (DRAFT) Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL’s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-41 Revision 1 (Draft) Natl. Inst. Stand. Technol. Spec. Publ. 800-41 rev1, 43 pages (Jul. 2008) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessa rily the best available for the purpose. iii GUIDELINES ON FIREWALLS AND FIREWALL POLICY (DRAFT) Acknowledgements The authors, Karen Scarfone of the National Institute of Standards and Technology (NIST) and Paul Hoffman of the Virtual Private Network Consortium (VPNC), wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content. The authors would like to acknowledge Tim Grance of NIST, and Matthew Goche, David Klug, Logan Lodge, John Pearce, Noel Richards, Anne Roudabush, and Steven Sharma of Booz Allen Hamilton, for their keen and insightful assistance throughout the development of the document. Special thanks go to Brahim Asfahani of Booz Allen Hamilton for his contributions to early drafts of the document. The authors also wish to express their thanks to the individuals and organizations that contributed to the original version of the publication, including John Wack of NIST and Ken Cutler and Jamie Pole of the MIS Training Institute, who authored the original version, and other contributors and reviewers— particularly Peter Batista and Wayne Bavry (U.S. Treasury); Harriet Feldman (Integrated Computer Engineering, Inc.); Rex Sanders (U.S. Geological Survey); and Timothy Grance, D. Richard Kuhn, Peter Mell, Gale Richter, and Murugiah Souppaya (NIST). Additional acknowledgements will be added to the final version of the publication. iv GUIDELINES ON FIREWALLS AND FIREWALL POLICY (DRAFT) Table of Contents Executive Summary..............................................................................................................ES-1 1. Introduction ......................................................................................................................1-1 1.1 Authority...................................................................................................................1-1 1.2 Purpose and Scope .................................................................................................1-1 1.3 Audience ..................................................................................................................1-1 1.4 Document Structure .................................................................................................1-1 2. Overview of Firewall Technologies ................................................................................2-1 2.1 Firewall Technologies ..............................................................................................2-2 2.1.1 Packet Filtering.............................................................................................2-2 2.1.2 Stateful Inspection ........................................................................................2-3 2.1.3 Application-Proxy Gateways.........................................................................2-5 2.1.4 Circuit-Level Gateways.................................................................................2-6 2.1.5 Dedicated Proxy Servers..............................................................................2-6 2.1.6 Virtual Private Networking ............................................................................2-8 2.2 Locations for Firewalls .............................................................................................2-8 2.2.1 Host-Based Firewalls and Personal Firewalls ..............................................2-9 2.2.2 Personal Firewall Appliances .....................................................................2-10 2.2.3 Distributed Firewalling ................................................................................2-10 2.3 Function-Specific Firewalls ....................................................................................2-10 2.3.1 PBX Firewall ...............................................................................................2-10 2.3.2 XML Firewall...............................................................................................2-11 2.3.3 Email Firewall .............................................................................................2-11 3. Firewalls and Network Architectures .............................................................................3-1 3.1 Network Layouts with Firewalls................................................................................3-1 3.2 Architecture with Multiple Layers of Firewalls ..........................................................3-3 4. Firewall Policy ..................................................................................................................4-1 4.1 Policies Based on IP Addresses and Protocols .......................................................4-1 4.1.1 IP Addresses and Other IP Characteristics ..................................................4-1 4.1.2 IPv6 ..............................................................................................................4-3 4.1.3 TCP and UDP...............................................................................................4-3 4.1.4 ICMP.............................................................................................................4-4 4.1.5 IPsec Protocols.............................................................................................4-4 4.2 Policies Based on Applications ................................................................................4-5 5. Firewall Planning and Implementation...........................................................................5-1 5.1 Plan..........................................................................................................................5-1 5.2 Configure .................................................................................................................5-3 5.2.1 Hardware and Software................................................................................5-3 5.2.2 Configure Rulesets .......................................................................................5-3 5.2.3 Configure Logging and Alerts .......................................................................5-4 5.3 Test ..........................................................................................................................5-4 5.4 Deploy......................................................................................................................5-5 5.5 Manage ....................................................................................................................5-5 5.6 General Recommendations .....................................................................................5-6 v GUIDELINES ON FIREWALLS AND FIREWALL POLICY (DRAFT) List of Appendices Appendix A— Glossary .......................................................................................................... A-1 Appendix B— Acronyms and Abbreviations ....................................................................... B-1 Appendix C— Resources ....................................................................................................... C-1 List of Figures Figure 2-1. TCP/IP Layers ........................................................................................................2-1 Figure 2-2. Packet Filter Used as Boundary Router .................................................................2-3 Figure 2-3. Typical Proxy Agents..............................................................................................2-5
Load more

Recommended publications
  • ITU Botnet Mitigation Toolkit Background Information
    ITU Botnet Mitigation Toolkit Background Information ICT Applications and Cybersecurity Division Policies and Strategies Department ITU Telecommunication Development Sector January 2008 Acknowledgements Botnets (also called zombie armies or drone armies) are networks of compromised computers infected with viruses or malware to turn them into “zombies” or “robots” – computers that can be controlled without the owners’ knowledge. Criminals can use the collective computing power and connected bandwidth of these externally-controlled networks for malicious purposes and criminal activities, including, inter alia, generation of spam e-mails, launching of Distributed Denial of Service (DDoS) attacks, alteration or destruction of data, and identity theft. The threat from botnets is growing fast. The latest (2007) generation of botnets such as the Storm Worm uses particularly aggressive techniques such as fast-flux networks and striking back with DDoS attacks against security vendors trying to mitigate them. An underground economy has now sprung up around botnets, yielding significant revenues for authors of computer viruses, botnet controllers and criminals who commission this illegal activity by renting botnets. In response to this growing threat, ITU is developing a Botnet Mitigation Toolkit to assist in mitigating the problem of botnets. This document provides background information on the toolkit. The toolkit, developed by Mr. Suresh Ramasubramanian, draws on existing resources, identifies relevant local and international stakeholders, and
    [Show full text]
  • Guidelines on Firewalls and Firewall Policy
    Special Publication 800-41 Revision 1 Guidelines on Firewalls and Firewall Policy Recommendations of the National Institute of Standards and Technology Karen Scarfone Paul Hoffman NIST Special Publication 800-41 Guidelines on Firewalls and Firewall Revision 1 Policy Recommendations of the National Institute of Standards and Technology Karen Scarfone Paul Hoffman C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 September 2009 U.S. Department of Commerce Gary Locke, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Deputy Director GUIDELINES ON FIREWALLS AND FIREWALL POLICY Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL’s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-41 Revision 1 Natl. Inst. Stand. Technol. Spec. Publ. 800-41 rev1, 48 pages (Sep. 2009) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately.
    [Show full text]
  • Firewalls and IDS
    Firewalls and IDS Dr. Natarajan Meghanathan Associate Professor of Computer Science Jackson State University E-mail: [email protected] Firewalls • A firewall is a device that filters traffic between a “protected” or inside network and a “less trustworthy” or outside network. • A firewall is basically an executable code run on a dedicated computer. • As all traffic should pass through the firewall, it is not a point of bottleneck for system performance and hence non-firewall functions are not performed on that machine running the firewall. • Also, since non-firewall code does not exist in the computer, it is hard for an attacker to make use of any vulnerability to compromise the firewall. • Design idea: – Firewalls implement a security policy that is specifically designed to address what bad things that should not happen in a “protected environment” – Security policies that dictate what to allow: Standard security practices dictate a “default-deny” ruleset for firewalls, implying that the only network connections allowed are the ones that have been explicitly stated to be allowed. – Security policies that dictate what not to allow: Users and business community who lack such a detailed understanding to explicitly state what should be allowed in prefer a “default-allow” ruleset, in which all traffic is allowed unless it has been specifically blocked. – Even though this configuration is relatively more prone to inadvertent network connections and system compromise, it is more commonly used because of mere lack of knowledge and new applications that come into existence. Firewalls • Not all firewalls need to have the same capability. • One cannot compare the “goodness” of two firewalls based on the security policies they are configured with.
    [Show full text]
  • Block Spoofed Packets at Source (BSPS): a Method for Detecting And
    International Journal of Networks and Communications 2012, 2(3): 33-37 DOI: 10.5923/j.ijnc.20120203.03 Block Spoofed Packets at Source (BSPS): A method for Detecting and Preventing All Types of Spoofed Source IP Packets and SYN Flooding Packets at Source: A Theoretical Framework Noureldien A. Noureldien, Mashair O. Hussein* Department of Computer Science, University of Science and Technology, Omdurman, Sudan Abstract In this paper, we present a theoretical framework for a simple and efficient method that detects and blocks source IP spoofed packets and TCP/SYN flooding packets at source. The method is based on a network authentication server (AS), which performs an authentication process on SYN packets. The authentication process verifies the legitimacy of SYN packet’s source IP address that initiate a connection request from a network subnet host to an external host. During the authentication process of SYN packets, AS identifies and blocks SYN packets with legal source IP address that chip in a TCP/SYN flooding attack. AS preserves network performance by exchanging authentication messages in plain text, and acts as a stateful inspection firewall and only SYN packets are subject for inspection. Our method which is capable to de- tect and prevent all types of spoofing packets including subnet spoofing contributes to standard ingress/egress methods in eliminating bogus traffic on the Internet. Keywords IP Spoofing, SYN Flooding, Authentication stamping packets with them. An En Route Spoofed Source 1. Introduction Address attack would spoof the address of a machine or subnet that lies along the path from the agent machine to the On TCP/IP networks, packets sent from one host to an- victim.
    [Show full text]
  • Botnets and Distributed Denial of Service Attacks a Project Report
    Botnets and Distributed Denial of Service Attacks A Project Report Presented to The Faculty of the Department of Computer Science San Jose State University In Partial Fulfillment of the Requirements for the Degree Master of Computer Science by Anilkumar Panicker December 2008 © 2008 Anilkumar Panicker ALL RIGHTS RESEREVED 2 APPROVED FOR THE DEPARTMENT OF COMPUTER SCIENCE Dr. Mark Stamp Dr. Robert Chun Dr. Teng Moh APPROVED FOR THE UNIVERSITY 3 ABSTRACT Botnets and Distributed Denial of Service Attacks With their ever increasing malicious capabilities and potential to infect a vast majority of computers on the Internet, botnets are emerging as the single biggest threat to Internet security. The aim of this project is to perform a detailed analysis of botnets and the vulnerabilities exploited by them to spread themselves and perform various malicious activities such as DDoS attacks. DDoS attacks are without doubt the most potent form of attacks carried out by botnets. In order to better understand this growing phenomenon and develop effective counter measures, it is necessary to be able to simulate DDoS attacks in a controlled environment. Simulating a DDoS attack with control over various simulation and attack parameters will give us insights into how attacks achieve stealth and avoid detection. A detailed analysis of existing DDoS defense strategies and proposals combined with the insights derived from simulation should enable us to come up with innovative and feasible solutions to prevent and mitigate DDoS attacks carried out using Botnets 4 ACKOWLEDGEMETS I would like to thank Dr. Mark Stamp for his guidance and support throughout the past year.
    [Show full text]
  • Guidelines on Firewalls and Firewall Policy
    Special Publication 800-41 Revision 1 Guidelines on Firewalls and Firewall Policy Recommendations of the National Institute of Standards and Technology Karen Scarfone Paul Hoffman NIST Special Publication 800-41 Guidelines on Firewalls and Firewall Revision 1 Policy Recommendations of the National Institute of Standards and Technology Karen Scarfone Paul Hoffman C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 September 2009 U.S. Department of Commerce Gary Locke, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Deputy Director GUIDELINES ON FIREWALLS AND FIREWALL POLICY Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL’s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-41 Revision 1 Natl. Inst. Stand. Technol. Spec. Publ. 800-41 rev1, 48 pages (Sep. 2009) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately.
    [Show full text]
  • IP Networking Part 5 ‐ Building the KSBE Network “A Webinar to Help You Prepare for the CBNE™ Certification”
    IP Networking Part 5 ‐ Building the KSBE Network “A webinar to help you prepare for the CBNE™ Certification” Wayne M. Pecena, CPBE, CBNE Texas A&M Information Technology Educational Broadcast Services IP Networking‐Part 5 ‐ Building the KSBE Network “A webinar to help you ppprepare for the CBNE™ Certification” Advertised Presentation Scope: The IP Networking webinar series continues with part 5 focusing on “Building the KSBE Network", by applying the concepts addressed in the first 4 parts of the IP Networking Webinar series. The end result of this webinar will be an understanding of how to build an IP network infrastructure often found in a broadcast environment. The “KSBE Network” will address layered IP netwo rk des ig n, app licat io n o f a n IP add ress ing p la n, use of VLAN’ s, r outin g pr otocol s, securin g th e n etw ork , an d access to the network through a secure VPN connection. The IP Networking Webinar series is focused on enhancing the Broadcast Engineers knowledge of the technology and practical concepts of IP Networking in the broadcast plant. In addition, the webinar series provides an excellent tutorial for those preparing for SBE networking certifications such as the CBNE. My Goals & Deliverables for This Afternoon: ‐ Provide an Awareness of Network Design Principals ‐ Provide an Understanding of Factors in Network Design ‐ Provide a Foundation for SBE CBNT & CBNE Certification Exams ‐ Provide Reference Material & Resources to Obtain Further Knowledge 2 Agenda • Introduction • Network Design Concepts • Layered
    [Show full text]
  • Spam Filter Protocol and Port Number
    Spam Filter Protocol And Port Number Davey unpinned daintily as green Jose deports her betrayers grabs little. Remindful Glynn still swim: crowning and fell Randal measure quite waveringly but reallocated her parchment rancorously. Bothered and boxlike Bear corrugates his sommeliers exteriorizing emotes probably. Use Telnet to test port 339 functionality Windows Client Microsoft. USI Access Control Filters USInternet. Tables show the firewall access required and optional TCP and UDP ports for the. MailCleaner Spam Filter How about Open a Port Add IPTables Firewall Rules. Symantec Mail Security for Microsoft Exchange Server 791. How moving I may if a port is open? Statistical document within it fit into all sizes of protocol and port number. This reduces the traffic to be analyzed for spam and viruses up to 90 and. Firewalls CSIAC. Spam and inappropriate content from entering the network. Chapter 4 Using the Barracuda Spam Firewall to Filter Your Emails65. Ham passwords are often combined with filtering systems which let through in those messages that. Protocol and therefore requires port 123 to flush open for inbound and outbound UDP. Connecting to the Internet will advise a lot safer for blonde and practice family Ports Transport Protocol Direction Filtered 25 TCP SMTP BOTH 0 TCP HTTP. Particular combination of port number and transport protocol on that ISP regardless. The newer protocol imap the Internet message access protocol uses port 143. SMTP Service Simple Mail Transfer Protocol is smile of those protocols which allow you to this relay. Like 57 to estimate the SMTP relay right and neck reduce the corn of spamming.
    [Show full text]
  • A Comprehensive Analysis of Spoofing
    (IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 1, No.6, December 2010 A Comprehensive Analysis of Spoofing P. Ramesh Babu D.Lalitha Bhaskari CH.Satyanarayana Dept of Information Technology Dept of C.S & S.E Dept of C.S.E Rajamahendri Inst. of Engg & AU College of Engineering (A) JNTUK College of Engineering Technology Visakhapatnam-530003, INDIA Kakinada – 533003, INDIA Rajahmundry-533103, INDIA E-mail:[email protected] E-mail: [email protected] E-mail:[email protected] Abstract--The main intention of writing this paper is to enable source address indicating that the packet is coming from a the students, computer users and novice researchers about trusted port or system. Attackers must go through some spoofing attacks. Spoofing means impersonating another person complicated steps to accomplish the task [1]. They must: or computer, usually by providing false information (E-mail name, URL or IP address). Spoofing can take on many forms in Obtain a target. the computer world, all of which involve some type false Obtain an IP address of a trusted machine. representation of information. There are a variety of methods Disable communication of the trusted machine (e.g. and types of spoofing. We would like to introduce and explain SYN flooding). following spoofing attacks in this paper: IP, ARP, E-Mail, Web, and DNS spoofing. There are no legal or constructive uses for Sample a communication between the target and implementing spoofing of any type. Some of the outcomes might trusted hosts be sport, theft, vindication or some other malicious goal.
    [Show full text]
  • NIST SP 800-41, Revision 1, Guidelines on Firewalls And
    Special Publication 800-41 Revision 1 Guidelines on Firewalls and Firewall Policy Recommendations of the National Institute of Standards and Technology Karen Scarfone Paul Hoffman NIST Special Publication 800-41 Guidelines on Firewalls and Firewall Revision 1 Policy Recommendations of the National Institute of Standards and Technology Karen Scarfone Paul Hoffman C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 September 2009 U.S. Department of Commerce Gary Locke, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Deputy Director GUIDELINES ON FIREWALLS AND FIREWALL POLICY Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL’s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-41 Revision 1 Natl. Inst. Stand. Technol. Spec. Publ. 800-41 rev1, 48 pages (Sep. 2009) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately.
    [Show full text]
  • 2021 International Botnet and Iot Security Guide
    INTERNATIONAL BOTNET AND IOT SECURITY GUIDE 2021 NOTICE The International Botnet and IoT Security Guide was developed to facilitate the mitigation of botnets and other automated, distributed threats through voluntary participation and collaboration among disparate stakeholders throughout the global internet and communications ecosystem. The Guide provides information and encouragement to Information and Communications Technology (ICT) stakeholders about affirmative measures to implement towards this goal as they deem appropriate, based upon their individual circumstances and their relationships with each other. The Guide highlights impactful voluntary practices for each segment of the ICT sector, ranging from “baseline” to “advanced.” While the industry leaders who have developed this Guide recognize that no combination of measures can guarantee the elimination of all threats and risks, they believe these practices, both baseline and advanced, present a valuable framework for ICT stakeholders to reference in identifying and choosing practices of their own to mitigate the threats of automated, distributed attacks. The Guide recognizes that different ICT stakeholders face different challenges, considerations, and priorities as they implement security measures. Accordingly, the practices identified in this Guide, and the Guide as a whole, are tools that ICT stakeholders should implement according to their circumstances; they are not requirements or mandates, or otherwise compulsory in any way. Many of the practices and technologies discussed in this document are already being used by large-scale enterprises to protect their networks and systems, ranging from contracting for deep packet inspection (DPI) from network service providers to prohibiting the use of devices that do not have sufficient built-in security measures. However, the implementation of these capabilities in the wider consumer space has broader policy implications.
    [Show full text]
  • Linux Firewall Exploration Lab 1
    SEED Labs – Linux Firewall Exploration Lab 1 Linux Firewall Exploration Lab Copyright c 2006 - 2014 Wenliang Du, Syracuse University. The development of this document is/was funded by three grants from the US National Science Foundation: Awards No. 0231122 and 0618680 from TUES/CCLI and Award No. 1017771 from Trustworthy Computing. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation. A copy of the license can be found at http://www.gnu.org/licenses/fdl.html. 1 Overview The learning objective of this lab is for students to gain the insights on how firewalls work by playing with firewall software and implement a simplified packet filtering firewall. Firewalls have several types; in this lab, we focus on two types, the packet filter and application firewall. Packet filters act by inspecting the packets; if a packet matches the packet filter’s set of rules, the packet filter will either drop the packet or forward it, depending on what the rules say. Packet filters are usually stateless; they filter each packet based only on the information contained in that packet, without paying attention to whether a packet is part of an existing stream of traffic. Packet filters often use a combination of the packet’s source and destination address, its protocol, and, for TCP and UDP traffic, port numbers. Application firewall works at the appli- cation layer. A widely used application firewall is web proxy, which is primarily used for egress filtering of web traffic.
    [Show full text]