|Date, Time||2014/08/05, 1000-1200|
|Participants||Josef.Noll, Seraj Fayyad, Iñaki Garitano|
|related to Project||NSHIELD|
|this page was created by Special:FormEdit/Meeting, and can be edited by Special:FormEdit/Meeting/NSHIELD-MultiMetrics SocialMobility|
About the Multi-Metrics Approach
The Multi-Metrics Approach has the goal to to measure the Security, Privacy and Dependability (SPD) level of a system. The objective is to achieve an overall system SPD level, SPDSystem. The main advantage of this methodology is that it provides a simple mechanism to measure and evaluate the system security, privacy and dependability levels.
SPDSystem is a triplet, composed of individual Security, Privacy and Dependability levels (s,p,d). Each of the levels is represented by a range between 0 and 100, i.e. the higher the number, the higher the Security, Privacy and Dependability level. However, in order to end up with SPDSystem, during the whole process, the criticality is evaluated. Criticality is again a triplet (Cs,Cp,Cd), defined as the complement of SPD, and expressed as (Cs, Cp, Cd) = (100, 100, 100) − (s, p, d).
The Figure shows a system being composed of multiple sub-systems, which at the same time consist of various components.
from Toktam: My suggestion is that since systems are complicated and nested, we may need to collect metrics and parameters in existing approaches for:
- Application security, by using and not limited to OWASP as a reference (regardless of the name, this reference is one of the best),
- Network security by using, but not limited to, CWE as a reference,
- System security based on risk assessment in which measurement of risk itself is useful, and also (1- risk) might give a promising view of the level of security preservation,
- and so on to collect and then make a contribution.
In addition, if instead of the security of the whole system, just data flow and information flow is the aim of the labeling, then such references could be investigated toward these (unfortunately it is time consuming).