Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Firewalls Rules of Thumb
  2. 2. Firewalls <ul><li>What is a Firewall </li></ul><ul><ul><li>Network Layer </li></ul></ul><ul><ul><li>Application Layer </li></ul></ul><ul><ul><li>Network Address Translations </li></ul></ul><ul><li>Appropriate use of Firewalls </li></ul><ul><li>Configuration considerations </li></ul>
  3. 3. What is a Firewall? <ul><li>A firewall's basic task is to transfer traffic between computer networks of different trust levels. Typical examples are the Internet which is a zone with no trust and an internal network which is a zone of higher trust. A zone with an intermediate trust level, situated between the Internet and a trusted internal network, is often referred to as a &quot;perimeter network&quot; or Demilitarized zone (DMZ). </li></ul>
  4. 4. What is a Firewall <ul><li>A firewall's function within a network is similar to firewalls in building construction, because in both cases they are intended to isolate one &quot;network&quot; or &quot;compartment&quot; from another. However, network firewalls, unlike physical firewalls, are designed to allow some traffic to flow. </li></ul>
  5. 5. What is a Firewall? <ul><li>Without proper configuration, a firewall can often become worthless. Standard security practices dictate a &quot;default-deny&quot; firewall ruleset, in which the only network connections which are allowed are the ones that have been explicitly allowed. Unfortunately, such a configuration requires detailed understanding of the network applications and endpoints required for the organization's day-to-day operation. Many businesses lack such understanding, and therefore implement a &quot;default-allow&quot; ruleset, in which all traffic is allowed unless it has been specifically blocked. This configuration makes inadvertent network connections and system compromise much more likely. </li></ul>
  6. 6. Types of Firewall <ul><li>Network layer firewalls, also called packet filters, operate at a relatively low level of the TCP/IP protocol stack not allowing packets to pass through the firewall unless they match the established ruleset. The firewall administrator may define the rules; or default rules may apply. </li></ul><ul><li>Network layer firewalls generally fall into two sub-categories, stateful and stateless. Stateful firewalls maintain context about active sessions, and use that &quot;state information&quot; to speed up packet processing. Any existing network connection can be described by several properties, including source and destination IP address, UDP or TCP ports, and the current stage of the connection's lifetime (including session initiation, handshaking, data transfer, or completion connection. If a packet does not match an existing connection, it will be evaluated according to the ruleset for new connections. If a packet matches an existing connection based on comparison with the firewall's state table, it will be allowed to pass without further processing. </li></ul>
  7. 7. Types of Firewalls <ul><li>Application-layer firewalls work on the application level of the TCP/IP stack (i.e., all browser traffic, or all telnet or ftp traffic), and may intercept all packets traveling to or from an application. They block other packets (usually dropping them without acknowledgement to the sender). In principle, application firewalls can prevent all unwanted outside traffic from reaching protected machines. </li></ul><ul><li>By inspecting all packets for improper content, firewalls can restrict or prevent outright the spread of networked computer worms and trojans. In practice, however, this becomes so complex and so difficult to attempt (given the variety of applications and the diversity of content each may allow in its packet traffic) that comprehensive firewall design does not generally attempt this approach </li></ul>
  8. 8. Types of Firewalls <ul><li> Network Address Translation ( NAT , also known as Network Masquerading , Native Address Translation or IP Masquerading ) involves re-writing the source and/or destination addresses of IP packets as they pass through a Router or firewall. Most systems using NAT do so in order to enable multiple hosts on a private network to access the Internet using a single public IP address. Many network administrators find NAT a convenient technique and use it widely. Nonetheless, NAT can introduce complications in communication between hosts and may have a performance impact </li></ul>
  9. 9. Types of Translation <ul><li>Network Address Translation </li></ul><ul><ul><li>One-to-One (One private address for One public address) </li></ul></ul><ul><ul><li>Geared for applications that require use of many ports/apps (i.e. ftp, www, 8081). </li></ul></ul><ul><li>Port Address Translation </li></ul><ul><ul><li>One-to-many (One public IP address is used, but specific ports are translated). </li></ul></ul><ul><ul><li>Geared for applications that only need 1 port in connection (i.e. basic web servers, e-mail). </li></ul></ul>
  10. 10. Appropriate use of Firewalls <ul><li>Firewalls are applicable when – </li></ul><ul><ul><li>When there is two networks that have a distinct trust factor (friend/foe). </li></ul></ul><ul><ul><li>When network topology is designed to flow all traffic thru a single interface which connects to the firewall (i.e. protected networks connection must terminate behind firewall). </li></ul></ul><ul><ul><li>When there is need for extra layer of protection for certain applications. </li></ul></ul>
  11. 11. Appropriate use of Firewalls <ul><li>Firewalls are NOT applicable when </li></ul><ul><ul><li>When applications that transverse two networks are QoS sensitive. </li></ul></ul><ul><ul><li>Vendors use scare tactics and not give a qualified reason for firewall. </li></ul></ul><ul><ul><li>When you are only support and haven’t been trained. </li></ul></ul><ul><ul><li>When application/resource accessibility is more critical than security (timing). </li></ul></ul>
  12. 12. Configuration Considerations <ul><li>By default, less trusted networks has NO access to the trusted network (deny all). </li></ul><ul><li>Be port specific as possible when allowing outside host to access applications. </li></ul><ul><li>Remember ANY means ANY in a firewall ruleset! Outside of web and e-mail, this should not be used to allow access into applications. </li></ul><ul><li>For vendor support, restrict access just to their network or IP Address. </li></ul><ul><li>Certain applications are very firewall sensitive (i.e. Voice, H323 or any QoS type apps). </li></ul>
  13. 13. Configuration Considerations <ul><li>Firewalls does not encrypt data unless specifically programmed( IPSec tunnel). </li></ul><ul><li>Rulesets/access-list will not work unless applied to interface. </li></ul><ul><li>When in doubt – call us! </li></ul>
  14. 14. <ul><li>Questions / Answers ??????????? </li></ul>