[Fiware-security] FI-WARE - Security - Audio-conference 07/10/2011 - 10am-12am (Minutes)

[TRABELSI, Slim]

Hi Pascal,

I updated the Wiki according to the last procedure https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Security_in_FI-WARE#Optional_Security_Enabler

Thank you
BR
Slim

=====================================
Dr Slim Trabelsi
Researcher

Security & Trust
SAP Labs France
805, Avenue du Docteur Maurice Donat
BP 1216 - 06254 Mougins Cedex, France
T +33 4 92 28 63 45
M + 33 6 11 99 85 79
www.sap.com

From: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of BISSON Pascal
Sent: lundi 10 octobre 2011 09:25
To: Fiware-security at lists.fi-ware.eu
Subject: [Fiware-security] FI-WARE - Security - Audio-conference 07/10/2011 - 10am-12am (Minutes)

Dear All,

Short minutes of WP8 audio conference of last Friday:

Present:
Antonio (ATOS)
Slim (SAP)
Robert (NSN)
Francesco (SAP)
Daniel (Thales)
Pascal (Thales
Alexandra (DT/T-Systems)
=MsoNormal>

1.       Production Vision for M5 / Security Features backlog

*         T8.1 (Thales)
Security monitoring GE section has been updated. Accordingly glossary of terms and question marks sections ha >
Assets description attached to that GE have not been yet entered.
Action Thales Daniel to have it done asap and by Monday EOB at the latest. This with support of asset owners. Daniel to drive the process.
Entries to the backlog: headlines of entries for Security Monitoring GE have been entered. Special attention has been paid to structure and organize entries according to Agile methodology definitions of themes, epics, features and user-stories. This has been even checked with Agile expert here at Thales. Action Th escriptions of entries. Deadline: 10/10/2011 EOB.

*         T8.2 (Thales)
Core Generic enablers section has not been yet updated on the wiki but content has been produced, checked and agreed.
Actions set for NSN (deadline 10/10/2011 EOB):

*         to upload new content of that section on the wiki.

*         to enter description of assets attached to each of the 3 GEs (IdMgt, Privacy, Data Control)

*         to add typed (Themes, EPICS, Features, User Stories) entries attached to these Core Generic enablers to the Security Features backlog
                               ISSUE RAISED with respect to INRIA asset - Action NSN Robert to organize an audio with INRIA (Daniel) and Pascal to discuss the issue and find a way out being the INRIA asset is not mature enough to be selected.
                          &nbs p;    Audio-conf with Use Case projects to introduce them to Core Generic Enablers as per today: Action NSN to send a reminder for a date to be announced by Pascal to Juanjo.

*         T8.3 (ATOS)
Descriptions of assets attached to T8.3 GE have been uploaded.
Actions set for ATOS (deadline 10/1 >

*         to check/update on the wiki the section devoted to T8.3 GE aka context-based security & compliance

*         to revisit entries attached to this Generic enabler and entered to the Security Features backlog since some of them do not perfectly fit w ry announced and/or are too close of asset description.

*         T8.4 (SLIM)
Descriptions of assets attached to T8.3 GE have been uploaded.
Actions set for SAP (deadline 10/10/2011 EOB):

*         to check/update on the wiki the section devoted to T8.4 GE aka optional generic security enablers

*         to move entries attached to this Generic enabler (EPICS, Features and User-stories) and entered them to the Security Features backlog to the right place (Materializing Security in FI-WARE ...)

*         to upload the description of each of the assets attached to T8.4 GE.
NB: Slim announced a internal meeting to come between FI-WARE and FINEST SAP teams.

*         since some of them do not perfectly fit with the Agile type category announced and/or are too close of asset description.


Action Thales Daniel to have it done asap and by Monday EOB at the latest. This with support of asset owners. Daniel to drive the process.
Entries to the backlog: headlines of entries for Security Monitoring GE have been entered. Special attention has been paid to structure and organize entries according to Agile methodology definitions of themes, epics, features and user-stories. This has been even checked with Agile expert here at Thales. Action Thales: to add the descriptions of entries. Deadline: 10/10/2011 EOB.

2.       Meetings

*         Virtual meeting with Usage Areas - date to be announced soon.

*         No WP8 physical planned so far

Update on the security requirements (question marks) coming from the other Chapters

*         So far no official update was provided to WP8 team but deadline was 07/10/2011 EOB.

*         According to report provided Pascal and Daniel may organize a Call during the week

*         In the meantime it is important that each of the representatives of this team appointed to follow-up activities of other teams to contact their counterparts, liaise with them on the topic in order to have an update and textual proposal to be discussed asap and at the latest at our next audio conference.

Action: Slim, Daniel, Xavier and Wolfgang/Alexandra to report at next meeting for what concerns respectively update of the security requirements/questions marks section of WP3, WP4&WP6, WP5 and WP7

3.       ISSUES FACED BY THIS TEAM

*                    Issues are mainly due to the fact that all content uploaded on the wiki would be made public. This has raised a number of serious concerns at the level of members of this team and called for a public and private wiki thus causing double work (decide on what to expose as public whereas still meaningful whereas to keep private to our team). Furthermore the tooling off the wiki was not in favor of performance  ...



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20111010/86035298/attachment.html>