Breach-Index Ontology
Firms, the third-party vendors they rely on, and the public supply-chain incidents those vendors were caught up in (MOVEit, SolarWinds, Okta). You only state who uses which vendor and which vendor was in which incident — the reasoner chains "exposedVia" to work out which firms inherit exposure to which breaches. Then propose "this vendor leaked data" and watch who becomes a victim, with a consistency verdict.
Suppose MOVEit is confirmed to have leaked customer data. Declare "a MOVEitVictim is any firm exposed to the MOVEit incident" — and ask the engine who that now covers.
MOVEitVictim ≡ ∃ exposedVia.{MOVEit incident}Supply-chain exposure the engine derived — who inherits which breach
You never said "Firm A is exposed to the MOVEit breach." You said Firm A uses MOVEit, and MOVEit was implicated in that incident. Because "exposedVia" is transitive and both statements are kinds of it, the reasoner chained them — surfacing every firm’s inherited third-party exposure. These are reasoned − asserted: 21 triples (owl-rl).
Frequently asked questions
Is the Breach-Index Ontology just a drawing?
No. The entities and relationships are curated from public sources (Public reporting on MOVEit (CVE-2023-34362), SolarWinds (SUNBURST) and Okta incidents), but the consequences are computed by the open-source Open Ontologies reasoning engine, not drawn by hand. The engine-derived panel lists exactly the facts the reasoner added on top of what was written down (83 reasoned minus 62 asserted triples), and the proposed-rule panel is the engine answering an OWL-DL query with a consistency verdict for the whole ontology.
What does "blast radius" mean here?
We add one new rule of intent and ask the reasoner what changes. Here the rule is: Suppose MOVEit is confirmed to have leaked customer data. Declare "a MOVEitVictim is any firm exposed to the MOVEit incident" — and ask the engine who that now covers. The engine (owl-dl, description logic SHIQ) returns exactly which entities are reclassified (3 here) and confirms the ontology stays logically consistent. You change a rule; the machine, not a person, works out every consequence.
What is Open Ontologies?
Open Ontologies (github.com/fabio-rovai/open-ontologies, MIT-licensed) is an open-source reasoning engine described as "Terraform for knowledge graphs." It loads RDF/Turtle, runs OWL-RL and OWL-DL reasoning over an in-memory triple store, answers SPARQL, and can produce checkable certificates for its conclusions. PlayCISO ships only the captured output it produces; the engine is not a runtime dependency.