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.
In order to provide the user with trustworthy information whether a reader adheres to defined privacy policies, proposes a trusted computing concept. A reader is split into three parts: the core, a policy engine and a consumer agent. The core should be small enough so that the integrity measures of trusted computing are feasible, i.e. secure booting, secure operating system etc. The policy engine should enforce privacy policies. The consumer agent eventual should allow individuals or organisations like privacy commissioners to monitor the activities of the RFID reader in order to detect any privacy breach. Furthermore, remote attestation in combination with the core should enable checks if a certain policy engine is trustworthy. The remote attestation can be used by concerned individuals to ensure that a reader runs a certain reader core, policy engine and consumer agent. Thus, privacy regulations can be controlled and the owner of the reader can furthermore check if the reader has been compromised.
The reader core, which is a so called “sealed storage”, can store secrets needed for a secure authentication or communication between reader and tag. The secret is secure even if the reader is controlled by an attacker. Thereby, confidentiality of transmitted data between an RFID tag and a reader can be ensured.
This concept has a couple of drawbacks. First of all, trusted computing is a quite new concept, and it is not evident that it can really provide the promised security like not revealing stored secrets when being compromised. Then, the introduction of the consumer agent is not reasonable: either one believes in the trustworthiness of trusted computing, then the consumer agent is redundant. Or one does not believe in trusted computing, adequately one cannot trust in the consumer agent either, since it could be compromised, too! Moreover, having the CA implies additional risks to privacy as the reader’s logs are transferred to some external (potential untrustworthy) third party.
34 / 38 |