Wireless Network Security

1
 IEEE 802.11
IEEE 802 committee for LAN standards
IEEE 802.11 formed in 1990s
charter to develop a protocol & transmission
specifications for wireless LANs (WLANs)
since then demand for WLANs, at different
frequencies and data rates, has exploded
hence seen ever-expanding list of standards
issued

2
 IEEE 802 Terminology
Access point (AP) Any entity that has station functionality and provides
access to the distribution system via the wireless
medium for associated stations
Basic service set A set of stations controlled by a single coordination
(BSS) function
Coordination function The logical function that determines when a station
operating within a BSS is permitted to transmit and
may be able to receive PDUs
Distribution system A system used to interconnect a set of BSSs and
(DS) integrated LANs to create an ESS
Extended service set A set of one or more interconnected BSSs and
(ESS) integrated LANs that appear as a single BSS to the LLC
layer at any station associated with one of these BSSs
MAC protocol data The unit of data exchanged between two peer MAC
unit (MPDU) entites using the services of the physical layer
MAC service data unit Information that is delivered as a unit between MAC
(MSDU) users
Station Any device that contains an IEEE 802.11 conformant MAC
and physical layer

3
 Wi-Fi Alliance
802.11b first broadly accepted standard
Wireless Ethernet Compatibility Alliance
(WECA) industry consortium formed 1999
to assist interoperability of products
renamed Wi-Fi (Wireless Fidelity) Alliance
created a test suite to certify interoperability
initially for 802.11b, later extended to 802.11g
concerned with a range of WLANs markets,
including enterprise, home, and hot spots
4
IEEE 802 Protocol Architecture

5
Network Components & Architecture

6
IEEE 802.11 Services

7
 802.11 Wireless LAN Security
Wireless traffic can be monitored by any radio in
range, not physically connected
Original 802.11 spec had security features
Wired Equivalent Privacy (WEP) algorithm
but found this contained major weaknesses
802.11i task group developed capabilities to address
WLAN security issues
Wi-Fi Alliance Wi-Fi Protected Access (WPA)
final 802.11i Robust Security Network (RSN)

8
802.11i RSN Services and Protocols

9
802.11i Phases of Operation

10
 802.11i Phases of Operation
The operation of an IEEE 802.11i RSN can be
broken down into five distinct phases of
operation, as shown in Stallings Figure 17.5

One new component is the authentication

server (AS). The five phase are:

Discovery: An AP uses messages called Beacons

and Probe Responses to advertise its IEEE
802.11i security policy

The STA uses these to identify an AP for a WLAN

with which it wishes to communicate
11
 802.11i Phases of Operation
The STA associates with the AP, which it uses to
select the cipher suite and authentication
mechanism when the Beacons and Probe
Responses present a choice

Authentication: During this phase, the STA and

AS prove their identities to each other

The AP blocks non-authentication traffic

between the STA and AS until the
authentication transaction is successful

12
 802.11i Phases of Operation
The AP does not participate in the
authentication transaction other than
forwarding traffic between the STA and AS

Key generation and distribution: The AP and

the STA perform several operations that cause
cryptographic keys to be generated and placed
on the AP and the STA

Frames are exchanged between the AP and STA

only

13
 802.11i Phases of Operation
Protected data transfer: Frames are exchanged
between the STA and the end station through
the AP

As denoted by the shading and the encryption

module icon, secure data transfer occurs
between the STA and the AP only; security is not
provided end-to-end

Connection termination: The AP and STA

exchange frames. During this phase, the secure
connection is torn down and the connection is
restored to the original state
14
 802.11i
Discovery and
Authent-
ication Phases

15
802.11i Discovery and Authentication
Phases
We now look in more detail at the RSN phases of
operation, beginning with the discovery phase

Which is illustrated in the upper portion of

Stallings Figure 17.6

The purpose of this phase is for an STA and an

AP to recognize each other, agree on a set of
security capabilities

16
802.11i Discovery and Authentication
Phases
Establish an association for future
communication using those security capabilities

Confidentiality and MPDU integrity protocols for

protecting unicast traffic, Authentication
method, Cryptography key management
approach

Confidentiality and integrity protocols for

protecting multicast/broadcast traffic are
dictated by the AP
17
802.11i Discovery and Authentication
Phases
Since all STAs in a multicast group must use the
same protocols and ciphers

The specification of a protocol, along with the

chosen key length (if variable) is know as a
cipher suite

The options for the confidentiality and integrity

cipher suite are as follows:

18
802.11i Discovery and Authentication
Phases
WEP, with either a 40-bit or 104-bit key (for
backward compatibility), TKIP, CCMP, vendor-
specific methods

The options for the authentication and key

management (AKM) suite are: IEEE 802.1X, pre-
shared key, vendor-specific methods)

The discovery phase consists of three exchanges:

Network and security capability discovery, Open
system authentication, and Association
19
802.11i Discovery and Authentication
Phases
The authentication phase enables mutual
authentication between an STA and an
authentication server (AS) located in the DS

Authentication is designed to allow only

authorized stations to use the network and to
provide the STA with assurance that it is
communicating with a legitimate network

The lower part of Figure 17.6 shows the IEEE

802.11 MPDU exchange for this phase
20
IEEE 802.1X Access Control
Approach

21
 802.11i
Key
Manage-
ment Phase

22
 802.11i Protected Data Transfer
Phase
Have two schemes for protecting data
Temporal Key Integrity Protocol (TKIP)
s/w changes only to older WEP
adds 64-bit Michael message integrity code (MIC)
encrypts MPDU plus MIC value using RC4
Counter Mode-CBC MAC Protocol (CCMP)
uses the cipher block chaining message authentication code
(CBC-MAC) for integrity
uses the CRT block cipher mode of operation

23
 Wireless Application Protocol
(WAP)
A universal, open standard developed to provide
mobile wireless users access to telephony and
information services
Have significant limitations of devices, networks,
displays with wide variations
WAP specification includes:
programming model, markup language, small browser,
lightweight communications protocol stack, applications
framework

24
WAP Programming Model

25
 WAP Programming Model
The WAP Programming Model is based on three
elements: the client, the gateway, and the original
server, as shown here in Stallings Figure 17.11

HTTP is used between the gateway and the

original server to transfer content

The gateway acts as a proxy server for the wireless

domain

Its processor(s) provide services that offload the

limited capabilities of the hand-held, mobile,
wireless terminals 26
 WAP Programming Model
For example, the gateway provides DNS services,
converts between WAP protocol stack and the WWW
stack (HTTP and TCP/IP)

Encodes information from the Web into a more

compact form that minimizes wireless communication

And, in the other direction, decodes the compacted

form into standard Web communication conventions

Gateway also caches frequently requested information

27
WAP Infra-
structure

28
 WAP Infra-structure
Stallings Figure 17.12 illustrates key components in
a WAP environment

Using WAP, a mobile user can browse Web content

on an ordinary Web server

The Web server provides content in the form of

HTML-coded pages that are transmitted using the
standard Web protocol stack (HTTP/TCP/IP)

The HTML content must go through an HTML filter,

which may either be colocated with the WAP proxy
or in a separate physical module 29
 WAP Infra-structure
The filter translates the HTML content into WML
content

If the filter is separate from the proxy, HTTP/TCP/IP

is used to deliver the WML to the proxy

The proxy converts the WML to a more compact

form known as binary WML and delivers it to the
mobile user over a wireless network using the WAP
protocol stack

30
 WAP Infra-structure
If the Web server is capable of directly generating
WML content, then the WML is delivered using
HTTP/TCP/IP to the proxy

which converts the WML to binary WML and then

delivers it to the mobile node using WAP protocols

31
 Wireless Markup Language
Describes content and format for data display
on devices with limited bandwidth, screen
size, and user input capability
Features include:
text / image formatting and layout commands
deck/card organizational metaphor
support for navigation among cards and decks
a card is one or more units of interaction
a deck is similar to an HTML page
32
WAP Architecture

33
 WAP Architecture
Stallings Figure 17.13 illustrates the overall stack
architecture implemented in a WAP client

In essence, this is a five-layer model. Each layer

provides a set of functions and/or services to other
services and applications through a set of well-
defined interfaces

Each of the layers of the architecture is accessible

by the layers above, as well as by other services
and applications
34
 WAP Architecture
Many of the services in the stack may be provided
by more than one protocol

For example, either HTTP or WSP may provide the

Hypermedia Transfer service

Common two all five layers are a sets of services

that are accessible by multiple layers

These common services fall into two categories:

security services and service discovery
35
 WAP Architecture
The WAP specification includes mechanisms to
provide confidentiality, integrity, authentication, and
nonrepudiation

There is a collection of service discovery services that

enable the WAP client and the Web server to
determine capabilities and services

The Wireless Application Environment (WAE)

specifies an application framework for wireless
devices such as mobile telephones, pagers, and PDAs
36
 WAP Architecture
In essence, the WAE consists of tools and formats
that are intended to ease the task of developing
applications and devices supported by WAP

37
 WAP Protocols
Wireless Session Protocol (WSP)
provides applications two session services
connection-oriented and connectionless
based on HTTP with optimizations
Wireless Transaction Protocol (WTP)
manages transactions of requests / responses
between a user agent & an application server
provides an efficient reliable transport service
Wireless Datagram Protocol (WDP)
adapts higher-layer WAP protocol to communication
38
 Wireless Transport Layer Security
(WTLS)
provides security services between mobile
device (client) and WAP gateway
provides data integrity, privacy, authentication,
denial-of-service protection
based on TLS
more efficient with fewer message exchanges
use WTLS between the client and gateway
use TLS between gateway and target server
WAP gateway translates WTLS / TLS
39
 WTLS Sessions and Connections
secure connection
a transport providing a suitable type of service
connections are transient
every connection is associated with 1 session
secure session
an association between a client and a server
created by Handshake Protocol
define set of cryptographic security parameters
shared among multiple connections
40
WTLS Protocol Architecture

41
 WTLS Protocol Architecture
WTLS is not a single protocol but rather two layers
of protocols, as illustrated in Stallings Figure 17.15

The WTLS Record Protocol provides basic security

services to various higher-layer protocols

In particular, the Hypertext Transfer Protocol

(HTTP)

42
 WTLS Protocol Architecture
which provides the transfer service for Web
client/server interaction, can operate on top of
WTLS

Three higher-layer protocols are defined as part

of WTLS: the Handshake Protocol, The Change
Cipher Spec Protocol, and the Alert Protocol

These WTLS-specific protocols are used in the

management of WTLS exchanges and are
examined next
43
WTLS Record Protocol

44
 WTLS Record Protocol
The WTLS Record Protocol takes user data from
the next higher layer (WTP, WTLS handshake
protocol, WTLS alert protocol, WTLS change
cipher spec protocol)

And encapsulates these data in a PDU. The

following steps occur (Figure 17.16):

1. The payload is compressed using a lossless

compression algorithm

45
 WTLS Record Protocol
2. A message authentication code (MAC) is
computed over the compressed data, using HMAC

One of several hash algorithms can be used with

HMAC, including MD-5 and SHA-1

The length of the hash code is 0, 5, or 10 bytes

The MAC is added after the compressed data

46
 WTLS Record Protocol
3. The compressed message plus the MAC code are
encrypted using a symmetric encryption algorithm

The allowable encryption algorithms are DES,

triple DES, RC5, and IDEA

4. The Record Protocol prepends a header to the

encrypted payload.

The Record Protocol header the fields as shown

in Stallings Figure 17.17
47
 WTLS Higher-Layer Protocols
Change Cipher Spec Protocol
simplest, to make pending state current
Alert Protocol
used to convey WTLS-related alerts to peer
has severity: warning, critical, or fatal
and specific alert type
Handshake Protocol
allow server & client to mutually authenticate
negotiate encryption & MAC algs & keys
48
Handshake
Protocol

49
 Cryptographic Algorithms
WTLS authentication
uses certificates
X.509v3, X9.68 and WTLS (optimized for size)
can occur between client and server or client may
only authenticates server
WTLS key exchange
generates a mutually shared pre-master key
optional use server_key_exchange message
for DH_anon, ECDH_anon, RSA_anon
not needed for ECDH_ECDSA or RSA
50
 WAP End-to-End Security
Have security gap end-to-end
at gateway between WTLS & TLS domains

51
 WAP End-to-End Security
The basic WAP transmission model, involving a
WAP client, a WAP gateway, and a Web server,
results in a security gap

As illustrated in Stallings Figure 17.19. The mobile

device establishes a secure WTLS session with the
WAP gateway

The WAP gateway, in turn, establishes a secure SSL

or TLS session with the Web server

52
 WAP End-to-End Security
Within the gateway, data are not encrypted during
the translation process

The gateway is thus a point at which the data may

be compromised

There are a number of approaches to providing

end-to-end security between the mobile client and
the Web server

53
 WAP End-to-End Security
In the WAP version 2 (known as WAP2)
architecture document, the WAP forum defines
several protocol arrangements that allow for end-
to-end security

Version 1 of WAP assumed a simplified set of

protocols over the wireless network

and assumed that the wireless network did not

support IP

54
 WAP End-to-End Security
WAP2 provides the option for the mobile device to
implement full TCP/IP-based protocols

And operate over an IP-capable wireless network

55