Survivability Enhancing Techniques for RFID Systems

Survivability Enhancing Techniques for RFID Systems

Copyright: © 2011 |Pages: 16
DOI: 10.4018/jhcr.2011010102
OnDemand:
(Individual Articles)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

Radio Frequency Identification (RFID) has been applied in various high security and high integrity settings. As an important ubiquitous technique, RFID offers opportunities for real-time item tracking, object identification, and inventory management. However, due to the high distribution and vulnerability of its components, an RFID system is subject to various threats which could affect the system’s abilities to provide essential services to users. Although there have been intensive studies on RFID security and privacy, there is still no complete solution to RFID survivability. In this paper, the authors classify the RFID security techniques that could be used to enhance an RFID system’s survivability from three aspects, i.e., resilience, robustness and fault tolerance, damage assessment and recovery. A threat model is presented, which can help users identify devastating attacks on an RFID system. An RFID system must be empowered with strong protection to withstand those attacks and provide essential functions to users.
Article Preview
Top

Introduction

Radio Frequency Identification (RFID) is a wireless technology for automatic item identification and data capture. It uses radio signals to identify a product, an animal or a person. Given its technical and economic advantages, RFID has been applied to various fields. Many retailers and wholesalers use RFID systems to manage product shipments and inventory tracking. RFID has also been used in critical information systems in military, healthcare, and crisis management. For instance, the US Food and Drug Administration proposed attaching RFID tags to prescription drug bottles as a pedigree. The Department of Defense is moving towards RFID-based logistic control.

The structure of a typical RFID system is shown in Figure 1 and such a system includes the following two major subsystems (Karygiannis, Eydt, Bunn, & Phillips, 2007; Zuo, Pimple, & Lande, 2009):

Figure 1.

Architecture of an enterprise RFID system

jhcr.2011010102.f01
  • 1)

    A Radio Frequency (RF) subsystem: It consists of components which perform tag identification and wireless communications and transactions between RFID readers and tags. A tag is physically attached to an item with a unique identification. A reader is a device that can recognize the presence of RFID tags and read the information supplied by them. It can be a PDA, a mobile phone or any kind of devices capable of communicating with an RFID tag. To obtain data from a tag, a reader first queries the tag and then forwards the received identity information to a backend server, which maintains a database of tag entries (see below). After being authorized, the reader can obtain more detailed information about the tag and the tagged item.

  • 2)

    An Enterprise subsystem: It consists of two components: a backend database and an RFID server.

    • a)

      Backend database: The backend database contains an entry for every valid tag in the system. Each entry corresponding to a tag contains at least the following information: the tag identification number, the secret key shared between the database and the tag, and optional item descriptions of the tagged item. An RFID reader and the backend server communicate through a secure channel;

    • b)

      RFID Server: It consists of systems and applications which communicate with the RFID readers and process data acquired from the RF subsystem. Three components constitute an RFID server:

      • i)

        Reader interface: an interface to communicate with the readers.

      • ii)

        Middleware: An intermediate layer between the lower level RF subsystem and the higher level database and a set of user applications. The main purpose of the middleware is to pre-process the data collected from the RF subsystem and provide cleaned data to the tag database to be used by the higher level business applications. The raw data collected from the RF subsystem must be pre-processed to remove redundancy and/or transformed to appropriate formats before they can be used. Middleware also contains security mechanisms to ensure data confidentiality and integrity.

      • iii)

        Tag Database: Cleaned tag data is stored in this database to be used by the high level applications. This database may also contain high level events retrieved from the lower level tag data.

Complete Article List

Search this Journal:
Reset
Open Access Articles: Forthcoming
Volume 8: 4 Issues (2017)
Volume 7: 4 Issues (2016)
Volume 6: 4 Issues (2015)
Volume 5: 4 Issues (2014)
Volume 4: 4 Issues (2013)
Volume 3: 4 Issues (2012)
Volume 2: 4 Issues (2011)
Volume 1: 4 Issues (2010)
View Complete Journal Contents Listing