1. Winter 2005 CMPE 151: Network Administration Network Gateways

2. Winter 2005 Announcements Guest lectures on 03.01 and 03.03. “Live test: Feb. 22 nd.

3. Winter 2005 Announcements Final project: Project proposals due by 02.19. Proposals: plain text e-mail to katia, isolis, and awander@soe.awander@soe

4. Winter 2005 Announcements Project presentations. Final exam day. Everyone needs to show up and stay for the whole time! Project reports: due by final exam day (midnight). Final exam date schedule: Friday, March 18 th, 8-11am. Can we slide it to a later slot?

5. Winter 2005 Project report Self-contained. Follow structure of a submission to a technical conference. Approximately 5-7 pages. Electronic submission. Only pdf submissions will be considered. E-mail to katia, isolis, awander@soe.

6. Winter 2005 Project report structure Abstract. Introduction/Motivation. Background. Approach. “Results”. Conclusions. Learning experience, etc.

7. Winter 2005 Project 6: Network Gateway Firewall. NAT.

8. Winter 2005 Firewalls What is a firewall? Security at the network level. Wide-area network access makes vital information/resources available (corporations, educational and research institutions). But, security threats from (mainly) the “outside world”. Secure each machine and/or protect the whole network.

9. Winter 2005 Firewalls “Outer security wall”. Protect organization’s network from attacks originating outside network. Also, single “choke point” for security and auditing purposes. Firewall can be a single machine or a group of machines performing the firewall functions collaboratively.

10. Winter 2005 Firewalls (cont’d) Convenient location for other “Internet- related” functions, e.g., NAT’ing, auditing Internet usage, Web proxies, etc.

11. Winter 2005 Firewall operation All incoming/outgoing traffic must pass through firewall. Only authorized traffic (as defined by local security policies) allowed to pass. Firewall itself immune to penetration (trusted system + secure OS).

12. Winter 2005 Types of access control Service control: types of service that can be accessed (inside and outside). Filtering based on IP address and TCP port #. Proxy services that receives and interprets traffic. May host service, e.g., Web server. Direction control: determines directions in which certain traffic allowed to flow.

13. Winter 2005 Types of access control (cont’d) User control: determines which user allowed to access which service. Behavior control: controls access to particular services (e.g., filtering out e- mail spam, enabling external access to only portion of Web server information, etc.).

14. Winter 2005 Types of firewalls Packet-filtering. Application-level. Stateful inspection. Circuit-level.

15. Winter 2005 Packet-filtering firewalls Restricts type of traffic that go through. Applies set of rules to each IP packet. Decides to forward or discard it. Filters packets in both directions. Filtering based on packet header (IP and transport) information (e.g., destination/source address, port number, IP protocol field).

16. Winter 2005 Rules Consist of and. : IP/TCP/UDP fields and values. : discard or forward. Default policies: Discard: whatever is not expressly permitted is discarded. Forward: … Rules are added as new threats become known.

17. Winter 2005 Example rules actionourhostporttheirhostport allow OUR-GW 25 * * block * * SPIGOT *

18. Winter 2005 Observations Service-specific filtering based on client using non-privileged port to contact privileged server port. FTP uses 2 TCP connections: one for control and another for data. Client initiates control connection and server initiates data connection. If FTP is allowed, need to allow inbound access to all non-privileged (> 1024) TCP ports.

19. Winter 2005 Two-stage filtering One machine gateways to the Internet; the other lies between the outer gateway and the rest of the local net. Outer gateway relatively open. Inner gateway very conservative. FTP and other “less secure” network services available from outer gateway.

20. Winter 2005 Limitations Cannot protect against attacks bypassing the firewall (e.g., local users with dial-up connections to ISP). Cannot protect against internal threats (e.g., malicious local user). Cannot protect against transfer of virus- infected files.

21. Winter 2005 Application-level firewalls Also called service proxy firewalls. Acts as relay for application-level traffic. Intercepts connections to/from outside world and establish connections to service outside/inside local network. User contacts firewall using specific application (e.g., telnet, http, etc.); firewall contacts remote host and relays application traffic between two endpoints. Firewall must support specific applications.

22. Winter 2005 Observations Application-level firewalls tend to be more secure: they only need to secure a few applications. Easier to log and audit application-level traffic. Drawbacks: Non-transparent. Slower. Less flexible.

23. Winter 2005 Stateful inspection firewalls Inspect traffic that flows through to detect “abnormal” activity. Example: Examine FTP control exchange for data port; firewall should expect data connection to that port. Problem: keep state for all active connections using different protocols. Current stateful inspection firewalls inspect limited number of connections/protocols. Or, search for known attack patterns.

24. Winter 2005 Circuit-level firewalls Acts as intermediate to all TCP connections. Always sets up 2 connections: between local user and itself and itself and remote host. Usually relays data without inspection. Security relies on determining which connections to allow.

25. Winter 2005 Circuit-level gateway example SOCKS package. SOCKS version 5 specified in RFC 1928. Client opens connection to appropriate SOCKs port on SOCKs server (port 1080). Authentication exchange and then relay request. Server evaluates request and establishes TCP connection or denies it.

26. Winter 2005 Firewall configurations More complex configurations. Combine multiple firewalls. For more details, “Network Security Essentials”, Stallings.

27. Winter 2005 How safe are firewalls? Should not be the single defense. Supplemental security measure. Negative effect if it causes other defenses to be weakned/not employed. Individual hosts should be protected. Tools like crack, COPS, tripwire, etc.

28. Winter 2005 Security policies Local users should be able to connect to any Internet service. But, outside users should only be allowed to connect to limited set of local services (e.g., FTP access to local archive, SMTP connections to mail server).

29. Winter 2005 Sources of security-related information CERT Computer Emergency Response Team. DARPA sponsored organization at CMU. Basically, informational: CERT advisories. Vendor security patches. Security tool announcements. Known security attacks. www.cert.org.

30. Winter 2005 More sources of security info… SecurityFocus.com Security information repository: news, relevant papers, tools. BugTraq mailing list. Discussion of security vulnerabilities and fixes. Mail to listserv@securityfocus.com.listserv@securityfocus.com SANS System Administrator, Networking and Security Institute. Sponsors conferences, training, etc. www.sans.org.

31. Winter 2005 NAT

32. Winter 2005 NAT Network address translation. Quick fix to address depletion problem. Organization assigned one or a few IP addresses. NAT box replaces “internal” addresses with real IP address on the way out.

33. Winter 2005 NAT Illustration Internet Private network NAT Pool of IP addresses and/or ports Operation:Sp wants to talk to Dg: Create Sg-Sp mapping Replace Sp with Sg for outgoing packets Replace Sg with Sp for incoming packets DgSp data DgSg data D PG Q: what happens if we reverse the question and Dg wants to talk to Sp?

34. Winter 2005 NAT disadvantages Need to keep track of who originated the connection to be able to route back to that host/port. TCP source port field replaced with index into NAT box translation table which holds internal IP address and port number.

35. Winter 2005 NAT disadvantages (cont’d) Violates “IP address uniqueness”. Violates “stateless” design principle. Violates layering principle or Internet’s “end2end”ness. What if TCP and UDP are not used? Application-specific gateways.

36. Winter 2005 More details “Network Security Essentials”, Stallings. “UNIX System Administrator Handbook”, Nemeth et al. Also, look at references on both books.