[Fiware-security] FI-WARE - Security AT - Work to be completed by tomorrow EOB !

[BISSON Pascal]

Many Thanks Antonio.

Will take care of your input

Regards,
Pascal

De : Antonio Garcia Vazquez [mailto:antonio.garcia at atosresearch.eu]
Envoyé : vendredi 11 novembre 2011 15:25
À : BISSON Pascal
Cc : Seidl, Robert (NSN - DE/Munich); DI CERBO, Francesco; TRABELSI, Slim; Pedro Soria Rodriguez; GIDOIN Daniel; LELEU Philippe; WALLER Adrian; EGAN Richard; fiware-security at lists.fi-ware.eu
Objet : RE: FI-WARE - Security AT - Work to be completed by tomorrow EOB !

Pascal,

See attached a sort document with the additional description for the WP8.3 open call topics

Best Regards

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

From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com]
Sent: jueves, 10 de noviembre de 2011 11:38
To: Antonio Garcia Vazquez; Seidl, Robert (NSN - DE/Munich); DI CERBO, Francesco; TRABELSI, Slim; Pedro Soria Rodriguez
Cc: GIDOIN Daniel; LELEU Philippe; WALLER Adrian; EGAN Richard; fiware-security at lists.fi-ware.eu
Subject: RE: FI-WARE - Security AT - Work to be completed by tomorrow EOB !

Thanks Antonio,

Could you please initiate now a text on each of these topics for the Open Call. Half A4 at this stage should be enough.

Reading you soon.

Regards,

Pascal



De : Antonio Garcia Vazquez [mailto:antonio.garcia at atosresearch.eu]
Envoyé : jeudi 10 novembre 2011 11:18
À : BISSON Pascal; Seidl, Robert (NSN - DE/Munich); DI CERBO, Francesco; TRABELSI, Slim; Pedro Soria Rodriguez
Cc : GIDOIN Daniel; LELEU Philippe; WALLER Adrian; EGAN Richard; fiware-security at lists.fi-ware.eu
Objet : RE: FI-WARE - Security AT - Work to be completed by tomorrow EOB !

Pascal,

As I’m not currently sure about the IPR status of CRLT Thales asset

From Task 8.3 I’d include in the initial list of topics for the open call it’s two related components:


1)      Monitor system: See Epic FIWARE.Epic.Security.Context-based security and compliance.Monitoring<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Context-based_security_and_compliance.Monitoring>

2)      Rule repository: See Epic FIWARE.Epic.Security.Context-based security and compliance.Rules<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Security.Context-based_security_and_compliance.Rules>

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, 09 de noviembre de 2011 19:13
To: Seidl, Robert (NSN - DE/Munich); DI CERBO, Francesco; TRABELSI, Slim; Antonio Garcia Vazquez; Pedro Soria Rodriguez
Cc: BISSON Pascal; GIDOIN Daniel; LELEU Philippe; WALLER Adrian; EGAN Richard; fiware-security at lists.fi-ware.eu
Subject: FI-WARE - Security AT - Work to be completed by tomorrow EOB !
Importance: High

Dear Colleagues,

This just to remind you that by EOB today we should have completed our work on the Wiki and the Backlog. As requested by TID and promised to our PO and so our reviewers …

As such it is important for each of you:

·         To complete your work on the wiki and the backlog (as per feedback already sent to us by TID),

·         To provide me with an initial list of topics for the Open Call (remember I already requested from you – so please deliver it to me by tomorrow morning 12am at the latest since I would have an audio conf with Juanjo on the topic after our Virtual workshop on T8.2 and the Core GEs !! – So I definitely need your input there …

·         To use the Backlog management tracker I created and attached to the Security Chapter to create  an entry per each of the entries that belong to your task (and so GEs attached).

o   I just did it for the T8.1 (Security Monitoring GE) entries. This should not take you too long being said you have now T8.1 example to follow and that you can also refer here to the following tutorial:
http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_entries_in_the_%22Backlog_Management%22_Tracker_of_a_FI-WARE_Chapter

to further help you on this let me say you would have to first log in (on the Security Chapter) clikc on Tracker (there you would see the entries I created fro T8.1 and then click on “Submit new” to submit a new entry.
From there it is very simple since you would have do the following (in bold the fields you would have to consider):
       First select the entry type to which belongs the entry , the GEs it relates to (select the one of the list),
       Link to backlog template (just copy and past the link to the wiki description of the security entry this new entry is about.
       Summary – just copy and paste there the name of the entry from the backlog
Detailed description – just copy there the goal content of your entry from the backlog
Assigned to – assign to you or a member of your team in charge of this feature and so entry on the tracker
And then just click on the submit button and it’s done with that one and could then proceed with the next one !

                Last but not least for entries that relate to either user stories or work items (if you decided to go with them according to email I forwarded you already – not my suggestion but ok if you decide to do so fine with me as well – this was not our choice at T8.1 level) you would have to  indicate the release id and the sprint id where it would be addressed through dedicated fields (FI-WARE Release Id & FI-WARE Sprint Id).

From T8.1 side this was not yet précised but I will work on it with Daniel and so it would be done by tomorrow EOB. So please make it as well !

In case of any problems you may encountered don’t hesitate to drop me an email and give me call on my mobile tomorrow’s afternoon.

Thanks in advance for your work on this and counting on you to have all finalized by tomorrow EOB as requested.

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.
------------------------------------------------------------------

------------------------------------------------------------------
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/20111111/2f20a36e/attachment.html>