Explore synthetic examples of the Engineer and Executive reports, plus a managed-audit comparison. All names, findings, dates and addresses in these examples are invented; they contain no customer or HOME audit data.
Engineer report
Useful for firewall engineers, security engineers, remediation planning, rule review, and technical audit follow-up.
Executive report
Useful for leadership review, compliance discussions, governance updates, and prioritising security work.
Illustrative change intelligence
Posture 72% to 78% (+6 points). One new Critical failure needs action; one High finding was resolved; two findings remain open. A new Critical alert is sent once for that failure episode. The still-failing items do not generate repeat alerts on every audit.
| Finding | Previous | Current | Action |
|---|---|---|---|
| Administrator MFA, global scope | Passed | New Critical failure | Assign an owner and due date |
| Restricted management sources, global scope | High failure | Resolved | Retain the audit evidence |
| Policy logging, root VDOM, policy 42 | Failed | Still failing | Continue remediation |
This is a synthetic example. A skipped or unevaluated rule is not counted as resolved.
Next step
Run a first audit when you are ready, or review the handling model before you upload an authorised config.