EU Cyber Resilience Act Guide for Gaming Hardware Manufacturers
Default class for most products, including consoles, handhelds and peripherals. Important Class I for a gaming router (Annex III, point 12) or a network adapter (Annex III, point 10)
Gaming hardware manufacturers producing gaming consoles, handheld gaming devices, gaming peripherals with network connectivity, and gaming-specific networking hardware for the EU market must comply with the EU Cyber Resilience Act. Article 14 incident reporting applies from 11 September 2026, and the remaining obligations apply from 11 December 2027. Gaming consoles with online services, account management, and payment processing present a substantial attack surface - and the large, active user base makes vulnerabilities in gaming platforms high-value targets for both financial fraud and account compromise.
Last updated 26 October 2026
CRA Scope and Classification for Gaming Products
Gaming consoles, handheld gaming devices, gaming PCs (when sold as integrated systems), gaming-focused routers and network adapters, streaming sticks for gaming, and gaming peripherals with embedded connectivity (wireless controllers with companion firmware, gaming headsets with companion apps) are products with digital elements within CRA scope.
Classification follows core functionality (Article 7(1)). Annex III lists no gaming category, so consoles, handheld gaming devices, gaming PCs and peripherals are default class. Online services, account management, payment processing and a large user base do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment has to address. An operating system or a browser integrated in a console does not make the console an important product (Article 7(1)). A gaming router is Important Class I (Annex III, point 12), and a network adapter, such as a Wi-Fi or Ethernet adapter, is Important Class I (Annex III, point 10). Wired peripherals with firmware, such as USB controllers and USB headsets, are also in scope, because USB is a direct physical data connection (Article 2(1)). Wireless peripherals with companion apps and OTA firmware updates are within scope. Manufacturers should audit their product portfolio and document the classification for each product line. The gaming peripheral category is large and varied - each SKU warrants individual assessment.
Technical Security Requirements for Gaming Hardware
Gaming hardware manufacturers - particularly console makers - are already among the more security-sophisticated consumer electronics companies, with active security research programmes and bug bounty programmes. CRA Annex I formalises obligations that leading manufacturers largely already satisfy, while establishing a floor for the entire sector:
- Secure boot chain: Console firmware must implement a verified boot process that prevents execution of unauthorised firmware. Bootloader vulnerabilities are a persistent focus of gaming hardware security research.
- Account and payment security: Account authentication must support strong credentials. Payment processing must use current cryptographic standards and must not expose cardholder data.
- Authenticated updates: Console system software updates must be cryptographically authenticated. The update mechanism must resist downgrade attacks that could restore known-vulnerable firmware versions.
- Sandboxing and isolation: Game code execution must be isolated from system-level processes. Exploits via malicious game content should not be able to escape the gaming sandbox.
- SBOM maintenance: Console operating systems are complex embedded Linux or custom RTOS environments with extensive open-source component libraries requiring SBOM documentation.
CVD Policy and Article 13 for Gaming Manufacturers
Major gaming console manufacturers already operate active security research programmes and bug bounty programmes that are substantially aligned with Article 13 requirements. For these vendors, CRA compliance is largely a matter of formalising existing practices and ensuring full Annex I alignment.
- A publicly accessible CVD policy covering all CRA-scoped products
- A formal submission channel accessible to security researchers
- Defined acknowledgement and response timelines
- A commitment to CSAF advisory publication for resolved vulnerabilities
Gaming manufacturers should also ensure that their CVD policy covers companion software (driver packages, companion apps, cloud services) in addition to hardware firmware. Many gaming peripheral vulnerabilities are found in companion software rather than in hardware firmware directly. CVD Portal can complement an existing bug bounty programme by providing standards-compliant CVD infrastructure and CSAF advisory generation.
Article 14 Incident Reporting for Gaming Products
Gaming platforms are high-value targets for exploitation due to the financial value of gaming accounts (in-game currency, digital game libraries, stored payment methods). Article 14 requires manufacturers to notify ENISA within 24 hours of confirming active exploitation of a product vulnerability.
- Active exploitation of a console firmware vulnerability used for persistent account compromise
- Mass exploitation of a companion app vulnerability used for credential theft
- Exploitation of a peripheral firmware vulnerability to execute malicious code on a user's PC
Gaming manufacturers with large online user populations face a particular challenge: exploitation of gaming hardware vulnerabilities often occurs at scale simultaneously, requiring both regulatory notification and mass consumer communication simultaneously. Manufacturers should maintain consumer communication channels (in-console notifications, email, social media) that can reach users with security-relevant information within hours of a confirmed incident.
Conformity Assessment for Gaming Hardware
Default-class consoles and peripherals can use Module A internal control (Article 32(1)). A default-class manufacturer can also choose Module B plus Module C or Module H with a notified body (Article 32(1)). A gaming router or a network adapter is Important Class I. It can use Module A only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level at least substantial (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so today such a product needs a notified body (Module B plus Module C, or Module H).
- Secure boot chain implementation and anti-downgrade mechanisms
- Account and payment security architecture
- Update mechanism cryptographic authentication
- Sandbox isolation of game execution environments
- CVD policy and bug bounty programme operational status
Manufacturers already holding Common Criteria evaluations for security elements of their console (e.g., secure enclave, TPM-equivalent components) can use these as supporting evidence. The technical depth of a gaming console security assessment is significant and needs relevant embedded security expertise, so manufacturers should plan the assessment early.
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
Are mobile gaming accessories (controllers for smartphones) subject to the CRA?+
Mobile gaming accessories with Bluetooth or USB connectivity and embedded firmware - particularly those with companion apps and OTA firmware update capability - are products with digital elements within CRA scope. A simple passive cable controller adapter without embedded software is likely outside scope. A Bluetooth gaming controller with companion app and firmware update capability is within scope. The class follows the core functionality of the product (Article 7(1)). A gaming controller matches no Annex III category, so it is default class and can use Module A internal control (Article 32(1)).
How do we handle CRA compliance for game cartridges or optical discs with embedded software?+
Game distribution media (cartridges, optical discs) containing game software are products with digital elements when placed on the EU market as commercial products. However, game software published by third-party game developers is subject to the CRA obligations of the game developer, not the console manufacturer (whose hardware is a separate product). Console manufacturers must ensure that their platform's execution environment satisfies Annex I requirements - particularly secure execution and sandbox isolation. Game developers distributing game software as standalone products in the EU market should assess their CRA obligations for their software products independently.
Are retro gaming products or re-releases of classic consoles subject to the CRA?+
Re-released retro gaming consoles with modern connectivity (HDMI, WiFi, USB) and any software components are products with digital elements subject to CRA when placed on the EU market as new products. The fact that the games are decades old does not affect the classification of the hardware. The CRA obligations apply to the hardware and software as placed on market - including any online features, companion app connectivity, and update mechanisms. Manufacturers of retro consoles should assess their products' network connectivity and software components and apply the appropriate CRA classification and conformity assessment process.
Compliance checklists for your products
Guides for related sectors
Free CRA tools
This industry guide is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.
Need a CVD policy template for Gaming Hardware Manufacturers?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.