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.

3.1. Attack Paths 69<br />

modules [63]. As soon as a potentially threaten<strong>in</strong>g event is detected, the memory<br />

hold<strong>in</strong>g secret keys is zeroed. Such measures are costly, and an acceptable<br />

trade-off must be found that takes the actual risk of such attacks <strong>in</strong>to account.<br />

<strong>Sensor</strong> devices, which have to be available <strong>in</strong> large quantities at low cost, are<br />

unlikely to <strong>in</strong>corporate such means. However, a certa<strong>in</strong> level of self-protection<br />

may be possible. The sensors that are already attached to a sensor device may<br />

be useful <strong>for</strong> detect<strong>in</strong>g certa<strong>in</strong> events, <strong>for</strong> example sudden movements, which<br />

may be sufficient <strong>for</strong> many practical applications.<br />

If tamper resistance is considered too costly, at least some level of tamper<br />

evidence may be provided. Upon <strong>in</strong>spection, this would make the fact that an<br />

attack has occurred obvious. Natural characteristics of the deployment area<br />

may also support the protection of a sensor network. For example, the terra<strong>in</strong><br />

where the nodes are placed may be <strong>in</strong>accessible, or sensor nodes may be concealed<br />

between other objects, mak<strong>in</strong>g them harder to detect. All these measures<br />

lead to a certa<strong>in</strong> level of tamper resilience, which <strong>in</strong>creases the cost <strong>for</strong> a successful<br />

attack, <strong>for</strong> example by delay<strong>in</strong>g the attacker or requir<strong>in</strong>g him to acquire<br />

specially crafted equipment.<br />

The risk of a physical attack depends on the environment and the context<br />

<strong>in</strong> which the sensor network is deployed. Questions to consider <strong>in</strong> order to<br />

assess the risks are: Who would be <strong>in</strong>terested <strong>in</strong> disabl<strong>in</strong>g the network? Where<br />

and when is the network deployed, and how high is the exposure to potential<br />

attackers? What is the potential impact of a disabled or manipulated sensor<br />

network? In many cases, one might be satisfied with the risk be<strong>in</strong>g reduced by<br />

<strong>in</strong>herent properties of sensor networks, i.e. the small size and high redundancy<br />

of sensor devices.<br />

3.1.2 Interface Attacks<br />

Interface attacks exploit vulnerabilities of the <strong>in</strong>terfaces a device provides <strong>in</strong><br />

order to allow access to its own services or to access external services. For<br />

wireless communication <strong>in</strong>terfaces, there are obvious attacks such as eavesdropp<strong>in</strong>g,<br />

jamm<strong>in</strong>g, traffic analysis, and message <strong>in</strong>jection among others. They<br />

are facilitated by the broadcast nature of wireless communication, and the fact<br />

that access is easily possible without the risk of detection. An overview can be<br />

found, e.g., <strong>in</strong> [129]. Interface attacks can also be executed on the level of a service<br />

API, <strong>for</strong> example those of security processors [28]. Here, valid commands<br />

are executed <strong>in</strong> unusual sequence, thereby provok<strong>in</strong>g un<strong>in</strong>tended behaviour <strong>in</strong><br />

favour of the attacker. To our knowledge, the service (message) <strong>in</strong>terfaces of<br />

sensor networks have not been <strong>in</strong>vestigated with regard to security vulnerabili-

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

Saved successfully!

Ooh no, something went wrong!