{
 "name": "Methods Matrix",
 "edition": "2026-11-19",
 "read_date": "2026-11-19",
 "source": "https://reachabilityanalysis.com/datasets/",
 "license": "CC BY 4.0",
 "cite": "Reachability Analysis, Exploitability Ledger and Methods Matrix, edition 19 Nov 2026 (first edition 10 Nov 2026), https://reachabilityanalysis.com/datasets/",
 "description": "7 rows, one per method, alphabetical by name: the question it answers, what it needs, proves and misses, who offers it and how many ledger entries it settles.",
 "rows": [
  {
   "method": "Agent investigation",
   "slug": "agent-investigation",
   "question": "What do the configuration, code, controls and logs say about this one finding?",
   "needs": "Read access to the cloud, code, logs and security controls involved, the scanner findings to investigate, and context such as owners and business criticality.",
   "proves": "One result per finding, in the label set that fits the question: reachable, not reachable or unknown; compromised, no evidence found or unknown; or the hosts at or above and below a fixed build. Each result comes with the configuration, code, controls, logs or paths it read, including what blocks a path and why a finding was closed.",
   "misses": "Anything outside the access granted, and evidence that no longer exists, such as rotated logs. A wrong 'not reachable' conclusion is caught only by the human review of closures.",
   "offered_by": "Astelia, Averlon, Backline, Cogent, Dux, Maze, Onit, Qualys, Rival Security, Seemplicity, Vicarius",
   "ledger_entries_settled": 3
  },
  {
   "method": "Attack-path analysis",
   "slug": "attack-path",
   "question": "Can an attacker reach the affected asset from outside?",
   "needs": "Read access to cloud, identity and network configuration (usually through agentless connectors), vulnerability and misconfiguration findings, and asset context such as internet exposure and data sensitivity.",
   "proves": "That a modeled route exists, or none does, from an external entry point through exposure, identity and network controls to the affected asset, and which single fix cuts the most routes.",
   "misses": "Whether the exploit works against your configuration, whether the vulnerable function is reachable in code, and anything the graph lacks.",
   "offered_by": "Astelia, Averlon, Microsoft, Rapid7, Tenable, Wiz, XM Cyber, Zafran",
   "ledger_entries_settled": 11
  },
  {
   "method": "EPSS exploit prediction",
   "slug": "exploit-prediction",
   "question": "How likely is exploitation activity in the next 30 days?",
   "needs": "A CVE identifier, the current EPSS score and percentile from FIRST's daily file or API, and a threshold your team chooses.",
   "proves": "FIRST's estimate, on a scale of 0 to 1, of the probability that exploitation activity is observed for this CVE in the next 30 days.",
   "misses": "Whether your instance is affected or reachable, which controls protect it, and how much damage a successful attack would cause.",
   "offered_by": "Empirical Security, FIRST",
   "ledger_entries_settled": 0
  },
  {
   "method": "Known-exploited lists",
   "slug": "known-exploited",
   "question": "Has exploitation been seen, and does CISA set a due date?",
   "needs": "A CVE identifier, a current copy of the catalog (CISA publishes JSON and CSV feeds) and an inventory that maps CVEs to the products you run.",
   "proves": "That CISA holds reliable evidence of exploitation in the wild for this CVE and that a clear remediation action exists.",
   "misses": "Flaws exploited but not yet listed, the manner and targets of the exploitation, and whether your own instance is reachable or protected.",
   "offered_by": "CISA",
   "ledger_entries_settled": 2
  },
  {
   "method": "Runtime reachability and live-state reads",
   "slug": "runtime-reachability",
   "question": "Is the vulnerable code loaded or the risky setting on in the running host?",
   "needs": "A sensor or agent on the workloads, hosts or containers (or instrumented test runs), software inventory and vulnerability data for each workload, and an observation window that exercises real behavior. For a live service, read access to its effective configuration, loaded modules and listening addresses.",
   "proves": "That the vulnerable package, module or function is present and loaded or executed in a workload that is running, or that the running service's effective setting or listening address meets the condition in the CVE record.",
   "misses": "Code paths that did not run while the sensor watched, who outside the host can reach a loaded package (only a read of the listening address or a request from an untrusted network settles that), compensating controls and any workload without a sensor.",
   "offered_by": "Astelia, Endor Labs, Oligo, Onit, Sysdig, Upwind, Zafran",
   "ledger_entries_settled": 7
  },
  {
   "method": "Severity scores",
   "slug": "severity-score",
   "question": "How severe is the flaw in the abstract?",
   "needs": "A CVE or advisory identifier and the published vector and base score from the CNA, vendor or NVD. Threat and Environmental values, if used, come from your team or from automation.",
   "proves": "How severe the flaw is in the abstract: attack vector, complexity, privileges required and impact on the vulnerable system, on a scale of 0 to 10.",
   "misses": "Whether anyone is exploiting the flaw, how exposed your instance is, what controls sit in front of it and whether the vulnerable code runs.",
   "offered_by": "FIRST, NVD",
   "ledger_entries_settled": 0
  },
  {
   "method": "Static reachability and configuration reads",
   "slug": "static-reachability",
   "question": "Is the affected version, package or code path in my build?",
   "needs": "Source code or build artifacts in a supported language, dependency manifests or lockfiles, and per-CVE data that names the vulnerable functions or code patterns. For appliances and hosts, read access to the version output and running configuration.",
   "proves": "That a call path exists from your code to the vulnerable function, shown step by step where one is found, and that the version, packaging and configuration facts in the CVE record hold or fail in the build.",
   "misses": "Network exposure, identity, controls, whether the code is deployed and running, and any setting changed after the read.",
   "offered_by": "Backline, Endor Labs, Semgrep, Snyk",
   "ledger_entries_settled": 14
  }
 ]
}