16.05.2014 Views

Wireless Security.pdf - PDF Archive

Wireless Security.pdf - PDF Archive

Wireless Security.pdf - PDF Archive

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.

<strong>Wireless</strong> Embedded System <strong>Security</strong> 613<br />

The network topologies supported by ZigBee vary, but depending on the type of network<br />

being deployed there are varying security considerations. In some ZigBee topologies,<br />

all nodes are considered equal and the network is basically an ad hoc peer-to-peer<br />

configuration. In some of the other topologies (star and tree forms), there must be a<br />

coordinator that facilitates the network. In such a topology, the end-nodes can be of<br />

reduced functionality to save cost, but there is an inherent problem: If the coordinator is<br />

disabled, reduced-functionality end nodes cannot reestablish the network. One way to get<br />

around this is to provide redundant full-function nodes that can all serve as a coordinator<br />

(this is a good idea for reliability, not just security). ZigBee nodes can also function as<br />

routers, directing communications between nodes that may not be able to communicate<br />

directly (as would be the case if the distance between those nodes was too great, but the<br />

router node bisected the path between them). If a ZigBee node is acting as a router, it is<br />

important that any information being passed along cannot be compromised if the router<br />

node is compromised.<br />

The ZigBee protocol provides low-level security for communications between individual<br />

nodes using AES and a message authentication code scheme, but this only protects the<br />

data between nodes, not on the nodes themselves. Normally this would be OK if the nodes<br />

in question were functioning as end-nodes, but if they are functioning as coordinators or<br />

routers, it may be desirable to use a higher-level security scheme to protect that data. This<br />

presents another interesting challenge due to the limited bandwidth of ZigBee and the<br />

extremely limited resources that are likely to be found on ZigBee devices. A full-blown<br />

security protocol like SSL will probably not work because of the extra overhead (especially<br />

when you consider running RSA on a ZigBee node). In fact, a number of protocols, like<br />

IPSEC, do not even make sense, since ZigBee networks are not based upon TCP/IP. What<br />

would make more sense would actually be to use a simple AES-based scheme similar<br />

to what is done later in the PIC case study. Authentication could be provided through a<br />

password or key that is passed in encrypted form to the end device.<br />

ZigBee is an exciting new technology that promises to bring a level of connectivity<br />

never before seen. Depending on how it is deployed, it may also represent a security<br />

challenge unlike any we have ever seen. What will be important to remember as ZigBee<br />

devices are deployed in factories and homes around the world is that these devices will<br />

probably not support a level of security equal to that of full-blown networking. Due to the<br />

extremely limited resources, some devices may have no security at all, so it will be vital<br />

to keep a constant vigil on what information is being sent over these networks. For these<br />

www.newnespress.com

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

Saved successfully!

Ooh no, something went wrong!