<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Classification of Diversity for Dependable and Safe Computing</article-title>
      </title-group>
      <fpage>0000</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>The article deals with generalization of diversity and version redundancy application to protect security and safety critical systems. The main problem for such systems is the occurrence of common cause failures (CCF). It is shown that as dependable computing is combining of reliable, safe and secure computing a principle of diversity can be applied to minimize risks of CCF and assurance of requirements to all attributes. It is reported about need to respond to new technologies and challenges in this area by improvement exist classifications of diversity. It is given the facet-hierarchical representation of the most representative schemes of diversity. The united classification of types of diversity from different domains is proposed. The classification scheme is based on the NUREG-7007. A possibility to assess and assure security and safety by using the resulting classification is discussed for clouds systems and other technologies.</p>
      </abstract>
      <kwd-group>
        <kwd>diversity</kwd>
        <kwd>NUREG</kwd>
        <kwd>facet-hierarchical classification</kwd>
        <kwd>united classification</kwd>
        <kwd>common cause failures</kwd>
        <kwd>critical systems</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1.1</p>
    </sec>
    <sec id="sec-2">
      <title>Introduction</title>
      <sec id="sec-2-1">
        <title>Motivation</title>
        <p>
          Development and implementation of dependable software and hardware components
becomes more and more important for safety and security critical systems. The main
problem for such applications is to reduce the risk of common cause failures (CCF).
CCF is coincidental failure of two or more structures, systems or components is
caused by any latent deficiency from design or manufacturing, from operation or
maintenance errors, and which is triggered by any event induced by natural
phenomenon, plant process operation, or action caused by man or by any internal event in the
instrumentation and control system [
          <xref ref-type="bibr" rid="ref1 ref2 ref3">1-3</xref>
          ].
        </p>
        <p>
          One of the most effective solutions to the CCF problem is diversity, which makes
each version of the system unique, that means the probability of occurrence of CCF is
minimized [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. Diversity is a principle in instrumentation systems of sensing different
parameters, using different technologies, using different logic or algorithms, or using
different actuation means to provide several ways of detecting and responding to a
significant event [
          <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
          ].
        </p>
        <p>Thus, solving the same problem in different ways, for example using different
programming languages or different development teams, you can avoid system failure
due to one error. Since in this case the faults will be various in each version, which
means that the probability of CCF is significantly reduced.</p>
        <p>Given the importance of effective implementation of diversity, there is a need to
evaluate and select the most appropriate type of diversity. However, with the
development of information technology, such task becomes more and more difficult, as the
question arises as to how to use diversity and how to evaluate the security of
multiversion systems when using such technologies. In addition, designers are trying to
apply new technologies to provide diversity. This leads to a difficult choice of the
type of diversity for a particular application.</p>
        <p>
          To make this choice, a clear, ordered structure is needed to narrow the search
circle. There are a large number of different classifications that represent various aspects
of diversity [
          <xref ref-type="bibr" rid="ref2 ref3 ref4 ref5 ref6 ref7 ref8 ref9">2-9</xref>
          ]. Despite this, over time emerges a need to update and generalize
them with considering of new technologies and challenges.
1.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>State of the art</title>
        <p>Currently, there are many different classifications of diversity, each of which deals
with a narrow aspect of the security of a particular system. However, such a deep
detail prevents to look at the situation as a whole. Consequently, it have to combine
the most well-known classifications, which cover a sufficiently large number of types
of diversity.</p>
        <p>
          The most representative on this topic are following works. The technical report of
the diversity of critical systems in the nuclear power industry NUREG-7007 [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ],
which in fact got status of standard, considers the protection of both software and
hardware components. At the same time, software diversity is limited to N-version
programming. The paper “The Multiple Faces of Software Diversity ...” [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] structures
the research devoted to software diversity. It is the most complete overview of works
on software diversity, although it does not contain its exhaustive classification. In
addition, there is the article describing where and when it is possible to apply
diversity to protect the software “SoK: Automated Software Diversity” [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. Besides, authors
analyze automated techniques of software diversity beyond the scope of N-version
programming and suggest the classification of diversity based on software life cycle.
However, it is not enough to describe all types of diversity.
        </p>
        <p>
          There is a number of works, which clarify some aspects of diversity. The
monograph [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] considers diversity to assure software fault tolerance. It is a classic work on
this topic, although it is somewhat outdated at the moment. The article [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] offers a
model of multi-version (n, m) – version systems that details the structure of N-version
programming. An extension of the classification [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] was proposed in [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>Hence, there are a lot of classifications and applications of diversity in safety and
security critical domains during last twenty years. However, there is not general
classification of diversity and techniques to join different version redundancy types.
1.3</p>
      </sec>
      <sec id="sec-2-3">
        <title>Goals and structure</title>
        <p>The goal of the paper is to develop the unified classification of diversity. For this, we
first consider the basic principles of the construction of classifications and describe
the general approach to the representation of diversity in the facet-hierarchical
structure (Section 2). Next, a plan for combining classifications is disclosed and the
process of building a unified classification of diversity is described (Section 3). Results
of the united classification development are presented (Section 4). Last section
concludes and presents future steps of research.
2
2.1</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Principles of classification</title>
      <sec id="sec-3-1">
        <title>Type of classifications for diversity</title>
        <p>
          The main types of classifications are faceted, hierarchical and facet-hierarchical (FIC)
[
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. The basis of the facet classifications is the emphasizing of classification features
in the subject domain under consideration, which are called facets. All terms from this
area attribute to a particular facet.
        </p>
        <p>The hierarchical classification method consists in dividing the whole set of terms
from the subject domain into groups, which are further divided into subgroups, and
these in turn can be further divided. Thus, subordination is established between the
classification groups, which has the form of a hierarchy.</p>
        <p>FIC consists of taxons and classification attributes. First, a set of objects form
taxons, which are divided into groups according to classification features, which in turn
are arranged in a certain hierarchy. The taxons themselves are also divided into
subgroups, thus forming a subordination between taxons.
2.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>General approach</title>
        <p>Depending on the type of classification, the approach to its construction is somewhat
different, but there is a general principle for constructing any classification.</p>
        <p>First of all, the formation of a set of studied objects is occurred. Each element of
which must be deterministic and should be given a semantic description. After that,
the set is divided into subsets according to certain attributes, which are unique for
each subset. At the same time, depending on the type of classification, subordination
is established between subgroups or this is not required.</p>
        <p>Thus, works on diversity that contain classification schemes can be analyzed.
These schemes are presented in the form of FIC. After that, they have been combined
into a unified classification to cover the overall picture, taking into account modern
technologies.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Integrating of classification schemes</title>
      <sec id="sec-4-1">
        <title>Faсet classifications</title>
        <p>
          The example of extending faceted classifications is obtaining NUREG-7007 [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] from
NUREG-6303 [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] by splitting one facet (Equipment diversity) into two (Equipment
manufacturer diversity and Logic processing equipment diversity), as well as
changing the semantic content of the other two facets (Software diversity and human
diversity). Software diversity has come to be called the logic diversity and human
diversity, respectively, is called the life-cycle diversity. Thus, the main changes in these
classifications are shown on figures 1 and 2 according with technique described in
[
          <xref ref-type="bibr" rid="ref10">10</xref>
          ].
The example of extending of a hierarchical classification is the combination of
software diversity (SoK: Automated Software Diversity and (n, m) – version systems).
The idea of extending is to divide the Implementation stage into 4 stages
(Requirements development, Design, Coding and debugging, Integration).
Taxonomic structure is set, consisting of three elements [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]:
        </p>
        <p>S {A, T, Ψ},
where A — a set of classification attributes A = {Ai}in=1, T — a set of taxons T =
{ti}in=1, Ψ — relationship between elements Ai ∈ A and Ti ∈ T: i.e.: A Ψ T.</p>
        <p>An example of the taxonomic structure is the facet classification discussed above.
The main feature of which is the independent of all facets.</p>
        <p>Since the types of diversity are not equivalent, but are subordinate to each other, it
is advisable to use faceted hierarchical structure. In which the classification attributes
and taxons have a hierarchical form. Thus, a hierarchical component is added to
equation (1).</p>
        <p>
          Facet-hierarchical structure is set, consisting of three elements [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]:
        </p>
        <p>SH = {AH, TH, ΨH},
where AH = {AHi}in=1 — a set of classification attributes in hierarchical structure, TH
= {... {tij...k} ...} — a set of taxons in hierarchical structure, ΔT = {ti} — subset of
taxons in hierarchical structure, which appropriate to classification attribute, Ψ: ∀AIi
↔ ΔTIi ⊂ TI —relation between taxonomic classification attributes and a variety of
taxons in a hierarchical structure.</p>
        <p>
          The example of applying facet-hierarchical classification is construction the main
part of software diversity from NUREG-7007 [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], Automated Software Diversity [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]
and (n,m)- version systems [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. The idea is to distribute the techniques of software
diversity according to the stage of the life cycle to which they apply. This example
can be represented as a matrix showing the relationship between attributes and taxons.
The result is presented in Table 1.
Then a hierarchy is built up between taxons according to their correlation. As a result,
a scheme describing some types of software diversity has been obtained (see Figure
5). Further, using the described procedure, the program diversity has been
supplemented. In particular, for the stages of Compilation and Linking, Updating, the
techniques that are used on them have been described.
        </p>
        <p>Classification
attributes
1. Software
diversity
1.1 Software
life-cycle
1.1.1 Stages
of
implementation
1.2
Implementation and
Installation
techniques
1.2.1 Types of
N-Version
programming</p>
        <p>Taxon 1
Postdistribution
Installation
Requirements
development
In-place
diversification
Different
algorithms,
logic</p>
        <p>Taxon 2
Predistribution
Loading
Design
N-self
checking
programming
Different
timing
and/or order
of execution</p>
        <p>Executing
Codding
and
debugging
Recovery
Blocks
Different
runtime
environment</p>
        <p>Implementation
Integration
N-Version
programming
Different
functional
representation</p>
        <p>Compilation and
Linking</p>
        <p>Updating</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Case study</title>
      <sec id="sec-5-1">
        <title>Basic classification schemes and features of integration</title>
        <p>
          To develop a generalized classification, the schemes described in [
          <xref ref-type="bibr" rid="ref2 ref3 ref4 ref5 ref6 ref7 ref8 ref9">2-9</xref>
          ] have been
selected. After that, they have been systematized into groups: Software, Hardware,
Information management system. Human diversity, which can be used for any system
and consists in using different teams of designers, developers and verifiers for each
version, is considered separately.
        </p>
        <p>The above classifications have been combined into a unified semantic
facethierarchical structure (2). Since the process of combining classifications is not fully
formalized in terms of the semantic component, expert support was used. To build a
unified classification, the following procedure can be used:
 Presenting the selected classifications in the form of FIS;
 Preparing the initial data for the united (classification attributes and taxons);
 Establishing the equivalences between attributes;
 Establishing the taxon equivalences for each attributes;
 Clarifying the hierarchies between attributes and between taxons;
 Developing the final version of the classification.
4.2</p>
      </sec>
      <sec id="sec-5-2">
        <title>Integrated diversity classification scheme</title>
        <p>Integrated diversity classification scheme presented in the figure 6. The scheme
demonstrates a facet-hierarchical representation of diversity, where the top level
contains such systems as software, hardware, information management. It also includes
human diversity, which can be used for any type of system.</p>
        <p>
          The general principle of construction of the scheme is the life cycle of diversified
systems .This is special clearly shown for software, where the techniques providing
diversity have been assigned to the stage of the life cycle to which they correspond.
Since the implementation stage is the most sought-after to provide protection, it was
described in more detail. Then attention was paid to fundamentally different
approaches to the diversity of software, such as automated and managed diversity. The
main difference of them is the origin of the diversity. This use of naturally established
features of software, or artificial [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] introduction of a diversity.
        </p>
        <p>The diversity of hardware has been structured according to the features of its
operation and the most important components such as equipment, design, functioning and
signal. In particular, the diversity of equipment is divided into two groups: equipment
manufacturer and equipment processing logic. The possibility of using the principle
of diversity at the network level has also been described.
4.3</p>
      </sec>
      <sec id="sec-5-3">
        <title>Applying diversity classification scheme in cloud computing</title>
        <p>
          One of the areas in which this classification can be used is the development of
applications hosted in the cloud [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. In this case, the first thing to do is to choose at what
stage of the life cycle to apply the principle of diversity. After evaluating the most
acceptable stage in terms of costs and security level, it is necessary to get acquainted
with the techniques which are used on it and select the appropriate one.
        </p>
        <p>Further, the decision is made on what type of application will be monolithic or
consisting of micro-services. In accordance with this, it is necessary to use techniques
of either managed diversity or automated one. This decision will also affect whether
different teams of developers, testers and others will be used.</p>
        <p>Since the cloud provider ensures the hardware, its diversity does not apply.
However, it is possible instead diversify the providers themselves or the geographical
location of their servers.</p>
        <p>Fig. 6. United classification scheme.</p>
        <p>
          Currently, web-services are actively developing. Their main components are
application layer, web server, apps server, operating system and database management
system. Web-services can be developed using cloud computing. In this case, the
application will consist of components-off-the-shelf [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. Thus, we can use natural diversity.
It is also necessary to use the principle of diversity on the network layer. Using the
methodology of faceted hierarchical structures and the constructed united
classification, you can choose which type of diversity to apply for cloud computing. For such
systems, the classification will take the form presented in figure 7.
In the article, the most representative classifications of diversity have been analyzed,
selected, combined and supplemented. Examples of the construction of various
taxonomic structures have been considered. Based on the complexity of describing the
types of diversity, it is suggested to use the FIS apparatus for the unification and a
corresponding procedure was proposed
        </p>
        <p>The main feature of this classification scheme is that it combines types of diversity
from different domains, takes into account new technologies that can be used in safety
critical systems. In addition, it is possible to choose ways to solve the security
problem by using the resulting classification. For this is necessary to select and apply
diversity taking into account the characteristics of domains. An example of using
classification for cloud computing was considered.</p>
        <p>Further, the diversity classification for IoT, cloud computing, AI, web-services and
other modern technologies will be detailed. To do this, it is necessary to design
certain filters that will allow moving from a general classification to an individual case
of diversity applied to a particular system.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Preckshot</surname>
          </string-name>
          , G.:
          <article-title>NUREG/CR6303, Method for performing diversity and defense-in-depth analyses of reactor protection systems</article-title>
          .
          <source>Division of Reactor Controls and Human Factors</source>
          , Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC (
          <year>1994</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Wood</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          : NUREG/CR7007,
          <article-title>Diversity strategies for nuclear power instrumentation and control systems</article-title>
          . U.S. Nuclear Regulatory Commission, Office of Nuclear Reactor Regulation, Washington, DC (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Yastrebenetsky</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kharchenko</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Nuclear Power Plant Instrumentation and Control Systems for Safety and Security</article-title>
          .
          <source>IGI Global</source>
          , USA. (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Baudry</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Monperrus</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The multiple facets of software diversity: Recent developments in year 2000 and beyond</article-title>
          .
          <source>CoRR. abs/1409</source>
          .7324, (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Larsen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Homescu</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brunthaler</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Franz</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>SoK: Automated software diversity</article-title>
          .
          <source>IEEE Symposium on Security and Privacy</source>
          . pp.
          <fpage>276</fpage>
          -
          <lpage>291</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Pullum</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Software Fault Tolerance Techniques and Implementation</article-title>
          . Artech House,
          <string-name>
            <surname>Norwood</surname>
          </string-name>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Siora</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sklyar</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kharchenko</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>(n, m)-version systems: Taxonomy, Models and Technologies</article-title>
          .
          <source>Mathematical Modelling, Information Technologies and Control Systems</source>
          .
          <volume>10</volume>
          ,
          <fpage>231</fpage>
          -
          <lpage>246</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Duzhyi</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kharchenko</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Panarin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rusin</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Diversity metric evaluation considering extended NUREG-7007 diversity classification</article-title>
          .
          <source>IEEE 9th International Conference on Dependable Systems, Services and Technologies (DESSERT)</source>
          . pp.
          <fpage>21</fpage>
          -
          <lpage>25</lpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Schaefer</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rabiser</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clarke</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bettini</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Benavides</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Botterweck</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pathak</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trujillo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Villela</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Software diversity: state of the art and perspectives</article-title>
          .
          <source>International Journal on Software Tools for Technology Transfer</source>
          .
          <volume>14</volume>
          ,
          <fpage>477</fpage>
          -
          <lpage>495</lpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Kharchenko</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gordieiev</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fedoseeva</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Profiling of Software Requirements for the Pharmaceutical Enterprise Manufacturing Execution System</article-title>
          . In: Bris,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Majernik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Pancerz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            and
            <surname>Zaitseva</surname>
          </string-name>
          , E. (ed.)
          <article-title>Applications of Computational Intelligence in Biomedical Technology</article-title>
          .
          <source>Studies in Computational Intelligence</source>
          . pp.
          <fpage>67</fpage>
          -
          <lpage>92</lpage>
          . Springer, Cham (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Just</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cornwell</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Review and analysis of synthetic diversity for breaking monocultures</article-title>
          .
          <source>11th ACM Conference on Computer and Communications Security</source>
          <year>2004</year>
          . pp.
          <fpage>23</fpage>
          -
          <lpage>32</lpage>
          .
          <source>Proceedings of the 2004 ACM Workshop on Rapid Malcode</source>
          , New York (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Sen</surname>
          </string-name>
          , J.:
          <article-title>Security and Privacy Issues in Cloud Computing</article-title>
          . In:
          <string-name>
            <surname>Ruiz-Martinez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>MarinLopez</given-names>
            , R. and
            <surname>Pereniguez-Garcia</surname>
          </string-name>
          ,
          <string-name>
            <surname>F</surname>
          </string-name>
          . (ed.)
          <article-title>Architectures and Protocols for Secure Information Technology Infrastructures</article-title>
          . pp.
          <fpage>1</fpage>
          -
          <lpage>45</lpage>
          . IGI Global, Hershey, PA (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Totel</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Majorczyk</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mé</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>COTS Diversity Based Intrusion Detection and Application to Web Servers. 8th International Symposium</article-title>
          ,
          <string-name>
            <surname>RAID</surname>
          </string-name>
          <year>2005</year>
          . pp.
          <fpage>43</fpage>
          -
          <lpage>62</lpage>
          . Springer, Berlin, Heidelberg (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>