{
 "page": "https://insights.moraph.com/compare/pen-test-and-vuln-scan-requirements",
 "csv": "https://insights.moraph.com/compare/pen-test-and-vuln-scan-requirements.csv",
 "publisher": "Moraph",
 "license": "https://creativecommons.org/licenses/by/4.0/",
 "license_note": "License: CC BY 4.0. Underlying government texts are public domain or under their own terms.",
 "attribution": "Moraph Insights, https://insights.moraph.com/compare/pen-test-and-vuln-scan-requirements",
 "slug": "pen-test-and-vuln-scan-requirements",
 "title": "Penetration testing and vulnerability scanning requirements compared",
 "sector": "Cross-sector",
 "lens": "Security & Resilience",
 "in_short": "The FTC Safeguards Rule requires annual penetration testing and vulnerability assessments at least every six months unless the institution has effective continuous monitoring, and NYDFS Part 500 requires penetration testing at least annually by a qualified internal or external party. The proposed HIPAA Security Rule update would require scans at least every six months and penetration testing at least every 12 months, but it is not final as of 2026-11-14. IRS Publication 1075 sets vulnerability scans every 30 days and penetration testing every 3 years for the FTI environment. CISA BOD 26-04, which replaced BOD 22-01 on June 10, 2026, sets remediation deadlines of 3, 14 or 60 calendar days, or the next system upgrade, for federal civilian agencies, depending on exposure, KEV listing, automatability and technical impact.",
 "method": "We read each rule in its official source: the eCFR for 16 CFR 314.4, the NYDFS copy of the amended Part 500, the Federal Register text of the proposed HIPAA Security Rule update, the FedRAMP Consolidated Rules for 2026 rule pages on fedramp.gov, CISA's web text of BOD 26-04 and its Table 1 of remediation timelines (published on the page as an image, which we opened), and the IRS's current Publication 1075. We checked the Federal Register on 2026-11-14 for a final HIPAA Security Rule and found none. Each cell was first checked on 2026-11-13 and re-checked on 2026-11-14 against the same sources. Where a rule says nothing about tester independence or reporting, the cell says so. PCI DSS is left out (see Omitted). This table explains the rules; it is not legal advice.",
 "published": "2026-11-13",
 "last_reviewed": "2026-11-14",
 "columns": [
  {
   "id": "rule",
   "label": "Rule"
  },
  {
   "id": "frequency",
   "label": "Frequency"
  },
  {
   "id": "scope",
   "label": "Scope"
  },
  {
   "id": "independence",
   "label": "Who tests"
  },
  {
   "id": "evidence",
   "label": "Evidence or report"
  }
 ],
 "rows": [
  {
   "id": "ftc-safeguards",
   "cells": {
    "rule": {
     "text": "FTC Safeguards Rule, 16 CFR 314.4(d)(2)",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "frequency": {
     "text": "Continuous monitoring, or else annual penetration testing and vulnerability assessments at least every six months; vulnerability assessments are also due whenever there are material changes to operations or business arrangements and when circumstances may materially affect the security program",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Information systems; each year's penetration test is based on relevant risks identified in the risk assessment",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "independence": {
     "text": "Not specified in 314.4(d)",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "evidence": {
     "text": "The Qualified Individual reports in writing at least annually to the board, including results of testing (314.4(i))",
     "source": "s1",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "nydfs-500-5",
   "cells": {
    "rule": {
     "text": "NYDFS Cybersecurity Regulation, 23 NYCRR 500.5",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "frequency": {
     "text": "Penetration testing at least annually; automated scans at a frequency set by the risk assessment and promptly after material system changes",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Information systems, tested from both inside and outside their boundaries; manual review of systems the automated scans do not cover",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "independence": {
     "text": "A qualified internal or external party",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "evidence": {
     "text": "Annual certification of material compliance, or acknowledgment of noncompliance, filed by April 15 and signed by the highest-ranking executive and the CISO (500.17(b))",
     "source": "s2",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "hipaa-proposed",
   "cells": {
    "rule": {
     "text": "HIPAA Security Rule update, proposed 45 CFR 164.312(h)",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "frequency": {
     "text": "Proposed, as of 2026-11-14: automated vulnerability scans at least every six months and penetration testing at least every 12 months, or more often if the risk analysis calls for it. No final rule in the Federal Register as of 2026-11-14",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Relevant electronic information systems of covered entities and business associates; the scanning tool itself is reviewed and tested at least every 12 months",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "independence": {
     "text": "Penetration testing by a qualified person: someone with appropriate knowledge of and experience with generally accepted cybersecurity principles and methods",
     "source": "s3",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "fedramp-rev5",
   "cells": {
    "rule": {
     "text": "FedRAMP Consolidated Rules for 2026 (Rev5); required for initial and ongoing certification from January 1, 2027, optional from July 4, 2026",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "frequency": {
     "text": "An independent assessment at least once per year (must for Class B, C and D; may for Class A). For Rev5 Class B, it must include CA-08 penetration testing.",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "The whole cloud service offering; vulnerability detection must use techniques such as assessment, scanning, bug bounties and penetration testing. Recommended detection on resources not likely to drift: at least every 6 months for Class A and B, at least monthly for Class C and D",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "independence": {
     "text": "A FedRAMP Recognized independent assessment service, or FedRAMP itself; assessment by FedRAMP is limited to cloud services FedRAMP explicitly prioritizes",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "evidence": {
     "text": "Initial certification at Class B, C or D needs a fresh independent assessment completed within the previous 3 months; providers stay accountable for the accuracy and completeness of everything in the FedRAMP Certification Package, including what third parties such as independent assessors supply",
     "source": "s6",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "cisa-bod-26-04",
   "cells": {
    "rule": {
     "text": "CISA Binding Operational Directive 26-04 (June 10, 2026); supersedes and revokes BOD 19-02 and BOD 22-01",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "frequency": {
     "text": "Remediate within 3, 14 or 60 calendar days, or at the next system upgrade, depending on public exposure, KEV listing, automatability and technical impact; some 3-day cases also need forensic triage. Phase III, due within 180 days of issuance, requires remediation within these timelines",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Agency assets in federal information systems of Federal Civilian Executive Branch agencies, including third-party and FedRAMP-hosted systems; contractors only where the contract directs",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "independence": {
     "text": "CISA runs Cyber Hygiene scanning; agencies keep it running and remove its source IP addresses from blocklists",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "evidence": {
     "text": "Automated KEV status reporting through the CDM Dashboard, or manual bi-weekly reports; quarterly attestation of publicly exposed IP addresses and domain names",
     "source": "s7",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "irs-pub-1075",
   "cells": {
    "rule": {
     "text": "IRS Publication 1075 (Rev. 11-2021), controls RA-5 and CA-8",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "frequency": {
     "text": "Vulnerability scans every 30 days, before a new system joins the network, to confirm remediation and when new vulnerabilities are reported; penetration testing every 3 years",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Systems and hosted applications that handle federal tax information (FTI); penetration testing on the FTI environment",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "independence": {
     "text": "Testers with demonstrable skills and experience; risk assessments guide the level of independence required",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "evidence": {
     "text": "Analyze scan reports (RA-5); vulnerability scanning policy and procedures are listed among evidentiary documents for the Safeguard Security Report",
     "source": "s8",
     "checked": "2026-11-14"
    }
   }
  }
 ],
 "sources": [
  {
   "id": "s1",
   "title": "16 CFR 314.4(d) and (i), Standards for Safeguarding Customer Information",
   "publisher": "Federal Trade Commission",
   "url": "https://www.ecfr.gov/current/title-16/section-314.4",
   "checked": "2026-11-14"
  },
  {
   "id": "s2",
   "title": "23 NYCRR 500.5 and 500.17, Second Amendment text (DFS copy; DFS notes it is not an official version)",
   "publisher": "New York State Department of Financial Services",
   "url": "https://www.dfs.ny.gov/system/files/documents/2026/10/NYCRR-part-500-Cybersecurity-Regulation_1.pdf",
   "checked": "2026-11-14"
  },
  {
   "id": "s3",
   "title": "HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule (90 FR 898), proposed 164.312(h)",
   "publisher": "U.S. Department of Health and Human Services",
   "url": "https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information",
   "checked": "2026-11-14"
  },
  {
   "id": "s4",
   "title": "FedRAMP Consolidated Rules for 2026, Rev5 Independent Verification and Validation rules (IVV-CSO-FIA, IVV-CSF-AIA)",
   "publisher": "FedRAMP (U.S. General Services Administration)",
   "url": "https://www.fedramp.gov/2026/providers/rev5/rules/independent-verification-and-validation/",
   "checked": "2026-11-14"
  },
  {
   "id": "s5",
   "title": "FedRAMP Consolidated Rules for 2026, Rev5 Vulnerability Detection and Response rules (VDR-CSO-DET, VDR-TFR-PCD)",
   "publisher": "FedRAMP (U.S. General Services Administration)",
   "url": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/",
   "checked": "2026-11-14"
  },
  {
   "id": "s6",
   "title": "FedRAMP Consolidated Rules for 2026, Rev5 FedRAMP Certification rules (FRC-APP-FIA)",
   "publisher": "FedRAMP (U.S. General Services Administration)",
   "url": "https://www.fedramp.gov/2026/providers/rev5/rules/fedramp-certification/",
   "checked": "2026-11-14"
  },
  {
   "id": "s7",
   "title": "BOD 26-04: Prioritizing Security Updates Based on Risk, including Table 1: Remediation Timelines",
   "publisher": "Cybersecurity and Infrastructure Security Agency",
   "url": "https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk",
   "checked": "2026-11-14"
  },
  {
   "id": "s8",
   "title": "IRS Publication 1075 (Rev. 11-2021), Tax Information Security Guidelines for Federal, State and Local Agencies, RA-5, CA-8 and Safeguard Security Report evidentiary documentation",
   "publisher": "Internal Revenue Service",
   "url": "https://www.irs.gov/pub/irs-pdf/p1075.pdf",
   "checked": "2026-11-14"
  }
 ],
 "notes": [
  "The FedRAMP detection timeframes are written as SHOULD; the annual independent assessment is a MUST for Class B, C and D.",
  "NYDFS publishes the amended Part 500 on its website with a note that its copy is not an official version."
 ],
 "omitted": [
  {
   "where": "hipaa-proposed/evidence",
   "reason": "No reporting or evidence duty tied to the proposed scanning and penetration testing provisions was confirmed in the proposed rule text."
  },
  {
   "where": "pci-dss/all",
   "reason": "PCI DSS is left out: the PCI Security Standards Council's Terms and Conditions (https://www.pcisecuritystandards.org/terms_and_conditions/), as read on 2026-11-14, permit use of site content for personal, non-commercial purposes only and bar use for any non-personal purpose without a separate written agreement."
  },
  {
   "where": "cisa-bod-22-01/all",
   "reason": "CISA revoked BOD 22-01 (and BOD 19-02) on June 10, 2026; its successor, BOD 26-04, is shown instead."
  }
 ]
}
