1. KEYSTONE EUROPEAN CROSS DOMAIN PKI ARCHITECTURE Sokratis K. Katsikas Professor & Head Dept. of Information & Communication Systems University of the Aegean

2. 6/5/1998 K E Y S T O N E 2 Project Participants u EXPERTNET S.A. (Greece) –University of the Aegean (Greece) u IGNIS Technologies Ltd. (Ireland)

3. 6/5/1998 K E Y S T O N E 3 Project objective robust, scaleable, based on standards, extensible, flexible and useful across application domains and national and administrative boundaries. u The main aim of KEYSTONE is to specify a logical PKI architecture which is robust, scaleable, based on standards, extensible, flexible and useful across application domains and national and administrative boundaries.

4. 6/5/1998 K E Y S T O N E 4 Technical Approach ACTS INFOSEC ARCHITECTURE METHODOLOGIES USER REQUIREMENTS TTP SERVICES & INFRASTRUCTURES FUNCTIONAL SPECS REFERENCE MODEL FUNCTIONAL ARCHITECTURE TECHNOLOGIES TECHNOLOGY EVALUATION STANDARDSBUSINESS MODEL MANAGEMENT ARCHITECTURE TECHNOLOGY PROFILES

5. 6/5/1998 K E Y S T O N E 5 WP1: D 1.1 & D 1.2 INFOSEC projects – The Nilson Marinade review report – S2101 project – THIS & TrustHealth-ETS in healthcare – TESTFIT in freight – BOLERO in shipping – Ebridge in distributed business services – EAGLE in several commercial activities ACTS projects – ABS – GAIA – MULTIMEDIATOR – OSM Overview of related INFOSEC and ACTS projects

6. 6/5/1998 K E Y S T O N E 6 TTP User Requirements Report: INFOSEC and ACTS Projects Review D 1.1 TTP User Requirements Report: INFOSEC and ACTS Projects Review u Issues studied: –Main objectives and description. –Technical overview. –How common threats are dealt with. –Organizational, legal and regulatory issues. –Achievements and expected impact. u Result: –Correlation of each project’s results and cross domain statement of the tools and services needed by TTP users.

7. 6/5/1998 K E Y S T O N E 7 Conclusions of the user requirements capture process Minimal set of security services: – authentication of users – integrity of messages – privacy and confidentiality of messages – non-repudiation of message origin and destination – availability of services – ease of use Additional services: – anonymity of participants – uniqueness of documents – protection from abuse of any participant by another Key escrow: Addressed only by EAGLE.

8. 6/5/1998 K E Y S T O N E 8 TTP services: INFOSEC Projects Review D 1.2 TTP services: INFOSEC Projects Review u Issues studied: –Trust model. –Certification infrastructure. –Functions and services for supporting the certification process.

9. 6/5/1998 K E Y S T O N E 9 Conclusions of Deliverable 1.2 u An overview of TTP infrastructures. u An overview of TTP services: –Primary services (e.g. certificate and key management). –Secondary services (e.g. audit and underwriting). –Value added services (e.g. to key generation/management ). –Services of strategic/organisational impact (e.g. TTP interoperation services).

10. 6/5/1998 K E Y S T O N E 10 D1.3 Architecture Specification Guidelines Issues Studied u Review of the architecture techniques in the projects –ABS –GAIA –MULTIMEDIATOR –OSM u Architecture specification guidelines for Keystone

11. 6/5/1998 K E Y S T O N E 11 D1.3 Results: Architecture Guidelines u Maximal compatibility & extensibility u Maximal re-use of existing solutions u Orientation towards parallel processing u RM-ODP elements in the ETS Reference Model u GAIA approach as the basis for the TTP Functional Architecture u Attention to TINA and OMA as service frameworks

12. 6/5/1998 K E Y S T O N E 12 Current work u The focus is on the services of the TTPs and the PKI: –Services link user requirements and PKI functions. –Example scenarios in which services are used. –Services examples: registration, certificate management, key management, etc.

13. 6/5/1998 K E Y S T O N E 13 Next steps... u Coming deliverables focus on: –Functional specification. –Reference model. –Functional architecture. –Environmental aspects. –Technology evaluation. –Integration.