Comparison tables

Penetration testing and vulnerability scanning requirements compared

Penetration testing and vulnerability scanning requirements compared Each number links to the cell's source. Cells checked unless the cell shows another date.
RuleFrequencyScopeWho testsEvidence or report
FTC Safeguards Rule, 16 CFR 314.4(d)(2)1FrequencyContinuous 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 program1ScopeInformation systems; each year's penetration test is based on relevant risks identified in the risk assessment1Who testsNot specified in 314.4(d)1Evidence or reportThe Qualified Individual reports in writing at least annually to the board, including results of testing (314.4(i))1
NYDFS Cybersecurity Regulation, 23 NYCRR 500.52FrequencyPenetration testing at least annually; automated scans at a frequency set by the risk assessment and promptly after material system changes2ScopeInformation systems, tested from both inside and outside their boundaries; manual review of systems the automated scans do not cover2Who testsA qualified internal or external party2Evidence or reportAnnual 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))2
HIPAA Security Rule update, proposed 45 CFR 164.312(h)3FrequencyProposed, 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-143ScopeRelevant electronic information systems of covered entities and business associates; the scanning tool itself is reviewed and tested at least every 12 months3Who testsPenetration testing by a qualified person: someone with appropriate knowledge of and experience with generally accepted cybersecurity principles and methods3Evidence or reportNot confirmed (see Method)
FedRAMP Consolidated Rules for 2026 (Rev5); required for initial and ongoing certification from January 1, 2027, optional from July 4, 20264FrequencyAn 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.4ScopeThe 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 D5Who testsA FedRAMP Recognized independent assessment service, or FedRAMP itself; assessment by FedRAMP is limited to cloud services FedRAMP explicitly prioritizes4Evidence or reportInitial 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 supply6
CISA Binding Operational Directive 26-04 (June 10, 2026); supersedes and revokes BOD 19-02 and BOD 22-017FrequencyRemediate 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 timelines7ScopeAgency assets in federal information systems of Federal Civilian Executive Branch agencies, including third-party and FedRAMP-hosted systems; contractors only where the contract directs7Who testsCISA runs Cyber Hygiene scanning; agencies keep it running and remove its source IP addresses from blocklists7Evidence or reportAutomated KEV status reporting through the CDM Dashboard, or manual bi-weekly reports; quarterly attestation of publicly exposed IP addresses and domain names7
IRS Publication 1075 (Rev. 11-2021), controls RA-5 and CA-88FrequencyVulnerability scans every 30 days, before a new system joins the network, to confirm remediation and when new vulnerabilities are reported; penetration testing every 3 years8ScopeSystems and hosted applications that handle federal tax information (FTI); penetration testing on the FTI environment8Who testsTesters with demonstrable skills and experience; risk assessments guide the level of independence required8Evidence or reportAnalyze scan reports (RA-5); vulnerability scanning policy and procedures are listed among evidentiary documents for the Safeguard Security Report8

Get the data: CSV · JSON

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.

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.

Omitted

What was left out, and why.

  • HIPAA Security Rule update, proposed 45 CFR 164.312(h) · Evidence or report: No reporting or evidence duty tied to the proposed scanning and penetration testing provisions was confirmed in the proposed rule text.
  • A row left out: 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.
  • A row left out: CISA revoked BOD 22-01 (and BOD 19-02) on June 10, 2026; its successor, BOD 26-04, is shown instead.

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.

Sources

  1. Federal Trade Commission. 16 CFR 314.4(d) and (i), Standards for Safeguarding Customer Information. Checked .
  2. New York State Department of Financial Services. 23 NYCRR 500.5 and 500.17, Second Amendment text (DFS copy; DFS notes it is not an official version). Checked .
  3. U.S. Department of Health and Human Services. HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule (90 FR 898), proposed 164.312(h). Checked .
  4. FedRAMP (U.S. General Services Administration). FedRAMP Consolidated Rules for 2026, Rev5 Independent Verification and Validation rules (IVV-CSO-FIA, IVV-CSF-AIA). Checked .
  5. FedRAMP (U.S. General Services Administration). FedRAMP Consolidated Rules for 2026, Rev5 Vulnerability Detection and Response rules (VDR-CSO-DET, VDR-TFR-PCD). Checked .
  6. FedRAMP (U.S. General Services Administration). FedRAMP Consolidated Rules for 2026, Rev5 FedRAMP Certification rules (FRC-APP-FIA). Checked .
  7. Cybersecurity and Infrastructure Security Agency. BOD 26-04: Prioritizing Security Updates Based on Risk, including Table 1: Remediation Timelines. Checked .
  8. Internal Revenue Service. 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. Checked .

How we source and check every fact: Editorial standards · Corrections

Last reviewed .

Spotted an error? Tell us and we will check it and correct the table where needed.