Collaborative Open Market to Place Objects at your Service

D5.1.1 Security requirements and architecture for COMPOSE

The envisioned COMPOSE platform will support the development of applications which want to make use of real-world smart objects and the data they generate. For this purpose, the project aims at the simplifying software development for the Internet of Things (IoT). This involves various stakeholders, ranging from Software developers, over data providers, to end-users. Of course, the development of application logic for various contexts, different user groups, and the processing of potentially security critical data induced delicate security problems. So far, single security components or interactions with them have been described in several deliverables. This is not surprising as security is usually constructed orthogonal to the rest of the system and is not directly relevant for functionality but must support it transparently. With this document, we provide the first overview and holistic presentation of the security architecture we will implement in COMPOSE. As such, it will also reflect a trade-off between security and flexibility and show the effort required to achieve both. Considering this goal from an extreme security point of view: the security architecture in COMPOSE must protect security critical data processed by any type of application, vulnerable or benign with negligible user interference. Of course, the security architecture must adapt to the system evolving in this project. As a consequence, this document can only introduce the first draft of the security architecture. It will be iterated and refined until the end of the project. We start from an elaborated collection of security requirements collected during the first year of COMPOSE and through the analysis of use-cases of pilot systems developed and considered in the project. Before the security system components and their interactions are explained in more detail, we give a general overview of the architecture. It is the basis for the rest of the document and should help the reader to better understand the overall concept. The remainder of the document will not only describe the internal structure of the main security components but also sketch their interactions. This is essential to understand the purpose of the single architectural entities and how they accomplish compliance with the security requirements. This does not only involve the description and partial definition of management information but also involves the enumeration of potential technologies feasible to implement the required infrastructure. To understand this deliverable, we strongly recommend to first become familiar with the general COMPOSE architecture. A feasible document for this purpose is deliverable D1.2.1.

Document Type: