[Fiware-security] FI-WARE - D8.5.1 -

[GIDOIN Daniel]

Please, find attached the Unit testing report concerning the Attack-Paths Engine .

Daniel

De : Antonio Garcia Vazquez [mailto:antonio.garcia at atosresearch.eu]
Envoyé : mercredi 25 juillet 2012 16:14
À : BISSON Pascal; GIDOIN Daniel; TRABELSI, Slim; DI CERBO, Francesco; Seidl, Robert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); Goetze, Norbert (NSN - DE/Munich); GASPARD Lucie; Wolfgang.Steigerwald at telekom.de
Cc : LELEU Philippe; fiware-security at lists.fi-ware.eu
Objet : RE: FI-WARE - D8.5.1 -

Pascal,


-          AP1: I've updated the tracker as requested

-          AP2: I can't report our test as passed since the component won't be ready until September (release 1.2), but as I guess  that 'N' could means that the component has failed the test I've filled the document with the status as 'Pending'

Best Regards


************************************
*      Antonio García-Vázquez      *
*        (+34) 91 214 9384         *
*  antonio.garcia at atosresearch.eu<mailto:antonio.garcia at atosresearch.eu>  *
************************************

From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com]
Sent: miércoles, 25 de julio de 2012 15:12
To: GIDOIN Daniel; TRABELSI, Slim; Antonio Garcia Vazquez; DI CERBO, Francesco; Seidl, Robert (NSN - DE/Munich); Meyer, Gerald (NSN - DE/Munich); Goetze, Norbert (NSN - DE/Munich); GASPARD Lucie; Wolfgang.Steigerwald at telekom.de<mailto:Wolfgang.Steigerwald at telekom.de>
Cc: BISSON Pascal; LELEU Philippe; fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu>
Subject: FI-WARE - D8.5.1 -
Importance: High

Dear Colleagues,

This to remind you as per instructions/guidelines provided by TID for D8.5.1 (available at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD3-8.5.1) that in complement of the issues raised by TID and that need to be fixed for each of the GE you know.

I'd like to draw your attention not raised by Miguel but clearly stated in the guidelines and as such needed to be addressed if we want to have our deliverable a chance to be first complete and second accepted:

1.       "a link to the section corresponding to the Unit Testing Plan document at the wiki will be included in a how-to-test field of the corresponding backlog entry. This will be a new field on the tracker that corresponds to the Feature. Please synchronize with your Chapter Lead, who is responsible for creating this new field in the tracker corresponding to your chapter."

·         Action Point 1: Being said I created this new field on the Security Tracker I would ask each of you for each of the features of you GE and part of the Unit test plan and report to go the feature on tracker and fill in the how-to-test field filling it with the proper link

2.       "For the WPLs/WPAs: when you generate the final pdf files with the deliverable, you must fill in the Unit Testing Report and append it at the end of the pdf file. Download the template here<https://forge.fi-ware.eu/docman/view.php/7/1142/Unit+Testing+Report.docx> and fill in adding as many blocks as GEs in the Release."

·         Action Point 2: I would ask  here each of you to urgently send or re-send me your Unit Testing Report for the GE you own (for your convenience I reattached the document)

o   Unit Testing Report IdM GE NSN => Robert

o   Unit Testing Report IdM GE DT => Wolfgang

o   Unit Testing Report Security Monitoring GE => Daniel

o   Unit Testing Report Data Handling  GE => Slim

o   Unit Testing Report DB Anonimyzer => Francesco

o   Unit Testing Report Secure Storage Service =>  Lucie


Counting on each of you to urgently perform Action Points 1 & 2 asap and preferably by end of business today or early tomorrow in order for us do final check and produce the corresponding PDF version of D8.5.1 that in any case should be delivered tomorrow prior to 5pm.

Please acknowledge receipt of this email and answer it promptly.

Best Regards,

Pascal

------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20120725/84f29aa8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Unit Testing Report_Thales-Mulval.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 15425 bytes
Desc: Unit Testing Report_Thales-Mulval.docx
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20120725/84f29aa8/attachment.docx>