[Fiware-security] FI-WARE - Security AT -

[TRABELSI, Slim]

Hi Rodrigo,

Maybe one comment concerning the list of assets, as announced and agreed before, SAP will not provide the monitoring and signaling component (from Master).
Thank you for your comprehension.
Regards
Slim

From: Rodrigo Diaz Rodriguez [mailto:rodrigo.diaz at atosresearch.eu]
Sent: jeudi 4 août 2011 09:11
To: BISSON Pascal; Antonio Garcia Vazquez; TRABELSI, Slim; Seidl, Robert (NSN - DE/Munich); Marton, Gabor (NSN - HU/Budapest)
Cc: GIDOIN Daniel; Michael Osborne; Jan Camenisch; TRABELSI, Slim; LELEU Philippe
Subject: RE: FI-WARE - Security AT -

Dear all,
Find attached the initial assessment for T8.3. It's a draft version that needs more refinement but it can be used to identify the main gaps. Antonio will continue working on this next week to provide a more refined version.

Regards,
Rodrigo


From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com]
Sent: miércoles, 27 de julio de 2011 11:28
To: Antonio Garcia Vazquez; Rodrigo Diaz Rodriguez; TRABELSI, Slim; Seidl, Robert (NSN - DE/Munich); Marton, Gabor (NSN - HU/Budapest)
Cc: BISSON Pascal; GIDOIN Daniel; Michael Osborne; Jan Camenisch; TRABELSI, Slim; LELEU Philippe
Subject: FI-WARE - Security AT -
Importance: High

Dear Task leaders,

The slide attached even if still incomplete (but Daniel is working hard its completion with the rest of the T8.1 team) gives you an idea of what I was requesting - among others - as per last audio conf minutes (see 22/07/11 audio conf minutes).

This slides is interesting in many respects as it gives you based on assets attached to a task (here T8.1)  the way we intend to link (orchestrate) altogether the assets we have, to achieve some of the new (innovative) functionalities that would be offered by the targeted enabler (here Security monitoring GE). It can be used as it is here to depict degree of complementarity (also overlap if any) of the assets we have selected to achieve GE functionalities.

Furthermore it can be used to clearly identify gaps we have and so that we would have to cover either through developments at the level of this (T8.1) team (e.g. network topology) or to be addressed through Open Calls to come. Materializing the way we see our assets working together to deliver GEs (innovative) functionalities would also force us to also address and start detailing the enhancements or changes we see in each of them (this being seen as as many features to be reported in the features backlog we are busy with).

Last but not least it can also help us to figure out we would be requested from other ATs (this is especially true in the attached slide for what concerns CMDB we would need to achieve our targeted functionalities).

Hope this email would be helpful to you and that with this email and slide we could produce similar slides for each of the GEs owned at the level of each of your task.

To be further discussed with you at our next audio conference. Would appreciate if you could come up at our audio conf of Friday with similar slides from your side to be introduced and discussed as it can only help us to make progress on this.

Hearing from you and talk with you on Friday.

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/20110804/adec6cbb/attachment.html>