Example reports
An appsec lead, a licensing owner and a SOC analyst need different parts of the same analysis.
Which sections a report shows is configurable. The three presets below are starting points rather than fixed views, and the control at the top of each report is real: it changes what is on the page, not what is highlighted on it.
| lens | sections | for |
|---|---|---|
| Minimal | 3 of 18 | Someone who needs an answer |
| Business | 11 of 18 | Someone making the decision |
| Technical | 18 of 18 | Someone checking the working |
| Custom | any | Define the sections you want. On the roadmap; the three above are the presets that ship. |
A signed vendor installer
Everything checks out
The full eighteen sections and the lens toggle. Vendor intelligence at verified identity, and the four bundled executables that appear in an endpoint register with no catalog entry of their own.
An unsigned binary
Nothing to verify against
Attribution where there is no signature to lean on. This artifact is a row in the endpoint register at fineness 720, same value, same meaning, and here is the working behind it. Contractor-supplied, never published, in no catalog: the case a catalog cannot answer at all.
A macro-bearing document
The file contradicts itself
A document whose stored macro source and compiled p-code describe different programs. Every tool that reads the source sees a date formatter. Extracted VBA, shown inert, with the divergence beside it: the case where reading the file is not merely better but is the only thing that works.
The data is fabricated and internally consistent: real vendors, real structures, written analysis. Sections marked in the margin are designed rather than shipped.