21.08.2013 Views

Protocols for Secure Communication in Wireless Sensor Networks

Protocols for Secure Communication in Wireless Sensor Networks

Protocols for Secure Communication in Wireless Sensor Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2.7. Security Requirements 43<br />

network is not under attack. Thus, there exists a short time w<strong>in</strong>dow dur<strong>in</strong>g<br />

which key material can be exchanged as pla<strong>in</strong>text. This essentially replaces<br />

authentication by a (temporarily) secure environment.<br />

L<strong>in</strong>k-level security is, however, only effective aga<strong>in</strong>st outsider attacks. A<br />

message that is transmitted over multiple hops is easily compromised if its path<br />

<strong>in</strong>cludes a malicious node. There<strong>for</strong>e, a mechanism to set up end-to-end secure<br />

connections is desirable. However, this requires a means to establish a shared<br />

key between the endpo<strong>in</strong>ts of a connection, which turns out to be challeng<strong>in</strong>g<br />

<strong>in</strong> sensor networks. This problem is further discussed <strong>in</strong> section 3.4.<br />

Sometimes, messages need to be delivered network-wide, <strong>for</strong> example code<br />

or configuration updates. Such messages orig<strong>in</strong>ate preferably at a base station<br />

that is trusted by all nodes, and must be authenticated. The µTESLA protocol<br />

[142] has been designed <strong>for</strong> authenticated broadcast and is suitable <strong>for</strong> this<br />

use case.<br />

2.7.2 Rout<strong>in</strong>g<br />

Multi-hop rout<strong>in</strong>g is a fundamental service <strong>in</strong> large-scale sensor networks. There<br />

are protocols that are specifically designed to address the needs of sensor network<br />

applications. Usually, they do not rely on up-to-date rout<strong>in</strong>g tables, which<br />

would be too complex to ma<strong>in</strong>ta<strong>in</strong>. Rather, they <strong>for</strong>ward a message based on<br />

features of the message itself, or they set up paths on demand.<br />

One important class of such protocols provide data-centric rout<strong>in</strong>g. They<br />

are either demand-driven, where a node that is <strong>in</strong>terested <strong>in</strong> a certa<strong>in</strong> type of<br />

events announces its <strong>in</strong>terest and thereby pulls messages towards itself [86], or<br />

event-driven, where a message source announces the availability of messages<br />

of a certa<strong>in</strong> type [31]. A path is then established between source and receiver.<br />

Another important class are geometric rout<strong>in</strong>g protocols [91, 100, 149, 201].<br />

They rely on nodes know<strong>in</strong>g their and their neighbours’ position <strong>in</strong> a real-world<br />

or virtual coord<strong>in</strong>ate space. Messages are routed accord<strong>in</strong>g to a target location<br />

without the need of sett<strong>in</strong>g up a path.<br />

A rout<strong>in</strong>g protocol ensures that messages reach their target. Attacks on the<br />

network layer, where rout<strong>in</strong>g functionality is located, aim at divert<strong>in</strong>g or suppress<strong>in</strong>g<br />

messages. This can lead to unauthorized data disclosure, miss<strong>in</strong>g critical<br />

events, energy exhaustion, or event trigger<strong>in</strong>g at undesired locations. A<br />

secure rout<strong>in</strong>g protocol must be resilient aga<strong>in</strong>st such attacks.<br />

Karlof and Wagner [90] have identified a number of ways to attack rout<strong>in</strong>g<br />

protocols designed <strong>for</strong> sensor networks, and propose countermeasures. These<br />

<strong>in</strong>clude l<strong>in</strong>k-layer encryption and authentication, multipath rout<strong>in</strong>g, identity

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!