Skip to content

Related Intelligence & Cross-Entity Graph Context

Density:
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ HERMES CROSS-ENTITY RELATED INTELLIGENCE (SECTION 88) โ”‚
โ”‚ โ”‚
โ”‚ CTI / Vulnerability / Software Entity: [TARGET INVESTIGATION NODE] โ”‚
โ”‚ โ”‚ โ”‚
โ”‚ โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚
โ”‚ โ–ผ โ–ผ โ–ผ โ”‚
โ”‚ โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚
โ”‚ โ”‚ VULNERABILITY โ”‚ โ”‚ THREAT ACTORS โ”‚ โ”‚ SOFTWARE โ”‚ โ”‚
โ”‚ โ”‚ CHIPS (CVE) โ”‚ โ”‚ & CAMPAIGNS โ”‚ โ”‚ & ASSETS โ”‚ โ”‚
โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ โ”‚
โ”‚ โ”‚ โ”‚ โ”‚ โ”‚
โ”‚ โ–ผ โ–ผ โ–ผ โ”‚
โ”‚ โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚
โ”‚ โ”‚ATTACK PATTERNSโ”‚ โ”‚AGENTIC SYSTEMSโ”‚ โ”‚ FORECASTS & โ”‚ โ”‚
โ”‚ โ”‚(ATT&CK/ATLAS) โ”‚ โ”‚& SIMULATORS โ”‚ โ”‚ RESEARCH (OBS)โ”‚ โ”‚
โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ โ”‚
โ”‚ โ”‚ โ”‚
โ”‚ โ–ผ โ”‚
โ”‚ [Automated Graph Neighborhood / โ”‚
โ”‚ Zero-404 Verified Hyperlinks] โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Under Section 88, the RelatedIntelligence architecture serves three fundamental operational objectives:

The component operates in two complementary modes:

  • Declarative Explicit Mode: Authors can manually specify contextual connections (vulnerabilities, software, attackPatterns, agents, forecasts, research, threatActors).
  • Automated Graph Traversal Mode: When provided with an entityId (e.g., CVE-2026-96560, PROD-LITELLM, ACTOR-VOID-ARACHNE), the component queries neighborhood-index.json to resolve incoming and outgoing relationships dynamically.

All generated hyperlinks undergo deterministic validation against precomputed linkify catalogs:

  • Vulnerabilities: Verified against cve-dossiers-list.json. If a dedicated dossier exists, links point to /cve/<year>/<cve>/; otherwise, gracefully fall back to /cve/<year>/#<cve>.
  • Software: Verified against product-slugs-list.json. Known products route to /software-intelligence/products/<slug>/.
  • Attack Patterns: Agentic Attack Patterns route to /agentic-attack-patterns/<slug>/; MITRE ATLAS and ATT&CK route to their respective foundational guides.
  • Forecasts & Decisions: Direct links to canonical /forecasts/<id>/ and /decisions/<id>/ dossiers.

Unlike traditional single-dimension links, Section 88 introduces first-class relational support for adversary clusters and intrusion operations (e.g., ShinyHunters / UNC6240, Void Arachne, CLOSEDQUORUM), bridging CTI investigations directly to affected enterprise assets.


Section 88 is governed by three strict structural invariants verified in CI:

  1. Non-Empty Rendering Invariant: If no associated entities are resolved or declared, the component gracefully renders nothing (hasAny === false), avoiding empty visual artifacts or broken layout blocks.
  2. Locale Consistency Invariant: All routes, tooltips, and badges automatically align with the active language context (/fr/... vs /...).
  3. De-duplication Invariant: Entities appearing in both explicit props and graph neighborhoods are automatically de-duplicated by canonical identifier.

The specification is formalized at /api/methodology/related-intelligence.json:

{
"$schema": "https://hermes-codex.org/schemas/methodology-spec-v1.json",
"methodology_id": "RELATED_INTELLIGENCE",
"name": "Hermes Related Intelligence & Cross-Entity Graph Context",
"section": "Section 88",
"active_version": "REL-1.0",
"supported_entity_categories": [
"vulnerabilities",
"threat_actors",
"software",
"attack_patterns",
"agents",
"forecasts",
"research"
]
}