📝 Reporting

Ship Clear, Actionable Findings

Use these outlines to keep Diablo reports concise, reproducible, and tailored to your audience. Pair them with evidence packs so remediation is fast.

Check readiness before delivery

📄 Templates

Markdown Skeletons

Copy, adjust, and keep consistent across engagements.

Executive Snapshot

Context (scope, timeline, owners).
Top 3 risks with business impact.
Remediation ETA and dependencies.

Technical Finding

Title + severity + asset identifier.
Repro steps with commands and responses.
Evidence links (hashes, screenshots, pcaps).
Fix guidance + validation steps.

Changelog

Runs executed (date/time/host).
Tools and versions used.
Cleanup and rollback actions taken.

🎯 Delivery

Tailor for the Audience

Pick a delivery path that meets stakeholders where they are.

Stakeholder Brief

Slides or PDF with visuals.

One slide per critical issue.
Impact framed in business terms.
Clear next steps and owners.

Engineer Hand-off

Repo or wiki entry with diffs.

Commands, configs, and sample payloads.
Tests to verify the fix (unit/integration).
Rollback steps documented.

Leadership Summary

Concise email or memo.

One paragraph of highlights.
Risk trend (improving/regressing).
Asks: budget, tooling, or policy changes.

✅ QA

Pre-Delivery Checklist

Last pass before you send anything out.

Content

Redacted secrets and client-identifying data.
CVSS/impact ratings match evidence.
Findings mapped to scope and ticket IDs.

Format

Headings and numbering consistent.
Images compressed; hashes recorded.
Accessibility tags on diagrams/charts.

Handoff

Delivery channel agreed (email, portal, live readout).
Links to evidence packs and lab notes.
Plan for follow-up validation scheduled.