A CVE lands. Two days later you still cannot say whether it touches you.
The public reference layer under OCO is open to AI agents as Lattice, in private beta. See Lattice
OCO is a cyber knowledge graph. It links a vulnerability to the exploited-list entry that points at it, the techniques it is used with, the detections written for them and the groups on record using them, and every record carries the public source it came from. It runs on local models: no external AI API, and no telemetry leaving the site.
Most people meet OCO without touching it. It is what we watch your estate on when we run the IT and security for a small firm, the reason that service can be priced for a twenty-person company rather than a two-hundred-person one. This page is for the reader who wants to know what is underneath.
- 1 · CVE recordCVE-2021-44228Apache Log4j2, as published by NVDSource: NVD
- 2 · Exploited-list entryLog4j2 remote code executionThe entry CISA added to its exploited-vulnerabilities catalogueSource: CISA KEV
- 3 · TechniquesT1190 · T1059Exploit Public-Facing Application; Command and Scripting InterpreterSource: MITRE ATT&CK
- 4 · DetectionsRules that cover T1190Microsoft Sentinel and Elastic rules, and the investigation guides written beside themSource: Rule sets
- 5 · Who is on record using itGroups and campaignsThreat groups and named campaigns that use T1190, each with its reportSource: Public reporting
Every record in the graph carries the public source it was drawn from. The local-model probe and the coverage-score probe were run on 29 October 2026 and passed. This page describes what is running on that date, not a roadmap.
Pick a record. See where it came from.
The Graph Explorer opens onto the whole graph. Search a CVE and its record opens beside it, with the source it was read from and the path to that source, so you can check the record rather than trust it.

The day’s signals, from public feeds.
The Threat Intelligence Hub reads the feeds the graph is built from: the CVE record, GitHub and vendor advisories, and CISA’s exploited-vulnerabilities list.


What to notice
- The actor reads unattributed, because CISA’s list names none and we do not guess one.
- Every row is a record with a source, so the panel is a way into the graph: from a CVE here to its techniques, detections and groups there.
- The list is CISA’s, not ours. A CVE being on it means exploitation has been seen; whether it matters to you depends on what you run, which is the question the rest of this page is about.
- Where we have written a note on one of these, it is in Insights, with its analysis report.
Ask in words. Get back the records the answer came from.
A question about your own estate, answered against your own data, with the source records listed underneath so you can check the answer rather than trust it.

Cross-linked, not just collected.
Each of the six kinds of record below is read from public sources: the CVE record and NVD, CISA’s exploited list, MITRE ATT&CK and CWE, D3FEND, Sigma and vendor rule sets, and advisory feeds from vendors, GitHub and the research blogs. The connections between them are what a list cannot give you.
Vulnerabilities
Techniques and who uses them
Detections
Countermeasures
Signals
Your estate
Three ways to meet it.
A small firm
A security team
An AI agent
Each of these has a probe behind it.
Runs fully local
Honest coverage
Multi-tenant from day one
What it does not do
OCO tells you what a record connects to. It does not hand you a ranked remediation plan, and it does not take any action on your systems. Deciding what to fix first, and doing the fixing, both stay with your team. If what you need is something that closes tickets on its own, that is not what this is today.
Each property corresponds to a capability probe that must pass before the statement may appear on this page.
Want to see it against your own estate?
For most firms the answer is to have us run it: that is the IT and security service, and it starts with an asset review. If you run your own security team and want the graph itself, sandbox access is granted case by case; a person reviews every request, and we will tell you when it is not a fit.
Request access