“An ontology defines the basic terms and relations comprising the vocabulary of a topic area, as well as the rules for combining terms and relations to define extensions to the vocabulary. ” (Neches R, Fikes R, Finin T, Gruber T, Patil R, Senator T, Swartout WR (1991) “Enabling Technology for Knowledge Sharing” AI Magazine. Winter 1991. 36-56.)

“An ontology is a formal, explicit specification of a shared conceptualization. ” (Studer, Benjamins, Fensel. Knowledge Engineering: Principles and Methods. Data and Knowledge Engineering. 25 (1998) 161-197)

Unified Cyber Ontology (UCO) is a community-developed ontology/model, which is intended to serve as a consistent foundation for standardized information representation across the cyber security domain/ecosystem.

Specific information representations focused on individual cyber security subdomains (cyber investigation, computer/network defense, threat intelligence, malware analysis, vulnerability research, offensive/hack-back operations, etc.) can be be based on UCO and defined as appropriate subsets of UCO constructs.

Through this approach not only are domain-focused representations defined consistently but they also can take advantage of shared APIs and information can flow in an automated fashion across subdomain boundaries.

The purpose of this repository is to provide a foundation for broader community involvement in defining what to represent and how.

The current release of UCO is v0.2.1

The content of v0.2.1 is primarily a specification formalization of the v0.1.0 content into OWL. Its content is driven primarily from the initial base requirements of expressing cyber investigation information and is the product of input from the Cyberinvestigation Analysis Standard Expression (CASE) community. It does contain a few enhancements and fixes identified after the release of v0.1.0.

Future versions of UCO will not only expand and refine the ontology itself but will also provide more complete and formalized documentation.

• Cyberinvestigation Analysis Standard Expression (CASE) v0.1.0 JSON-LD examples