Skip to content

Evidence & Provenance Engine

Density:
PRIMARY SOURCE (e.g. CISA KEV, Vendor Security Advisory, GitHub Commit)
โ”‚
โ–ผ
EVIDENCE OBJECT (Empirical observation, packet capture, exploit sample)
โ”‚
โ–ผ
FORMAL CLAIM (Classified assertion with mathematical confidence)
โ”‚
โ–ผ
RELATIONSHIP (Directed edge in Knowledge Graph)
โ”‚
โ–ผ
OPERATIONAL SCORE (Hermes Threat Score / HASS)

Whenever Hermes asserts a relationship or elevates a threat score, analysts can query:

  1. Why does Hermes believe this?
  2. What exact evidence would refute or overturn this conclusion?

Hermes enforces a strict epistemic taxonomy. AI pipelines are forbidden from presenting inferences or predictions as facts:

An assertion directly corroborated by verifiable physical, mathematical, or authoritative primary evidence.

  • Example: โ€œA public proof-of-concept exploit script was committed to GitHub on September 5.โ€
  • Criteria: Verifiable SHA256, URL timestamp, or signed vendor release.

A logical conclusion deduced from one or more corroborated facts.

  • Example: โ€œThe availability of an unauthenticated token forgery script significantly lowers the exploitation barrier for script kiddies.โ€
  • Criteria: Explicit causal chain linking observations.

A plausible operational explanation that has not yet been independently verified.

  • Example: โ€œThe observed scanning pattern may be attributed to Void Arachne preparing a wider ransomware wave.โ€
  • Criteria: Must be explicitly labeled with CONTESTED or UNDER_REVIEW lifecycle status.

A forward-looking probabilistic forecast with an explicit evaluation window.

  • Example: โ€œCVE-2026-59822 is likely to be incorporated into automated botnet loaders within 14 days.โ€
  • Criteria: Audited post-facto to calculate calibration curves for the Hermes Prediction Engine.

Evidence objects are weighted according to empirical reliability:

Evidence TypeDescriptionBaseline Strength
direct_observationDirect telemetry, honeypot capture, or network dump0.98
vendor_confirmationOfficial vulnerability disclosure or patch commit0.98
government_confirmationInclusion in official catalogs (CISA KEV, CERT-FR)0.99
exploit_codeFunctional, independently verified PoC code0.95
technical_analysisDeep forensic teardown by recognized security lab0.92
telemetryAggregated sensor counts or port scanning spikes0.85
researcher_statementPublic disclosure by credited vulnerability finder0.88
secondary_reportingTech journalism or secondary aggregator0.65