<!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>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Network: the first building block for a comprehensive Cybersecurity Knowledge Graph</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mikel Egaña Aranguren</string-name>
          <email>mikel.egana@ehu.eus</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jesualdo Tomás Fernandez Breis</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alexander Garcia Castro</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Markus Rompe</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Cybersecurity, Ontology, Knowledge Graph, Data integration</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Siemens Energy</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Basque Country (UPV/EHU)</institution>
          ,
          <country country="ES">Spain</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Murcia (UM)</institution>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2024</year>
      </pub-date>
      <fpage>0000</fpage>
      <lpage>0001</lpage>
      <abstract>
        <p>The escalating complexity and dynamism of the cybersecurity landscape necessitates a robust, adaptive framework for the integration, analysis, and dissemination of cybersecurity knowledge. This paper introduces the Cybersecurity Ontology Network (CON), a foundational step towards establishing a comprehensive Cybersecurity Knowledge Graph (CKG). The CON framework is designed to semantically organize and interconnect diverse cybersecurity information, focusing on software components, thus including vulnerabilities, libraries, and projects. By leveraging ontological structures, CON enables a more nuanced, context-aware synthesis of cybersecurity data from disparate sources, facilitating advanced analytical capabilities.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>CEUR
ceur-ws.org</p>
    </sec>
    <sec id="sec-2">
      <title>1. Introduction</title>
      <p>
        Data-centric architectures in enterprises emphasize the role of data as first class citizens,
as opposed to the traditional “one application one database” architectures, that emphasized
applications over data [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ]. Companies have realized that data is their most important asset,
whereas applications are ephemeral.
      </p>
      <p>
        Knowledge Graphs (KGs) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] generally combine data from diferent sources of varying
structure and granularity. From an industrial perspective, the concept of enterprise KG (EKG)
[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] would facilitate the development of a KG that contains and connects all the relevant data
for a company. The industrial relevance of EKGs is supported by the existence of the OMG
EKG Forum1. Despite graph-based representations do not require a schema, KGs are usually
Proceedings of the Joint Ontology Workshops (JOWO) - Episode X: The Tukker Zomer of Ontology, and satellite events
co-located with the 14th International Conference on Formal Ontology in Information Systems (FOIS 2024), July 15-19,
https://mikel-egana-aranguren.github.io/ (M. E. Aranguren)
structured by the content of ontologies, which also provide a precise meaning to the data
represented in the KG.
      </p>
      <p>Cybersecurity is one of the most salient domains in this transition to EKGs, since it requires up
to date data from heterogeneus sources that needs to be integrated. We present the Cybersecurity
Ontology Network (CON), a first step towards the creation of a Cybersecurity KG at Siemens
Energy (SE).</p>
    </sec>
    <sec id="sec-3">
      <title>2. The need for data integration in Cybersecurity</title>
      <p>Currently, information related to Cybersecurity at SE is scattered in data silos: software projects,
software library data, and vulnerabilities. Figure 1 shows that (1) the software project data
stores information about the organization that owns the project, the authors of the software
project, the name, the components, etc.; (2) the software library data includes information about
software libraries, their versions, dependencies with other libraries, etc.; and (3) the vulnerability
data includes information about the name, efect, level of risk and mitigation of risk, and the
libraries and versions afected by the vulnerabilities.</p>
      <p>From this description it can be easily noticed that there is an overlap in the data, but that
the heterogeneity of the data makes their interoperability dificult. The lack of interoperability
implies that answering critical questions such as the next ones becomes cumbersome:
• Which components are afected by the Vulnerability CVE-2021-33430?
• If I update a package then how is that updating going to afect other packages?
• Which components can be updated in the projects afected by the vulnerability?</p>
      <p>The KG approach would speed up the process of getting the answers to those questions
through meaningful data integration and exploitation. The first step towards such graph is the
ontology that provides the structure and meaning to the data, that is, the set of classes and
properties of the entities involved, and hence facilitate integration. Figure 2 depicts a possible
graph-based representation and connection of the entities described in Figure 1. There, we can
see how overlapping entities are not represented in a redundant way and that there are links
connecting the previous data silos. In the next section, we describe how we are approaching
the development of the ontology network that will enable data interoperability for the efective
management of software vulnerabilities.</p>
    </sec>
    <sec id="sec-4">
      <title>3. The Cybersecurity Ontology Network</title>
      <p>
        The Cybersecurity Ontology Network (CON) is an OWL2 ontology developed with the ontology
editor Protégé [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. CON is based on the CycloneDX specification 3, and all the elements of the
specification can be found in the ontology (Figure 3). Therefore, the current CON is focused on
the central element of CycloneDX, that is, the Software Bill of Materials (SBOM).
      </p>
      <p>An SBOM is essentially a comprehensive inventory of all the components that make up a
piece of software. This includes not only the direct code written by the software developers
but also any third-party components, libraries, frameworks, and other dependencies that the
software uses to function. The Component class presents a rich axiomization as seen in Figure
4. For example, a common pattern used in diferent parts of the ontology is the inclusion of a
2https://www.w3.org/TR/owl2-overview/
3https://cyclonedx.org/specification/overview/
covering axiom when the specification presents a given set of values (Figure 4). The mapping
annotation property has been used to provide best practices when the ontology is used to map
data from external sources to RDF (Figure 4).</p>
    </sec>
    <sec id="sec-5">
      <title>4. Conclusions</title>
      <p>In this work we have presented the initial steps towards the development of a KG for handling
cybersecurity information. The CON ofers a vocabulary to model vulnerabilities and afected
libraries and projects. Its design has been driven by the practicalities of KG generation. In
future extensions, the vulnerability and the software library modules will be further developed.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.</given-names>
            <surname>McComb</surname>
          </string-name>
          ,
          <article-title>Software Wasteland: How the Application-centric Mindset is Hobbling Our Enterprises</article-title>
          , Technics Publications,
          <year>2018</year>
          . URL: https://books.google.es/books?id= _6JutAEACAAJ.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>D.</given-names>
            <surname>McComb</surname>
          </string-name>
          ,
          <article-title>The Data-centric Revolution: Restoring Sanity to Enterprise Information Systems</article-title>
          , Technics Publications,
          <year>2019</year>
          . URL: https://books.google.es/books?id=5XuIxwEACAAJ.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A.</given-names>
            <surname>Hogan</surname>
          </string-name>
          , E. Blomqvist,
          <string-name>
            <given-names>M.</given-names>
            <surname>Cochez</surname>
          </string-name>
          , C. d'Amato,
          <string-name>
            <given-names>G. D.</given-names>
            <surname>Melo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gutierrez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kirrane</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. E. L.</given-names>
            <surname>Gayo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Navigli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Neumaier</surname>
          </string-name>
          , et al.,
          <string-name>
            <surname>Knowledge</surname>
            <given-names>graphs</given-names>
          </string-name>
          ,
          <source>ACM Computing Surveys (Csur) 54</source>
          (
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>37</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Gomez-Perez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. Z.</given-names>
            <surname>Pan</surname>
          </string-name>
          , G. Vetere, H. Wu,
          <article-title>Enterprise knowledge graph: An introduction, in: Exploiting linked data and knowledge graphs in large organisations</article-title>
          , Springer,
          <year>2017</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>14</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Musen</surname>
          </string-name>
          ,
          <article-title>The protégé project: a look back and a look forward</article-title>
          ,
          <source>AI</source>
          Matters
          <volume>1</volume>
          (
          <year>2015</year>
          )
          <fpage>4</fpage>
          -
          <lpage>12</lpage>
          . URL: https://doi.org/10.1145/2757001.2757003. doi:
          <volume>10</volume>
          .1145/2757001.2757003.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>