Patch Management Policy

Patch compliance report: what an auditor can check

A patch compliance report an auditor can test lists each asset, the date the fix became available, the date it was installed and the deadline that applied. Cyber Essentials v3.3 measures from release; FedRAMP's legacy page from discovery. The clock start must be on the report. Read 19 Nov 2026.

Fields to keep per patch per asset

Evidence record (one row per asset per patch)

  • Asset ID and group
  • Patch or advisory ID
  • Severity and who assigned it (vendor wording, scanner, or reviewer)
  • Clock start: release | discovery | KEV listing, with the date
  • Deadline applied and the policy clause it came from
  • Install date and the verification method
  • Exception ID, if any, with owner, control and end date
  • Result: within deadline | late | excepted

Each field answers a test an assessor can run. Cyber Essentials v3.3 needs the release date to compute "within 14 days of release". An exception under NIS2 point 6.6.2 needs the documented reason. The proposed HIPAA rule would require the patch policy itself to be reviewed and tested every 12 months, so the review date is evidence too.

What tools say they export

These are vendor statements, read 19 Nov 2026, in alphabetical order. Action1 says it can export audit evidence and schedule customized reports. Automox says it offers 20 prebuilt reports, exportable as PDF, CSV or XLSX. Microsoft documents Intune and Autopatch reports for devices that are "Not up to date". Each is a feature claim; whether a given export satisfies an auditor is for the auditor to say.

The directory records the reporting fields for each tool, deploy kind and prioritize kind kept apart.

Gaps to state openly

PCI DSS v4.0.1 requirement text could not be read on 19 Nov 2026, so this page cannot quote the standard's evidence requirements. The evidence the Council's FAQs 1597 and 1572 point to is on the PCI DSS patch window page; read the requirement in the standard you are assessed against before copying a list. The same applies to ISO/IEC 27001 and SOC 2.

Next: the rate that sits above these records is in patch compliance rate, and the reporting section of the policy is in reporting and metrics.

4.3 Patch windows

SeverityWindow3143090180 days
1. Known exploited, internet-facing3 calendar daysApplies to: Systems reachable from the internet
1. Known exploited, other14 calendar daysApplies to: All other systems
2. Critical14 calendar days
3. High30 calendar daysApplies to: All systems [set 14 if you hold Cyber Essentials]
4. Medium90 calendar days
5. Low180 calendar days
Routine baselineEvery month, or more oftenApplies to: Operating system and application updates

No framework selected: every window above is the site template's suggested default, and the clock starts as this section states.

Questions

patch compliance report

It is a per-asset record of what was patched, when the fix became available, when it was installed and which deadline applied. The record format is in the evidence guide.

what is patch compliance report

A patch compliance report shows, for a set of assets, which fixes are installed against the deadline in the policy. It is only checkable if the clock start and any exceptions are on it.

Sources

Last reviewed 19 Nov 2026