Report Gallery
Use these examples when you need a polished output quickly. Each template keeps claims bounded: what changed, what is known, what is not proven, who owns the next step, and when to review.
Gallery
Product Demo
Domain score, business impact, fix order, technical appendix, and a demo-only boundary.
Leadership
Plain-language risk themes, decisions needed, owners, blockers, and evidence caveats.
SOC
What to hunt, where to look, what the portal cannot prove, and when to escalate.
Patch
Affected scope, fixed version, owner ask, rollback notes, and closure evidence expectations.
Vendor
Precise questions for unclear affected ranges, mitigations, fixed versions, or support statements.
Program
Trends, aging work, exceptions, blockers, owner progress, and next-week improvements.
Safe Output Rules
Name the CVE, domain, advisory, finding, or control that changed.
Use source, owner, scan, version, or configuration evidence.
Avoid claiming compromise, exposure, or compliance without proof.
End with owner, next step, due window, and review trigger.
Recommended use: start with a gallery format, then use the linked page to fill in evidence-backed details.