ebiquity / unified-cybersecurity-ontology

Unified Cybersecurity Ontology

Unified-Cybersecurity-Ontology

Unified Cybersecurity Ontology

UCO_1_5.owl

The Unified Cybersecurity Ontology (UCO) is intended to support information integration and cyber situational awareness in cybersecurity systems. The ontology incorporates and integrates heterogeneous data and knowledge schemas from different cybersecurity systems and most commonly used cybersecurity standards for information sharing and exchange. The UCO ontology has also been mapped to a number of existing cybersecurity ontologies as well as concepts in the Linked Open Data cloud. Similar to DBpedia which serves as the core for general knowledge in Linked Open Data cloud, we envision UCO to serve as the core for cybersecurity domain, which would evolve and grow with the passage of time with additional cybersecurity data sets as they become available.

If you use UCO or want to refer to it in a paper, please cite:

Zareen Syed, Ankur Padia, Tim Finin, Lisa Mathews and Anupam Joshi, UCO: Unified Cybersecurity Ontology, AAAI Workshop on Artificial Intelligence for Cyber Security, February 2016. http://ebiq.org/p/722

Current versions of the UCO family of ontologies are stored in this repository. We recommend using the following URIs to refer to the ontologoes, This will redirect to the current current versions and will be maintained for the forseeable future.

@prefix atk: <http://purl.org/cyber/atk#> .
@prefix capec: <http://purl.org/cyber/capec#> .
@prefix ckg: <http://purl.org/cyber/ckg#> .
@prefix cve: <http://purl.org/cyber/cve#> .
@prefix cwe: <http://purl.org/cyber/cwe#> .
@prefix cyber: <http://purl.org/cyber#> .
@prefix misp: <http://purl.org/cyber/misp#> .
@prefix mitre: <http://purl.org/cyber/mitre#> .
@prefix stx: <http://purl.org/cyber/stix#> .
@prefix txi: <http://purl.org/cyber/taxii#> .
@prefix uco: <http://purl.org/cyber/uco#> .

unified-cybersecurity-ontology's Issues

Why # in different locations?

Hi there. I just discovered UCO yesterday and am very excited about using it in our cybersecurity tool, DarkLight (https://darklightcyber.com). I'm curious why some classes and properties have a # in different places. For example:

    <!-- http://ffrdc.ebiquity.umbc.edu/ns/ontology/TemporalGroup -->

    <Class rdf:about="http://ffrdc.ebiquity.umbc.edu/ns/ontology/TemporalGroup">
        <rdfs:subClassOf rdf:resource="http://ffrdc.ebiquity.umbc.edu/ns/ontology/#UCOThing"/>
    </Class>



    <!-- http://ffrdc.ebiquity.umbc.edu/ns/ontology/#Address -->

    <Class rdf:about="http://ffrdc.ebiquity.umbc.edu/ns/ontology/#Address">
        <rdfs:subClassOf rdf:resource="http://ffrdc.ebiquity.umbc.edu/ns/ontology/#UCOThing"/>
    </Class>

Looking forward to working with you. ~ian