CCE.owl

<?xml version="1.0"?>


<!DOCTYPE Ontology [
    <!ENTITY xsd "http://www.w3.org/2001/XMLSchema#" >
    <!ENTITY xml "http://www.w3.org/XML/1998/namespace" >
    <!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#" >
    <!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#" >
]>


<Ontology xmlns="http://www.w3.org/2002/07/owl#"
     xml:base="http://ffrdc.ebiquity.umbc.edu/ns/ontology/"
     xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:xml="http://www.w3.org/XML/1998/namespace"
     ontologyIRI="http://ffrdc.ebiquity.umbc.edu/ns/ontology/"
     versionIRI="http://ffrdc.ebiquity.umbc.edu/ns/ontology/">
    <Prefix name="" IRI="http://www.w3.org/2002/07/owl#"/>
    <Prefix name="cbx" IRI="http://cybox.mitre.org/cybox_v1#"/>
    <Prefix name="owl" IRI="http://www.w3.org/2002/07/owl#"/>
    <Prefix name="rdf" IRI="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
    <Prefix name="xsd" IRI="http://www.w3.org/2001/XMLSchema#"/>
    <Prefix name="rdfs" IRI="http://www.w3.org/2000/01/rdf-schema#"/>
    <Declaration>
        <Class IRI="#CCE"/>
    </Declaration>
    <Declaration>
        <DataProperty IRI="#hasAssociatedTechnicalMechanism"/>
    </Declaration>
    <Declaration>
        <DataProperty IRI="#hasConceptualParameter"/>
    </Declaration>
    <Declaration>
        <DataProperty IRI="#hasDescription"/>
    </Declaration>
    <Declaration>
        <DataProperty IRI="#hasReferences"/>
    </Declaration>
    <Declaration>
        <DataProperty IRI="#onPlatform"/>
    </Declaration>
    <AnnotationAssertion>
        <AnnotationProperty abbreviatedIRI="rdfs:comment"/>
        <IRI>#hasAssociatedTechnicalMechanism</IRI>
        <Literal datatypeIRI="&rdf;PlainLiteral">for any given configuration issue there may be one or more ways to implement the desired result</Literal>
    </AnnotationAssertion>
    <AnnotationAssertion>
        <AnnotationProperty abbreviatedIRI="rdfs:comment"/>
        <IRI>#hasConceptualParameter</IRI>
        <Literal datatypeIRI="&rdf;PlainLiteral">parameters that would need to be specified in order to implement a CCE on a system</Literal>
    </AnnotationAssertion>
    <AnnotationAssertion>
        <AnnotationProperty abbreviatedIRI="rdfs:comment"/>
        <IRI>#hasDescription</IRI>
        <Literal datatypeIRI="&rdf;PlainLiteral">a humanly understandable description of the configuration issue</Literal>
    </AnnotationAssertion>
    <AnnotationAssertion>
        <AnnotationProperty abbreviatedIRI="rdfs:comment"/>
        <IRI>#hasReferences</IRI>
        <Literal datatypeIRI="&rdf;PlainLiteral">pointers to the specific sections of the documents or tools in which the configuration issue is described in detail</Literal>
    </AnnotationAssertion>
    <AnnotationAssertion>
        <AnnotationProperty abbreviatedIRI="rdfs:comment"/>
        <IRI>#onPlatform</IRI>
        <Literal datatypeIRI="&rdf;PlainLiteral">A CCE &quot;platform group&quot; roughly identifies the operating system or application to which a CCE entry applies. CCE’s platform groups adhere to the same level of granularity commonly found in security configuration guidance that are written for individual platforms, as well as in the sets of checks and other features found in configuration audit and management tools. They are a set of high-level &quot;buckets&quot; that imply a particular CCE is &quot;related to&quot; the OS or application named by the platform group. These groups are meant for human interpretation, and are not definitive declarations of a CCE entry’s relation to a particular platform.</Literal>
    </AnnotationAssertion>
</Ontology>



<!-- Generated by the OWL API (version 3.4.2) http://owlapi.sourceforge.net -->