https://ontology.solveit-df.org/solveit/tool-profile/MitigationCapability
A declared capability that a specific mitigation is provided by a tool, optionally subject to conditions expressed as SHACL shapes.
Instances of solveit-tool-profile:MitigationCapability can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|
By the associated SHACL property shapes, instances of solveit-tool-profile:MitigationCapability can have the following properties:
| PROPERTY | PROPERTY TYPE | DESCRIPTION | MIN | MAX | VALUE TYPE | OTHER CONSTRAINTS | GLOBAL RANGE |
|---|---|---|---|---|---|---|---|
| solveit-tool-profile:MitigationCapability | |||||||
| solveit-tool-profile:establishedForWeakness | owl:ObjectProperty | established for weakness The weaknesses this capability was established against. One mitigation typically addresses many weaknesses, and a capability that names only its mitigation is read as covering all of them, including the ones the publisher never tested. Naming weaknesses here records what was actually established rather than what the mitigation could in principle address. There is no minimum: a capability naming no weakness declares no weakness scope and keeps the meaning it was published with, because every profile published before this term existed carries none. sh:message establishedForWeakness must reference a solveit-core:Weakness. A weakness given as a literal, or as a node with no type, cannot be matched against the knowledge base.; This capability declares no weakness scope, so it is read as covering every weakness its mitigation addresses. If it was established for fewer than that, name those weaknesses with establishedForWeakness. |
1 | * | solveit-core:Weakness sh:IRI |
sh:severity
sh:Info
|
solveit-core:Weakness |
| solveit-tool-profile:supportingCitation | owl:ObjectProperty | supporting citation Evidence for this capability - a test report, a validation study, a published paper. The idiom here is that the profile mints its own Citation, carrying solveit-core:citationPlaintext or solveit-core:citationBibtex and omitting solveit-core:citationID, so a publisher can cite their own test report without it being registered in the DFCite series and the profile depends on nothing outside itself. This departs from the comment on solveit-core:Citation, which describes a registry reference reached from a Technique, Weakness or Mitigation. The departure is recorded here rather than reconciled there, because widening a core term to serve one module would put the change in the module that did not need it. sh:message supportingCitation must reference a solveit-core:Citation. A profile may mint its own Citation carrying citationPlaintext or citationBibtex; it need not be a registered DFCite entry. |
0 | * | solveit-core:Citation sh:IRI |
solveit-core:Citation | |
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix solveit-tool-profile: <https://ontology.solveit-df.org/solveit/tool-profile/> .
@prefix uco-core: <https://ontology.unifiedcyberontology.org/uco/core/> .
solveit-tool-profile:MitigationCapability a owl:Class ;
rdfs:label "Mitigation Capability"@en ;
rdfs:comment "A declared capability that a specific mitigation is provided by a tool, optionally subject to conditions expressed as SHACL shapes."@en ;
rdfs:subClassOf uco-core:UcoObject .