Skip to content
Reachability Analysis

The Methods Matrix: what each method needs, proves and misses

Read , with 35 sources listed at the end.

Scroll the table sideways for more columns

Alphabetical by method name. The last column counts the 37 ledger entries by the method each record names as settling it: 14 + 11 + 7 + 3 + 2 + 0 + 0 = 37. EPSS exploit prediction and Severity scores settle none of them, because neither says anything about one instance.
MethodQuestion it answersNeedsProvesMissesOffered byLedger entries it settles (of 37)
Agent investigationWhat do the configuration, code, controls and logs say about this one finding?Read access to the cloud, code, logs and security controls involved, the scanner findings to investigate, and context such as owners and business criticality.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.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.Astelia, Averlon, Backline, Cogent, Dux, Maze, Onit, Qualys, Rival Security, Seemplicity, Vicarius3
Attack-path analysisCan an attacker reach the affected asset from outside?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.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.Whether the exploit works against your configuration, whether the vulnerable function is reachable in code, and anything the graph lacks.Astelia, Averlon, Microsoft, Rapid7, Tenable, Wiz, XM Cyber, Zafran11
EPSS exploit predictionHow likely is exploitation activity in the next 30 days?A CVE identifier, the current EPSS score and percentile from FIRST's daily file or API, and a threshold your team chooses.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.Whether your instance is affected or reachable, which controls protect it, and how much damage a successful attack would cause.Empirical Security, FIRST0
Known-exploited listsHas exploitation been seen, and does CISA set a due date?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.That CISA holds reliable evidence of exploitation in the wild for this CVE and that a clear remediation action exists.Flaws exploited but not yet listed, the manner and targets of the exploitation, and whether your own instance is reachable or protected.CISA2
Runtime reachability and live-state readsIs the vulnerable code loaded or the risky setting on in the running host?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.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.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.Astelia, Endor Labs, Oligo, Onit, Sysdig, Upwind, Zafran7
Severity scoresHow severe is the flaw in the abstract?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.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.Whether anyone is exploiting the flaw, how exposed your instance is, what controls sit in front of it and whether the vulnerable code runs.FIRST, NVD0
Static reachability and configuration readsIs the affected version, package or code path in my build?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.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.Network exposure, identity, controls, whether the code is deployed and running, and any setting changed after the read.Backline, Endor Labs, Semgrep, Snyk14

Sources

  1. Onit blog on reachable vulnerabilities, 6 Nov 2026 (vendor claim), read 19 Nov 2026
  2. Qualys agentic AI page (vendor claim), read 19 Nov 2026
  3. Astelia platform page (vendor claim), read 10 Nov 2026
  4. Averlon platform page (vendor claim), read 10 Nov 2026
  5. Backline product page (vendor claim), read 10 Nov 2026
  6. Cogent AI engine page (vendor claim), read 10 Nov 2026
  7. Dux home page (vendor claim), read 10 Nov 2026
  8. Maze cloud platform page (vendor claim), read 10 Nov 2026
  9. Rival Security home page (vendor claim), read 10 Nov 2026
  10. Seemplicity AI Analysts announcement (vendor claim), read 10 Nov 2026
  11. Vicarius home page (vendor claim), read 10 Nov 2026
  12. Microsoft Learn: Defender for Cloud attack paths, read 19 Nov 2026
  13. XM Cyber glossary: attack path analysis, read 19 Nov 2026
  14. Wiz Academy: attack path analysis, read 10 Nov 2026
  15. Tenable One page (vendor claim), read 10 Nov 2026
  16. Rapid7 Exposure Command page (vendor claim), read 10 Nov 2026
  17. Zafran Attack Chains announcement, 3 Aug 2026 (vendor claim), read 10 Nov 2026
  18. CISA KEV JSON feed, version 2026.11.18, read 19 Nov 2026
  19. FIRST EPSS FAQ: what EPSS is, is not, and threshold guidance, read 19 Nov 2026
  20. FIRST EPSS home, read 10 Nov 2026
  21. FIRST EPSS article on probability and percentile, read 10 Nov 2026
  22. CISA BOD 22-01, read 19 Nov 2026
  23. CISA KEV catalog page: three criteria and FAQ, read 19 Nov 2026
  24. Endor Labs instrumented container reachability, read 19 Nov 2026
  25. Sysdig vulnerability management documentation, read 19 Nov 2026
  26. Upwind home page (vendor claim), read 10 Nov 2026
  27. Oligo home page (vendor claim), read 10 Nov 2026
  28. Onit platform page (vendor claim), read 10 Nov 2026
  29. Zafran home page (vendor claim), read 10 Nov 2026
  30. FIRST CVSS v4.0 specification, version 1.2, read 19 Nov 2026
  31. FIRST CVSS v4.0 user guide: Base score measures severity, not risk, read 19 Nov 2026
  32. Snyk reachability analysis documentation, including limits, read 19 Nov 2026
  33. Endor Labs reachability analysis overview, read 19 Nov 2026
  34. Semgrep Supply Chain overview, read 19 Nov 2026
  35. Endor Labs call graphs, read 10 Nov 2026

Last reviewed 19 Nov 2026.