cision support system capable of providing the sys-
tem security manager with an easy and understand-
able mechanism to tune and trigger security-related
actions and rules based on fine-grained input metrics
and measurements.
2 SPD METRICS IN
HETEROGENEOUS DEVICE
ECOSYSTEMS
The meaning of metric can be understood from a
naive business standpoint in the sense that metrics
should be made similar to human understanding
because they need to be recognized and understood
by both business and technical engineers operating on
the systems. Informational SPD metrics are deemed
an important factor when making reliable, well-
grounded decisions about several aspects of security
and dependability, ranging from the design of SPD
architectures and controls to the effectiveness and
efficiency of SPD operations. SPD metrics strive to
offer a quantitative and objective basis for security
assurance.
Given the application scope in Industrial Systems
of Systems (SoS) environment tackled in this paper,
we will analyze and combine traditional operational
indicators with SPD metrics. Metrics in industrial
operations (i.e. metrology) have always been regu-
lated and certified by a higher authority. In the IT
area this methodology has been applied in a less rigor-
ously manner, since safety has always prevailed over
security. However, SoS environments require both se-
curity and safety (part of dependability) requisites, as
threats could proceed from both virtual and real (un-
predicted/failure threats) worlds.
The spectrum of SPD metrics derived in
nSHIELD constitute the first attempt in the related lit-
erature to correlate operational and SPD metrics so
as to develop a business continuity approach for in-
dustrial sectors. It is important to highlight that con-
trol systems such as SCADAS or ICS (Industrial Con-
trol Systems) not only depend on the operational pro-
cess (which is linked directly to business), but also
is becoming progressively more dependent on robust-
ness, resilience and security factors that preserve op-
eration from malicious attacks and large failures. In-
deed, the dependability concept guarantees this fact:
dependability mechanisms deal with availability (e.g.
threats against DDoS), which is the most important
feature for industrial operations. However, security
may also be threatened in terms of integrity; for in-
stance, a man-in-the-middle attack for value modi-
fication in the communications link from smart me-
ters to concentrators could cause less profit to elec-
tric vendors and an unequal operation for distribu-
tion system operators when balancing energy offer-
ing & demand. On the other hand, the notion of pri-
vacy implies confidentiality and anonymity, and is be-
coming essential as Big Data gets involved within in-
dustrial and large organizational settings. Therefore,
nSHIELD metrics are set towards business continuity:
1) heterogeneous but measurable; 2) understandable
by the human being with comprehensible, possibly
fuzzy glossary; and 3) composable since inputs are
aggregated through an expert system. This envisaged
portfolio of requirements makes the nSHIELD view
fulfill with the so-called Security by Design (SbD)
principles (Cavoukian & Dixon, 2013): nSHIELD
SPD metrics apply to security, privacy and depend-
ability built-in concepts and functionalities within the
whole engineering process. Furthermore, such func-
tionalities are not seen as the final patch but as an in-
trinsic conceptualization of the whole and holistic en-
gineering and operation procedure. SPD metrics are
extracted from a set of SPD requirements and risks
statements within SoS scenarios.
Bearing this rationale in mind, the nSHIELD
multi-metric approach follows a quantitative focus.
This approach provides a metric template for metrics
identification and gathering process. In the first spec-
ification approach more than 60 metrics were iden-
tified and structured in layers {SPD, L
x
}. Metrics
identified as heterogeneous sometimes overlap in dif-
ferent layers. The result of measurements according
to these metrics has to be described quantitatively.
The following list oversees some of the most relevant
metrics concluded after this study
1
:
1. Code execution (Node Layer): verification that
only authorized code (booting, kernel, applica-
tion) runs on the system.
2. Network delay (Network Layer): this is a perfor-
mance metric used for measuring the delay in-
duced by a node in retransmitting incoming data.
3. Network Capacity (Network Layer): this is a per-
formance metric used for measuring the networks
capacity, which shall be large enough to allow
the necessary traffic to go through. As a rule of
thumb, at normal operation, the traffic should be
about 60-70% of the network capacity, so as to
avoid bottlenecks when there will be traffic peaks.
4. Discovery frequency (Middleware Layer):
amount of discovery events per protocol and unit
1
Upon its acceptance a more detailed list of metrics will
be presented and discussed, along with their corresponding
formulae.
PECCS2014-InternationalConferenceonPervasiveandEmbeddedComputingandCommunicationSystems
232