Resources
Identity Use Cases & Scenarios.
FIDIS Deliverables.
Identity of Identity.
Interoperability.
Profiling.
Forensic Implications.
HighTechID.
D3.1: Overview on IMS.
D3.2: A study on PKI and biometrics.
D3.3: Study on Mobile Identity Management.
D3.5: Workshop on ID-Documents.
D3.6: Study on ID Documents.
D3.7: A Structured Collection on RFID Literature.
D3.8: Study on protocols with respect to identity and identification – an insight on network protocols and privacy-aware communication.
D3.9: Study on the Impact of Trusted Computing on Identity and Identity Management.
D3.10: Biometrics in identity management.
D3.11: Report on the Maintenance of the IMS Database.
D3.15: Report on the Maintenance of the ISM Database.
D3.17: Identity Management Systems – recent developments.
D12.1: Integrated Workshop on Emerging AmI Technologies.
D12.2: Study on Emerging AmI Technologies.
D12.3: A Holistic Privacy Framework for RFID Applications.
D12.4: Integrated Workshop on Emerging AmI.
D12.5: Use cases and scenarios of emerging technologies.
D12.6: A Study on ICT Implants.
D12.7: Identity-related Crime in Europe – Big Problem or Big Hype?.
D12.10: Normality Mining: Results from a Tracking Study.
Privacy and legal-social content.
Mobility and Identity.
Other.
IDIS Journal.
FIDIS Interactive.
Press & Events.
In-House Journal.
Booklets
Identity in a Networked World.
Identity R/Evolution.
D3.7 A Structured Collection on Information and Literature on Technological and Usability Aspects of Radio Frequency Identification (RFID)
When considering the security challenges of RFID in a broader perspective, one has to take into account the infrastructure including a back office where additional information of all tags is stored, and the aspect of convenience in use. A general architecture of RFID systems is depicted in :
User Interface
Figure : A general RFID architecture
Real-life RFID deployments employ a wide variety of physically distributed RFID readers, access gateways, and databases. The middleware of the gateway receives events from the RFID readers when tags are scanned. These events are passed through a number of filters, which process the events in an application-specific manner (e.g. by filtering irrelevant or faulty data out). When an event has passed through all filters, it is dispatched to the components that have registered an interest in such events. Often, one of these components will store the event in a database, for further processing.
RFID readers are generally connected to the middleware using modular drivers much like Windows uses device drivers to communicate with a graphics card. This allows different readers to be used with the middleware, without having to modify the middleware.
In addition to event-processing, the middleware handles different kinds of user interfaces. A user interface is generally provided for system-management purposes, for example to modify the series of filters through which an event is passed. There will also be user interfaces that allow regular users to access the system and use it. For example, in a supermarket distribution centre, there will be a user interface that provides information on the current stock levels.
The middleware also communicates with other software systems, which implement the application’s business logic. To stay with the supermarket example, it is likely that the supermarket RFID system is connected to a stock management system, which orders new stock from suppliers before it runs out.
A good overview on security aspects of RFID and related systems can be found in the “Guidance for Securing RFID Systems” published by the (U.S.) National Institute of Standards and Technology (NIST).
|
|
|
Denis Royer | 12 / 46 |