Guide, read 12 Nov 2026

# Regulators want evidence that controls work, and validation records supply it

**The short answer:** Five rules ask regulated companies for proof that security controls work: DORA, applying since 17 Jan 2025 with threat-led penetration testing; NIS2; the SEC cybersecurity reporting rule of 26 Jul 2023; PCI DSS 4.0 requirement 11, with quarterly external scans; and NYDFS Part 500.5, with annual penetration testing. CTEM validation records feed all five.

[Stage Coverage Map](https://ctemvendors.com/stage-coverage-map/) | [All guides](https://ctemvendors.com/guides/)

## DORA and threat-led penetration testing

The Digital Operational Resilience Act, Regulation (EU) 2022/2554, entered into force on 16 Jan 2023 and has applied since 17 Jan 2025, according to ESMA. It requires financial entities to run a digital operational resilience testing program covering a range of tests, including advanced testing, and the European supervisory authorities issued regulatory technical standards on threat-led penetration testing (TLPT) under its Article 26(11).

The ECB's TIBER-EU framework, revised in its 2025 edition to align with those standards, shows the scale of a TLPT. It runs tests on live production systems, keeps the blue team unaware, allocates at least 12 weeks to active red team testing, and treats 3-year intervals as the norm. Each test ends in a test summary report, a remediation plan and an attestation.

CTEM does not replace TLPT. It fills the years between tests: per-cycle validation of the same critical or important functions, and a record showing the remediation plan's items were fixed and re-tested.

## NIS2 risk-management measures

NIS2, Directive (EU) 2022/2555, entered into force in January 2023 and Member States had until 17 Oct 2024 to transpose it. The European Commission says it imposes a risk management approach with a minimum list of basic security elements, makes top management accountable for non-compliance with those measures, and requires an early warning within 24 hours of becoming aware of a significant incident. Fines for essential entities reach a maximum of at least EUR 10,000,000 or 2% of worldwide annual turnover, whichever is higher.

For digital infrastructure and ICT service providers, Commission Implementing Regulation (EU) 2024/2690 of 17 Oct 2024 sets the technical requirements, and ENISA's implementation guidance gives examples of evidence for each. A CTEM program's scope statements, validation results and closed-item re-tests are the kind of evidence that guidance describes. National transposition differs, so check the local law.

## The SEC cybersecurity reporting rule

The SEC adopted its rule on 26 Jul 2023. Form 8-K Item 1.05 filings are generally due four business days after a registrant determines a cybersecurity incident is material. Regulation S-K Item 106 requires the annual Form 10-K to describe processes for assessing, identifying and managing material cybersecurity risks, board oversight, and management's role, for fiscal years ending on or after 15 Dec 2023.

The rule asks for a description of process, not test results. A CTEM program makes that description accurate: the five stages are the process, the cycle records show it runs, and the [quarterly board page](https://ctemvendors.com/guides/reporting-exposure-to-a-board/) shows oversight.

## PCI DSS 4.0 requirement 11

PCI DSS v4.0's future-dated requirements took effect on 31 Mar 2025. The PCI Security Standards Council says v4.0.1, a limited revision, changed neither that date nor the set of requirements: none added, none deleted. Within requirement 11, requirement 11.3.2 requires evidence of passing external scans by an Approved Scanning Vendor at least once every three months.

Map the cardholder data environment as a CTEM scope. Discovery and scanning evidence supports 11.3; validation results on the same scope show whether controls hold between the formal tests the standard requires. Keep the formal tests as the standard defines them.

Segmentation matters here more than anywhere. If validation shows a path from outside the cardholder data environment into it, that result goes to the top of the mobilization list and into the assessor's file with its re-test.

## NYDFS Part 500

New York's Part 500.5, as amended by the Second Amendment, requires covered entities to conduct penetration testing from inside and outside system boundaries at least annually by a qualified party, automated scans at a frequency set by the risk assessment and promptly after material system changes, and timely remediation prioritized by risk. Part 500.13 requires an asset inventory with owner, location, classification, support expiration and recovery time objective for each asset.

A CTEM program's scope statements reuse the 500.13 fields, and its re-test records show the remediation 500.5 asks for.

## One evidence trail for several rules

Many regulated companies fall under two or more of these rules at once: a European bank with a US listing and a New York license, for example. Running separate testing for each rule produces duplicate work and inconsistent findings. A CTEM program can keep one trail: scope statements that name the regulated functions, one validation log with dated results, and one register of fixes, mitigations and accepted risks. Each regulator's report then draws from the same records, and the formal tests each rule names are scoped from them.

## Evidence map

The table pairs each rule's ask with the CTEM record that supports it. It is a planning aid, not legal advice.

| Rule | What it asks for | CTEM record that supports it |
|---|---|---|
| DORA (TLPT) | Advanced testing of critical or important functions; remediation plan | Per-cycle validation on the same functions; re-tests of plan items |
| NIS2 | Risk-management measures with management accountability | Scope statements, validation results, closed items |
| SEC rule (Item 106) | Description of risk processes and board oversight | Cycle records; quarterly board decisions |
| PCI DSS 4.0 req. 11 | Scans and testing of the cardholder data environment | CDE as a scope; scan and validation evidence |
| NYDFS 500.5, 500.13 | Annual penetration test, risk-based scans, remediation, asset inventory | Inventory with owners; validation and re-test logs |

## Where CTEM evidence falls short

Automated validation does not satisfy a rule that names a specific test. A TIBER-EU test needs an external threat intelligence provider and red team testers who meet the framework's procurement requirements; PCI DSS needs ASV scans and testing as the standard defines them; NYDFS needs penetration testing by a qualified party. Validation records support those tests and fill the time between them.

Evidence also has to be dated and attributable. Keep each validation result with its date, technique and control, and each closed item with its re-test. The [validation guide](https://ctemvendors.com/guides/what-validation-proves/) covers what a result can claim, and the [situations pages](https://ctemvendors.com/situations/) show stage coverage for regulated buyers.

## Sources

- [https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/digital-operational-resilience-act-dora](https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/digital-operational-resilience-act-dora), read 12 Nov 2026
- [https://www.ecb.europa.eu/paym/cyber-resilience/tiber-eu/html/index.en.html](https://www.ecb.europa.eu/paym/cyber-resilience/tiber-eu/html/index.en.html), read 12 Nov 2026
- [https://www.ecb.europa.eu/pub/pdf/other/ecb.tiber_eu_framework_2025~b32eff9a10.en.pdf](https://www.ecb.europa.eu/pub/pdf/other/ecb.tiber_eu_framework_2025~b32eff9a10.en.pdf), read 12 Nov 2026
- [https://digital-strategy.ec.europa.eu/en/policies/nis2-directive](https://digital-strategy.ec.europa.eu/en/policies/nis2-directive), read 12 Nov 2026
- [https://digital-strategy.ec.europa.eu/en/faqs/directive-measures-high-common-level-cybersecurity-across-union-nis2-directive-faqs](https://digital-strategy.ec.europa.eu/en/faqs/directive-measures-high-common-level-cybersecurity-across-union-nis2-directive-faqs), read 12 Nov 2026
- [https://www.enisa.europa.eu/publications/nis2-technical-implementation-guidance](https://www.enisa.europa.eu/publications/nis2-technical-implementation-guidance), read 12 Nov 2026
- [https://www.sec.gov/newsroom/press-releases/2023-139](https://www.sec.gov/newsroom/press-releases/2023-139), read 12 Nov 2026
- [https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1](https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1), read 12 Nov 2026
- [https://blog.pcisecuritystandards.org/resource-guide-vulnerability-scans-and-approved-scanning-vendors](https://blog.pcisecuritystandards.org/resource-guide-vulnerability-scans-and-approved-scanning-vendors), read 12 Nov 2026
- [https://www.dfs.ny.gov/system/files/documents/2023/12/rf23_nycrr_part_500_amend02_20231101.pdf](https://www.dfs.ny.gov/system/files/documents/2023/12/rf23_nycrr_part_500_amend02_20231101.pdf), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://ctemvendors.com/guides/ctem-for-regulated-companies/
