Daniel About this review and regarding with Context-based security and compliance GE and Service level SIEM component we've taken with the following actions 1) FIWARE.ArchitectureDescription.Security.Context-based security & compliance (pages 4 & 5) We've revised the following points: - Comment 12: Chapter wording has been revised - Comment 13: Disclaimer wording revised - Comment 15: As rule manager was part of our proposed (and not selected) EPICS for the second Open Call their features are still pending - Comment 16: Wording revised - Comment 17: Wording revised - Comment 18: "Chapter" has been used instead of WP3. - Comment 19: No changes at this moment, see answer to comment 15. However we have still pending actions to this one: FIWARE <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> . <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> ArchitectureDescription <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> . <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> Security <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> . <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> Context <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> - <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> based <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> security <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> & <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> compliance <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Security.Context-based_security_%26_compliance> Pier Garino General comment to this page: The context-aware capabilities mentioned in the name of this GE call for some explanation about possible interactions (or about impossibility to have interactions) with context/data Management chapter (e.g.: aren't there GEs which might be exploited in the architecture of the Context-based security & compliance GE?). This should help dissipating some doubts which might arise in readers and adopters of FI-WARE architecture. I do not understand this comment. Could be possible that Pierangelo Garino will provide more details about it? 2) Security-Monitoring: OSSIM SIEM Component (PRELIMINARY) (page 12) Page wording has been revised in order to make clear that Atos tasks will be: - Configure OSSIM according with FI-WARE monitoring GE needs - Develop an advance service level SIEM component on top of OSSIM. This advanced SIEM is going to be delivered on future releases of the security monitoring GE Best Regards ************************************ * Antonio García-Vázquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of GIDOIN Daniel Sent: martes, 28 de agosto de 2012 17:59 To: fiware-security at lists.fi-ware.eu Subject: [Fiware-security] TR: Review of Architecture and Open Specifications of Security Chapter Dear all, Thank a lot to take into account the attached review on the Secutity GE which concerns you, and to keep me informed. Best regards Daniel De : Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Envoyé : mardi 28 août 2012 16:06 À : BISSON Pascal; GIDOIN Daniel; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : Review of Architecture and Open Specifications of Security Chapter Dear All, Please find attached the document containing the comments for the Security chapter. The document contains two tables concerning Architecture description and Open Specs review respectively. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non è necessario. ________________________________ ------------------------------------------------------------------ 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/20120904/7e4c0c02/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20120904/7e4c0c02/attachment.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy