Live HTML report · obxlab.local

This is what an Obexum report looks like.

Below is the actual findings.html generated by the most recent lab engagement — not a mockup, not a screenshot. Filter by severity, search by rule_id, click any finding to expand its evidence. Every Obexum scan produces this same artifact, ready to share with your auditor.

Embedded report. For the full experience, open it in a new tab.

Anatomy of an Obexum report.

The same shape for every scan. Auditors love it because the layout is consistent.

Executive summary at the top

Target identity, generation timestamp, total findings, severity breakdown and a one-line call-out telling the operator how many findings have a shipped remediation playbook. Designed to be screen-shareable in a 60-second status meeting.

Top fixes by impact

The remediation plan is ranked by composite impact (severity × finding count × KEV proximity). Operators can copy obexum fix --scan-id ... straight from the call-out.

Sticky filter bar

Search by rule_id / title / category, toggle severities, see live counts. Vanilla JS, no external dependencies — the report is fully self-contained and works offline.

Per-finding evidence

Every finding shows raw probe output, the rule reference, MITRE mapping, location metadata, and a remediation note. Print to PDF gives you a clean, audit-grade artefact in one click.

Run it on your own host.

The same report against your AD — in five minutes.