Dear WP3 Partners,
In line with the recent intentions to extend SPARTA brought up at
project level (see below), the Roadmap Committee has carried internal
discussions and found beneficial to postpone "D3.4 Updated SPARTA SRIA
(Roadmap v3)" to M48 instead of M36. As for "D3.5 SPARTA SRIA Lesson
Learned and Future Assessment", we believe that it does not require an
extension, so we intend to keep it due at M36.
As partners in WP3, you are welcome to spend your allocated resources by
M48, if the extension of the deliverable is granted. Otherwise, feel
free to use your PMs for WP3 within the originally allocated time, until
M36. Since the SPARTA roadmap is a living document, contributions to it
can be submitted at any time, regardless of how far the deliverable
deadline is.
In addition, the WP leaders TUM, INRIA, and CNR have been carrying
cross-pilot interactions with the roadmapping teams of the other
cybersecurity pilots within a commissioned Focus Group. We believe that
this joint effort could prove very useful for the EC and the
cybersecurity ecosystem of the EU if it gets materialized. Therefore, we
will propose an additional deliverable for M48 that will synthesize the
outcomes of the FG, with additional PMs for the 3 partners involved as
follows: 6 PMs for TUM, 6 PMs for INRIA, 3 PMs for CNR.
Please let us know if you have any thoughts or objections on the
aforementioned points, as an amendment to the original GA must be agreed
upon by all, if the extension proposal gets through.
Sincerely,
Marius & the Spartan Roadmap Committee
-------- Forwarded Message --------
Subject: [SPARTA - bodies.executive-board] SPARTA - Extension
Date: Thu, 3 Jun 2021 12:18:16 +0000
From: LEMESLE Augustin <augustin.lemesle(a)cea.fr>
To: bodies.executive-board(a)internal.sparta.eu
<bodies.executive-board(a)internal.sparta.eu>
Dear all,
As discussed in last EB & SD calls, we will move forward w.r.t. the
extension of SPARTA. For this, our first step will be to make a concrete
proposition to our PO giving a rough idea of what we want to do and the
necessary efforts. We, thus, propose that you, as WP leaders, start this
discussion in your respective WP with its participants to propose
suggestions for this extension.
For each suggestion, we propose to fill the small form below to have a
quick view of the efforts, motivation and impact involved.
• Type: [Extension of Task / WP / New Task / New WP / …]
• Potential participants:
• New deliverables:
• New estimated PMs per participant:
• Summary: [Short and factual description of the new
proposition]
• Motivation: [What will it bring to SPARTA?]
• Impact: [What will be the impact on SPARTA and more
generally the cybersecurity ecosystem?]
• Strategic Planning: [How does it relate to the 9 axis and
topic from the Strategic planning proposed by the Commission?]
As this matter is also linked with the self-assessment and suggestion we
sent to the EC recently, we have also added a line to explicit this
link. For this part you can find attached the latest version of the
self-assessment that we sent to the EC.
We will fix a deadline for this at *30^th June*, after which we will
filter and compile the proposition before discussing it with you and
submitting it to the PO. If you have any additional question or remark
concerning this, feel free to ask us.
Best regards,
Augustin.
Dear SPARTA Partners,
The WP3 Roadmap Committee is actively preparing the release of the
*SPARTA SRI Roadmap V2*. In this respect, the European Commission is
interested in understanding which challenges from the SPARTA roadmap are
of higher priority for strengthening the digital sovereignty of Europe
in cybersecurity. In addition, the European Commission is curious which
challenges are more critical considering the recent rapid technological
adoptions enforced by the Corona pandemic.
The SPARTA roadmap is an evolving document and already contains a rich
collection of cybersecurity challenges. So far we have added challenges
in no particular order and independent of their size and urgency. As
part of the roadmap process, we want all partners to give their view on
how we should***prioritize**these challenges with respect to digital
sovereignty and the Corona pandemic*.
To do so, we have provided an online questionnaire to be filled-in:
https://www.cybersecurityosservatorio.it/Services/sparta_roadmap_grading.js…
<https://www.cybersecurityosservatorio.it/Services/sparta_roadmap_grading.js…>
The questionnaire has three parts: *Emerging Challenges*, *Education and
Certification*, and *The SPARTA Programs*. In each section, we ask you
to give a *priority from 1 (low) to 5 (high)* to the challenges with
respect to digital sovereignty and Corona, and to *provide a (brief)
explanation for your choice*. Once you land on the questionnaire's
homepage, you can either click on the /"Anonymous Mode"/ checkbox to
start a non-authenticated questionnaire session, or create a new account
on the platform and submit the input while logged-in. If you opt for
/"Anonymous Mode"/, please save the hash of the new session, as it
allows you to continue filling at a later point the questionnaire
session that you started.
Please provide your input to the questionnaire by the *11th of December
(Friday)*. Your contribution will be highly appreciated!
All the best,
Marius in the name of the Spartan Roadmap Committee
--
Marius Momeu, M.Sc.
Wissenschaftlicher Mitarbeiter
Technische Universität München
Fakultät für Informatik
Lehrstuhl für Sicherheit in der Informatik
Boltzmannstraße 3
85748 Garching (bei München)
Tel. +49 (0)89 289-18592
Fax +49 (0)89 289-18579
Dear WP3 Participants,
this is a second attempt on sending out the following email from Prof.
Claudia Eckert concerning the WP3 Roadmap Template.
---
Dear WP3 Participants,
Thanks again to all who attended our WP3 kick-off meeting on July 11th and for participating in the very fruitful discussions. Based on our discussion, we have updated our first version of a roadmap skeleton/template we presented during the KoM.
Just a short wrap up: we decided to specify several roadmap units. The roadmap committee will select the most appropriate 'units' to be integrated into the SPARTA roadmap step by step. During the meeting we identified appropriate criteria to select these units.
During KoM TUM has promised to define a template to specific roadmap unit candidates.
Attached, you will find the template for each unit that should comprise the following extensive description (in Table 1) covering all points which we have highlighted during the KoM (we also attach a shortened example that can be used as a reference):
(1) A problem and opportunity description, which describes the addressed challenge,
(2) the status quo with respect to, e.g., technologies/solution/methods already available to address the problem,
(3) an estimation until when the challenge/problem should be solved;
(4) as we would like to focus on research and innovation (TRL level up to 5), the roadmap unit should describe in a comprehensive manner: which concrete research questions should be addressed;
(5) since the challenge should be beneficial for the industry as well, the industrial needs should be elaborated;
(6) as a unique SPARTA approach, we would like to consider the social aspects of the challenge as well and,
(7) the benefit for EU should be made clear. This is very important, as we want t set up ann European roadmap.
(8) To be able to understand the importance of the challenge the description should comprise a SWOT analysis that enables to derive the opportunities, but the risks as well.
(9) Describe which security domain will be addressed (see JRC taxonomy), as well as
(10) which sector or vertical is addressed (see JRC taxonomy).
(11) Another USP of the SPARTA roadmap might be our early consideration of emerging technologies. That is why we ask whether the solved challenge might be related to emerging technologies (e.g. post quantum crypto is closely related to the development of quantum computers though the technology is used in normal computer architectures).
With these 11 elements, the challenge and its impacts should be sufficiently described. As part of the next step, we can use the template to define the different steps that are required to solve the problem/challenge (by means of the Table 2 and 3).
During our meeting, we have emphasized, that we would like to have a combined roadmap which describes the technological development steps (TRL-level) as well as relations to education capabilities that must be developed as well as certification measures. These are the three dimensions of the roadmap and the dependencies between the different elements.
To reach the final goal, i.e., to solve the challenge, several (readiness) levels (i.e., several stages in the Table 2) of development are required. Further, Table 2 allows to define relations among different stages. That is, it allows to consider prerequesite stages that need to be completed before we can start with a particular stage. Each stage should be described in more detail in Table 3. Here, we should outline the individual steps, provide an exact mapping to the JRC taxonomy, and state potential obstacles.
Next steps: urgent, June, mid of July:
According to the SPARTA proposal we have to deliver a first version of the SPARTA roadmap until end of July. As there is an additional need from the EU commission as Thibaud explained during the KoM meeting, to define a comprehensive roadmap as early as possible before end of July, we need the input for the first draft as early as possible, latest end of June.
Input required:
(1) End of June: responsible actors: 4 program leads
We would like to ask the four program leads to fill out the attached template with the challenges that are pursued as part of the individual programs. The filled out templates should be stored on the svn and should in addition be sent to Thomas Jensen from INRIA (cc Sergej Proskurin proskurin(a)sec.in.tum.de).
In addition: I ask the leads of the WP lead Education as well as WP-lead Certification to fill out the template with respect to their WPs as well.
(2) 10th of July: responsible actor: INRIA
INRIA is responsible for compiling the first version of the SPARTA roadmap. To this end I ask Thomas and his INRIA team to compile a first version from the unit-descriptions of the 4 programs.
In addition, as discussed during the KoM, INRIA should use their results of the summarized/aggregated classification of the initial 60 proposal-challenges to further derive 2-3 aggregated/bigger challenges that INRIA should describe with help of the template.
The initial roadmap comprising a comprehensive report as well as a first visualization /timeline and dependencies) should be delivered to TUM (Claudia, Sergej, Bojan, Mohamad) and should be stored on svn as well.
(3) End of July latest: responsible actor TUM
Due to task 3.5 TUM will review the initial roadmap compiled by INRIA and will produce the final delivery based on the INRIA report.
Please be aware, that due to the tight timeline for the first roadmap deliverable, we kindly and urgently ask you to provide us with the needed information. Please stick to the defined template though it might not be perfect at this stage. Please send us your comments and suggestions for improvement in a separate mail. This can be taken into account during the next cycle of roadmap maintenance
Other next steps: National Associate workshops, Stakeholder Workshops:
The initial roadmap should be discussed during the upcoming workshops and should be extended and aligned if necessary. To extend the roadmap with new roadmap-units we kindly ask all WP3 partners to use the template as well during the workshops.
Please do not hesitate to contact Sergej or Bojan for any questions you may have.
Thank you in advance for your cooperation.
Best regards,
Claudia Eckert
---
Best,
~Sergej
--
Sergej Proskurin, M.Sc.
Wissenschaftlicher Mitarbeiter
Technische Universität München
Fakultät für Informatik
Lehrstuhl für Sicherheit in der Informatik
Boltzmannstraße 3
85748 Garching (bei München)
Tel. +49 (0)89 289-18592
Fax +49 (0)89 289-18579
Dear all,
in addition to the links I already sent: here's a deliverable from the roadmapping WP in the Graphene Flagship project with a chapter (Chapter 2) outlining the roadmapping methodology that I presented at our Munich meeting.
Best
Michael
--
Dr. Michael Friedewald
Coordinator ICT Research
Competence Center Emerging Technologies
Fraunhofer-Institut für System- und Innovationsforschung ISI
Breslauer Straße 48 | 76139 Karlsruhe
fon: +49 721 6809-146 | fax: +49 721 6809-315
assistent: +49 (0) 721/6809-189 (Silke Just)
mailto: michael.friedewald(a)isi.fraunhofer.de
http://www.isi.fraunhofer.dehttp://works.bepress.com/michael_friedewald/
________________________________
V
Dear WP3 Participants,
Thanks again to all who attended our WP3 kick-off meeting on July 11th and for participating in the very fruitful discussions. Based on our discussion, we have updated our first version of a roadmap skeleton/template we presented during the KoM.
Just a short wrap up: we decided to specify several roadmap units. The roadmap committee will select the most appropriate 'units' to be integrated into the SPARTA roadmap step by step. During the meeting we identified appropriate criteria to select these units.
During KoM TUM has promised to define a template to specific roadmap unit candidates.
Attached, you will find the template for each unit that should comprise the following extensive description (in Table 1) covering all points which we have highlighted during the KoM (we also attach a shortened example that can be used as a reference):
(1) A problem and opportunity description, which describes the addressed challenge,
(2) the status quo with respect to, e.g., technologies/solution/methods already available to address the problem,
(3) an estimation until when the challenge/problem should be solved;
(4) as we would like to focus on research and innovation (TRL level up to 5), the roadmap unit should describe in a comprehensive manner: which concrete research questions should be addressed;
(5) since the challenge should be beneficial for the industry as well, the industrial needs should be elaborated;
(6) as a unique SPARTA approach, we would like to consider the social aspects of the challenge as well and,
(7) the benefit for EU should be made clear. This is very important, as we want t set up ann European roadmap.
(8) To be able to understand the importance of the challenge the description should comprise a SWOT analysis that enables to derive the opportunities, but the risks as well.
(9) Describe which security domain will be addressed (see JRC taxonomy), as well as
(10) which sector or vertical is addressed (see JRC taxonomy).
(11) Another USP of the SPARTA roadmap might be our early consideration of emerging technologies. That is why we ask whether the solved challenge might be related to emerging technologies (e.g. post quantum crypto is closely related to the development of quantum computers though the technology is used in normal computer architectures).
With these 11 elements, the challenge and its impacts should be sufficiently described. As part of the next step, we can use the template to define the different steps that are required to solve the problem/challenge (by means of the Table 2 and 3).
During our meeting, we have emphasized, that we would like to have a combined roadmap which describes the technological development steps (TRL-level) as well as relations to education capabilities that must be developed as well as certification measures. These are the three dimensions of the roadmap and the dependencies between the different elements.
To reach the final goal, i.e., to solve the challenge, several (readiness) levels (i.e., several stages in the Table 2) of development are required. Further, Table 2 allows to define relations among different stages. That is, it allows to consider prerequesite stages that need to be completed before we can start with a particular stage. Each stage should be described in more detail in Table 3. Here, we should outline the individual steps, provide an exact mapping to the JRC taxonomy, and state potential obstacles.
Next steps: urgent, June, mid of July:
According to the SPARTA proposal we have to deliver a first version of the SPARTA roadmap until end of July. As there is an additional need from the EU commission as Thibaud explained during the KoM meeting, to define a comprehensive roadmap as early as possible before end of July, we need the input for the first draft as early as possible, latest end of June.
Input required:
(1) End of June: responsible actors: 4 program leads
We would like to ask the four program leads to fill out the attached template with the challenges that are pursued as part of the individual programs. The filled out templates should be stored on the svn and should in addition be sent to Thomas Jensen from INRIA (cc Sergej Proskurin proskurin(a)sec.in.tum.de).
In addition: I ask the leads of the WP lead Education as well as WP-lead Certification to fill out the template with respect to their WPs as well.
(2) 10th of July: responsible actor: INRIA
INRIA is responsible for compiling the first version of the SPARTA roadmap. To this end I ask Thomas and his INRIA team to compile a first version from the unit-descriptions of the 4 programs.
In addition, as discussed during the KoM, INRIA should use their results of the summarized/aggregated classification of the initial 60 proposal-challenges to further derive 2-3 aggregated/bigger challenges that INRIA should describe with help of the template.
The initial roadmap comprising a comprehensive report as well as a first visualization /timeline and dependencies) should be delivered to TUM (Claudia, Sergej, Bojan, Mohamad) and should be stored on svn as well.
(3) End of July latest: responsible actor TUM
Due to task 3.5 TUM will review the initial roadmap compiled by INRIA and will produce the final delivery based on the INRIA report.
Please be aware, that due to the tight timeline for the first roadmap deliverable, we kindly and urgently ask you to provide us with the needed information. Please stick to the defined template though it might not be perfect at this stage. Please send us your comments and suggestions for improvement in a separate mail. This can be taken into account during the next cycle of roadmap maintenance
Other next steps: National Associate workshops, Stakeholder Workshops:
The initial roadmap should be discussed during the upcoming workshops and should be extended and aligned if necessary. To extend the roadmap with new roadmap-units we kindly ask all WP3 partners to use the template as well during the workshops.
Please do not hesitate to contact Sergej or Bojan for any questions you may have.
Thank you in advance for your cooperation.
Best regards,
Claudia Eckert
---
On 17.06.19 20:56, Eckert, Claudia wrote:
> Gallo Zusammen,
> ich wollte das template beschreiben, siehe weiter unten meine Beschreibung, und habe gemerkt, dass das viel zu kompliziert wird. Die dritte Tabelle finde ich sehr unglücklich und verwirrend.
> Bitte ändert das Template wie folgt ab: in den großen beschreibenden Block sollte aufgenommen werden, welche Domänen und welche Sectoren adressiert werden. Der Punkt Application aus Tabelle 3 ist sowieso überflüssig, der ist mit der Technologie-Dimension erfasst, das ist ja die JRC Taxonomy.
> Damit haben wir einen ausführlichen Beschreibungsblock und eine Tabelle mit den Dimensionen und Abhängigkeiten und eine Beschreibung der Zwischenschritte, der Stages: wo genauer beschrieben wird, was das Ergebnis in diesem Stage sein wird: welche Technologie, etc. vorhanden ist.
> Bitte vereinfacht die Templates entsprechend und schaut Euch bitte meien Beschreibung unten an und vervollständigt sie, so dass den Empfängern der Mail eine Erklärung zu dem Template mitgegeben wird. Das Template ist ja alles andere als selbsterklärend.
>
> Bitte schreibt mir auch einen ausführlichen Draft, was genau wir von INRIA erwarten, der Einzeoler ist mir zuwenig an Handlungsanweisung, bitte schreibt auch, an wen die 4 Programme leads ihren Input senden sollen: nämlich an INRIA, die daraus die erste Roadmap zusammen mit einer Aufbereitung von ca 2-3 Challenges aus den 60 ursprünglichen Challenges schreiben sollen.
>
> Bitte sendet mir das überarbeitete Template und Beispiel sowie die ausführlichere Mail an die Partner bis morgen (Dienstag) Mittag zu.
> Danke
> Claudia
>
> -----
>
> Dear WP3 Participants,
>
> Thanks again to all who attended our Kick-Off on July 11th and for participating in the very fruitful discussions. Due to our discussion we updated our first version of a roadmap skeleton we presented during the KoM. Just a short wrap up: we decided to specify several roadmap units.
> Each unit should comprise:
> (1) a problem description, which describes the addressed challenge, (2) the status quo with respect to e.g. technologies/solution/methods already available to address the problem, (3) an estimation until when the challenge should be solved; (4) as we want to focus on research and innovation, the roadmap unit should describe in a comprehensive manner: which concrete research questions should be addressed; (5) as the challenge should be beneficial for industry as well, the industrial need should be elaborated as well. (6) as a unique SPARTA approach, we want to consider the social aspects of the challenge as well and, (7) the benefit for EU should be made clear. (8) to be able to understand the importance of the challenge the description should comprise a SWOT analysis that enables to derive the opportunities, but the risks as well.
> (9) which security domain will be addressed (see JRC taxonomy), (10) which sector or vertical is addressed (see JRC taxonomy)
> (11) another USP of the SPARTA roadmap might be our early consideration of emerging technologies. That is why we ask whether the solved challenge might be related to emerging technologies (e.g. post quantum crypto is closely related to the development of quantum computers though the technology is used in normal computer architectures).
>
> With these 11 elements the challenge and its impacts should be described sufficiently.
>
> Next: we have to define the different steps to solve the problem/the challenge.
> During our meeting we emphasized, that we want to describe a combined roadmap which describes the technological development steps (TRL-level) as well as relations to education capabilities that must be developed as well as certification measures. These are the three dimensions of the roadmap and the dependencies between the different elements.
> To reach the final goal, ie. to solve the challenge, several (readiness) levels, i.e. several stages of development are required. Each such stage should be described in more detail.
>
> ----
> At the meeting we have agreed to send out a template for contribution to the roadmap. It should be used by:
>
> 1) INRIA, to create an initial roadmap
> 2) Program leads and leads of other WPs that provide feedback to the roadmap.
> 3) SPARTA Workshop organizers, to include inputs from associates
>
> We attached the template and an example of a filled out document to this e-mail.
>
> Furthermore, here are the meeting minutes from our Kick-Off meeting:
>
> https://docs.google.com/document/d/1R5ttrQPHN0OixKter0MqAsmabCYFVtEe6JCMkqA…
>
> Viele Grüße,
>
> Sergej und Bojan
>
>
>
> --
> Bojan Kolosnjaji
> Chair of IT Security - Prof. Dr. Claudia Eckert Department of Informatics Technical University of Munich Boltzmannstr. 3
> 85748 Garching
> Tel. +49 89 289 18585
> Fax +49 89 289 18579
> e-mail: kolosnjaji(a)sec.in.tum.de
> http://www.sec.in.tum.de
--
Sergej Proskurin, M.Sc.
Wissenschaftlicher Mitarbeiter
Technische Universität München
Fakultät für Informatik
Lehrstuhl für Sicherheit in der Informatik
Boltzmannstraße 3
85748 Garching (bei München)
Tel. +49 (0)89 289-18592
Fax +49 (0)89 289-18579
Dear WP3 Partners,
As already announced, we will host the WP3 kick-off meeting at TUM in Garching near Munich on Tuesday, the 11th of June. We would like to cordially invite you to join us! Every partner is asked to give a little talk (10 minutes, see Agenda below). We plan to discuss the topics very carefully with all participants. Discussing complex topics via telephone conference calls are always very inefficient. Hence, I urgently ask you to participate physically in the KoM at Munich. At least, I expect all WP3 partners with at least 6PM to physically attend the KoM. These partners are: INRIA, CNR, YWH, IMT, CINI, L3CE, ITTI.
While there will be sufficient technical support for remote participation, your active participation is key to our success. As such, please fill out the following attendance list and join us in Garching:
https://docs.google.com/spreadsheets/d/1wDN9fs0ng1lZr7ERxwsPq8yFvML__CAwXXL…
For the KoM, we would like you to ask every partner to prepare an introductory presentation (10 min in total) for the Session 2 (see agenda below). The presentation should briefly introduce the partner (2 min) and mainly focus on the partner's view/understanding of the "definition of a roadmap" (8 min). Together, we will collect the most important points and compose a first definition of the SPARTA roadmap.
In Session 3, we would like to ask the task leaders to prepare a presentation covering the individual tasks, the current state, and future agenda (20 min). We would like to use the presentations as starting points for a discussion (25 min) targeting to clarify open questions and future directions.
Please find the agenda for the KoM under the following link (please consider that the agenda might still be subject to change):
https://docs.google.com/document/d/1eLmJeOI-n5wH2iAOJdgZDjVXZ24nMxz8EQMt--H…
Besides, we would like to invite you to the evening event, during which we will enjoy the Bavarian cuisine.
In regard to a potential venue location close to TUM, you can think of choosing Motel One [0]. (This hotel is two metro-stops away from TUM.) Otherwise, there are lots of possibilities directly in Munich or Garching.
I am looking forward to meet with you preferable face-to-face on 11th of June in Munich.
Regards
Claudia Eckert
[0] https://www.motel-one.com/de/hotels/muenchen/hotel-muenchen-garching/
--
Prof. Dr. Claudia Eckert
Fraunhofer-Institut für Angewandte und Integrierte Sicherheit (AISEC) Institutsleitung Parkring 4, 85748 Garching bei München Tel. +49 89 3 22 99 86-285 Fax +49 89 3 22 99 86-299
e-mail: claudia.eckert(a)aisec.fraunhofer.de<mailto:claudia.eckert@aisec.fraunhofer.de>
http://www.aisec.fraunhofer.de
Technische Universität München
Lehrstuhl für Sicherheit in der Informatik Fakultät für Informatik Boltzmannstr. 3
Tel.: +49 (0)89 289 18578
Fax: +49 (0)89 289 18579
85748 Garching, Germany
http://www.sec.in.tum.de
My signature is certified by Deutsche Telekom Root CA 2:
http://wwwca.telesec.de/cgi-bin/caservice/Common/InstallRoot/DT-Root-CA-2.d…
Dear all,
not really a roadmap but a well argued analysis of China's digital rise including some considerations of cyberrisks.
Michael
--
Dr. Michael Friedewald
Coordinator ICT Research
Competence Center Emerging Technologies
Fraunhofer-Institut für System- und Innovationsforschung ISI
Breslauer Straße 48 | 76139 Karlsruhe
fon: +49 721 6809-146 | fax: +49 721 6809-315
assistent: +49 (0) 721/6809-189 (Silke Just)
mailto: michael.friedewald(a)isi.fraunhofer.de
http://www.isi.fraunhofer.dehttp://works.bepress.com/michael_friedewald/
Dear WP3 Partners,
We set the date for the WP3 Kick-Off Meeting at TUM, it will be the 11th
of June. Multiple people asked me if remote attendance is possible. We
will make an effort to enable that, although we encourage you to be
physically present if you can.
Soon we will get back to you with more information about the meeting.
Best regards,
Bojan
--
Bojan Kolosnjaji
Chair of IT Security - Prof. Dr. Claudia Eckert
Department of Informatics
Technical University of Munich
Boltzmannstr. 3
85748 Garching
Tel. +49 89 289 18585
Fax +49 89 289 18579
e-mail: kolosnjaji(a)sec.in.tum.de
http://www.sec.in.tum.de