Report types
The PDF reports RevoSecure generates, who each one is for, and how to generate them.
Updated
On this page
Reports are white-labelled PDFs with your logo, colour, contact details and footer. Generate them from Reports in a customer's workspace: pick a type and generate it. In the portfolio, Reports offers workspace reports and asks which customer for the others. Finished reports are downloaded, shown to portal users (client reports only) or emailed on a schedule.
Client-facing reports
| Report | For | Contents |
|---|---|---|
| Risk assessment | Prospects and client reviews | Score and grade, key findings, quick wins, and for every finding: what it is, why it matters, the recommended action and what the check can't tell you. Ends with methodology and a plain-language glossary |
| Executive summary | Leadership | Score, top risks, recommended actions, and a "How we can help" section for prospects |
| Technical report | Engineers | Every open finding with evidence, CVEs, remediation and methodology |
| Progress | Client reviews | What improved and regressed over a period (7 days to a year): updates, software, protection and findings resolved, with per-device highlights |
| Path to 100% patching | Clients and your team | Patch compliance against the 100% target, trend, SLA adherence, mean time to patch, and everything in the way, each with an owner and a next step |
| Ideal-state compliance | Clients and your team | Control by control against the customer's ideal state, with device and user coverage and what was deliberately left out |
Internal reports
These include data you may not share with the customer and are never visible in the portal.
| Report | Contents |
|---|---|
| Action plan | Ticket-ready work items with an effort estimate (quick fix, moderate, project), evidence, recommended action and a completion check. Includes findings hidden from the customer |
| Internal progress | Everything in Progress, plus findings hidden from the customer and the change in score, findings, vulnerabilities, patching and MFA |
| Portfolio compliance | Every customer ranked by ideal-state compliance, with 30-day movement, the biggest movers and gaps many customers share. A workspace report, not about one customer |
Honest reporting rules
- Patching counts every managed device. A device that's offline or hasn't reported isn't compliant, so going quiet can't make the number look better. Controls left out of the ideal state are listed as accepted, not counted.
- Coverage notices. If some checks couldn't run in the latest assessment (a network timeout, say), the report shows a Coverage notice listing them, so nobody mistakes "not checked" for "no issues".
- Dark web results say "none found in the sources checked", never "no exposure".
- Hidden findings stay hidden. Client reports leave out anything not marked Show to customer (see Branding and sharing).
AI-written summaries
Report summaries are written by the AI analyst and count as one AI request against your monthly allowance. When the allowance is used up, a standard written summary is used instead.
Limits
At most two reports per workspace are queued or generating at once, and about ten can be started an hour. If you hit either limit, wait for the current reports to finish. Archived customers can't get new reports.
Prospect assessments
Prospect assessment runs a passive external assessment for a new prospect and generates the reports you ticked when it finishes (by default the client-facing Risk assessment and the internal Action plan). See Prospect risk assessment.