← CRA Glossary
Technical Security

Penetration Testing

Penetration testing is a structured, authorised security assessment in which testers simulate real-world attack techniques to identify exploitable vulnerabilities in a product, system, or network before malicious actors discover them. The EU Cyber Resilience Act implicitly requires manufacturers to test their products' security prior to market placement.

Penetration testing is a structured, authorised security assessment in which testers simulate real-world attack techniques to identify exploitable vulnerabilities in a product, system, or network before malicious actors discover them. The EU Cyber Resilience Act implicitly requires manufacturers to test their products' security prior to market placement.

Technical Security

Last updated 17 October 2026

What Is Penetration Testing?

Penetration testing (pen testing) is a controlled security exercise in which a qualified tester - internal or external - attempts to compromise a target system using the same techniques and tools a real attacker would use. The scope, rules of engagement, and target environment are agreed in advance. Pen testing goes beyond automated vulnerability scanning: it involves manual analysis, exploit chaining, and attacker-perspective reasoning to uncover vulnerabilities that automated tools miss. Outputs include a report of confirmed vulnerabilities, exploitation paths, and remediation recommendations. Common methodologies include OWASP, PTES, and OSSTMM.

CRA reference:Annex I Part I, Article 13(1)

Why Penetration Testing Matters Under the CRA

The CRA's essential cybersecurity requirements in Annex I require manufacturers to ensure their products are designed, developed, and produced to achieve an appropriate level of cybersecurity. Conducting penetration testing before market placement is the most credible demonstration that a manufacturer has proactively searched for exploitable weaknesses - not merely assumed their product is secure. For Important Class I and Class II products, conformity assessment bodies and notified bodies will expect evidence of pre-release security testing as part of the technical documentation. Pen test reports form a core part of the technical documentation drawn up under Article 31 and Annex VII.

CRA reference:, Article 31, Annex VII

How Manufacturers Implement Penetration Testing

Manufacturers should embed penetration testing into their secure development lifecycle (SDLC), not treat it as a one-time pre-release activity. Best practice includes: (1) threat modelling early in design to focus testing on the highest-risk attack surfaces; (2) automated vulnerability scanning during CI/CD pipelines; (3) manual penetration testing of release candidates against defined scope before market placement; (4) re-testing after significant architectural changes or when critical third-party components are updated. Test reports, including findings, risk ratings (CVSS), and remediation evidence, should be retained as part of technical documentation for the duration of the product's support period.

CRA reference:(2), Article 13

Common Mistakes

A frequent error is treating a single pre-launch pen test as a permanent proof of security. Threat landscapes evolve and new attack techniques emerge, so periodic re-testing is essential. Manufacturers also commonly scope tests too narrowly - for example, testing only the web interface while leaving firmware, update mechanisms, and cloud APIs untested. Another mistake is failing to remediate and retest: a pen test report that documents critical findings not fixed before market placement provides evidence of non-compliance rather than compliance. Finally, using unqualified internal staff for complex embedded system assessments often yields incomplete coverage.

CRA reference:Annex I Part I

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Is penetration testing mandatory under the EU Cyber Resilience Act?+

The CRA does not mandate penetration testing by name, but Annex I requires manufacturers to ensure their products achieve an appropriate level of cybersecurity. For Important Class I and Class II products, conformity assessment involves demonstrating that security has been actively verified. In practice, penetration testing is the primary method of providing this evidence, and conformity assessment bodies will expect to see documented test results in the technical file.

How often should a manufacturer conduct penetration testing?+

At minimum, manufacturers should conduct a penetration test before the initial market placement of any product and after any major update that changes the attack surface - for example, adding a new network interface, API endpoint, or authentication mechanism. Industry best practice recommends annual testing for products with active internet connectivity. Manufacturers must also respond to newly discovered vulnerabilities in components, which may require targeted retesting.

What should be included in penetration test scope for a CRA-compliant assessment?+

A CRA-relevant penetration test should cover the full attack surface of the product: hardware interfaces (USB, JTAG, UART), firmware and bootloader security, wireless communications (Wi-Fi, BLE, Zigbee), cloud back-end APIs, the software update mechanism, authentication and session management, and network-facing services. Testing only the user-facing web interface while ignoring firmware and hardware attack vectors is a common compliance gap that market surveillance authorities are increasingly scrutinising.

Sector checklists covering Penetration Testing

Industrial Controllers & PLCsIndustrial controllers, PLCs, and SCADA components are default-class products under the CRA, because classification follows core functionality (Article 7(1)) and Annex III lists no industrial control category. They can use Module A internal control (Article 32(1)). These products have long operational lifetimes (10–20+ years), network connectivity, and significant safety implications. These facts raise the risk that the Article 13(2) risk assessment must address. Article 14 reporting applies from 11 September 2026, and the conformity obligations apply from 11 December 2027.Medical DevicesMedical devices regulated under the EU Medical Device Regulation (MDR) or In Vitro Diagnostic Regulation (IVDR) are generally excluded from the CRA. However, software products used in healthcare that are not classified as medical devices under MDR may fall within CRA scope. Manufacturers should carefully verify their product's regulatory classification.Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Penetration Testing fits into your complete CRA compliance programme.

View checklists →