Patch Management Policy

PCI DSS patch management policy

PCI SSC FAQ 1597 (May 2025) says Requirement 6.3.3 of PCI DSS v4.0.1 requires patches for critical vulnerabilities within one month of release. The standard's own text could not be read on 19 Nov 2026, so this variant cites the FAQ for that figure and adds a stricter 14 day company standard.

Payment card variant: paste over the same-numbered sections of the general policy

1 Purpose and scope

1.1 This policy applies to every system component in the cardholder data environment of [Company name], every system connected to it, and every system that can affect its security. The scope diagram dated [date] is kept by [role].

1.2 Third parties that host or manage in-scope components are named in [register] and are bound by clause 4.

4 Severity and patch windows

4.1 Patch windows

Windows for in-scope components, from vendor release

SeverityWindow3143090180 days
Critical vulnerabilities14 calendar days (company standard); never more than one monthBasis: PCI SSC FAQ 1597: Requirement 6.3.3, one month from release for critical vulnerabilities
Known exploited3 days internet-facing, otherwise 14 daysBasis: Company standard (CISA BOD 26-04 tiers)
High and other30, 90 and 180 days as in the general policyBasis: Company standard; non-critical windows follow the entity's risk analysis (FAQ 1597)

Windows as this template sets them, on the same 0 to 180 day scale as the builder.

4.2 Where the QSA or the assessor reads the requirement differently, [role] amends this clause within [10] working days and records the reason.

4.3 In-scope components that cannot meet clause 4.1 are recorded under Annex A with the requirement reference [number from your copy of the standard].

8 Reporting and metrics

8.1 The monthly report adds: in-scope components with a critical vulnerability past 14 days; oldest open critical age; scope changes.

8.2 Evidence of each patch (date installed, component, vulnerability) is kept for [period set by the assessor].

How the one month figure was read

Two PCI SSC sources were read: the blog post announcing v4.0.1 (11 June 2024) and FAQ 1597 (May 2025). FAQ 1597 says Requirement 6.3.3 requires patches for critical vulnerabilities within one month of release, and that all other patches follow time frames the entity sets from the risk levels it assigns under 6.3.1. The standard's own text returned HTTP 403 on 19 Nov 2026, so its wording is not quoted.

Three dates from the blog post matter for scope. PCI DSS v4.0 was retired on 31 December 2024, which leaves v4.0.1 as the only active version. The effective date for the new requirements, 31 March 2025, was not moved by v4.0.1. And v4.0.1 added no new or deleted requirements, being a limited revision.

What a policy should and should not claim

  • Do claim: critical vulnerabilities in scope are patched within one month of release at most. That is FAQ 1597's statement of Requirement 6.3.3.
  • Do not claim: wording from the standard itself, or a fixed number for non-critical vulnerabilities; FAQ 1597 leaves those to the entity's targeted risk analysis.
  • Do record the numbered requirement from your own licensed copy in clause 4.3; the bracket is there for that.
  • The company standard of 14 days is this site's default, aligned to UK Cyber Essentials v3.3 and sitting well inside 30.

Because PCI rules apply to the in-scope environment only, clause 1.1 asks for a dated scope diagram. Out-of-scope systems follow the general policy.

The PCI DSS patch window page lists what was and was not read, line by line. For proving the clause to an assessor see proving patch compliance to an auditor. Variants for other regimes are in the template set.

Sources

Last reviewed 19 Nov 2026