cse543 computer and network security module firewalls
play

CSE543 - Computer and Network Security Module: Firewalls Professor - PowerPoint PPT Presentation


  1. ������� ��� �������� �������������� �������� � � ������� ��� �������� �������� ������ ���������� �� �������� ������� ��� ����������� ������������ ����� ��������������������� ���� �� CSE543 - Computer and Network Security Module: Firewalls Professor Patrick McDaniel Fall 2011 CMPSC443 - Introduction to Computer and Network Security Page 1

  2. Firewalls • A firewall ... is a physical barrier inside a building or vehicle, designed to limit the spread of fire, heat and structural collapse. CMPSC443 - Introduction to Computer and Network Security Page 2

  3. Filtering: Firewalls • Filtering traffic based on policy ‣ Policy determines what is acceptable traffic ‣ Access control over traffic ‣ Accept or deny Application • May perform other duties ‣ Logging (forensics, SLA) Network ‣ Flagging (intrusion detection) ‣ QOS (differentiated services) Link CMPSC443 - Introduction to Computer and Network Security Page 3

  4. IP Firewall Policy • Specifies what traffic is (not) allowed ‣ Maps attributes to address and ports ‣ Example: HTTP should be allowed to any external host, but inbound only to web-server CMPSC443 - Introduction to Computer and Network Security Page 4

  5. X-Listing • Blacklisting - specifying specific connectivity that is explicitly disallowed ‣ E.g., prevent connections from badguys.com • Whitelisting - specifying specific connectivity that explicitly allowed ‣ E.g., allow connections from goodguys.com • These is useful for IP filtering, SPAM mitigation, … • Q: What access control policies do these represent? CMPSC443 - Introduction to Computer and Network Security Page 5

  6. Stateful, Proxy, and Transparent • Single packet contains insufficient data to make access control decision ‣ Stateful: allows historical context consideration ‣ Firewall collects data over time • e.g., TCP packet is part of established session • Firewalls can affect network traffic ‣ Transparent: appear as a single router (network) ‣ Proxy: receives, interprets, and reinitiates communication (application) ‣ Transparent good for speed (routers), proxies good for complex state (applications) CMPSC443 - Introduction to Computer and Network Security Page 6

  7. DMZ (De-militarized Zone) (servers) LAN LAN Internet • Zone between LAN and Internet ( public facing ) CMPSC443 - Introduction to Computer and Network Security Page 7

  8. Practical Issues and Limitations • Network layer firewalls are dominant ‣ DMZs allow multi-tiered fire-walling ‣ Tools are widely available and mature ‣ Personal firewalls gaining popularity • Issues ‣ Network perimeters not quite as clear as before • E.g., telecommuters, VPNs, wireless, … ‣ Every access point must be protected • E.g., this is why war-dialing/driving is effective ‣ Hard to debug, maintain consistency and correctness ‣ Often seen by non-security personnel as impediment • E.g., Just open port X so I can use my wonder widget … • SOAP - why is this protocol an issue? CMPSC443 - Introduction to Computer and Network Security Page 8

  9. The Wool firewall study .. • 12 error classes ‣ No default policy, automatic broad tools ‣ NetBIOS (the very use of the Win protocol deemed error) ‣ Portmapper protocols ‣ Use of “any wildcards” ‣ Lack of egress rules • Interesting questions: ‣ Is the violation of Wool’s errors really a problem? ‣ “DNS attack” comment? ‣ Why do you think more expensive firewalls had a higher occurrence of errors? • Take away: configurations are bad CMPSC443 - Introduction to Computer and Network Security Page 9

  10. Practical Firewall Implementations • Primary task is to filter packets ‣ But systems and requirements are complex • Consider ‣ All the protocols and services ‣ Stateless vs. stateful firewalls ‣ Network function: NAT, forwarding, etc. • Practical implementation: Linux iptables ‣ http://www.netfilter.org/documentation/HOWTO/packet- filtering-HOWTO.html ‣ http://linux.web.cern.ch/linux/scientific3/docs/rhel-rg-en-3/ch- iptables.html CMPSC443 - Introduction to Computer and Network Security Page 10

  11. Netfilter hook • Series of hooks in Linux network protocol stack • An iptable rule set is evaluated at each ‣ “PREROUTING”: before routing ‣ “INPUT”: inbound to local destination ‣ “FORWARD”: inbound but routed off host ‣ “OUTPUT”: outbound to remote destination ‣ “POSTROUTING”: after routing Preroute Routing Forward Postroute Input Output CMPSC443 - Introduction to Computer and Network Security Page 11

  12. iptables Concepts The iptables firewall looks in the firewall table to seek if the chain associated with the current hook matches a packet, and executes the target if it does. • Table : allows policies to be cleanly separated by purpose (default: “-t filter”, also: “-t nat”, “-t mangle” and “-t raw”) Each table as a set of default chains. • Chain : list of rules associated with the chain identifier, e.g., hook name (INPUT, OUTPUT, etc) • Match : when all a rule’s field match the packet • Target : operation to execute on a packet given a match CMPSC443 - Introduction to Computer and Network Security Page 12

  13. Table/Chain Traversal http://www.linuxtopia.org/Linux_Firewall_iptables/c951.html CMPSC443 - Introduction to Computer and Network Security Page 13

  14. iptables Commands iptables [-t <table_name>] <cmd> <chain> <plist> • Commands ‣ Append rule to end or specific location in chain ‣ Delete a specific rule in a chain ‣ Flush a chain ‣ List a chain ‣ Create a new user-specified chain ‣ Replace a rule CMPSC443 - Introduction to Computer and Network Security Page 14

  15. iptables Rule Parameters • Things you can match on ‣ Destination/Source • IP address range and netmask ‣ Protocol of packet • ICMP , TCP , etc ‣ Fragmented only ‣ Incoming/outgoing interface ‣ Target on rule match CMPSC443 - Introduction to Computer and Network Security Page 15

  16. Test it out • PING on localhost ‣ ping -c 1 127.0.0.1 • Add iptables rule to block ‣ iptables -A INPUT -s 127.0.0.1 -p icmp -j DROP • Try ping • Delete the rule ‣ iptables -D INPUT 1 ‣ iptables -D INPUT -s 127.0.0.1 -p icmp -j DROP ‣ iptables -F INPUT CMPSC443 - Introduction to Computer and Network Security Page 16

  17. Testing • Use loopback to test the rules locally on your machine ‣ IP address 127.0.0.1 • ICMP ‣ submit ping requests to 127.0.0.1 as above • TCP ‣ submit requests to 127.0.0.1 at specific port ‣ server • nc -l -p 3750 • listen at port 3750 ‣ client • nc -p 3000 localhost 3750 • send from port 3000 to localhost at port 3750 CMPSC443 - Introduction to Computer and Network Security Page 17

  18. Per Protocol Options • Specialized matching options for rules ‣ Specific to protocol • TCP ‣ Source/destination ports ‣ SYN ‣ TCP flags CMPSC443 - Introduction to Computer and Network Security Page 18

  19. Targets • Define what to do with the packet at this time • ACCEPT/DROP • QUEUE for user-space application • LOG any packet that matches • REJECT drops and returns error packet • RETURN enables packet to return to previous chain • <user-specified> passes packet to that chain CMPSC443 - Introduction to Computer and Network Security Page 19

  20. Examples iptables -A INPUT -s 200.200.200.2 -j ACCEPT iptables -A INPUT -s 200.200.200.1 -j DROP iptables -A INPUT -s 200.200.200.1 -p tcp -j DROP iptables -A INPUT -s 200.200.200.1 -p tcp --dport telnet -j DROP iptables -A INPUT -p tcp --destination-port telnet -i ppp0 -j DROP CMPSC443 - Introduction to Computer and Network Security Page 20

  21. Best Rule Placement? • An iptable rule set is evaluated at each ‣ “PREROUTING”: before routing ‣ “INPUT”: inbound to local destination ‣ “FORWARD”: inbound but routed off host ‣ “OUTPUT”: outbound to remote destination ‣ “POSTROUTING”: after routing Preroute Routing Forward Postroute Input Output CMPSC443 - Introduction to Computer and Network Security Page 21

  22. Example: Gateway/DMZ Firewalls • Assume you have two firewalls (FW1 and FW2), each with FW2 FW1 two ethernet interfaces eth0 eth1 eth0 eth1 (eth0 and eth1). • FW1 protects the DMZ, and FW2 protects the LAN • Define an iptables policy for FW1 that ‣ Allows new Internet traffic to reach port 80 on 10.0.1.13 ‣ Does not allow traffic to reach the LAN (10.0.2.0/24) • Define an iptables policy for FW2 that ‣ Allows internal hosts to reach the webserver, but nothing else in the DMZ (10.0.1.0/24) ‣ Prevents DMZ hosts from initiating connections to LAN CMPSC443 - Introduction to Computer and Network Security Page 22

Recommend


More recommend