You are here

ReCRED project Implementation

The overall work plan structure is depicted in the following figure:

The project deploys eight work packages (WPs), which cover coordination (WP1) and three major dimensions directly mapped onto three strategic project goals:

Technological Dimension:

ReCRED's goal is to innovate technologies in the broad field of Identity Management and Access Control, as well as demonstrate the real world viability of beyond the state of the art approaches and extensions. This is accomplished via three technical work packages, each dedicated to a core technical aspect: WP3 (Beyond the Password: Device-centric Authentication), WP4 (Identity Consolidation and Real-to-Online Identity Mapping) and WP5 (Attribute-Based Access Control).

System Dimension:

Besides the punctual technical solutions and advances ReCRED's ultimate goal is to promote the user's personal mobile device to the holistic role of unified authentication and authorization proxy towards the digital world. To accomplish this goal, ReCRED deploys two specific work packages, WP2 (Requirements, Business Cases and Architecture) and WP6 (Integration, System-level Prototyping, and Testing), dedicated to design and develop a device-centric comprehensive authentication and authorization system integrating the technical advances accomplished throughput the project.

End user and business impact dimension:

Being an innovation project, ReCRED does not nearly limits to develop and prototype technologies or systems, but comprises a broad set of activities devised to assess the impact of such technologies over real world end users, identify business strategies to exploit the ReCRED system and its individual technology components, and promote ReCRED's technologies to the perspective users and the research and innovation community. This is accomplished via two work packages, WP7 (Large Scale Pilots and User Experience Assessment) and WP8 (Dissemination and Exploitation), plus dedicated tasks in WP2 (Task 2.1: business cases and Task 2.2: business requirements).