nSHIELD – TA Amendments

1. nSHIELD – TA Amendments TMC Call Conference

2. TMC Members Gordana Mijic Paolo Azzoni - Antonio Abramo Marco Cesena Andrea Morgagni Elisabetta Campaiola Poulakidas Athanasios Francesco Flammini Luigi Trono Josef Noll Spase Drakul Andrea Fiaschetti Antonio Ruggieri 2

3. Amendments Amendment #1 – WP5 - UNIROMA Amendment #2 – WP3 - ISD & Eurotech Amendment #3 – WP3 - SICS Amendment #4 – WP3 - SICS Amendment #5 – WP3 – SICS Amendment #6 – All WPs - Tecnalia Amendment #7 – WP3-WP4-WP5 - Eurotech Amendment #8 – WP1 – Acorde Amendment #9 – TUC (Harry Manifavas) 3

4. Amendments Amendment #1 –UNIROMA (Andrea Fiaschetti) Andrea Fiaschetti will give a short description by January 30 2012.

5. Amendments Amendment #2 – ISD & Eurotech (Paolo Azzoni) The Work Package 3 will be under the responsibility of «Integrated Systems Development» (ISD). ISD will replace Eurotech (ETH) as WP3 Leader. ETH will still work and support all the tasks in TA where ETH is mentioned. Reason: After nSHield project reformulation, ETH doesn't have enough MM to perform a full time coordination for WP3. The leadership goes to ISD since it has the greater number of MM (58) in WP3. ISD accepted the WP3 leadership role.

6. Amendments Amendment #3 – SICS (Christian German) Under current Task 3.1 on page 73 below the paragraph ending with: "... process of refinement and enrichment not only within asingle layer (e.g SPD Node) but also among all nSHIELD layers." Add the following short paragraph:"While the Nano Node is quite small, it may still contain a number of relatively complex and/or security sensitive software components. To minimize success rate of malicious attacks, software components must be isolated from each other. A secure and power efficient method for achieving this is provided in many modern microcontrollers in form of privilege rings and virtualization support. Secure virtualization technologies for Nano Nodes will be investigated and implemented."

7. Amendments Amendment #4 – SICS (Christian German) Under Current Task 3.2 on page 74 below the paragraph ending with: "...strictly connected with SPD Network level (WP4) of nSHIELDframework supporting secure and dependable communication strategies among differentnodes." Add the following short paragraph:"Given the amount of software running on Micro Nodes, in conjunction with the complex communication protocols and interfaces and cryptographic operations, security evaluation of the Micro Nodes may become very challenging. To minimize such effort, software running on the Micro Node should use some isolation method, for instance by means of hardware virtualization. Secure virtualization technologies for Micro Nodes will be investigated and implemented."

8. Amendments Amendment #5 – SICS (Christian German) Replace the following text on page 74:"Trusted ESs based on TPM or smartcard which offer facilities for the secure generation of cryptographic keys, and limitation of their use, in addition to a hardware pseudo-random number generator (T3.5). For instance, TPM for trust ESs also includes capabilities such as remote attestation and sealed storage. Such a Trusted Platform Module can be used to authenticate hardware devices. Since each TPM chip has a unique and secret RSA key burned in as it is produced, it is capable of performing platform authentication. One possible application of this technology is the verification that a system seeking access is the expected system (T3.5). The development of this technology relies on the identification and definition of proper trust-oriented specification as well as on the conceiving and design of innovative architectures (WP2) and is strictly connected with SPD Network level (WP4) of nSHIELD framework supporting secure and dependable communication strategies among different nodes."

9. Amendments Amendment #5 – SICS (Christian German) With the following (a couple of small additions to cover authorization not just authentication):"Trusted ESs based on TPM or smartcard which offer facilities for the secure generation of cryptographic keys, verification of digital signatures, and limitation of their use, in addition to a hardware pseudo-random number generator (T3.5). For instance, TPM for trust ESs also includes capabilities such as remote attestation and sealed storage. Such aTrusted Platform Module can be used to authenticate hardware devices and/or verify their privileges. Since each TPM chip has a unique and secret RSA key burned in as it is produced, it is capable of performing platform authentication and authorization. Possible applications ofthis technology include the verification that a system seeking access is the expected system or that it has sufficient privileges to perform the requested action (T3.5). The development of this technology relies on the identification and definition of proper trust-oriented specificationas well as on the conceiving and design of innovative architectures (WP2) and is strictly connected with SPD Network level (WP4) of nSHIELD framework supporting secure and dependable communication strategies among different nodes."

10. Amendments Amendment #6 – Tecnalia (Eider Iturbe) • In Section 3.1.2 Gantt chart (pag.61), the deliverables numbers inside the chart don't match the numbers in "List of Deliverables" in pages 63-65. Besides the tasks of WP7 in Gantt chart don't match WP7 description in pages 89-95. • Section 3.1.3, in "Milestones" list, the deliverables numbers defined as means of verification don't match the numbers  in "List of Deliverables" in pages 63-65.

11. Amendments Amendment #7 – Eurotech (Paolo Azzoni) • Regarding WP3, WP4 and WP5, the TA doesn’t show clearly who is the Responsible for the any deliverables. As it is, each of these deliverables is shared between the WP tasks without having a unique Responsible. To resolve this problem and avoid any misunderstanding each deliverable has to be spilt in different parts (one part for each task). In this way for each part we have a unique Responsible. At the end, the WP Leader will collect the input from the Task Leaders and will finalize the document. This clarification will be included in the next TA Amendment. • The template for the WP3 as example. The WP4 and WP5 have to follow this example according with their own tasks and deliverables.

12. Amendments Amendment #8 – Acorde (Lorena de Celis) • In task 1.2, it is indicated SC as a partner. To delete.

13. Amendments Amendment #9 – TUC (Harry Manifavas) We propose the following amendment: Reduce the number of tasks TUC participates in. In the initial proposal we stated that we could provide contribution to 27 tasks (out of 29 in total). We have come up with a more realistic figure (15) that is consistent with the average figure (tasks/partner) for all the partners. I have moved the MM allocation inside every WP, so now all our MMs appears only in the tasks that we are interesting in. We have abandoned completely only one WP (WP6). I have also moved the previous MM number from WP6 to other WPs. In this way we can concentrate on specific tasks instead of spreading thin our efforts and man power all over the project’s space. On top of that, we have not signed contracts yet with the relevant authorities in Greece. As a consequence it is much more difficult to promise contribution to such an extent. However, by focusing on less tasks that is realistically more manageable.