BB3.4.F Measurable security and privacy

BB26.F
Home Meetings Publications Student corner Factpage

Title	Multi-metrics assessment for measurable security and privacy
Page Title	BB3.4.F Measurable security and privacy
Technology Line	Reference Architecture/Implementation
Lead partner	UiO
Leader	Toktam Ramezani
Contributors	UiO, SmartIO
Related to Use Cases	SCOTT:WP7, SCOTT:WP8, SCOTT:WP11, SCOTT:WP12, SCOTT:WP13, SCOTT:WP14, SCOTT:WP15
Description	One aspect of SCOTT is the security (and privacy) assessment of system- of-systems. Assessing security, privacy or other properties that give a system its trustworthiness is challenging for the fact that such properties are not easy to measure. Some would say that e.g. security cannot be measured fully. Nevertheless, in practice we always try to calculate the damages of an envisaged attack, and then weigh in with the costs of implementing countermeasures. Therefore, what we often do as system analysts is more or less ad-hoc, and this is understandable because we are trying to “measure the unmeasurables”. This Building Block aims to make explicit into metrics and processes the methods that are normally used to assess various aspects of a system. These would guide an analyst during an evaluation and automate some of the more tedious tasks.
Main output	This Building Block will develop methodologies and processes to help with measuring different trust aspects of a system, including security, privacy, dependability. We will develop metrics for measuring such properties of a complex system, along with techniques to work with and combine metrics. We will develop tool prototypes and test them together with the Use Case partners.
BB category	Methodology (for SW/HW development), SW component, Tool or tool chain, Process, Other
Baseline	The Multi-metrics methodology from SHIELD is suggested as a starting point, to convert application requirements into e.g. network resources. The flow is as follows: a) applications having b) security and privacy requirements in need of c) network resources (in terms of security, privacy, reliability, ++). Example: a) Health Care services might need a b) privacy level A+, thus have c) requirements for isolation (VPN) when it comes to network resources. We will build on and extend the work done in previous Artemis projects. We will extend theoretical and methodological concepts developed there, as well as tools that have been developed for manipulating metrics for security, privacy, and dependability.
Current TRL	TRL 4
Target TRL	TRL 6

Activities

• Title= A language-based policy specification and enforcement in a semantic-directed, integrated and automated approach.
• status= Progress
• author= Toktam Ramezani

• Title= attribute-based encryption (from Chalmers via WP21 SharePoint)
• status= Initiation
• author= Christian Johansen

Home Facts about SCOTT-NO Assessment of Technology-TL Objectives Abbreviations in SCOTT Structure of SPs and WPs Gantt charts Meetings & Action Items Links to Sharepoint ToDo

Building Blocks(NO) BB-UC_Relation BB24.A Managed Wireless BB24.I S-ABAC BB24.L network slicing BB26.F Measurable BB26.G Privacy labels Add/edit BB

WPs, Responsibilities (NO) WP3 Distributed Cloud WP8 Managed Wireless WP22 Tech.Lines WP24 Cloud Integration WP26 Reference Architecture WP28 Building Trust Systems WP30 Open Innovation all WP

NO-Partner contrib Eye Networks OsloMet Movation NCE Smart Telenor UiO (Old) TellU Wolffia

Forms/Wiki Semantic structure Add User Add ActionItem Add PhoneConf Add Meeting Edit Footer