stork - A-SIT

STORK
Secure Identity Across Borders Linked
5th STORK Industry Group Meeting
STORK Sustainability Solution
Herbert Leitold
Poznań, November 16th, 2011
Stork is an EU co-funded project INFSO-ICT-PSP-224993
Sustainability at the end of a project




To have it maintained
To get grip on governance
To get it taken up
To have it used
FOG
AHEAD
Sustainability History
 Sustainability actions started 1 ½ years ago
√
With the success of STORK an
urgent need to have a solution
beyond 2011 has been seen
 Meeting of EC and MS
in September 2010
√
√
Discuss MS responsibilities
Discuss EC responsibilities
 The ISA Programme has been
considered the best candidate for proceeding
 By chance, STORK 2.0 appeared for 2012-2015
The ISA Solution
 Became part of the
ISA Work Programme 2011
 ISA Action 1. “STORK Sustainability”
√
√
Period: 2010 – 2012
Budget: 910 k€
 Two main action items
1.
2.
Governance activities
Development works
To h a v e i t m a i n t a i n e d
 Maintenance, update and upgrade of the
Common SW modules:
√
√
√
√
√
√
√
Implement agreed changed in the common
software, as well for PEPS as for V-IDP
Test changes in all relevant environments (Tomcat, JBoss, Glassfish; all
on Windows / Linux) and others
according to MS needs
Test compatibility with actual production versions
Maintenance of test-laboratory
Publish the new software, together with release notes
Active bug-tracking and error solution
Technical support for the Member States 8x5x52
To g e t g r i p o n g o v e r n a n c e ( I / I I )
 Update of Common Specifications (CS):
√
√
√
√
√
√
√
Initiate and coordinate discussions on new
data or data to be changed as well as new
functionalities or actual ones to be changed.
Reflect agreed changes in documentation.
Quality control on the implementation
of changed specifications
Coordinate support groups.
Coordinate implementation in Member States.
Quality assessment for implementation with new/
changed Service Providers and new Member States.
etc.
To g e t g r i p o n g o v e r n a n c e ( I I / I I )
 Update of the QAA levels according to the
following task breakdown:
√
√
√
√
Once a year to discuss, vote on and
formally agree on changes.
Twice a year collect by e-mail
change requests.
Twice a year the dissemination of
an assessment of requested changes.
Once a year a publication of an updated
"QAA" document.
To g e t i t t a k e n u p
 Standardization as a
basis of industry take-up
√
√
√
√
Investigate data standards and promote their
implementation.
Promote the acceptance of the CS in
appropriate forums (eGOV events, standardization organizations, Industry players…).
Active collaboration with EU sponsored
projects and other sectoral eGOV solutions
across-Europe;
propose changes to the common specs which
are required or useful to those projects.
Policy Framework: Legal Basis
Propose by
2012 a Council and
Parliament Decision to ensure mutual
recognition of e-identification and eauthentication across the EU based on
online 'authentication services' to be
offered in all Member States (which may
use the most appropriate official citizen
documents – issued by the public or
the private sector)
In 2011
propose a revision of
the eSignature Directive
with a view to provide a
legal framework for crossborder recognition and
interoperability of secure
eAuthentication
systems
To g e t i t u s e d
 Creating facts with having the infrastructure
used beyond the project lifetime
√
√
Change from piloting to production
Integration in Services Directive
Points of Single Contacts (e.g. ES)
 Applications with immanent
cross-border needs:
√
√
√
√
ETS
CIRCABC
IMI
…
The End ..
Time is flying …
… so I thank You for Your
patience and attention.