AGILE 2nd F2F MEETING, 14-15 April 2016, Athens, GR

1. WP5 - Gateway Security, Data
Provenance & Access Control
LEADER: PASSAU (JUAN DAVID PARRA)
INVOLVED PARTNERS: CANONICAL, RULEMOTION
AGILE TECHNICAL MEETING ATHENS, 14-15 March 2016, Trento IT

2. Partner Contacts
Partner Name Email
Passau Juan David Parra dp@sec.uni-passau.de
Joachim Posegga jp@sec.uni-passau.de
Canonical Alexander Sack asac@canonical.com
Maarten Ectors maarten.ectors@canonical.com
Rulemotion Georgios Michalakidis georgios@resin.io
INRIA Cedric Adjih cedric.adjih@inria.fr
Emmanuel Baccelli emmanuel.baccelli@inria.fr

3. WP5 - Timeline
AGILE KICK-OFF MEETING, 12-14 January 2016, Trento IT
D5.1 [M12] D5.2 [M20] D5.3 [M24]
D5.1. First Prototype of the AGILE Identity Management System
D5.2 Usage Control and Provenance Management
D5.3 Secure Data Sharing System
MS1: Initial Design & Draft Framework
MS2: Agile Framework Release and Initial Integration
MS3: Agile Component Final Integration
MS4: Agile Integration with External Clouds
MS1[M9] MS2[M18] MS3[M24] MS5MS4[M30]

4. Progress so far (Wp8)
•We have been interacting with use cases to try to understand the data
flows
•We have looked how other projects IoT-related elicited their security
requirements:
• RERUM
• COMPOSE
• iCore
• IoT@Work (Any more EU projects? Please drop me an email)
We are reviewing different methodologies to create security
requirements to find one suitable. i.e., from use cases.
Starting to draft a small paper related to security requirements from the
Quantified-self use case.
AGILE KICK-OFF MEETING, 12-14 January 2016, Trento IT

5. Issues Identified
•Processing in the gateway is not yet clear in the use cases.
• Several use cases were (or still are) focused on pushing raw data to the
Cloud.
•We have to determine which use cases are the best for security show
casing (do we need them all?)
• It would be good to discuss the collaboration between WP5 and
JOLOCOM to understand better the Usage Control envisioned for WP5
and the data sharing app with linked data.
•Still have to clarify some contributions from other partners in WP5.
• Have we reached a decision on Node-RED and Ubuntu Core? If not,
when do we expect to know this?
AGILE KICK-OFF MEETING, 12-14 January 2016, Trento IT

6. Issues Identified (2)
•We need to clarify some questions to start IDM:
• Can the devices connected to a gateway be owned by different users?
• Do we want to consider cases when AGILE gateways communicate with each
other to build a distributed application?
• Will users download applications that map directly to their own sensors? Or
do we expect them to do some configuration/edition of the code or flows?
AGILE KICK-OFF MEETING, 12-14 January 2016, Trento IT

7. Next Steps
•Now WP5 starts!!
• Produce a simple prototype of IDM.
• Probably (Node Js + Data base)
• Start from basic functionalities (create entity, update entity, etc.)
• Refine security features afterwards (authentication protocols, access control
to change entities, etc.)
• Start discussing integration points for IDM early with partners in WP3:
• Whenever we register a sensor
• Whenever we create an application/workflow in the gateway
AGILE KICK-OFF MEETING, 12-14 January 2016, Trento IT

8. Next Milestones
AGILE KICK-OFF MEETING, 12-14 January 2016, Trento IT
D5.1 [M12] D5.2 [M20] D5.3 [M24]
D5.1. First Prototype of the AGILE Identity Management System
D5.2 Usage Control and Provenance Management
D5.3 Secure Data Sharing System
MS1: Initial Design & Draft Framework
MS2: Agile Framework Release and Initial Integration
MS3: Agile Component Final Integration
MS4: Agile Integration with External Clouds
MS1[M9] MS2[M18] MS3[M24] MS5MS4[M30]