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.1: Overview on IMS
Structure for the Database
Attribute Label | Definition | Values |
Name | Name of the IMS | Text |
Version number | Version of IMS | Text |
Manufacturer / distributor | Main manufacturer or provider of the IMS | Text |
Nature of provider / distributor | Description of the nature of the provider of the system. (e.g. public, private, regional, national, international) | Text |
Nation | Nation of the manufacturer’s resp. of provider’s location | Text |
Geographical scope |
| Enumerated: National, European, International |
Supported languages |
| Text |
State of development | Statement whether the IMS is an available product or a service on the market (Available), still a Prototype, a Suspended prototype, or just a Concept. | Enumerated: Available, Prototype, Suspended prototype, Concept |
Type of IMS | 1: Access Management System; 2: Profiling System; 3: IMS for user-controlled context-dependent role and pseudonym management | Enumerated: see left |
Class of IMS | Class 1, 2 or 3 as per definition of types outlined in section 1 | Enumerated: type 1, 2 or 3 |
Closed/open IMS | “Closed IMS” means that the scope of the managed identities is restricted to the IMS context. “Open IMS” means that the managed identities work with several systems or applications. | Enumerated: Closed, Open |
Main functionality | Short description (e.g. form fill-in, single sign-on, etc.) |
|
Technical requirement | Description of the hardware, software, operating system and services the IMS requires | Text |
Price | Price of the IMS | Integer / Text |
Installation base of the IMS | Number of users of the IMS / Penetration of market | Integer / Text |
Interoperability / standards | Description if the IMS can be used with other applications and systems. This could be achieved by using standards like protocols for communication. | Text |
Seals etc. | Description of seals and other awards, etc. | Text |
Server-side component(s) | Description of the server-side-components (data storage and processing) | Text |
Control of the server-side data by the user | Description of methods (e.g. encryption), how the control of the user over his identity related data is established with respect to availability, integrity and confidentiality | Text |
Client-side component(s) | Description of the client-side-components (data storage and processing) | Text |
Support by third parties | Description of which third party or intermediary support is integrated, e.g., certificate providers, IMS providers, delivery services, payment services, … | Boolean (yes/no) + text |
References | Sources of information, literature, links etc. | Text |
Attribute Label | Definition | Values |
Description of functionality / features (client and server) | What are the characteristics / specialities? Handling of identities? Use of pseudonyms / roles? Support of anonymity? Use of electronic signatures / PKI? Storage of data? Handling of accounts? Password management? Security / encryption, etc.? Data protection? Privacy Enhancing Technologies? Data minimisation? Support of law enforcement? Usability? […] | Long free text |
Screenshot | One screenshot | Picture |
Flow chart | Shows how data is processed within the IMS, which parts are involved. | Picture |
Evaluators | Name(s) and organisation(s) of the evaluator(s) | Text |
Date of contribution | Date(s) of the evaluation of the IMS and of the contribution | Date |
Table : Suggested structure of the database on IMS
| 9 / 31 |
