Sample report · demonstration data
Sample customer exposure report
What a customer-facing Exploit Hound report contains, produced by the product’s own report generator from the demonstration tenant. Every hostname is under example.com and no customer data is involved.
Exported 15 October 2026 from the executive report generator. The hosts are invented; the vulnerabilities cited are real CVEs, each chosen to match the finding it is attached to.
Demonstration data · Northwind Demo (fictitious)
Executive Security Summary
Exposure summary — last 30 days
Driven by the highest-risk open exposure (100/100) with additional weight from the next 9 highest-risk findings.
- Your exposure score is 82 out of 100 (high), across 10 open findings.
- 3 open finding(s) involve vulnerabilities that are known to be exploited in the wild and should be treated as urgent.
- 3 open finding(s) affect systems reachable from the Internet.
- 2 potential attack path(s) currently reach a system marked Critical.
- 9 open finding(s) are past their remediation target date.
What is open now
Known exploited means the vulnerability is on CISA’s Known Exploited Vulnerabilities catalog — an authority has published evidence it is being exploited. A vulnerability with published exploit code but no such listing is not counted here. The oldest open finding has been outstanding for 79 day(s).
Attack paths
| Entry point | Reaches | Hops | Score | Confidence |
|---|---|---|---|---|
| Internet | web01.example.com | 2 | 50 | potential |
| Internet | vpn.example.com | 2 | 50 | potential |
Potential routes derived from collected evidence, not exploitation attempts — nothing here was executed.
What to do first
| Action | Why | Paths removed | Findings | Est. reduction |
|---|---|---|---|---|
| Patch CVE-2024-21762 on vpn.example.com | Clears 1 known exploited vulnerability; 1 finding here is both known-exploited and reachable from the Internet; Reduces 1 Internet-facing exposure; Highest risk score in this group is 100/100; Addresses a known-exploited vulnerability; no modeled-path reduction identified | 0 | 1 | 0% (estimate) |
| Patch CVE-2025-53770 on web01.example.com | Clears 1 known exploited vulnerability; 1 finding here is both known-exploited and reachable from the Internet; Reduces 1 Internet-facing exposure; Highest risk score in this group is 100/100; Addresses a known-exploited vulnerability; no modeled-path reduction identified | 0 | 1 | 0% (estimate) |
| Reduce Internet exposure of web01.example.com | Could remove 1 modeled attack path; Protects critical system: web01.example.com; Reduces 1 Internet-facing exposure | 1 | 0 | 50% (estimate) |
| Reduce Internet exposure of vpn.example.com | Could remove 1 modeled attack path; Protects critical system: vpn.example.com; Reduces 1 Internet-facing exposure | 1 | 0 | 50% (estimate) |
| Patch CVE-2024-37085 on esx01.example.com | Clears 1 known exploited vulnerability; Addresses a known-exploited vulnerability; no modeled-path reduction identified | 0 | 1 | 0% (estimate) |
Estimated reduction is a projection from the current exposure model, not a measurement. What the work actually removed is reported after it is done.
Change over the period
0 finding(s) closed against 0 newly found. Net exposure was unchanged over the period. None of the closures were confirmed by re-checking. Exposure Score was unchanged from 68.7 to 68.7 (+0.0) across 31 measurement(s) between 2026-09-15 and 2026-10-15. Lower is better.
Basis: measured from stored Exposure Score snapshots, with finding lifecycle counts alongside.
Assets with the most open findings
| Asset | Open findings |
|---|---|
| backup01.example.com | 1 |
| app01.example.com | 1 |
| web01.example.com | 1 |
| vpn.example.com | 1 |
| fs01.example.com | 1 |
How to read it
The demonstration tenant is static
Nothing in the demonstration estate is being fixed, so this sample shows zero resolved and zero confirmed fixes, and an unchanged score. That is the report telling the truth about the data it was given. A customer report fills the same sections from that customer’s own measurements.
Estimates are labelled as estimates
“Est. reduction” is what the current model projects. The period change and “Confirmed by recheck” are measured. A report never presents the first as the second.
Illustration · demonstration data
Before remediation, and after verification
One Fix First action followed through the states the platform records. The hosts and outcome are invented to show the structure; they are not a customer result and not a measurement of anything.
Before
- Action: Patch CVE-2024-37085 on esx01.example.com
- Why it ranks: clears 1 known exploited vulnerability
- Finding status: open
- Ticket: raised, in progress
After the work, before the recheck
- Patch job: 2 of 3 devices succeeded; 1 failed, reboot pending
- Action status: partial
- Finding status: potentially remediated — still counted as open exposure
- Ticket: annotated and left open
After verification
- Recheck: each finding re-observed and recorded as fixed, still present or inconclusive
- Fixed: the finding moves to verified and leaves the open count
- Still present or inconclusive: it stays open; nothing is reported as fixed on the strength of the patch job
- Report: “Confirmed by recheck” counts only the first
What would change in this report
Only verified fixes move “Confirmed by recheck”. A ticket closed or a job marked successful moves nothing on its own; see why a successful patch job is not verification.
Want this report for one of your customers?
A one-customer pilot produces it from a scope you authorize. The checklist sets out what to have ready.