Penetration Testing Requirements in the United States: FTC, NYDFS, HIPAA, PCI DSS, CMMC and FedRAMP
Published by Zero Hunt, an autonomous AI red team on an on-premise appliance running private AI: automated penetration testing for networks and infrastructure, black-box or gray-box, with a human approving every step that matters.
Short definition
There is no single US law that requires penetration testing. The duty comes from the rule that governs your sector: the FTC Safeguards Rule, NYDFS Part 500, PCI DSS, CMMC Level 3 and FedRAMP name the test and a 12-month floor; HIPAA, the banking guidelines and SEC rules leave type and frequency to your risk assessment.
Why this matters now
Most US organizations answer to more than one of these regimes, and the texts differ on exactly the points that decide the budget: whether a penetration test is named, how often, and who may run it. The FTC Safeguards Rule covers thousands of non-bank financial companies that rarely think of themselves as regulated, and the HIPAA proposal that would add an annual test is still not final in November 2026. Knowing which rule says what lets one testing program serve all of them.
Key points
- ▸FTC Safeguards Rule 16 CFR 314.4(d)(2): annual penetration testing and vulnerability assessments at least every six months, unless you run effective continuous monitoring; applies since 9 June 2023, with an exemption below 5,000 consumers.
- ▸NYDFS 23 NYCRR 500.5: penetration testing from inside and outside the boundaries at least annually by a qualified internal or external party, plus risk-based automated scans.
- ▸HIPAA: the current Security Rule requires a risk analysis and periodic evaluation, not a named test. The January 2025 proposal (annual pentest, six-monthly scans) is not final; the latest agenda lists final action for July 2027.
- ▸PCI DSS v4.0.1 11.4: internal and external penetration tests at least every 12 months and after significant changes; quarterly scans under 11.3, external ones by an ASV.
- ▸CMMC Level 3 requires penetration testing at least annually; Level 2 requires periodic scans (at most yearly). Phase 2 third-party assessments are suspended since 13 July 2026.
- ▸FedRAMP requires a 3PAO penetration test before authorization and at least every 12 months after; SEC rules and Regulation S-P require programs and disclosure, not a named test.
The short answer: which US rules name a penetration test
The United States has no horizontal cybersecurity law like the EU's NIS2. Whether you must run a penetration test, how often, and who may run it depends on the rule that governs your sector or your contracts. The texts fall into three groups:
- Rules that name the test and a 12-month floor: the FTC Safeguards Rule for non-bank financial institutions, NYDFS Part 500 for New York-regulated financial services, PCI DSS for anyone who stores, processes or transmits card data, CMMC Level 3 for the most sensitive defense contracts, and FedRAMP for cloud services sold to federal agencies.
- Rules that require testing but leave the type and frequency to your risk assessment: the HIPAA Security Rule, the federal banking agencies' Interagency Guidelines and the FFIEC handbook, CMMC Level 2.
- Rules that require a program or a disclosure, not a test: the SEC cybersecurity disclosure rules and the 2024 Regulation S-P amendments. California's cybersecurity audit regulation asks the auditor to assess penetration testing where applicable.
Voluntary attestations sit outside this list: SOC 2 has no penetration testing requirement, although customers often ask for one. CISA's BOD 26-04 sets patch deadlines for federal civilian agencies and does not mention penetration testing. The requirements by regulation guide compares the US rules with the EU, UK, Middle East and Asia-Pacific.
US penetration testing rules at a glance
| Rule | Penetration test | Scans / vulnerability assessment | Who may test | |
|---|---|---|---|---|
| Non-bank financial institutions | FTC Safeguards Rule, 16 CFR 314.4(d)(2) | Annual, scoped by the risk assessment (unless effective continuous monitoring) | At least every six months and after material changes | Not specified; qualified personnel, internal or a service provider |
| Banks (federal supervision) | Interagency Guidelines, e.g. 12 CFR 364 App. B | Regular testing of key controls; type and frequency by risk assessment | By risk assessment | Independent third parties or independent staff |
| NY-regulated financial services | 23 NYCRR 500.5 | At least annually, from inside and outside the boundaries | Risk-based frequency, and after material changes | Qualified internal or external party |
| Healthcare (in force) | HIPAA 45 CFR 164.308(a)(1), (a)(8) | Not named; risk analysis and periodic evaluation | Not named | Not specified |
| Healthcare (proposed) | HIPAA NPRM, 90 FR 898 | At least every 12 months (not final) | At least every six months (not final) | A qualified person |
| Card payments | PCI DSS v4.0.1, 11.3 and 11.4 | Internal and external every 12 months and after significant change; segmentation every 12 months (6 for service providers) | Quarterly internal; quarterly external by an ASV | Qualified and organizationally independent; ASV for external scans |
| Defense contractors | CMMC Level 2 / Level 3, 32 CFR 170 | Level 3: at least annually or after significant security changes | Level 2: periodically, at most every 12 months | Self-assessment during the Phase 2 suspension |
| Cloud services for agencies | FedRAMP Penetration Test Guidance v3.0 | Before authorization, then at least every 12 months | Under the continuous monitoring program | 3PAO (JAB P-ATO) or assessor designated by the agency AO |
| Public companies, broker-dealers, advisers | SEC Item 106, Item 1.05, Regulation S-P | Not named | Not named | Item 106 asks whether third-party assessors are used |
| California businesses above thresholds | CPPA regulations §7120-7123 | Audit assesses pentesting if applicable | Audit assesses internal and external scans if applicable | Qualified, objective, independent auditor (audit, not test) |
Rule
- Non-bank financial institutions
- FTC Safeguards Rule, 16 CFR 314.4(d)(2)
- Banks (federal supervision)
- Interagency Guidelines, e.g. 12 CFR 364 App. B
- NY-regulated financial services
- 23 NYCRR 500.5
- Healthcare (in force)
- HIPAA 45 CFR 164.308(a)(1), (a)(8)
- Healthcare (proposed)
- HIPAA NPRM, 90 FR 898
- Card payments
- PCI DSS v4.0.1, 11.3 and 11.4
- Defense contractors
- CMMC Level 2 / Level 3, 32 CFR 170
- Cloud services for agencies
- FedRAMP Penetration Test Guidance v3.0
- Public companies, broker-dealers, advisers
- SEC Item 106, Item 1.05, Regulation S-P
- California businesses above thresholds
- CPPA regulations §7120-7123
Penetration test
- Non-bank financial institutions
- Annual, scoped by the risk assessment (unless effective continuous monitoring)
- Banks (federal supervision)
- Regular testing of key controls; type and frequency by risk assessment
- NY-regulated financial services
- At least annually, from inside and outside the boundaries
- Healthcare (in force)
- Not named; risk analysis and periodic evaluation
- Healthcare (proposed)
- At least every 12 months (not final)
- Card payments
- Internal and external every 12 months and after significant change; segmentation every 12 months (6 for service providers)
- Defense contractors
- Level 3: at least annually or after significant security changes
- Cloud services for agencies
- Before authorization, then at least every 12 months
- Public companies, broker-dealers, advisers
- Not named
- California businesses above thresholds
- Audit assesses pentesting if applicable
Scans / vulnerability assessment
- Non-bank financial institutions
- At least every six months and after material changes
- Banks (federal supervision)
- By risk assessment
- NY-regulated financial services
- Risk-based frequency, and after material changes
- Healthcare (in force)
- Not named
- Healthcare (proposed)
- At least every six months (not final)
- Card payments
- Quarterly internal; quarterly external by an ASV
- Defense contractors
- Level 2: periodically, at most every 12 months
- Cloud services for agencies
- Under the continuous monitoring program
- Public companies, broker-dealers, advisers
- Not named
- California businesses above thresholds
- Audit assesses internal and external scans if applicable
Who may test
- Non-bank financial institutions
- Not specified; qualified personnel, internal or a service provider
- Banks (federal supervision)
- Independent third parties or independent staff
- NY-regulated financial services
- Qualified internal or external party
- Healthcare (in force)
- Not specified
- Healthcare (proposed)
- A qualified person
- Card payments
- Qualified and organizationally independent; ASV for external scans
- Defense contractors
- Self-assessment during the Phase 2 suspension
- Cloud services for agencies
- 3PAO (JAB P-ATO) or assessor designated by the agency AO
- Public companies, broker-dealers, advisers
- Item 106 asks whether third-party assessors are used
- California businesses above thresholds
- Qualified, objective, independent auditor (audit, not test)
Summarized from the texts as read on 20 November 2026. The HIPAA row marked proposed is not law. Check the official text and your regulator's guidance before relying on it.
FTC Safeguards Rule: who it covers and what §314.4(d)(2) says
The Safeguards Rule, 16 CFR Part 314, implements the Gramm-Leach-Bliley Act (GLBA) for the financial institutions under the Federal Trade Commission's jurisdiction, which in practice means non-bank companies whose business is financial in nature. The FTC's guidance lists mortgage lenders and brokers, payday lenders, finance companies, account servicers, check cashers, wire transferors, collection agencies, credit counselors and other financial advisors, tax preparation firms, non-federally insured credit unions and investment advisers that are not required to register with the SEC.
The testing duty is in §314.4(d):
- (d)(1): regularly test or otherwise monitor the effectiveness of the safeguards' key controls, systems and procedures, including those that detect actual and attempted attacks on, or intrusions into, information systems.
- (d)(2): for information systems, the monitoring and testing must include continuous monitoring or periodic penetration testing and vulnerability assessments. Absent effective continuous monitoring or other systems that detect, on an ongoing basis, changes that may create vulnerabilities, you must conduct:
- Annual penetration testing of your information systems, determined each year based on relevant identified risks in accordance with the risk assessment;
- Vulnerability assessments, including systemic scans or reviews reasonably designed to identify publicly known vulnerabilities, based on the risk assessment, at least every six months, whenever there are material changes to your operations or business arrangements, and whenever circumstances you know or have reason to know may have a material impact on your information security program.
The rule defines penetration testing in §314.2 as a test methodology in which assessors attempt to circumvent or defeat the security features of an information system by attempting penetration of databases or controls from outside or inside your information systems. An information system includes any system that contains customer information or is connected to one, explicitly including industrial controls, telephone switching and environmental control systems.
The paragraph came in with the 2021 amendments (86 FR 70272). Its compliance date was delayed once, and §314.4(d)(2) has applied since 9 June 2023 (87 FR 71509).
FTC Safeguards Rule: continuous monitoring or annual testing
Paragraph (d)(2) gives two routes, and the choice should be written down, because it decides what evidence you will need.
Route 1, effective continuous monitoring. The rule does not define the term. The preamble to the 2021 final rule recalls the explanation given in the proposal: any system that allows real-time, ongoing monitoring of an information system's security, including monitoring for security threats, misconfigured systems and other vulnerabilities. The word that matters in the rule is effective: monitoring that sees threats but not configuration changes and new vulnerabilities across the systems holding customer information is hard to present as a substitute for testing.
Route 2, periodic testing. An annual penetration test and vulnerability assessments every six months, plus the event-driven assessments after material changes. Two details are easy to miss:
- The annual test is scoped by the risk assessment each year. The rule does not ask you to test every system every year, but the written risk assessment required by §314.4(b)(1) has to explain the scope you chose.
- The six-month interval is a floor. Material changes to operations or business arrangements, such as an acquisition, a new loan servicing platform or a move to a new hosting provider, trigger another assessment.
Many institutions combine the two: ongoing scanning and monitoring for the six-month and event-driven duties, and a penetration test at least once a year. Whatever you choose, §314.4(g) requires you to evaluate and adjust the program in light of the results of that testing and monitoring.
FTC Safeguards Rule: who may test, the board report and the exemption
- Who may test. The rule does not require an external or certified tester. The definition speaks of assessors, and §314.4(e)(2) requires qualified information security personnel employed by you, an affiliate or a service provider. The Qualified Individual who oversees the program (§314.4(a)) can also be employed by an affiliate or service provider, but you keep responsibility for compliance.
- What the board sees. Under §314.4(i) the Qualified Individual reports in writing, regularly and at least annually, to the board or equivalent governing body. The report covers the overall status of the program and material matters, explicitly including the results of testing, security events and management's responses.
- Service providers. §314.4(f) requires you to select capable providers, bind them by contract to appropriate safeguards and periodically assess them based on the risk they present. A testing vendor that handles customer information falls under that rule too.
- Small institutions. §314.6 exempts institutions that maintain customer information on fewer than 5,000 consumers from the written risk assessment, from §314.4(d)(2), from the written incident response plan and from the annual board report. Paragraph (d)(1), regular testing or monitoring, still applies.
- When it goes wrong. Since 13 May 2024, §314.4(j) requires notice to the FTC as soon as possible, and no later than 30 days after discovery, of a notification event involving the information of at least 500 consumers. Testing and remediation records are what show that the safeguards existed before the event.
Banks and other institutions supervised by the federal banking agencies follow the Interagency Guidelines instead; broker-dealers and registered investment advisers follow the SEC's Regulation S-P.
Banks: the Interagency Guidelines and the FFIEC
For banks, GLBA safeguards are set by the federal banking agencies' Interagency Guidelines Establishing Information Security Standards. The FDIC version, 12 CFR Part 364, Appendix B, paragraph III.C.3, requires the institution to regularly test the key controls, systems and procedures of its information security program. The frequency and nature of the tests are determined by the institution's risk assessment, and tests should be conducted or reviewed by independent third parties or staff independent of those that develop or maintain the security programs.
The FFIEC IT Examination Handbook, Information Security booklet (September 2016), is what examiners read alongside it. It describes penetration tests as real-world attacks selected and conducted by the testers, says that their frequency and scope should be a function of the assurance the institution needs and be determined by the risk assessment, and allows them to be performed internally by independent groups, internally by the business unit, or by an independent third party, with management deciding the level of independence.
The FFIEC Cybersecurity Assessment Tool (CAT) is gone: the Federal Reserve's SR 24-7 announced that it would no longer be updated and would be removed from the FFIEC website on 31 August 2025. The agencies pointed to NIST CSF 2.0, CISA's Cybersecurity Performance Goals, the Cyber Risk Institute Profile and the CIS Controls, and do not endorse any particular self-assessment tool. Examinations remain risk-focused, so the testing evidence is what carries the conversation. See the US financial services page.
NYDFS Part 500: §500.5
New York's cybersecurity regulation, 23 NYCRR Part 500, covers banks, insurers and other entities licensed by the Department of Financial Services, whether or not they are also supervised federally. As amended by the Second Amendment (effective 1 November 2023), §500.5(a) requires at a minimum:
- Penetration testing of information systems from both inside and outside the information systems' boundaries, by a qualified internal or external party, at least annually;
- Automated scans of information systems and a manual review of systems not covered by them, at a frequency determined by the risk assessment and promptly after any material system changes.
§500.5(b) and (c) add a monitoring process for new vulnerabilities and timely, risk-prioritized remediation. The amended scanning duty in (a)(2) applied from 1 May 2025.
The rest of the regulation turns testing into signed evidence: the annual notice of compliance is due by 15 April for the prior calendar year (§500.17(b)), and the records supporting it are kept for five years. Class A companies must also conduct independent audits of their cybersecurity program (§500.2(c)). Entities under the §500.19(a) limited exemption (fewer than 20 employees and contractors, less than $7.5 million in revenue, or less than $15 million in assets) are exempt from §500.5.
Consent orders, exemptions and the evidence file are covered in the NYDFS Part 500 playbook.
HIPAA: what applies today and where the 2025 proposal stands
The HIPAA Security Rule in force does not mention penetration testing or vulnerability scanning. It requires an accurate and thorough risk analysis (45 CFR 164.308(a)(1)(ii)(A)) and a periodic technical and nontechnical evaluation (164.308(a)(8)), and testing is how most covered entities and business associates make those defensible.
The HHS proposal published on 6 January 2025 (90 FR 898, RIN 0945-AA22) would add a new §164.312(h): automated vulnerability scans at least once every six months or more often if the risk analysis requires, and penetration testing by a qualified person at least once every 12 months.
Status on 20 November 2026: still a proposal. The Federal Register lists no final rule under the RIN, only the January 2025 proposal. The current Unified Agenda on reginfo.gov lists the rulemaking under long-term actions, with final action projected for July 2027. It has not been withdrawn either. A program described to auditors as “HIPAA-required annual penetration testing” overstates the law; a program that already meets the proposed floors is a reasonable reading of the risk analysis duty.
The clause-by-clause reading, the OCR enforcement record and the 405(d) practices are in the HIPAA penetration testing guide and on the US healthcare page.
PCI DSS v4.0.1: Requirements 11.3 and 11.4
PCI DSS is a contractual standard, not a federal law, but it binds every US merchant and service provider that stores, processes or transmits card data through their acquirer and the card brands. v4.0.1 (June 2024) is the only active version; it added no requirements, and the future-dated requirements of v4.x have been mandatory since 31 March 2025.
- 11.3.1 and 11.3.2: internal vulnerability scans at least once every three months, and external scans at least once every three months by a PCI SSC Approved Scanning Vendor (ASV), plus scans after significant changes.
- 11.4.2 and 11.4.3: internal and external penetration tests at least once every 12 months and after any significant infrastructure or application upgrade or change, by a qualified internal resource or qualified external third party with organizational independence. The tester does not have to be a QSA or ASV.
- 11.4.4: exploitable findings are corrected and the test is repeated to verify the corrections.
- 11.4.5 and 11.4.6: segmentation controls are tested every 12 months, or every six months for service providers.
The requirement-by-requirement reading and the assessor's evidence list are in the PCI DSS 11.4 guide.
CMMC and NIST SP 800-171: defense contractors
Contractors handling Controlled Unclassified Information (CUI) must implement NIST SP 800-171 Rev 2, which CMMC Level 2 assesses. Two requirements carry the testing duty: 3.11.2, scan for vulnerabilities periodically and when new vulnerabilities affecting the systems are identified, and 3.12.1, periodically assess the security controls. In the CMMC program rule, 32 CFR Part 170, “periodically” means at a regular interval set by the organization that may not exceed one year.
CMMC Level 3 adds the enhanced requirements of NIST SP 800-172, including CA.L3-3.12.1e: penetration testing at least annually or when significant security changes are made, leveraging automated scanning tools and ad hoc tests by subject matter experts.
Status: on 13 July 2026 the Department of War suspended the November 2026 transition to Phase 2. During the suspension, solicitations may only require CMMC Level 1 (Self) or Level 2 (Self); Level 2 (C3PAO) and Level 3 (DIBCAC) assessments may not be designated. The NIST SP 800-171 requirements, self-assessments and DFARS 252.204-7012 remain in effect. Assessment evidence and POA&M limits are in the CMMC evidence playbook and on the defense industrial base page.
FedRAMP: cloud services sold to federal agencies
FedRAMP is the most prescriptive US regime on who tests and what they test. The FedRAMP Penetration Test Guidance, version 3.0 (30 June 2022), applies to Rev. 5 authorizations:
- When: a penetration test is part of every initial authorization and must be completed no more than six months before the Security Assessment Report is submitted. In continuous monitoring, testing must be repeated at least every 12 months, unless an authorizing body approves otherwise with documented rationale.
- Who: a FedRAMP-recognized Third Party Assessment Organization (3PAO) is required for JAB P-ATO systems; for an agency ATO the assessor may be any organization designated by the agency's authorizing official. The 3PAO must show penetration testing proficiency, and the team lead must hold an industry-recognized penetration testing credential.
- What: six mandatory attack vectors: external to corporate (including phishing of system administrators), external to the CSP target system, tenant to CSP management system, tenant to tenant, mobile application to target system, and client-side applications or agents to target system.
FedRAMP is changing its process. Under FedRAMP 20x, now in its third phase, FedRAMP says it will stop accepting new Rev. 5 certifications on 11 June 2027. Cloud providers should check the current 20x requirements before planning the next cycle.
SEC rules and Regulation S-P: programs and disclosure, not a named test
- Cybersecurity disclosure (2023). Public companies disclose material cybersecurity incidents on Form 8-K Item 1.05, generally within four business days after determining materiality, and describe each year in the 10-K (Regulation S-K Item 106) their processes for assessing, identifying and managing material cybersecurity risks. Item 106 asks, among other things, whether the company engages assessors, consultants, auditors or other third parties in those processes. No test is named, but the description must match what the company can show. See the Form 8-K Item 1.05 playbook.
- Regulation S-P amendments (2024). Broker-dealers, investment companies, registered investment advisers and transfer agents must keep a written incident response program reasonably designed to detect, respond to and recover from unauthorized access to customer information, and notify affected individuals within 30 days. Larger entities had 18 months and smaller ones 24 months from publication on 3 June 2024 to comply. The amendments do not mention penetration testing.
For these firms, testing is not a line item in the rule but the most direct evidence that the safeguards and the incident response program work.
State law: California's cybersecurity audit
Most state data security laws ask for reasonable security without naming tests. Two state regimes stand out. New York is covered above through NYDFS Part 500.
California: the California Privacy Protection Agency's regulations, approved on 22 September 2025 and in effect since 1 January 2026, require an annual cybersecurity audit from businesses whose processing presents significant risk to consumers' security (§7120 ties this to the CCPA's applicability thresholds, including businesses that in the preceding year processed the personal information of 250,000 or more consumers or households, or the sensitive personal information of 50,000 or more consumers). The audit must be performed by a qualified, objective, independent auditor (§7122). Among the components the audit must assess, if applicable, §7123 lists internal and external vulnerability scans, penetration testing, and vulnerability disclosure and reporting.
The first audit reports are due by 1 April 2028 for businesses with 2026 revenue above $100 million, by 1 April 2029 for those between $50 and $100 million, and by 1 April 2030 for the rest. The rule audits whether testing exists and works; it does not itself set a test frequency.
We did not find another state law that names penetration testing. This page does not attempt a 50-state survey; check the rules of the states where you hold residents' data.
One testing program for several US rules
- List the rules that apply to each legal entity: FTC or banking agencies for GLBA, NYDFS if licensed in New York, PCI DSS for the card environment, HIPAA for ePHI, CMMC or FedRAMP for federal work, SEC if listed or registered, California if above the thresholds.
- Set the floor from the strictest rule: an internal and external penetration test at least every 12 months and after significant changes, and vulnerability scans at least every six months (quarterly where PCI DSS applies), with segmentation tests if you rely on segmentation.
- Write the scope into the risk assessment each year, as the FTC rule and NYDFS expect, and record why any system is out of scope.
- Decide who tests what: an ASV for PCI external scans, a 3PAO for FedRAMP, a qualified and independent tester for PCI, NYDFS and the banking guidelines; internal teams can cover the rest where independence is documented.
- Re-test every fix and keep the proof: PCI 11.4.4 requires it, and every other regime reads remediation as the evidence that testing worked.
- Feed the board report: the FTC rule's annual report, the NYDFS certification and the 10-K description all draw on the same testing record.
- Keep records for the longest period that applies to you, such as five years for the NYDFS certification and six years for HIPAA documentation.
Where Zero Hunt fits
Zero Hunt is an autonomous AI red team on an on-premise appliance. It runs black-box and gray-box penetration tests of networks and infrastructure from inside your environment, on its own models with no third-party LLM, so no customer data leaves your network. Campaigns run once or on a schedule, so the six-month assessments, the event-driven tests after material changes and the re-tests can follow the floors above. Operators choose one of five autonomy levels that decide which intrusive steps wait for human approval.
Findings are mapped to 34 compliance frameworks, including the US ones on this page: GLBA / FTC Safeguards Rule, NYDFS Part 500, HIPAA Security Rule, PCI DSS, CMMC, NIST SP 800-53, SEC cybersecurity disclosure rules, CCPA / CPRA cybersecurity audit, SOX IT controls and SOC 2. Every attack attempt is recorded as signed, hash-chained evidence, and exported reports are ECDSA-signed.
What it is not: Zero Hunt is not a PCI QSA or ASV, not a FedRAMP 3PAO and not FedRAMP authorized, not a CMMC C3PAO, and not the independent auditor California requires. Where a rule asks for an ASV, a 3PAO or an independent assessor, Zero Hunt supports continuous internal testing and the evidence between those engagements; it does not replace them.
Questions
Is penetration testing required by law in the United States? Not by one general law. It is required by sector rules: the FTC Safeguards Rule (annually, unless you run effective continuous monitoring), NYDFS Part 500 (annually), CMMC Level 3 (annually) and FedRAMP (before authorization and annually), and contractually by PCI DSS (annually and after significant changes).
Does the FTC Safeguards Rule require an annual penetration test? Yes, under 16 CFR 314.4(d)(2), unless you have effective continuous monitoring or other systems that detect changes creating vulnerabilities on an ongoing basis. Vulnerability assessments are due at least every six months and after material changes. Institutions with customer information on fewer than 5,000 consumers are exempt from that paragraph.
Does the penetration tester have to be external? Usually not. The FTC rule, NYDFS and PCI DSS accept qualified internal testers; PCI DSS and the banking guidelines require independence from the systems tested. External parties are required for PCI external scans (an ASV) and for FedRAMP JAB authorizations (a 3PAO).
Is the HIPAA annual penetration test requirement in force? No. It is part of the January 2025 proposal, which is not final. The latest Unified Agenda lists it under long-term actions with final action projected for July 2027.
Does continuous automated testing replace the annual penetration test? Under the FTC rule, effective continuous monitoring is an alternative to the periodic route. Under NYDFS, PCI DSS, CMMC Level 3 and FedRAMP, the annual test by a qualified or designated tester stays; continuous testing adds evidence between those tests.
Sources
- 16 CFR Part 314, Standards for Safeguarding Customer Information (eCFR)
- Final rule, 86 FR 70272, 9 December 2021 (Federal Register)
- Delay of effective date to 9 June 2023, 87 FR 71509 (Federal Register)
- FTC extends deadline by six months for compliance with some changes to financial data security rule, 15 November 2022 (FTC)
- FTC Safeguards Rule: What Your Business Needs to Know (FTC)
- 12 CFR Part 364, Appendix B, Interagency Guidelines Establishing Information Security Standards (eCFR)
- SR 24-7: Sunset of the FFIEC Cybersecurity Assessment Tool (Federal Reserve)
- 23 NYCRR Part 500 as amended by the Second Amendment (NYDFS, PDF)
- HIPAA Security Rule proposed rule, 90 FR 898, 6 January 2025 (Federal Register)
- RIN 0945-AA22, current Unified Agenda entry (reginfo.gov)
- Just Published: PCI DSS v4.0.1, 11 June 2024 (PCI SSC blog)
- 32 CFR Part 170, CMMC Program (eCFR)
- Implementing the suspension of CMMC Phase II, 13 July 2026 (DoW CIO, archived copy)
- NIST SP 800-171 Rev. 2 (NIST, PDF)
- FedRAMP Penetration Test Guidance v3.0, 30 June 2022 (archived copy of fedramp.gov)
- FedRAMP 20x (FedRAMP)
- SEC adopts rules on cybersecurity disclosure, 26 July 2023 (SEC)
- 17 CFR 229.106, Item 106 Cybersecurity (eCFR)
- SEC adopts amendments to Regulation S-P, 16 May 2024 (SEC)
- Regulation S-P final rule, 89 FR 47688, 3 June 2024 (Federal Register)
- CCPA updates, cybersecurity audits, risk assessments and ADMT regulations (CPPA)
- Approved regulations text (CPPA, PDF)
- BOD 26-04: Prioritizing Security Updates Based on Risk (CISA)
Goes deeper
- Worldwide guide: pentest requirements by regulation →
- Playbook: NYDFS Part 500 penetration testing (§500.5) →
- HIPAA penetration testing requirements →
- PCI DSS 11.4 penetration testing requirements →
- CMMC assessment evidence playbook →
- SOC 2 penetration testing requirement →
- SEC Form 8-K Item 1.05 playbook →
- CISA BOD 26-04 risk-based patch deadlines →
- Industry: US financial services (NYDFS Part 500, GLBA, PCI DSS) →
- Industry: US healthcare (HIPAA Security Rule) →
- Industry: US defense industrial base (CMMC) →
- Continuous penetration testing →
- Book a 30-minute testing readiness call →
Want this against your environment?
Book a 30-minute scoping call — we will map this directly to your current compliance scope and threat profile.