© 2017 FutureTrust www.futuretrust.eu H2020 FutureTrust “Standards & Gaps” V 102 Jon Shamah EEMA v201
© 2017 FutureTrust www.futuretrust.eu
H2020 FutureTrust“Standards & Gaps”
V 102
Jon Shamah EEMA
v201
>> 2
FutureTrust Partners
(Serbia)
(Georgia)
(Turkey)
(S.Africa)
Focus of FutureTrust
>> 3
Existing and Missing APIs and Standards
>> 4
ETSI TS 119 612 (2.1.1)
OASIS DSS‐X (v2)
SAML, OpenID Connect
RFC 3161RFC 5280, RFC 6960
„Preservation API“ as outlined in ETSI SR 019 510
„ChipGateway API“
„Enrolment API“
Direct Issues• Enrolment API
• Undefined• ChipGateway API
• Defined within OASIS DSS‐X• Preservation API
• Outlined in ETSI SR 019 510
• Underlying Trust beyond eIDAS• How to notify non MS eIDs for use with eIDAS – scalable?
• EU 910/2014 Art 14…where the trust services originating from the third country are recognised under an agreement concluded between the Union and the third country in question or an international organisation in accordance with Article 218 TFEU.
• ‘Sister Project’ H2020 LIGHTest (www.lightest‐community.org) provides transparency of Trust Chain for decision‐making with other schemes
>> 5
Lack of agility of SDOs and EU Regulations
• Example eIDAS• First conceived circa 2005 (Manchester Declaration)• Methodologies circa 2009 (STORK et al)• eIDAS goals Nov 2011 (Poznan Ministerial)• First notified eID – February 2017 and ongoing (Germany)
• ……Yet all standards still not complete
>> 6
Thank you very much for your attention!
>> 7
[email protected]@FutureTrust_EU www.linkedin.com/groups/8562515