{
  "name": "Patch Window Table",
  "edition": "2026-11-19",
  "license": "CC BY 4.0",
  "license_url": "https://creativecommons.org/licenses/by/4.0/",
  "cite": "Patch Management Policy, Patch Window Table, edition 19 Nov 2026, https://patchmanagementpolicy.com/patch-windows/",
  "fields": [
    "framework",
    "version",
    "clause_id",
    "clause_text",
    "timing_set",
    "applies_to",
    "severity_basis",
    "source_url",
    "read_date",
    "notes",
    "kind"
  ],
  "rows": [
    {
      "framework": "PCI DSS",
      "version": "4.0.1",
      "clause_id": "6.3.3",
      "clause_text": "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)",
      "timing_set": "1 month (30 days) from release for critical vulnerabilities",
      "applies_to": "Entities in PCI DSS scope (scope text not read)",
      "severity_basis": "Critical vulnerabilities",
      "source_url": "https://www.pcisecuritystandards.org/faqs/1597",
      "read_date": "2026-11-19",
      "notes": "Read from PCI SSC FAQ 1597 (May 2025), not from the standard: the standard PDF returned HTTP 403 on 2026-11-19 (docs-prv.pcisecuritystandards.org) and the document library download needs an agreement form, so the requirement's own wording is not quoted. The PCI SSC blog of 2024-06-11 adds that v4.0.1 reverted to PCI DSS v3.2.1 language that installing patches/updates within 30 days applies only for “critical vulnerabilities”.",
      "kind": "primary"
    },
    {
      "framework": "PCI DSS",
      "version": "4.0.1",
      "clause_id": "6.3.3, other patches",
      "clause_text": "“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” (FAQ 1597)",
      "timing_set": "No number set; entity's risk assessment",
      "applies_to": "Entities in PCI DSS scope",
      "severity_basis": "Risk levels assigned under 6.3.1",
      "source_url": "https://www.pcisecuritystandards.org/faqs/1597",
      "read_date": "2026-11-19",
      "notes": "Read from PCI SSC FAQ 1597 (May 2025), not from the standard: the standard PDF returned HTTP 403 on 2026-11-19 (docs-prv.pcisecuritystandards.org) and the document library download needs an agreement form, so the requirement's own wording is not quoted.",
      "kind": "primary"
    },
    {
      "framework": "PCI DSS",
      "version": "4.0.1",
      "clause_id": "6.3.1, 11.3.1, 11.3.1.1",
      "clause_text": "Assign risk levels to vulnerabilities; resolve critical and high-risk vulnerabilities and address lower levels in line with the entity's targeted risk analysis (FAQ 1597)",
      "timing_set": "No number set; entity's targeted risk analysis",
      "applies_to": "Entities in PCI DSS scope",
      "severity_basis": "Risk levels based on impact to the entity",
      "source_url": "https://www.pcisecuritystandards.org/faqs/1597",
      "read_date": "2026-11-19",
      "notes": "Read from PCI SSC FAQ 1597 (May 2025), not from the standard: the standard PDF returned HTTP 403 on 2026-11-19 (docs-prv.pcisecuritystandards.org) and the document library download needs an agreement form, so the requirement's own wording is not quoted. Exact wording, scope notes and testing procedures of these requirements remain unread.",
      "kind": "primary"
    },
    {
      "framework": "NIST SP 800-40",
      "version": "Rev. 4 (April 2022)",
      "clause_id": "Section 3.5",
      "clause_text": "A maintenance plan defines the actions to be taken when a scenario occurs for a maintenance group, including the timeframes for beginning and ending each action",
      "timing_set": "no number set",
      "applies_to": "Organizations planning enterprise patch management; guidance, not a mandate",
      "severity_basis": "Risk response scenario (routine patching, emergency patching, emergency mitigation, unpatchable assets) set by the organization",
      "source_url": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
      "read_date": "2026-11-19",
      "notes": "The publication gives no fixed day count for its own recommendations. Each organization defines timeframes in its maintenance plans.",
      "kind": "primary"
    },
    {
      "framework": "NIST SP 800-40",
      "version": "Rev. 4 (April 2022)",
      "clause_id": "Section 3.5.2",
      "clause_text": "emergency patching itself could occur in the following hours or days, depending on how urgent the emergency is",
      "timing_set": "no number set (hours or days, depending on urgency)",
      "applies_to": "Emergency patching scenario",
      "severity_basis": "How urgent the emergency is",
      "source_url": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
      "read_date": "2026-11-19",
      "notes": "Described as an accelerated version of the routine approach, with a canary period of \"a few minutes to a few hours\".",
      "kind": "primary"
    },
    {
      "framework": "NIST SP 800-40",
      "version": "Rev. 4 (April 2022)",
      "clause_id": "Section 3.5 (CISA KEV note)",
      "clause_text": "CISA’s Binding Operational Directive 22-01 [4] requires federal agencies to remediate new vulnerabilities added to the catalog within two weeks.",
      "timing_set": "2 weeks (stated for U.S. federal agencies under BOD 22-01, described by NIST; not a NIST requirement)",
      "applies_to": "U.S. federal agencies (BOD 22-01); other organizations may use the catalog voluntarily",
      "severity_basis": "Vulnerability listed in the CISA Known Exploited Vulnerabilities Catalog",
      "source_url": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
      "read_date": "2026-11-19",
      "notes": "The two-week figure comes from CISA’s directive as reported in the NIST text. The directive itself was not read.",
      "kind": "primary"
    },
    {
      "framework": "CIS Controls",
      "version": "v8 (August 2023 guide PDF)",
      "clause_id": "7.3",
      "clause_text": "Perform operating system updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.",
      "timing_set": "monthly, or more frequent",
      "applies_to": "Enterprise assets, operating systems; IG1, IG2, IG3",
      "severity_basis": "No severity tiers; cadence applies to operating system updates",
      "source_url": "https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf",
      "read_date": "2026-11-19",
      "notes": "v8.1 safeguard text was not read: the v8.1 download sits behind a form. This row is v8 as published in the August 2023 guide PDF.",
      "kind": "primary"
    },
    {
      "framework": "CIS Controls",
      "version": "v8 (August 2023 guide PDF)",
      "clause_id": "7.4",
      "clause_text": "Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.",
      "timing_set": "monthly, or more frequent",
      "applies_to": "Enterprise assets, applications; IG1, IG2, IG3",
      "severity_basis": "No severity tiers; cadence applies to application updates",
      "source_url": "https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf",
      "read_date": "2026-11-19",
      "notes": "v8.1 text not read.",
      "kind": "primary"
    },
    {
      "framework": "CIS Controls",
      "version": "v8 (August 2023 guide PDF)",
      "clause_id": "7.7",
      "clause_text": "Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.",
      "timing_set": "monthly, or more frequent",
      "applies_to": "Detected software vulnerabilities; IG2, IG3",
      "severity_basis": "Set by the documented remediation process",
      "source_url": "https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf",
      "read_date": "2026-11-19",
      "notes": "v8.1 text not read.",
      "kind": "primary"
    },
    {
      "framework": "CIS Controls",
      "version": "v8 (August 2023 guide PDF)",
      "clause_id": "7.2",
      "clause_text": "Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.",
      "timing_set": "monthly, or more frequent (reviews of the remediation strategy)",
      "applies_to": "Enterprises; IG1, IG2, IG3",
      "severity_basis": "Risk-based",
      "source_url": "https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf",
      "read_date": "2026-11-19",
      "notes": "The cadence is for review of the strategy, not for installing patches.",
      "kind": "primary"
    },
    {
      "framework": "CIS Controls",
      "version": "v8 (August 2023 guide PDF)",
      "clause_id": "7.1",
      "clause_text": "Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.",
      "timing_set": "annual review of the documentation (no patch deadline)",
      "applies_to": "Enterprise assets; IG1, IG2, IG3",
      "severity_basis": "Not stated",
      "source_url": "https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf",
      "read_date": "2026-11-19",
      "notes": "No patch timing in this safeguard.",
      "kind": "primary"
    },
    {
      "framework": "CIS Controls",
      "version": "v8 (August 2023 guide PDF)",
      "clause_id": "7.5 and 7.6",
      "clause_text": "Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. | Perform scans on a monthly, or more frequent, basis.",
      "timing_set": "quarterly or more frequent (7.5, internal); monthly or more frequent (7.6, externally exposed)",
      "applies_to": "Internal and externally exposed enterprise assets; IG2, IG3",
      "severity_basis": "Not stated",
      "source_url": "https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf",
      "read_date": "2026-11-19",
      "notes": "Scanning cadence, not patch timing. 7.5 and 7.6 quotes are from two safeguards, joined here with a vertical bar.",
      "kind": "primary"
    },
    {
      "framework": "ISO/IEC 27001",
      "version": "2022",
      "clause_id": "Annex A 8.8",
      "clause_text": "",
      "timing_set": "not read on 2026-11-19",
      "applies_to": "not read",
      "severity_basis": "not read",
      "source_url": "https://www.iso.org/standard/27001",
      "read_date": "2026-11-19",
      "notes": "iso.org returned HTTP 403 (bot challenge page) for every page tried, and the standard text is sold. No text is quoted. Nothing is recorded about the content of the control.",
      "kind": "primary"
    },
    {
      "framework": "HIPAA Security Rule (current rule)",
      "version": "45 CFR 164.308, eCFR current text (latest amendment 2016-12-30, eCFR current as of 2026-11-17)",
      "clause_id": "164.308(a)(1)(ii)(B)",
      "clause_text": "Implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level to comply with § 164.306(a).",
      "timing_set": "no number set",
      "applies_to": "Covered entities and business associates",
      "severity_basis": "Risk analysis result; reasonable and appropriate",
      "source_url": "https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C/section-164.308",
      "read_date": "2026-11-19",
      "notes": "The section does not use the word patch in the text read. Protection from malicious software, 164.308(a)(5)(ii)(B), is addressable: \"Procedures for guarding against, detecting, and reporting malicious software.\"",
      "kind": "primary"
    },
    {
      "framework": "HIPAA Security Rule (current rule)",
      "version": "45 CFR 164.308, eCFR current text",
      "clause_id": "164.308(a)(1)(ii)(A)",
      "clause_text": "Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information held by the covered entity or business associate.",
      "timing_set": "no number set",
      "applies_to": "Covered entities and business associates",
      "severity_basis": "Risk analysis",
      "source_url": "https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C/section-164.308",
      "read_date": "2026-11-19",
      "notes": "Risk analysis is the stated input to what gets fixed; no days are set.",
      "kind": "primary"
    },
    {
      "framework": "HIPAA Security Rule NPRM (proposed, not in force)",
      "version": "90 FR 898, published 2025-01-06 (document 2024-30983)",
      "clause_id": "Proposed 164.308(a)(4)(ii)(C)(1)",
      "clause_text": "Within 15 calendar days of identifying the need to patch, update, or upgrade the configuration of a relevant electronic information system to address a critical risk in accordance with this paragraph (a)(4)(ii)(C), where a patch, update, or upgrade is available",
      "timing_set": "15 calendar days (proposed)",
      "applies_to": "Relevant electronic information systems of covered entities and business associates",
      "severity_basis": "Critical risk, per the regulated entity’s risk analysis",
      "source_url": "https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information",
      "read_date": "2026-11-19",
      "notes": "Proposal only. Where no patch is available, the 15 days run from when one becomes available. In the proposal text read on 2026-11-19, no final rule was found (see dates file).",
      "kind": "primary"
    },
    {
      "framework": "HIPAA Security Rule NPRM (proposed, not in force)",
      "version": "90 FR 898, published 2025-01-06",
      "clause_id": "Proposed 164.308(a)(4)(ii)(C)(2)",
      "clause_text": "Within 30 calendar days of identifying the need to patch, update, or upgrade the configuration of a relevant electronic information system to address a high risk in accordance with this paragraph (a)(4)(ii)(C), where a patch, update, or upgrade is available",
      "timing_set": "30 calendar days (proposed)",
      "applies_to": "Relevant electronic information systems",
      "severity_basis": "High risk, per the regulated entity’s risk analysis",
      "source_url": "https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information",
      "read_date": "2026-11-19",
      "notes": "Proposal only.",
      "kind": "primary"
    },
    {
      "framework": "HIPAA Security Rule NPRM (proposed, not in force)",
      "version": "90 FR 898, published 2025-01-06",
      "clause_id": "Proposed 164.308(a)(4)(ii)(C)(3)",
      "clause_text": "As determined by and documented in the covered entity’s or business associate’s policies and procedures under paragraph (a)(4)(ii)(A) of this section for all other patches, updates, and upgrades to the configuration of a relevant electronic information system.",
      "timing_set": "no number set for other patches (set by the entity’s own written policy)",
      "applies_to": "Relevant electronic information systems",
      "severity_basis": "Everything below critical and high",
      "source_url": "https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information",
      "read_date": "2026-11-19",
      "notes": "Proposal only.",
      "kind": "primary"
    },
    {
      "framework": "HIPAA Security Rule NPRM (proposed, not in force)",
      "version": "90 FR 898, published 2025-01-06",
      "clause_id": "Proposed 164.308(a)(4)(ii)(D)",
      "clause_text": "(1) A patch, update, or upgrade to the configuration of a relevant electronic information system is not available to address a risk identified in the risk analysis under paragraph (a)(2) of this section. (2) The only available patch, update, or upgrade would adversely affect the confidentiality, integrity, or availability of electronic protected health information.",
      "timing_set": "exceptions to the 15 and 30 day periods, documented, with compensating controls",
      "applies_to": "Relevant electronic information systems",
      "severity_basis": "Documented exception",
      "source_url": "https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information",
      "read_date": "2026-11-19",
      "notes": "Proposal only. Exceptions require documentation and compensating controls under proposed (E) and (F).",
      "kind": "primary"
    },
    {
      "framework": "HIPAA Security Rule NPRM (proposed, not in force)",
      "version": "90 FR 898, published 2025-01-06",
      "clause_id": "Proposed 164.308(a)(4)(ii)(B)",
      "clause_text": "Review and test written policies and procedures required by paragraph (a)(4)(ii)(A) of this section at least once every 12 months",
      "timing_set": "12 months (review and test of the patch policy)",
      "applies_to": "Covered entities and business associates",
      "severity_basis": "Not applicable",
      "source_url": "https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information",
      "read_date": "2026-11-19",
      "notes": "Proposal only. Policy review cadence, not a patch deadline.",
      "kind": "primary"
    },
    {
      "framework": "SOC 2 Trust Services Criteria",
      "version": "2017 TSC with revised points of focus 2022",
      "clause_id": "CC7.1",
      "clause_text": "",
      "timing_set": "not read on 2026-11-19",
      "applies_to": "not read",
      "severity_basis": "not read",
      "source_url": "https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022",
      "read_date": "2026-11-19",
      "notes": "The AICPA download page loaded only as a JavaScript app with a free-account download; the criteria text could not be read. Nothing is recorded about the content.",
      "kind": "primary"
    },
    {
      "framework": "SOC 2 Trust Services Criteria",
      "version": "2017 TSC with revised points of focus 2022",
      "clause_id": "CC8.1",
      "clause_text": "",
      "timing_set": "not read on 2026-11-19",
      "applies_to": "not read",
      "severity_basis": "not read",
      "source_url": "https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022",
      "read_date": "2026-11-19",
      "notes": "Same as CC7.1: text not readable on 2026-11-19. Nothing is recorded about the content.",
      "kind": "primary"
    },
    {
      "framework": "CISA BOD 26-04",
      "version": "Issued 2026-06-10",
      "clause_id": "Required action 6 and Table 1: Remediation Timelines",
      "clause_text": "Remediate each vulnerability as quickly as possible and no later than the timelines set forth in Table 1: Remediation Timelines.",
      "timing_set": "3 days (with forensic triage for the highest-risk rows), 14 days, 60 days, or fix on system upgrade, depending on Table 1",
      "applies_to": "Federal agency assets in any federal information system; excludes national security systems; contractors only if the contract says so",
      "severity_basis": "Four inputs: publicly exposed (yes/no), in the KEV Catalog (yes/no), automatable by adversary (yes/no), technical impact (total or partial control). Calendar days. Clock starts at KEV listing or agency identification in the CDM dashboard, whichever comes first.",
      "source_url": "https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk",
      "read_date": "2026-11-19",
      "notes": "Table 1 is an image on the page; values read from the image on 2026-11-19: 16 rows, e.g. exposed + in KEV + automatable + total control = 3 days and forensic triage; not exposed, not in KEV, not automatable = fix on system upgrade. Per the page, CISA reassesses Table 1 once per fiscal year. Phases: I effective immediately, II within 60 days, III within 180 days of issuance.",
      "kind": "primary"
    },
    {
      "framework": "CISA BOD 22-01",
      "version": "Issued 2021-11-03; revoked, superseded by BOD 26-04 (page dated 2026-06-10)",
      "clause_id": "Required actions, due dates",
      "clause_text": "remediate within 6 months for vulnerabilities with a Common Vulnerabilities and Exposures (CVE) ID assigned prior to 2021",
      "timing_set": "2 weeks for KEV entries with a CVE ID assigned 2021 or later; 6 months for CVE IDs assigned before 2021 (historical; directive revoked)",
      "applies_to": "Federal civilian agencies (historical)",
      "severity_basis": "Presence in the CISA KEV Catalog; due date set per catalog entry",
      "source_url": "https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities",
      "read_date": "2026-11-19",
      "notes": "The directive page now reads: This Directive has been revoked. It is superseded by BOD 26-04. The page also says the default timelines may be adjusted in the case of grave risk to the Federal Enterprise. The 2-week and 6-month figures are shown here as history, not as a current rule.",
      "kind": "primary"
    },
    {
      "framework": "CISA BOD 19-02",
      "version": "Issued 2019-04-29; revoked, superseded by BOD 26-04",
      "clause_id": "Required actions",
      "clause_text": "Critical vulnerabilities must be remediated within 15 calendar days of initial detection.",
      "timing_set": "15 calendar days for critical; 30 calendar days for high (historical; directive revoked)",
      "applies_to": "Federal agency internet-accessible systems (historical)",
      "severity_basis": "Critical and high ratings from CISA Cyber Hygiene scanning",
      "source_url": "https://www.cisa.gov/news-events/directives/bod-19-02-vulnerability-remediation-requirements-internet-accessible-systems",
      "read_date": "2026-11-19",
      "notes": "The page states: This Directive has been revoked. It is superseded by BOD 26-04. High text read: High vulnerabilities must be remediated within 30 calendar days of initial detection. The page is marked as archived.",
      "kind": "primary"
    },
    {
      "framework": "CISA KEV Catalog",
      "version": "Catalog page read 2026-11-19; no catalog version number shown",
      "clause_id": "Per-entry Due Date field",
      "clause_text": "Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable.",
      "timing_set": "Per-entry due date; no general rule stated on the catalog page",
      "applies_to": "Federal agencies; others may use the catalog voluntarily",
      "severity_basis": "Entry is in the KEV Catalog",
      "source_url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
      "read_date": "2026-11-19",
      "notes": "The catalog page lists a Due Date for each entry and references BOD 26-04, not BOD 22-01. The only dated item on the page is JSON Schema (updated 09-02-2026), format as printed.",
      "kind": "primary"
    },
    {
      "framework": "FedRAMP Consolidated Rules for 2026, Rev5 path, Vulnerability Detection and Response",
      "version": "Launched 2026-06-24; control mappings updated 2026-10-13",
      "clause_id": "VDR-TFR-PVR (Class A and B)",
      "clause_text": "Providers with Class A Certifications SHOULD partially mitigate vulnerabilities, fully mitigate vulnerabilities, or remediate vulnerabilities to a lower potential agency impact within the timeframes from evaluation shown below",
      "timing_set": "Class A and B, by Potential Agency Impact N-rating 5 to 2: 4 to 96 days when likely exploitable and internet-reachable; 8 to 160 days when likely exploitable and not internet-reachable; 32 to 192 days when not likely exploitable (maximums, SHOULD)",
      "applies_to": "FedRAMP Rev5 certification holders, Classes A and B (the page lists B, C, D for the section and A for this table)",
      "severity_basis": "Potential Agency Impact N-rating (per VER-EVA-EPA), internet reachability, likely exploitability",
      "source_url": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/",
      "read_date": "2026-11-19",
      "notes": "Table values (days) for N-rating 5/4/3/2: 4/8/32/96 (LEV + IRV: likely exploitable, internet-reachable), 8/32/64/160 (LEV + NIRV: likely exploitable, not internet-reachable), 32/64/192/192 (NLEV: not likely exploitable). Column abbreviations (LEV, IRV, NIRV, NLEV) are not expanded on the page; these labels read them from the factors the rule names, internet reachability and likely exploitability. Mandatory for initial and ongoing certification from 2026-12-07; grace period ends 2027-03-07.",
      "kind": "primary"
    },
    {
      "framework": "FedRAMP Consolidated Rules for 2026, Rev5 path, Vulnerability Detection and Response",
      "version": "Launched 2026-06-24",
      "clause_id": "VDR-TFR-PVR (Class C)",
      "clause_text": "Providers with Class C Certifications SHOULD partially mitigate vulnerabilities",
      "timing_set": "Class C, N-rating 5/4/3/2: 2/4/16/48 days (likely exploitable, internet-reachable); 4/8/32/128 days (likely exploitable, not internet-reachable); 16/64/128/192 days (not likely exploitable) (maximums, SHOULD)",
      "applies_to": "FedRAMP Rev5 certification holders, Class C",
      "severity_basis": "Potential Agency Impact N-rating, internet reachability, likely exploitability",
      "source_url": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/",
      "read_date": "2026-11-19",
      "notes": "Quote is the start of the Class C rule as printed; the rest of the sentence follows the Class A wording. Same status dates as the Class A and B row.",
      "kind": "primary"
    },
    {
      "framework": "FedRAMP Consolidated Rules for 2026, Rev5 path, Vulnerability Detection and Response",
      "version": "Launched 2026-06-24",
      "clause_id": "VDR-TFR-PVR (Class D)",
      "clause_text": "Providers with Class D Certifications SHOULD partially mitigate vulnerabilities",
      "timing_set": "Class D, N-rating 5/4/3/2: 12 hours/2 days/8 days/24 days (likely exploitable, internet-reachable); 1/8/16/96 days (likely exploitable, not internet-reachable); 8/32/64/192 days (not likely exploitable) (maximums, SHOULD)",
      "applies_to": "FedRAMP Rev5 certification holders, Class D",
      "severity_basis": "Potential Agency Impact N-rating, internet reachability, likely exploitability",
      "source_url": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/",
      "read_date": "2026-11-19",
      "notes": "Quote is the start of the Class D rule as printed. Class D is the only row that uses hours.",
      "kind": "primary"
    },
    {
      "framework": "FedRAMP Consolidated Rules for 2026, Rev5 path, Vulnerability Detection and Response",
      "version": "Launched 2026-06-24",
      "clause_id": "VDR-TFR-KEV",
      "clause_text": "Providers SHOULD remediate Known Exploited Vulnerabilities according to the due dates in the CISA Known Exploited Vulnerabilities Catalog",
      "timing_set": "Follows the CISA KEV due date for each entry; no separate number set by FedRAMP",
      "applies_to": "FedRAMP certification holders",
      "severity_basis": "KEV listing; applies even if the vulnerability has been fully mitigated",
      "source_url": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/",
      "read_date": "2026-11-19",
      "notes": "The rule continues: as required by CISA Binding Operational Directive (BOD) 26-04 or any successor guidance from CISA.",
      "kind": "primary"
    },
    {
      "framework": "FedRAMP Consolidated Rules for 2026, Rev5 path, Vulnerability Detection and Response",
      "version": "Launched 2026-06-24",
      "clause_id": "VDR-TFR-RMN",
      "clause_text": "Providers SHOULD mitigate or remediate remaining vulnerabilities during routine operations as determined necessary by the provider.",
      "timing_set": "no number set",
      "applies_to": "FedRAMP certification holders",
      "severity_basis": "Vulnerabilities not covered by the PVR table or KEV rule",
      "source_url": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/",
      "read_date": "2026-11-19",
      "notes": "Explicitly leaves timing to the provider.",
      "kind": "primary"
    },
    {
      "framework": "FedRAMP Consolidated Rules for 2026, 20x path, Vulnerability Detection and Response",
      "version": "Launched 2026-06-24",
      "clause_id": "VDR-TFR-KEV (20x page)",
      "clause_text": "Providers SHOULD remediate Known Exploited Vulnerabilities according to the due dates in the CISA Known Exploited Vulnerabilities Catalog",
      "timing_set": "Follows the CISA KEV due date; no separate number on this rule",
      "applies_to": "FedRAMP 20x certification holders; page lists Classes B, C, D",
      "severity_basis": "KEV listing",
      "source_url": "https://www.fedramp.gov/2026/providers/20x/rules/vulnerability-detection-and-response/",
      "read_date": "2026-11-19",
      "notes": "Status on the page: Required, mandated by CISA BOD 26-04; optional adoption from 2026-07-04; initial and ongoing certification 2026-12-07; grace period ends 2027-03-07. The 20x per-class timeframe tables were not compared line by line with the Rev5 tables.",
      "kind": "primary"
    },
    {
      "framework": "FedRAMP legacy documentation (Rev5 playbook, POA&M page)",
      "version": "Legacy section of fedramp.gov; legacy changelog last entry 2026-10-27 (site change only)",
      "clause_id": "Remediation Requirements",
      "clause_text": "FedRAMP requires Critical and High risks to be remediated within 30 days of discovery, Moderate risks within 90 days of discovery, and Low risks within 180 days of discovery.",
      "timing_set": "30 days (critical and high), 90 days (moderate), 180 days (low), from discovery",
      "applies_to": "Legacy FedRAMP Rev5 cloud service providers",
      "severity_basis": "Critical/High, Moderate, Low risk rating",
      "source_url": "https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/",
      "read_date": "2026-11-19",
      "notes": "This text sits in the legacy playbook, not in the 2026 Consolidated Rules. The Continuous Monitoring Strategy Guide itself was not opened by name on 2026-11-19, so the 30/90/180 figures are attributed only to this legacy page. The same page says High-risk VDs must be mitigated to a Moderate level through compensating controls within thirty (30) days. The 2026 VDR page does not mention 30, 90 or 180 days.",
      "kind": "primary"
    },
    {
      "framework": "UK Cyber Essentials, Requirements for IT Infrastructure",
      "version": "v3.3, April 2026, effective 27 April 2026",
      "clause_id": "Security Update Management, Requirements",
      "clause_text": "be updated, including vulnerability fixes, within 14 days of release, where: the update fixes vulnerabilities described by the vendor as critical or high risk",
      "timing_set": "14 days of release",
      "applies_to": "All in-scope software on servers, desktops, laptops, tablets, mobile phones, firewalls, routers, IaaS, PaaS, SaaS",
      "severity_basis": "Vendor-described critical or high risk; or CVSS v3 base score of 7 or above; or no vendor severity details given",
      "source_url": "https://www.ncsc.gov.uk/sites/default/files/2026-11/Cyber-Essentials-Requirements-for-IT-Infrastructure-v3-3.pdf",
      "read_date": "2026-11-19",
      "notes": "Applying all updates within 14 days is recommended but not mandatory. A single update that covers any critical or high issue must be installed within 14 days. The document also requires software to be licensed and supported and removed when unsupported. Text was extracted from the PDF by script; read on 2026-11-19. Note: the PDF has 'April 2026' on its cover and the NCSC resources page lists it as 27 April 2026.",
      "kind": "primary"
    },
    {
      "framework": "EU NIS2 Implementing Regulation 2024/2690",
      "version": "Dated 2024-10-17; published OJ 2024-10-18",
      "clause_id": "Annex, point 6.6.1(a)",
      "clause_text": "security patches are applied within a reasonable time after they become available",
      "timing_set": "no number set (reasonable time)",
      "applies_to": "DNS service providers, TLD registries, cloud computing, data centre, CDN, managed service and managed security service providers, online marketplaces, search engines, social networks, trust service providers",
      "severity_basis": "None stated; 6.6.1 requires alignment with change, vulnerability and risk management",
      "source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402690",
      "read_date": "2026-11-19",
      "notes": "6.6.1(b) to (d) also require testing before production, trusted and integrity-checked sources, and added measures plus accepted residual risk where a patch is unavailable or not applied.",
      "kind": "primary"
    },
    {
      "framework": "EU NIS2 Implementing Regulation 2024/2690",
      "version": "Dated 2024-10-17; published OJ 2024-10-18",
      "clause_id": "Annex, point 6.6.2",
      "clause_text": "the relevant entities may choose not to apply security patches when the disadvantages of applying the security patches outweigh the cybersecurity benefits",
      "timing_set": "no number set; a documented derogation is allowed",
      "applies_to": "Same entity types as point 6.6.1",
      "severity_basis": "Judgment of disadvantages versus cybersecurity benefits, documented and substantiated",
      "source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402690",
      "read_date": "2026-11-19",
      "notes": "The text adds that entities shall duly document and substantiate the reasons for any such decision.",
      "kind": "primary"
    },
    {
      "framework": "EU DORA RTS, Commission Delegated Regulation 2024/1774",
      "version": "Adopted 2024-03-13; published OJ 2024-06-25",
      "clause_id": "Article 10(4)(d)",
      "clause_text": "set deadlines for the installation of software and hardware patches and updates and escalation procedures in case those deadlines cannot be met",
      "timing_set": "no number set; the financial entity sets its own deadlines",
      "applies_to": "Financial entities under Regulation (EU) 2022/2554 (the simplified framework is covered separately)",
      "severity_basis": "None stated in the article; Article 10(2)(f) says to prioritise patches and mitigations for identified vulnerabilities",
      "source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32024R1774",
      "read_date": "2026-11-19",
      "notes": "Article 10(4) also requires automated identification of patches where possible, emergency procedures for patching, and testing and deployment. DORA itself (2022/2554) applies from 2025-01-17.",
      "kind": "primary"
    },
    {
      "framework": "NYDFS 23 NYCRR Part 500",
      "version": "Section 500.5 as amended, effective 2023-11-01 (original 2017-03-01)",
      "clause_id": "500.5(c)",
      "clause_text": "timely remediate vulnerabilities, giving priority to vulnerabilities based on the risk they pose to the covered entity",
      "timing_set": "no number set (timely, risk-prioritized)",
      "applies_to": "Covered entities under Part 500",
      "severity_basis": "Risk the vulnerability poses to the covered entity",
      "source_url": "https://www.law.cornell.edu/regulations/new-york/23-NYCRR-500.5",
      "read_date": "2026-11-19",
      "notes": "Read on the Cornell LII copy of the regulation, not on dfs.ny.gov (the DFS regulations page was reached but the Part 500 text was not read there). 500.5(a) also requires annual penetration testing and automated scans at a frequency set by the risk assessment.",
      "kind": "primary"
    }
  ],
  "unread": [
    "PCI DSS v4.0.1 standard PDF (docs-prv.pcisecuritystandards.org): HTTP 403; listings.pcisecuritystandards.org needs an agreement form; Wayback copy also 403. The standard's own wording of Requirements 6.3.1, 6.3.3 and 11.3.1 is not quoted; the PCI rows come from PCI SSC FAQ 1597 (May 2025) and the PCI SSC blog of 2024-06-11.",
    "CIS Controls v8.1 safeguard text: download is behind a form; the cisecurity.org control 7 page shows only the overview. v8 (August 2023 guide PDF, via learn.cisecurity.org) was read instead. The v8.1 wording of 7.3, 7.4 and 7.7 is unconfirmed.",
    "ISO/IEC 27001:2022 Annex A 8.8: every iso.org page returned HTTP 403 (Cloudflare challenge); standard text is paywalled. Not read.",
    "SOC 2 TSC CC7.1 and CC8.1: AICPA page is a JavaScript app, download needs an account; not read.",
    "HHS HIPAA Security Rule NPRM fact sheet (hhs.gov): HTTP 403. Unified Agenda entry for the rule: not read.",
    "CISA BOD 22-01 itself: not read; the two-week figure is as reported in NIST SP 800-40 Rev. 4.",
    "Australian Essential Eight Maturity Model (cyber.gov.au): page and PDF not readable on 2026-11-19 (curl connection error, WebFetch timed out three times). No row written; 48 hours / two weeks / one month figures and the current version date were not read. The Wayback Machine lists only a 2025-02-28 snapshot, not opened.",
    "FedRAMP Continuous Monitoring Strategy Guide by name: not opened; 30/90/180 days read only on the legacy POA&M playbook page.",
    "FedRAMP 20x per-class timeframe tables: only status and VDR-TFR-KEV confirmed on the 20x page.",
    "dfs.ny.gov Part 500 text: not read; Cornell LII used instead.",
    "IASME question set changes and 'Danzell': term not present in the Requirements v3.3 PDF or the NCSC overview and resources pages; iasme.co.uk returned 403. Not confirmed.",
    "CISA BOD 26-04 Table 1: values read from an image by eye, not from page text.",
    "Australian Essential Eight maturity model: cyber.gov.au did not load by curl or WebFetch on 2026-11-19; no row written, figures not recorded"
  ]
}