ipsec: network layer security

24
8: Network Security 8-1 IPsec: Network Layer Security network-layer secrecy: sending host encrypts the data in IP datagram TCP and UDP segments; ICMP and SNMP messages. network-layer authentication destination host can authenticate source IP address two principal protocols: authentication header (AH) protocol encapsulation security payload (ESP) protocol for both AH and ESP, source, destination handshake: create network-layer logical channel called a security association (SA) each SA unidirectional. uniquely determined by: security protocol (AH or ESP) source IP address 32-bit connection ID

Upload: lotta

Post on 06-Jan-2016

66 views

Category:

Documents


4 download

DESCRIPTION

network-layer secrecy: sending host encrypts the data in IP datagram TCP and UDP segments; ICMP and SNMP messages. network-layer authentication destination host can authenticate source IP address two principal protocols: authentication header (AH) protocol - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: IPsec: Network Layer Security

8: Network Security 8-1

IPsec: Network Layer Security network-layer secrecy:

sending host encrypts the data in IP datagram

TCP and UDP segments; ICMP and SNMP messages.

network-layer authentication destination host can

authenticate source IP address

two principal protocols: authentication header

(AH) protocol encapsulation security

payload (ESP) protocol

for both AH and ESP, source, destination handshake: create network-layer

logical channel called a security association (SA)

each SA unidirectional. uniquely determined by:

security protocol (AH or ESP)

source IP address 32-bit connection ID

Page 2: IPsec: Network Layer Security

8: Network Security 8-2

Firewalls

isolates organization’s internal net from larger Internet, allowing some packets to pass, blocking others.

firewall

administerednetwork

publicInternet

firewall

Page 3: IPsec: Network Layer Security

8: Network Security 8-3

Firewalls: Why

prevent denial of service attacks: SYN flooding: attacker establishes many bogus

TCP connections, no resources left for “real” connections

prevent illegal modification/access of internal data. e.g., attacker replaces CIA’s homepage with

something elseallow only authorized access to inside network (set of

authenticated users/hosts)three types of firewalls:

stateless packet filters stateful packet filters application gateways

Page 4: IPsec: Network Layer Security

8: Network Security 8-4

Stateless packet filtering

internal network connected to Internet via router firewall

router filters packet-by-packet, decision to forward/drop packet based on: source IP address, destination IP address TCP/UDP source and destination port numbers ICMP message type TCP SYN and ACK bits

Should arriving packet be allowed

in? Departing packet let out?

Page 5: IPsec: Network Layer Security

8: Network Security 8-5

Stateless packet filtering: example

example 1: block incoming and outgoing datagrams with IP protocol field = 17 and with either source or dest port = 23. all incoming, outgoing UDP flows and

telnet connections are blocked. example 2: Block inbound TCP segments with

ACK=0. prevents external clients from making TCP

connections with internal clients, but allows internal clients to connect to outside.

Page 6: IPsec: Network Layer Security

8: Network Security 8-6

Policy Firewall Setting

No outside Web access. Drop all outgoing packets to any IP address, port 80

No incoming TCP connections, except those for institution’s public Web server only.

Drop all incoming TCP SYN packets to any IP except 130.207.244.203, port 80

Prevent Web-radios from eating up the available bandwidth.

Drop all incoming UDP packets - except DNS and router broadcasts.

Prevent your network from being used for a smurf DoS attack.

Drop all ICMP packets going to a “broadcast” address (eg 130.207.255.255).

Prevent your network from being tracerouted

Drop all outgoing ICMP TTL expired traffic

Stateless packet filtering: more examples

Page 7: IPsec: Network Layer Security

8: Network Security 8-7

actionsourceaddress

destaddress

protocolsource

portdestport

flagbit

allow222.22/1

6outside of222.22/16

TCP > 1023 80any

allowoutside

of222.22/1

6

222.22/16TCP 80 > 1023 ACK

allow222.22/1

6outside of222.22/16

UDP > 1023 53 ---

allowoutside

of222.22/1

6

222.22/16UDP 53 > 1023 ----

deny all all all all all all

Access Control Lists ACL: table of rules, applied top to bottom to

incoming packets: (action, condition) pairs

Page 8: IPsec: Network Layer Security

8: Network Security 8-8

Stateful packet filtering stateless packet filter: heavy handed tool

admits packets that “make no sense,” e.g., dest port = 80, ACK bit set, even though no TCP connection established:

actionsourceaddress

destaddress

protocolsourceport

destport

flagbit

allow outside of222.22/16

222.22/16TCP 80 > 1023 ACK

stateful packet filter: track status of every TCP connection track connection setup (SYN), teardown (FIN): can

determine whether incoming, outgoing packets “makes sense”

timeout inactive connections at firewall: no longer admit packets

Page 9: IPsec: Network Layer Security

8: Network Security 8-9

actionsourceaddress

destaddress

protosource

portdestport

flagbit

check conxion

allow 222.22/16outside of222.22/16

TCP > 1023 80any

allow outside of222.22/16

222.22/16TCP 80 > 1023 ACK

x

allow 222.22/16outside of222.22/16

UDP > 1023 53 ---

allow outside of222.22/16

222.22/16UDP 53 > 1023 ----

x

deny all all all all all all

Stateful packet filtering

ACL augmented to indicate need to check connection state table before admitting packet

Page 10: IPsec: Network Layer Security

8: Network Security 8-10

Application gateways

filters packets on application data as well as on IP/TCP/UDP fields.

example: allow select internal users to telnet outside.

host-to-gatewaytelnet session

gateway-to-remote host telnet session

applicationgateway

router and filter

1. require all telnet users to telnet through gateway.2. for authorized users, gateway sets up telnet connection

to dest host. Gateway relays data between 2 connections

3. router filter blocks all telnet connections not originating from gateway.

Page 11: IPsec: Network Layer Security

8: Network Security 8-11

Limitations of firewalls and gateways

IP spoofing: router can’t know if data “really” comes from claimed source

if multiple app’s. need special treatment, each has own app. gateway.

client software must know how to contact gateway. e.g., must set IP address

of proxy in Web browser

filters often use all or nothing policy for UDP.

tradeoff: degree of communication with outside world, level of security

many highly protected sites still suffer from attacks.

Page 12: IPsec: Network Layer Security

8: Network Security 8-12

Intrusion detection systems

packet filtering: operates on TCP/IP headers only no correlation check among sessions

IDS: intrusion detection system deep packet inspection: look at packet

contents (e.g., check character strings in packet against database of known virus, attack strings)

examine correlation among multiple packets• port scanning• network mapping• DoS attack

Page 13: IPsec: Network Layer Security

8: Network Security 8-13

Webserver

FTPserver

DNSserver

applicationgateway

Internet

demilitarized zone

internalnetwork

firewall

IDS sensors

Intrusion detection systems

multiple IDSs: different types of checking at different locations

Page 14: IPsec: Network Layer Security

8: Network Security 8-14

Network Security (summary)

Basic techniques…... cryptography (symmetric and public) message integrity end-point authentication

…. used in many different security scenarios secure email secure transport (SSL) IP sec 802.11

Operational Security: firewalls and IDS

Page 15: IPsec: Network Layer Security

Availability

Access over Internet must be unimpeded Context: flooding attacks, in which attackers try to

overwhelm system resources Denial of service (DoS) attacks disrupt

availability Distributed DoS is a coordinated attack from multiple

attackers Example: SYN flood

Problem: server cannot distinguish legitimate handshake from one that is part of this attack

• Only difference is whether third part of TCP handshake is sent

Flood can overwhelm communication medium• Can’t do anything about this (except buy a bigger pipe)

Flood can overwhelm resources on legitimate system

Page 16: IPsec: Network Layer Security

Regular TCP handshake

Page 17: IPsec: Network Layer Security

Too many half-opened TCP connections at server creates a DoS attack

Server is waiting client to finish the connection

Buffer space is full and legitimate connection cannot be completed

Page 18: IPsec: Network Layer Security

Flooding DoS attack

Page 19: IPsec: Network Layer Security

Prevention of SYN flood: SYN Cookies Server no longer keeps the client’s state

Embed the state in the sequence number When SYN received, server computes a

sequence number to be function of source, destination, counter, and a secret

• The function may be one-way hash function• The secret is known only by the server• Use as reply SYN sequence number• When reply ACK arrives, validate it

The sequence number must be hard to guess

Page 20: IPsec: Network Layer Security

SYN Cookie

y = H(source, destination, secret, counter) computed by servers is secret known only by serverH is a one-way hash function

Server no longer keeps client’s state

Server verifies sequence number with s

Client cannot forge a sequence number without actually engaging in handshake

Page 21: IPsec: Network Layer Security

Alternative prevention to SYN flood: adaptive Time-Out Change time-out time as space available for

pending connections decreases Example: modified SunOS kernel

Time-out period shortened from 75 to 15 sec Formula for queueing pending connections changed:

• Process allows up to b pending connections on port• a number of completed connections but awaiting

process• p total number of pending connections• c tunable parameter• Whenever a + p > cb, drop current SYN message

Page 22: IPsec: Network Layer Security

ICMP: Internet Control Message Protocol

used by hosts & routers to communicate network-level information error reporting:

unreachable host, network, port, protocol

echo request/reply (used by ping)

network-layer “above” IP: ICMP msgs carried in IP

datagrams ICMP message: type, code

plus first 8 bytes of IP datagram causing error

Type Code description0 0 echo reply (ping)3 0 dest. network unreachable3 1 dest host unreachable3 2 dest protocol unreachable3 3 dest port unreachable3 6 dest network unknown3 7 dest host unknown4 0 source quench (congestion control - not used)8 0 echo request (ping)9 0 route advertisement10 0 router discovery11 0 TTL expired12 0 bad IP header

Page 23: IPsec: Network Layer Security

Flooding DoS attacks

Page 24: IPsec: Network Layer Security

2: Application Layer 24

Slides credits

J.F Kurose and K.W. Ross