# PCI DSS v4.0.1 Patching: One Month for Critical Flaws

Canonical: https://patchmanagementpolicy.com/patch-windows/pci-dss/
Last reviewed: 19 Nov 2026

## PCI DSS patching requirements

PCI SSC FAQ 1597 says Requirement 6.3.3 of PCI DSS v4.0.1 requires patches for critical vulnerabilities within one month of release; all other patches follow time frames the entity sets from its own risk assessment. The standard's PDF returned HTTP 403 on 19 Nov 2026, so this page quotes the Council's FAQs and blog.

### What could and could not be read

The standard itself (docs-prv.pcisecuritystandards.org) returned HTTP 403 on 19 Nov 2026, and the document library download sits behind an agreement form, so no clause text is quoted from the PDF. Two statements of the PCI Security Standards Council were read instead: FAQ 1597, titled "What are the expectations for entities when assigning risk rankings to vulnerabilities and resolving or addressing those vulnerabilities?" (dated May 2025), and the Council's blog post of 11 Jun 2024 announcing v4.0.1. Each is quoted below and labeled.

The requirement numbers 6.3.1, 6.3.3, 11.3.1 and 11.3.1.1 come from FAQ 1597. Their exact wording, scope notes and testing procedures remain unread.

### The timing rule in the Council's words

- **Critical vulnerabilities:** Requirement 6.3.3 "specifies time frames for installing security patches/updates", and "those for critical vulnerabilities must be resolved within one month of release." (FAQ 1597)
- **Everything else:** "all other applicable security patches/updates must be installed within appropriate time frames determined by the entity's assessment of the risk to their environment," aligned with the risk levels assigned under 6.3.1, "for example, resolving high-risk vulnerabilities more quickly than lower-ranked vulnerabilities." (FAQ 1597)
- **The v4.0.1 change:** the 11 Jun 2024 blog says Requirement 6 "reverted to PCI DSS v3.2.1 language that installing patches/updates within 30 days applies only for 'critical vulnerabilities.'" It adds that v4.0.1 has no new or deleted requirements.

### Assigning levels, resolving and addressing

FAQ 1597 splits the work into two steps. Requirement 6.3.1 has the entity assign risk levels "based on impact to the entity" and identify at a minimum the high-risk or critical vulnerabilities; it "does not require that an entity accepts risk rankings assigned by external sources." Requirements 11.3.1 and 11.3.1.1 then ask that critical and high-risk vulnerabilities be resolved and lower-level ones addressed "in accordance with the entity's risk as defined and documented in a targeted risk analysis (TRA)."

| Council term | Council definition (FAQ 1597) |
|---|---|
| Resolved | "the entity solves or fixes the vulnerability" |
| Addressed | "the entity determines whether to resolve the vulnerability or to mitigate the risk by addressing the vulnerability in another way (e.g., with a compensating control or by disabling a vulnerable service)" |

PCI SSC FAQ 1597, footnotes to the resolve and address steps, read 19 Nov 2026.

### Missing the window cannot be fixed afterwards

FAQ 1572 (June 2025) asks whether a compensating control can cover a requirement with a defined frequency when the activity was not performed in time. The answer is No: there is "no way for them to perform the control retroactively or backdate a later occurrence of the control to an earlier period." The Council's examples include "not installing a critical security patch within 30 days of release."

An assessor can still find the requirement In Place if the entity has implemented corrective actions and the assessor has assurance that the entity has a repeatable and documented process, that the miss was due to an exceptional circumstance ("poor security practices and recurring failures are not 'exceptional circumstances'"), that the cause was addressed, and that steps to prevent recurrence are in the process. Otherwise "Not in Place" is a possible finding.

### What a policy must write to meet it

1. Define critical for the entity's environment and say it comes from the entity's own risk assessment process, not from a scanner label alone.
2. State that critical patches are installed within one month (30 days) of release, and that the month starts at the vendor's release.
3. State that every other patch has a time frame tied to the risk level, with a faster window for high-risk items, and cite the targeted risk analysis that supports each window.
4. State what is done for lower-level items: resolve, or address by another documented route.
5. Describe the corrective-action record kept whenever a window is missed, covering the points FAQ 1572 lists.

### Evidence an assessor looks for

From the two FAQs: the risk-level method and its output (6.3.1), the targeted risk analysis behind non-critical time frames, patch install dates compared with vendor release dates for critical items, and, for any miss, the documented corrective actions and the repeatable process the assessor must be assured of. Which artifacts a particular assessor requests for a Report on Compliance or Self-Assessment Questionnaire is not stated in the sources read. The [payment card policy template](https://patchmanagementpolicy.com/templates/payment-card-pci-dss/) uses the one-month rule, and the [Patch Window Table](https://patchmanagementpolicy.com/patch-windows/) and [severity and patch window section](https://patchmanagementpolicy.com/policy-sections/severity-and-patch-windows/) show how it sits beside other frameworks.

### Sources

- [PCI SSC, FAQ 1597, assigning risk levels and resolving or addressing vulnerabilities (May 2025)](https://www.pcisecuritystandards.org/faqs/1597), read 19 Nov 2026
- [PCI SSC, FAQ 1572, compensating controls and missed frequencies (June 2025)](https://www.pcisecuritystandards.org/faqs/1572), read 19 Nov 2026
- [PCI SSC blog, Just Published: PCI DSS v4.0.1 (11 Jun 2024)](https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/)
- [PCI DSS Patch Management Policy Template](https://patchmanagementpolicy.com/templates/payment-card-pci-dss/)
- [Severity and Patch Windows: What Each Framework Sets](https://patchmanagementpolicy.com/policy-sections/severity-and-patch-windows/)
- [Patch Management Compliance Dates: 7 Dec 2026 and Back](https://patchmanagementpolicy.com/dates-to-know/)
