TAS$^3$ Architecture (Deliverable 2.1, Draft 20)

Architect: Sampo Kellomäki (sampo@zxidp.org), Unaffiliated

Disclaimer: This document contains Intellectual Property developed by Sampo Kellomäki, who at the time of development does not have any affiliation with the TAS3 Consortium. Such Intellectual Property is not covered by the TAS3 Consortium agreement. The Consortium and Sampo Kellomäki are negotiating an arrangement for Sampo Kellomäki to be affiliated with some member of the Consortium to clarify the status of the IPR.

Disclaimer: This document has not been reviewed or approved by European Commission.

This document contains version 1 of the TAS3 system architecture (by system architecture we mean the conceptual design that defines the structure and behaviour of a TAS3 trust network). As the Description of Work states, the TAS3 project's main objective is to provide a next generation trust & security architecture that is ready to (1) meet the requirements of complex and highly versatile business processes, (2) enable the dynamic user-centric management of policies and (3) ensure end-to-end secure transmission of personal information and user- controlled attributes between heterogeneous, context dependent and continuously changing systems. This architecture has been designed to fulfill the above objectives through a combination of:

This architecture document describes the conceptual entities that are needed and the services they should provide in order to operate a TAS3 trust network. These trust and privacy enhancing services include: authorization services, secure business process management services, delegation services, privacy preserving discovery services, identity management services, secure repository services and trust and reputation services. All of these services are usually needed regardless of the applications that might run in a TAS3 trust network. However, small centralized trust networks may be able to dispense with one or more of these trust and privacy enhancing services, e.g. discovery or delegation services, depending upon their requirements.

This architecture contains many novel features such as: a trust infrastructure based on novel metrics, actor behaviour and structural components which can be correlated together, an authorisation infrastructure which supports multiple policy languages and conflict resolution, an obligation infrastructure which enforces privacy throughout the trust network, and a distributed audit system which can be cross correlated with the necessary permissions. These are described in more detail in the specific work package deliverables.

The TAS3 architecture is designed to be standards, protocol, data and application agnostic so that any protocol capable of implementing the flows and satisfying the service requirements can potentially be used by any application. Annex A maps these services onto the latest state of the art application independent protocols as far as is currently possible. This is to ensure interworking between the prototypes that will be developed in this project. Further standardization effort will be needed in order to fully complete this mapping and this will be documented in a future version of this architecture (or in other TAS3 deliverables).

Annex B shows an example deployment architecture that maximizes a service's availability and is resilient to both system and network failures including denial of service attacks.

Annex C states the compliance requirements for participants in a TAS3 trust network. Legal, policy and technical compliance requirements are covered.

Annex D provides a set of use cases which allows the reader to see how an end user might use the services of a TAS3 trust network.

Annex E contains the first version of a business model that could be used to successfully operate a TAS3 trust network

Annex F summarizes the threats that the TAS3 architecture is designed to protect against

Annex G lists the events that should be captured in the secure audit trails of a TAS3 trust network

Annex H gives some example protocol messages based on the mapping provided in Annex A

Annex I provides a glossary of terms

Scope. The TAS3 project has a narrower scope than the architecture that is documented here. This is natural as the novel research contributions of TAS3 are being made only in some areas of the architecture. However the full architecture needs to be documented as this will be needed both to successfully test the research results and to provide a production service. We present a comprehensive architecture that addresses actual use cases end-to-end, rather than simply an architecture of the services that are within the scope of our research.

[Prev | Next]