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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

2.9. Exist<strong>in</strong>g Approaches to <strong>Wireless</strong> <strong>Sensor</strong> Network Security 61<br />

<strong>in</strong> 2.7.4.<br />

2.9.3 <strong>Secure</strong> Rout<strong>in</strong>g<br />

Cryptographic keys, be<strong>in</strong>g established through techniques discussed <strong>in</strong> the previous<br />

subsection, help to ensure secure communication with regard to the confidentiality<br />

and the authenticity of messages. It has to made sure, however,<br />

that messages <strong>in</strong>deed arrive at their dest<strong>in</strong>ations without be<strong>in</strong>g misrouted or<br />

dropped.<br />

Ariadne [82] is a route discovery protocol that is able to f<strong>in</strong>d routes from a<br />

source to a dest<strong>in</strong>ation <strong>in</strong> a multi-hop network and pass them back to the sender.<br />

It is secure <strong>in</strong> the sense that (1) the hosts authenticate themselves and (2) each<br />

host certifies the previous piece of the path from the source to itself. (3) All<br />

host identities are l<strong>in</strong>ked through a hash cha<strong>in</strong>. (4) A basic assumption is an<br />

end-to-end secure l<strong>in</strong>k between the source and the dest<strong>in</strong>ation. (This could be<br />

provided by a pre-arranged secret key between both hosts.)<br />

It is assured that malicious hosts cannot cut nodes off the path or <strong>in</strong>sert<br />

new ones. h0 is the <strong>in</strong>itial value, the authentication code of the <strong>in</strong>itial request<br />

message. This is equivalent to a digitally signed request. Each follow<strong>in</strong>g host<br />

identity X is appended to the hash cha<strong>in</strong> as hi+1 = H[X,hi] where H is a oneway<br />

function. Dest<strong>in</strong>ation D can easily verify whether the hash cha<strong>in</strong> matches<br />

the path, s<strong>in</strong>ce it can reconstruct h0. Requests with mismatch<strong>in</strong>g items will be<br />

dropped. Intermediate hosts cannot do this verification step and will <strong>for</strong>ward<br />

also bogus messages.<br />

Ariadne does not prevent a malicious host from gett<strong>in</strong>g on the selected path<br />

if it follows the protocol. For example, it could then later drop messages be<strong>in</strong>g<br />

sent along the path. On the network layer, this will be noticed as a path failure.<br />

A new path discovery request would be issued by the source. Unless the malicious<br />

node creates a bottleneck between source and dest<strong>in</strong>ation, a path will be<br />

eventually found that passes by the malicious host.<br />

This protocol is not well-suited <strong>for</strong> wireless sensor networks <strong>for</strong> several reasons.<br />

(1) The route request is flooded through the network. This is efficient<br />

only <strong>in</strong> highly dynamic networks. (2) Source rout<strong>in</strong>g, <strong>for</strong> which the protocol<br />

provides the basis, requires node identifiers <strong>in</strong> the path to be sent along the<br />

node each time the route is used. This is undesirable overhead. The alternative,<br />

cach<strong>in</strong>g routes, would require additional memory <strong>in</strong> hosts. (3) A secure<br />

channel between source and dest<strong>in</strong>ation hosts is a prerequisite. This implies<br />

that the identity of the dest<strong>in</strong>ation is known to the source <strong>in</strong> advance. In sensor<br />

networks, such close l<strong>in</strong>ks between hosts (sensor nodes) are not a common

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

Saved successfully!

Ooh no, something went wrong!