[Fiware-security] Topic for Open 1st Call

[BISSON Pascal]

Thanks Antonio.

And yes as discussed and agreed at our last audio conference we can wait till the second Open Call to present the 2 topics you briefly introduced hereafter.

Regards,
Pascal

De : Antonio Garcia Vazquez [mailto:antonio.garcia at atosresearch.eu]
Envoyé : mardi 13 décembre 2011 18:38
À : BISSON Pascal; Seidl, Robert (NSN - DE/Munich); TRABELSI, Slim; DI CERBO, Francesco; ext Anja Lehmann; GIDOIN Daniel
Cc : fiware-security at lists.fi-ware.eu
Objet : RE: Topic for Open 1st Call

Pascal,

As I've told you last month I've two topics that could be addressed in the context of Task 8.3

The fact is that their features could be covered by Compliance Governance Dashboard & CRLT Thales assets but I don't know if we unfortunately will have to reject them  because they still have some open issues:


-          CRLT : Its IPR details are not clear at this moment. Daniel is still waiting an answer from Tilburg about this

(Ref wiki asset description: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/CRLT_Compliance_Request_Language_Tools)



-          Governance Dashboard: Its IPR details addresses to its Web page, but the Web is not available anymore.

(Ref wiki asset description: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Compliance_Governance_Dashboard)


@Daniel: Do you have additional information about them?

If you and Daniel are agree with me we could wait till the second call for their publication in the case we are not able to solve these problems

The  topics to be published would be


1)      Monitor system ( 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> ):

This GE component will analyze context and status information from the End-User environment and will check security solution's performance level by comparing the obtained information with the compliance conditions PRRS framework had previously sent; on a noncompliance situation monitoring systems should trigger PRRS framework sending the signal previously defined in the set of rules received.

As an additional feature Monitoring services will have the capability to produce periodical reports to get expert users the possibility of produce performance and other statistical analysis

Note: In the case we could get the IPR details on time this component should be covered by Runtime compliance monitoring system from CRLT asset and from Governance Dashboard asset.

2)      Rule repository ( 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> ):

This GE component will be in charge of managing the applicable set of rules that will determinate the compliance situation of an end user context.

It will allow storing and managing compliance requirements and relevant specifics at various abstraction levels as well as give the possibility of checking end-to-end business processes for compliance against the set of applicable constraints during design-time as well as will also signal PRRS framework when a rule is changed.

Note: In the case we could get the IPR details on time this component should be covered by Compliance requirements manager, Compliance rule modeler and Design-time compliance verification manager from CRLT asset.

Additionally Fragmento asset will also should be integrated with this component to give the component reuse of already defined rules capabilities


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: martes, 13 de diciembre de 2011 13:28
To: Seidl, Robert (NSN - DE/Munich); TRABELSI, Slim; Antonio Garcia Vazquez
Cc: DI CERBO, Francesco; ext Anja Lehmann; GIDOIN Daniel; BISSON Pascal; fiware-security at lists.fi-ware.eu
Subject: TR: Topic for Open 1st Call

Dear Task leads/GE owners,

It appears that a Google spreadsheet has been put in place to advertise on candidate topics FI-WARE is proposing for Call 1. This document is shared with UC projects that have or would also have their own candidate topics for each of our calls. The topics present in this shared Google spreadsheet would be the ones presented and discussed at the AB meeting that would take place on Dec 15. For those of you who have candidate topics ready for call 1 please put them in the same way we did for the digital forensics for evidence topics Daniel and I added there. Drop me and Daniel an email once done.

Please notice that for the time being there are more topics coming from UC projects which have been proposed rather than from FI-WARE which is a good sign to give to UC Project with respect to Open Call (at least first one) but in the meantime we should come up with some from FI-WARE side. That's side it is important as we agreed to propose from our Security side a few (hot/burning) topics. The other topics will go to the second Open Call.

Regards,
Pascal

De : BISSON Pascal
Envoyé : mardi 13 décembre 2011 12:51
À : 'Juanjo Hierro'
Cc : BISSON Pascal; GIDOIN Daniel
Objet : Topic for Open 1st Call

Hi Juajno,

I added a topic on Digital Forensic for evidence in scope of task T8.1 and GE attached.

https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdHFLUXozQU9lem5rWVRBeS02czJmNlE#gid=1

please have a look and provide me and Daniel with feedback. If more is requested please let us know.

In the meantime I found the file a little bit sparse especially for what concerns FI-WARE topics for first open call which worries me a little bit. How much topics do you expect coming from FI-WARE for this first Open Call ? BTW could you please remind me the budget for now the three Open Calls ?

Hearing from you and many thanks in advance fro your feedback.

Regards,
Pascal

PS: From our WP8 side we should have two more topics from open call coming from Core GE in scope of T8.2 (the topics I reported already at the review meeting).




------------------------------------------------------------------
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/20111213/8f70a82f/attachment.html>