Secure Chain Ontology
Release: 2024-10-20
- This version:
- https://w3id.org/secure-chain/1.0.0
- Latest version:
- https://w3id.org/secure-chain
- Revision:
- 1.0.0
- Authors:
- Yifeng Di
- Hadi Askari
- Shushan Arakelyan
- Xiangyu Zhang
- Xiang Ren
- Muhao Chen
- Tianyi Zhang
- Extended Ontologies:
- Schema.org
- Download serialization:
- License:
- Visualization:

- Cite as:
- Yifeng Di, Hadi Askari, Shushan Arakelyan, Xiangyu Zhang, Xiang Ren, Muhao Chen, Tianyi Zhang. Secure Chain Ontology. Revision: 1.0.0. Retrieved from: https://w3id.org/secure-chain/1.0.0
Abstract
The Secure Chain Knowledge Graph is a comprehensive knowledge graph designed to model the relationships between software, hardware, vulnerabilities, and other entities to support secure and transparent management of software supply chains.
Introduction back to ToC
In today's increasingly complex technological ecosystem, software has become an integral part of crucial infrastructures. Underlying modern software systems is the supply chain of open-source software components, such as Apache Spark, whose functionalities are reused and integrated into various systems underpinning modern society.
While software supply chains empower the rapid development of software systems, they also increase the risks, since any bugs, vulnerabilities, and unauthorized changes in upstream components can propagate to downstream systems and cause severe consequences. This is evident through many software crises witnessed in recent years, such as the [Heartbleed bug](https://heartbleed.com/), the [Equifax data breach](https://www.securityweek.com/equifax-confirms-apache-struts-flaw-used-hack/#:~:text=U.S.%20credit%20reporting%20agency%20Equifax,used%20to%20breach%20its%20systems.), and the [NPM left-pad incident](https://qz.com/646467/how-one-programmer-broke-the-internet-by-deleting-a-tiny-piece-of-code) that almost broke the Internet.
Therefore, the Secure Chain Ontology is designed to provide a unified knowledge graph ontology that can capture rich, up-to-date information about software components in heterogenous software ecosystems. By extending widely adopted ontologies such as [Schema.org](http://schema.org/) and incorporating principles from software description vocabularies, the Secure Chain Ontology facilitates interoperability with existing data sources and standards, making it a powerful tool for security professionals, developers, and researchers.
The ontology supports key use cases such as risk analysis, secure software development lifecycle management, and compliance monitoring, by allowing users to trace dependencies between software and hardware components, identify which versions are affected by certain vulnerabilities, and ensure that all components in the chain are properly licensed. Additionally, the Secure Chain Ontology supports concepts such as vulnerability types and discovery, allowing for more detailed and actionable information when assessing the security posture of a system. As part of its design, the ontology aims to be flexible and extendable, enabling integration with domain-specific ontologies or other metadata vocabularies that may exist in different areas of the supply chain ecosystem.
Namespace declarations
Table 1: Namespaces used in the document
dc | <http://purl.org/dc/elements/1.1/> |
dcterms | <http://purl.org/dc/terms/> |
owl | <http://www.w3.org/2002/07/owl#> |
rdf | <http://www.w3.org/1999/02/22-rdf-syntax-ns#> |
rdfs | <http://www.w3.org/2000/01/rdf-schema#> |
sc | <https://w3id.org/secure-chain/> |
schema | <http://schema.org/> |
vann | <http://purl.org/vocab/vann/> |
voaf | <http://purl.org/vocommons/voaf#> |
widoco | <https://w3id.org/widoco/vocab#> |
xml | <http://www.w3.org/XML/1998/namespace> |
xsd | <http://www.w3.org/2001/XMLSchema#> |
Secure Chain Ontology: Overview back to ToC
This ontology has the following classes and properties.
Classes
Object Properties
Data Properties
Secure Chain Ontology: Description back to ToC
The Secure Chain Ontology builds on top of [Schema.org](http://schema.org/), as shown in the figure below, extending its vocabulary to seamlessly integrate with its metadata properties and enhance interoperability across various systems.
We use sc:Software as a central concept in the Secure Chain Ontology to represent software within secure supply chains, with associated sc:SoftwareVersions capturing the evolution of software over time. These versions are critical for tracking vulnerabilities, compliance, and updates. The ontology models dependencies between software versions and other components, such as hardware, through properties like sc:dependsOn and sc:OperatesOn, which help assess potential risks and identify vulnerabilities. Additionally, sc:License links each software version to its legal aspects, ensuring compliance across the supply chain. The ontology also extends to hardware through sc:Hardware and sc:HardwareVersions, allowing for comprehensive tracking of both digital and physical components. Vulnerabilities are represented through sc:Vulnerability and sc:VulnerabilityType, with links to the entities that discover them, providing a detailed view of security risks across software and hardware versions.
Cross-reference for Secure Chain Ontology classes, object properties and data properties back to ToC
This section provides details for each class and property defined by Secure Chain Ontology.
Classes
IRI: https://w3id.org/secure-chain/License
-
has super-classes
-
Creative Work c
Object Properties
IRI: https://w3id.org/secure-chain/dependsOn
IRI: https://w3id.org/secure-chain/discover
IRI: https://w3id.org/secure-chain/hasHardwareVersion
IRI: https://w3id.org/secure-chain/hasSoftwareVersion
IRI: https://w3id.org/secure-chain/operatesOn
IRI: https://w3id.org/secure-chain/vulnerabilityType
IRI: https://w3id.org/secure-chain/vulnerableTo
Data Properties
IRI: https://w3id.org/secure-chain/versionName
Legend back to ToC
c: Classes
op: Object Properties
dp: Data Properties
Acknowledgments back to ToC
The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.