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.
HiPath SIcurity DirX Feedback
HiPath SIcurity Identity Management System
Verification of data – Instructions
Please indicate with a Yes/No in the respective field of the following table the correctness / completeness of the data held in our database. If you find that the data is not correct and/or complete, please proceed with making the appropriate corrections / additions by appropriately filling in the next field (“Correction / Completion”).
For a description / definition of each field, you can refer at Table B.
TABLE A – Verification of Data | ||||
Data held in database | Yes/No | Correction / Completion | ||
Evaluation of IMS | ||||
Evaluator: | Christian Krause |
|
| |
Organisation: | ICCP |
|
| |
Date of evaluation: | 20-Jan-2006 |
|
| |
Identification of IMS | ||||
Sources of information: | Yes | http://www.siemens.com/hipath-sicurity | ||
Version: | 7.0 | Yes |
| |
Manufacturer: | Siemens | No | Siemens AG | |
Nature: | international | Yes |
| |
Country: | Germany | Yes |
| |
Regions: | Global | Yes |
| |
Language: | ENGLISH,GERMAN | Yes |
| |
State: | Available | Yes |
| |
Open/Closed: | Closed IMS: the scope of the identities is restricted to the IMS context. | Yes |
| |
Platform & Environment | ||||
Requirements: | Intel Server Platform or SPARC, 1GB RAM, 700+MB HD, Windows, Solaris, Red Hat, SuSE | Yes |
| |
Number of users: | n.a. | Yes |
| |
Standards: | LDAPv3, DSMLv2, DAP, DSP, DISP, IDM, X.500, X.509, X521 | Yes |
| |
Description of Server - Side components: | DirX is a meta directory allowing interoperability between directory services. To achieve this the directory service’s data is reproduced in the meta directory. | No | Server components are: Identity Server, Agents and Connectors, Identity Store. The Identity Server provides a comprehensive runtime environment for event-triggered and scheduled provisioning workflows. Agents and connectors provision and synchronize accounts/groups in target systems. The Identity Store is an LDAPv3 directory server. | |
Description of methods: | n.a. | No | DirX Identity provides provisioning and synchronization based on a metadirectory technology. | |
Descriptor of Client - | n.a. | No | The Identity Web Center is the component that enables user self-service and delegated administration from a Web browser. | |
Seals: | No | Yes |
| |
Which seal: |
|
|
| |
Third party: | no | Yes |
| |
Which third party: |
|
|
| |
Features: | Among other identity management-features meta directories faciltate single sign-on. | No | Web-based user self-service and delegated administration, password management, user management, cross-platform provisioning and metadirectory functionality. The provisioning of users and their access rights in various target systems is driven by a powerful, centralized privilege management component which deals with the business roles, permissions, user groups, and includes a flexible policy and workflow engine. In addition, comprehensive scheduling, monitoring and auditing are available. | |
Screenshot picture: |
|
| ||
Flowchart: |
|
| ||
Cost | ||||
Price: | 0 |
|
| |
Comment to the Cost: | depends on product | No | Product pricing depends on the number of managed identities | |
Type & Class of IMS | ||||
Type of IMS: | Type 1: IMS for account management. | Yes |
| |
Class of IMS: | Class 1: Pure IMS which main objective is to support or implement identity management functionality. | Yes |
| |
Functionality: | metadirectory, account management, single sign-on | No | metadirectory, account management, password management | |
Suggestions: | Meta directories in general connect different directory services. Data from one directory service is available for another. To achieve this, data is reproduced in a central database. |
|
|
10 / 15 |