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.2. Attack Objectives 73<br />

• Timel<strong>in</strong>ess<br />

• Orig<strong>in</strong><br />

The first three of these po<strong>in</strong>ts refer to the “classical” security properties that<br />

have to be protected <strong>in</strong> virtually any security sensitive application. We consider<br />

timel<strong>in</strong>ess as an additional essential security goal <strong>in</strong> sensor networks. It may<br />

be possible to subsume this goal under availability, but <strong>in</strong> many applications,<br />

tim<strong>in</strong>g is crucial and seem<strong>in</strong>gly <strong>in</strong>significant delays could have severe impact.<br />

When referr<strong>in</strong>g to the orig<strong>in</strong> of some piece of data (or a message), we assume<br />

that a party obta<strong>in</strong><strong>in</strong>g the data (<strong>for</strong> example, by read<strong>in</strong>g from a sensor or<br />

receiv<strong>in</strong>g a message) also obta<strong>in</strong>s some statement about the association of the<br />

data with its orig<strong>in</strong>, i.e. the source from which it has been obta<strong>in</strong>ed. This statement<br />

could be backed up by a digital signature, or it might be implicit as when<br />

read<strong>in</strong>g from a sensor. If the evidence support<strong>in</strong>g the statement is sufficiently<br />

strong, the party may decide to attests its f<strong>in</strong>d<strong>in</strong>g, thus further support<strong>in</strong>g the<br />

statement. It is there<strong>for</strong>e crucial that a statement about the orig<strong>in</strong> of a piece of<br />

data cannot be <strong>for</strong>ged or tampered with by an attacker.<br />

Usually, the orig<strong>in</strong> of a message refers to the entity that has generated the<br />

message. Orig<strong>in</strong> authentication is based on some feature of the source, such as<br />

a public/private key pair, a common secret key, location, or a biometric attribute<br />

(<strong>in</strong> real life, voice is often used).<br />

Integrity and orig<strong>in</strong> authentication are often achieved through the same mechanisms.<br />

An important mechanism is the concept of message authentication<br />

code (MAC). Such a MAC provides a means <strong>for</strong> the receiver of a message to<br />

verify the message’s orig<strong>in</strong> and its <strong>in</strong>tegrity at the same time. Both concepts are<br />

closely connected, as when the <strong>in</strong>tegrity of a message is violated, it is essentially<br />

trans<strong>for</strong>med <strong>in</strong>to a different message, which has a different orig<strong>in</strong> as well.<br />

Vice versa, if the orig<strong>in</strong> of a message cannot be verified, it does not necessarily<br />

follow that the <strong>in</strong>tegrity of the message has been violated. Stated differently,<br />

even if we don’t know where a message comes from, it could still be a valid<br />

message. Thus, it is valid to say that orig<strong>in</strong> authentication implies <strong>in</strong>tegrity, but<br />

not the other way around.<br />

3.2.2 Resource Types<br />

It very much depends on the level of abstraction what components of a networked<br />

computer system are regarded as valuable resources that require protection.<br />

In a transaction-oriented system, the database would be the most valuable<br />

resource. On a home desktop PC, personal <strong>in</strong><strong>for</strong>mation such as credit card

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

Saved successfully!

Ooh no, something went wrong!