Security analysts reviewing vulnerability findings
Vulnerability management

Vulnerability reporting

A falling vulnerability total can mean successful remediation, retired assets or failed collection. Without coverage and context, you cannot tell which. We structure reporting so engineers can act and directors can see the unresolved business exposure.

Show the collection health before the result

Report the expected estate, observed assets, authenticated coverage, agent health and failed checks. Use the same scope between periods or explain the change. A report covering only devices that checked in hides the machines most likely to have drifted.

Reconcile duplicate and retired records deliberately. Keep a record of removals so legitimate decommissioning can be distinguished from lost visibility. Where a system cannot be assessed safely, identify the alternate evidence or unresolved gap.

Split the operational and executive views

Engineers need affected assets, software versions, fix guidance, owner and maintenance grouping. Directors need the affected service, overdue priority exposure, blocked changes and decisions. Sending the same unfiltered export to both groups rarely serves either.

Qualys tags can support the grouping when they reflect real ownership and service boundaries. A tag naming a location is not necessarily enough to route work. Review the source of each tag and the process for new and moved assets.

Explain what closed and how it was verified

Count verified remediation separately from planned work, accepted exceptions and retired systems. Record rescans or version evidence where appropriate. A successful deployment message does not establish that every installed application copy or pending restart was resolved.

Use age bands and recurring findings alongside an average remediation time. Otherwise many easy closures can hide a small persistent backlog on the most important services. Investigate recurrence as an operational issue, not just another detection to close.

Make exceptions a decision, not a hiding place

State why a fix is delayed, which controls limit exposure, who approved the exception and when it expires. If exploitation or reachability changes, reassess it. Exceptions should remain visible in the reporting baseline rather than vanish from totals.

Where the consequence is material, link the issue to a maintained risk record and its business owner. Horizon can organise that governance evidence; it does not substitute for the scanner, change approval or technical verification. Keep the report focused on what must happen next.

Questions

Frequently asked questions

Why do totals increase after improving scanning?

Better authentication, new agents or broader scope can reveal previously unknown findings. Explain the coverage change and establish a comparable baseline before interpreting the trend.

Should accepted risks be removed from reports?

No. Separate them from outstanding remediation work, but retain their exposure, approval, review date and mitigation evidence. Acceptance is not the same as a fix.

Can a scanner export be the monthly report?

It can provide supporting data. A useful monthly report also needs scope, ownership, verified progress, exceptions and the business decisions the export cannot explain.

Work through your vulnerability backlog with us.

Bring the coverage report as well as the vulnerability totals. We will discuss ownership, patch constraints and what would make remediation workable in your environment.

Book a consultation