Hello, From Task 8.3 we decided at the beginning of the project that the asset would better suit on Task 8.1 as a prove to get information at network level has no relation with the context information to be monitored by dynamic security component. Anyway I think we can pass over this one without further impact. 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: lunes, 26 de septiembre de 2011 9:52 To: BISSON Pascal; fiware-security at lists.fi-ware.eu Subject: Re: [Fiware-security] TR: FI-WARE - WP8 Audio conference on Friday cancelled and replaced by one on next Monday (26/09 4pm-6pm) Dear all, I apologize but it’s not possible for to take part in the WP8 audio conf but I want to give you any precisions concerning the withdrawal of TID from WP8. It results in: - The loss of assets "Advanced Event Correlation" and "Abnormal Behaviour Detection System Network" (T8.1) - The loss of asset « Dynamic Security System (DSS) »(T8.3) And the loss of 40 man-months. In T8.1, TID delivered anomaly detection applications able to detect threats based on different parameters and correlation applications in charge of aggregating and analysing the information captured by those applications and making it available to reporting applications. Advanced Event Correlation TID asset proposal employed artificial intelligence algorithms to create correlations based on tags instead of identifiers, much more easier to understand and allowing sources of events independency. This asset needs a traditional SIEM to be used as collector (and presentation interface) of information. Once the alarm has been output it can be captured and processed by the traditional SIEM. ð we cannot provide an equivalent asset Behaviour Anomalies Network Detection system The goal was to identify the normal or abnormal behaviour. This behaviour, both users and systems or services, allows us to establish a baseline from which is able to detect any “standard deviation”, time and characteristic of traffic. In addition to this, this also allows us to detect both current and future threats ð we cannot provide an equivalent asset In T8.3, TID provided network security enablers providing valuable security information only available at the network level, and supporting the upper, application, level security mechanisms ð we cannot provide an equivalent asset In conclusion, concerning the T8.1, it is necessary for us to research a traditional SIEM and to develop the interface with another assets. It not possible to find equivalent assets to those initially proposed by TID. We will have to find a "siem" and develop interfaces so that we lose 40 men months. Best regards Daniel De : fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] De la part de BISSON Pascal Envoyé : mercredi 21 septembre 2011 12:24 À : fiware-security at lists.fi-ware.eu Objet : [Fiware-security] TR: FI-WARE - WP8 Audio conference on Friday cancelled and replaced by one on next Monday (26/09 4pm-6pm) Dear All, Sorry for the typo in the email I sent you regarding the date of our next audio conference. For the sake of clarification, let me confirm you that our next WP8 audio conf would be on Monday 26th September from 4pm till 6pm (max). Best Regards, Pascal PS: Details remain the same as usual to join this audio. De : BISSON Pascal Envoyé : mercredi 21 septembre 2011 11:55 À : fiware-security at lists.fi-ware.eu Cc : BISSON Pascal; GIDOIN Daniel; slim.trabelsi at sap.com; Antonio Garcia Vazquez; 'Michael Osborne'; LELEU Philippe; 'Seidl, Robert (NSN - DE/Munich)'; 'Marton, Gabor (NSN - HU/Budapest)' Objet : FI-WARE - WP8 Audio conference on Friday cancelled and replaced by one on next Monday (26/09 4pm-6pm) Importance : Haute Dear WP8 colleagues, Due to another meeting I would have on Friday 23 I’m obliged to cancel our WP8 audio planned this week and to reschedule it to next Monday afternoon. So our next WP8 audio conf will take place exceptionally on Tuesday 26th for 4pm till 6pm max (the one of this week being cancelled). Here is the provisional Agenda for our WP8 audio conf of next Monday (in case you’d like to change or add something please let me know) · Short report on the FI-GA (incl. WP8 session) held in Turin last week o With respect to this let me inform you that I uploaded my presentations together with the ones of each of the task lead on the Forge (see “WP8 at GA September 13-16, 2011” folder where all presentations have been uploaded) · Review of progress (per task and per GEs) this in view of Milestone we have (especially M5) o Prior to our meeting I invite you to have a look at the Features backlog we came up with so far for each of the GE we have now (this information is available on our Web Site – Security Project > Features backlog folder (I invite here Task lead and/or GE owners to update if any those backlogs) 1. Cross-review of features backlog would also be organized here. · Addressing M2 review comments for M5 o Report on things engaged to have it done: 1. with other WPs (as per demand expressed by WP8 Lead/Architect at each of the joint session with other TWP at last GA) – work engaged to be reported by WP8 liaison person with each of the other WPs 2. at task level by each of the task lead (redrafting engaged of their section for M5 update) 3. additional proposals coming from other participants also other Security AT caretakers (IBM, SAP) · Update of the week regarding information coming from Project Management and useful for our WP8 work · Other topics (please drop me an email on other topics you’d like to be discussed) o One from my side: Demand I got from TID (CA) for TID to withdraw from WP8 · To discussed based on impact assessment performed by T8.1 lead (Daniel to prepare/report at this audio) 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/20110926/41bd2d75/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy