Ch09 (Firewalls)
Ch09 (Firewalls)
Ch09 (Firewalls)
Practice
2
Firewall Access Policy
• A critical component in the planning and
implementation of a firewall is specifying a
suitable access policy
– Types of traffic authorized to pass through the firewall
– Includes address ranges, protocols, applications and
content types
• The policy should be developed from the
organization’s security risk assessment and
policy
• Should be developed from a broad specification
of which traffic types the organization needs to
support
– Then refined to detail the filter elements which can then
be implemented within an appropriate firewall topology
3
Firewall Capabilities & Limits
• Capabilities
– Defines a single choke point
– Provides a location for monitoring security events
– Convenient platform for some Internet functions such as
NAT, usage monitoring, IPSEC, VPNs
• Limitations
– Cannot protect against attacks bypassing firewall
– May not protect fully against internal threats
– Improperly secure wireless LAN
– Laptop, PDA, portable storage device infected outside
then used inside
4
Firewall Filter Characteristics
5
Types of
Firewalls
Positive (negative) filter:
Allow (reject) packets that
meet a criteria
6
Packet Filtering Firewall
7
Packet
Filter
Rules
Default rule (usually
the last rule)
A way of handling
FTP
8
Packet Filter
Rules
9
Packet Filter Weaknesses
• Weaknesses
– Cannot prevent attack on application bugs
– Limited logging functionality
– Do no support advanced user authentication
– Vulnerable to attacks on TCP/IP protocol bugs (e.g., IP
address spoofing)
– Improper configuration can lead to breaches
• Attacks
– IP address spoofing
– Source route attacks (srs dictates the pkt route)
– Tiny fragment attacks (to circumvent filtering rules that
depend on TCP header info)
10
Stateful Inspection Firewall
11
Connection State Table
12
Application-Level (Proxy)
Gateway
• Acts as a relay of application-level traffic
– User contacts gateway with remote host name
– Authenticates themselves
– Gateway contacts application on remote host
and relays TCP segments between server and
user
• Must have proxy code for each application
– May restrict application features supported
– Some services may not be available
• More secure than packet filters
• But have higher overheads
13
Circuit-Level Gateway
15
Firewall Basing
• Several options for locating firewall:
• Bastion host
• Individual host-based firewall
• Personal firewall
17
Bastion Hosts
• Critical strongpoint in network
• Hosts application/circuit-level gateways
• Common characteristics:
– Runs secure O/S, only essential services
– May require user auth to access proxy or host
– There may be many proxy services
– Each proxy can restrict features, hosts accessed
– Each proxy small, simple, checked for security
– Each proxy is independent, can be uninstalled
18
Host-Based Firewalls
19
Personal Firewall
• Controls traffic flow to/from PC/workstation
• For both home or corporate use
• May be software module on PC
• Or in home cable/DSL router/gateway
• Typically much less complex
• Primary role to deny unauthorized access
• May also monitor outgoing traffic to
detect/block worm/malware activity
20
Firewall
Locations
Internal firewall:
21
Virtual Private Networks
22
Distributed
Firewalls
23
Firewall Topologies
• Host-resident firewall: personal firewall and firewall
on servers (used alone or part of a defense in-depth)
• Screening router: a single router between internal
and external networks, e.g., SOHO apps)
• Single bastion inline: single firewall device between
an internal and external router (stateful or app
proxies)
• Single bastion T: similar to above but has a 3rd NIC
on bastion to a DMZ (for medium to large
organizations)
• Double bastion inline: DMZ is between (for large
organizations)
• Distributed firewall configuration
24
Intrusion Prevention Systems
(IPS)
• Recent addition to security products which
– Inline network-/host-based IDS that can block
traffic
– Functional addition to firewall that adds IDS
capabilities
• Using IDS algorithms but can block or
reject packets like a firewall
• May be network or host based
25
Host-Based IPS
• Identifies attacks using both:
– Signature techniques
• malicious application packets
– Anomaly detection techniques
• behavior patterns that indicate malware
– Example of malicious behavior: buffer overflow,
access to email contacts, directory traversal
• Can be tailored to the specific platform
– e.g. general purpose, web/database server specific
• Can also sandbox applets to monitor behavior
• May give desktop file, registry, I/O protection
26
Unified
Threat
Management
Products
Reduce admin burden by replacing
network products (firewall, IDS, IPS, …)
With a single device
28
Summary
• Introduced need for & purpose of firewalls
• Types of firewalls
– packet filter, stateful inspection, application
and circuit gateways
• Firewall hosting, locations, topologies
• Intrusion prevention systems
29