eID task force meeting.

This task force has worked on integration of eID levels 1, 2 and 3. What is the mandate and definition of tasks (definition of mandate, success factors...) for this task force?

Meetings discussing on:

What is missing?
What is to be done for levels 4 and 5 (which are not yet specified).

We should not only be implementers but we should also raise our voice. Today we are struggling with our vision of what is next to do?

eID Universe Expansion

eHOMB
1. Feasibility Study (from Deloitte) (available probably by 30 Jun 2016)
2. How far will this study put pressure on the work of this task force?
  1. No one fits all solution, no idea if the study will put pressure?
    1. How far the study would be? Focus on CEF eID building block, part of the study was to understand who is who, work done after eSENS workshop in Brussels to coordinate on the implications. DIGIT recommendation to SANTE: several options are available, MS are welcome to come with their options
  2. Study will be available from the 30th June (intermediary version available beginning of June)
3. What other points should we follow-up, what should we look upon?
  1. eSENS component and specs are to be considered as recommendations. No guarantee, nor obligation. We're a project, downstream activities.
    1. We need to provide the best OpenNCP reference implementation ever
    2. From eSENS, providing recommendations. It leaves a huge gap (legal requirements, security...) + timeline towards eHealth DSI
      1. eHDSI has a need to have something operation ready
      2. Proposition that OpenNCP Steerco should raise the voice to fill the gaps and communicate strongly with other stakeholders to make the OpenNCP a success.
      3. eSENS handover sustainability? End eSENS in March 2017, developments may end this summer, no support anymore... the only entity to ensure continuity activity is OpenNCP.
        To be scaled to the Steering board.
      4. Piloted this summer and then handovered
    3. how far are we going towards EIDAS? It cannot deviate. eHealth is the only domain that has eID token leveraged on qualified material but not notified. Only PT, IT and AU have merged their cards
      1. Level 4 and 5: EIDAS nodes defined. For level 3 we could use them.
eIDAS
1. Legal Regulation
  1. Relevant aspects to OpenNCP integration?
    1. Are being dealt in eSENS => Zoi
2. Specification
  1. Relevant aspects to OpenNCP integration?
    1. Public space available on Joinup
      1. Waiting for sector specific attributes
      2. Topics to be raised at the Steering Committee:
        Should we (OpenNCP Communiuty) reinforce eSENSE request for these attributes?
        and recommend JASeHN to communicate these attributes ASAP to the eID governance otherwise we may loose the opportunity window for he specifications
        How far and how much do we want OpenNCP engagement in the eID topic and eSENSE revamp in the following couple of months?
      3. Need to empower OpenNCP to develop further level 4 and 5
    2. There will be recommendations from different domains
eSENS
1. eHealth Pilot (WP5.2 timeline extension has been approved, the projetct project will run until March 2017)
2. Scope:
  1. eID BB
  2. Nonrepudiation BB:
  3. SMP/SML BB:
JAseHN

...

LEVEL

Description

BB Dev STATUS

OpenNCP Integration Status

Open Issues

Level 0 – manual input of ID – traditional epSOS

This is the most basic level of identification. It only requires the Health Professional to identify the patient by requesting his/her ID, and enter it manually in the system. This is the approach used in the epSOS pilot.

The main advantage of this level is in an emergency setting where no other method of identification and authentication is available.

Status

title	NONE

Status

colour	Green
title	DONE

Status


colour	Green
title	NONE

Level 1 – Passive read of eID token – e-SENS LARMS

This level requires the existence of an eID token, usually this token is a smart card. The token has identification attributes that can be publicly read.

In the eSENS project the asset used provide this level is the e-SENS Local Attribute Mapping and Retrieval Service (LARMS). This level is safer than the previous, because of the input of the identification is automatic and not manual.

Status

colour	Green
title	DONE

Status

colour	Green
title	DONE

Status


colour	Green
title	NONE

Level 2 – Localy signed eID with token – e-SENS LAM

This level also requires the existence of an eID token, as the previous on, but this token has to be capable of patient authentication, usually by entering a PIN code.

In the eSENS project the asset used provide this level is e-SENS Local Authentication Module (e-SENS LAM) with the Digital Signature Add-On (DSig).

Signing of a patient consent is made possible with the introduction of this level.

This level is safer than the previous, because the introduction of the identification attributes is authenticated by the patient. In this level, as well in the previous ones, a network connection is not needed. The inexistence of a network connection, and thus the connectivity to a PKI (Public Key Infrastructure) to validate this authentication is a liability, which, however, can be mitigated by the signature and certificate validation performed through the ACS in country-A. Consequently, it is possible to issue a mismatched data disclosure request (e.g. signing with a certificate of someone else) or using an irregular certificate (e. g. suspended) in country-B but it should not be able to successfully pass ACS inspection in A.

Status

colour	Green
title	DONE

(maintenance)

Status

colour	Green
title	DONE

1st Step:

provision of authenticated attributes

2nd Step:

Capability of signing the SAML assertion created by the TRC service, with the certificates of the SmartCard instead of using the NCP certificates.

Issues identified on:

--- https://openncp.atlassian.net/projects/EID/issues/EID-1?filter=allopenissues

Licinio Kustra Mano: decision was taken regarding including eID Level 2 on the OpenNCP 2.4.0.

-- So far this is the best ever released version of OpenNCP;

Level 3 – Localy signed eID with realtime validation – LAM+

This level has the same functionality of the previous, but with the availability of a network connection and connectivity to the required PKI infrastructures. This level mitigates the liability introduced in the previous level. So the validation of the authentication of identification and patient consents is possible.- Full advantage of having access to Country A to validate the identification and signature of certificates.

Status

colour	Green
title	DONE

Soeren Bittins: will release the tech artefact and

Status


subtle	true
colour	Red
title	NOTHING TO BE DONE

Joao Cunha + Hugo Soares

- Codification of attributes, with STorK and eIDAS there is a limitation on the attributes can be coded (Doctor name), that causes loss of semantic on the exchange of the information. - Wow can the eIDAS token support this requirements? "http://www.futureid.eu/attributes/common/cardIssuerCountry":"it", "http://www.futureid.eu/attributes/cardType":"it-cns", "http://www.futureid.eu/attributes/common/healthInsuranceId":{"urn:oid:1.2.3.4.5.6.7.8.9":"030225BM526"}, "http://www.stork.gov.eu/1.0/surname":"INCONTATTOZERO",

@Alice: Will be following this up. Report on (4th and 5th February workshop: focused on the adapter from STorK 2 to eIDAS)
Soeren Bittins: Prepare problem Statement.

Level 4 – Distributed Cross-Border Authentication (DCA)

This level introduces the e-SENS Authentication Broker, that is leveraged by the STORK 2.0/ eIDAS infrastructure. All authentication and authorisation activities are fulfilled outside of the local environment based on an initial authentication information acquired locally from an eID token.

If interested, MS need to provide the following information:

Soeren Bittins: provide info

Status

subtle	true
title	NOT STARTED

Status

subtle	true
title	NOT STARTED

Access to Stork 2 instance (DE is not part of the system)

Currently is being evaluated by a German partner access to eIDAS service in Germany.

For sake of integration, can we work with a citizen from a different nationality with a Stork 2 system running.

For testing purposes STorK: @Alice may point the eSENS eID for eHealth, to a test environment so that development activities can proceed.

Level 5 – Virtual eID (mobile eID)status

subtle	true
colour	Green
title	DONE

This level leverages the previous by giving the possibility of authentication and authorisation on without the need of a physical eID token, just using a mobile app a smartphone with a virtual token, specifically developed for this.

If interested, MS need to provide the following information:

....

Soeren Bittins: provide info

Status

subtle	true
title	NOT STARTED

Status

subtle	true
title	NOT STARTED

Soeren Bittins is currently studying materials that just came out recently published materials from e-SENS. Follow up in next meeting.

e-SENS WP5.2] [e-SENS] mobile eID actions and plan WP6 // TF eID Integration (Soeren Bittins email from 01 Feb 2016 10:51 CET)
- the eID Integration TF released the following documents in:
  [1] https://www.jol.nrw.de/bscw/bscw.cgi/6109921
  [2] http://wiki.ds.unipi.gr/display/ESENS/.MobileID+v1.2.0

View file

name	e-SENS D5 2 - SD-DSS change request.pdf
height	250

Next Steps:

Meetings:
1. Next meetingmeetings: 07 Jun 2016 16:00 to 17:00 CEST. + 21 Jun 2016
  1. Most probably lead by @Tome since Licinio Kustra Mano will be on holidays (leaving SPMS on the 30 Jun 2016 )
  2. Proposed agenda:
  3. 1. steerco messages
    2. eSENS progress level 4 and 5
    3. MS attributes
    4. CEF eID
2. e-SESN eHealth Pilot: 28 Jun 2016 29 Jun 2016
  1. Is there anything to be prepared by the OpenNCP Community?
ACTIONS

Versions Compared

Old Version 2

New Version 3

Key

eID task force meeting.

Agenda:

Meeting Notes:

OpenNCP Steering Committee notes

eID Universe Expansion

Next Steps:

Page Comparison

Versions Compared

Old Version 2

New Version 3

Key

eID task force meeting.

Agenda:

Meeting Notes:

OpenNCP Steering Committee notes

eID Universe Expansion

Next Steps: