← CRA Glossary
CVD & Vulnerability Management

Bug Bounty Programme

A bug bounty programme is a formal scheme in which a manufacturer or organisation offers financial rewards to external security researchers who discover and responsibly disclose security vulnerabilities in their products or systems. Bug bounty programmes are a supplementary CVD mechanism - they add financial incentive to an underlying CVD policy - but are not themselves a substitute for the CRA's mandatory vulnerability disclosure requirements.

A bug bounty programme is a formal scheme in which a manufacturer or organisation offers financial rewards to external security researchers who discover and responsibly disclose security vulnerabilities in their products or systems. Bug bounty programmes are a supplementary CVD mechanism - they add financial incentive to an underlying CVD policy - but are not themselves a substitute for the CRA's mandatory vulnerability disclosure requirements.

CVD & Vulnerability Management

Last updated 17 October 2026

What Is a Bug Bounty Programme?

A bug bounty programme is a structured initiative in which a manufacturer publicly invites external security researchers to find and report security vulnerabilities in defined products or systems, in exchange for a financial reward (the 'bounty'). Bounties are typically scaled by severity: critical vulnerabilities command the highest rewards, while informational or low-severity findings may receive smaller payments or acknowledgement only. Bug bounty programmes operate within a scope that defines which products, services, and vulnerability types are eligible, and they include the same core components as a CVD programme - a reporting channel, a triage process, safe harbour terms, and a disclosure timeline - with financial incentives layered on top.

CRA reference:, Recital 63

Bug Bounty Programmes and CRA Compliance

Bug bounty programmes are complementary to CRA compliance but are not a substitute for the mandatory CVD policy required by . The CRA's requirement is for a coordinated vulnerability disclosure process - a mechanism through which any researcher or user can report a vulnerability and receive a timely response. A bug bounty programme can satisfy this requirement if it includes all the elements of a CVD policy (published contact, scope, safe harbour, timelines, and response commitment), but a bug bounty programme that offers rewards without a defined response process, or that discourages disclosure of out-of-scope findings, is not a compliant CVD policy. CRA compliance requires the CVD channel to be open and unconditional.

CRA reference:, Recital 63

How Manufacturers Run Effective Bug Bounty Programmes

An effective bug bounty programme is built on a functioning CVD foundation. Key design elements include: a clearly defined scope identifying which products and systems are in scope; a severity-banded bounty table with transparent payout criteria; explicit safe harbour language protecting good-faith researchers from legal action; a defined response SLA (e.g. 5-day acknowledgement, 30-day triage, 90-day resolution target); a clear disclosure policy - most programmes use coordinated disclosure with a fixed embargo period; and a researcher communication commitment ensuring reporters receive regular updates. Manufacturers should also consider whether a public or private programme is appropriate: public programmes attract more researchers but also more noise; private programmes (invite-only) provide higher signal-to-noise ratios.

CRA reference:

Common Mistakes

The most damaging bug bounty mistake is creating a programme that is too narrow in scope - excluding cloud backends, mobile applications, or specific product lines - and then refusing to process vulnerability reports that fall outside scope. Researchers who discover critical vulnerabilities outside scope have nowhere to go and may resort to public disclosure. Any product with digital elements subject to the CRA must have a CVD channel that accepts reports on all covered products, regardless of bug bounty scope. A second error is slow payment and opaque decision-making, which damages the manufacturer's reputation with the research community and reduces future report quality.

CRA reference:

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 a bug bounty programme required by the EU Cyber Resilience Act?+

No. The CRA requires a coordinated vulnerability disclosure policy and process (), but does not require financial rewards for reporters. A bug bounty programme is optional and supplementary. Manufacturers who want to incentivise high-quality research and attract experienced security researchers may choose to run a bug bounty programme, but CRA compliance does not mandate it. The baseline requirement is a functioning, open CVD channel with defined response commitments.

Can a bug bounty programme replace a CVD policy for CRA compliance?+

Only if the bug bounty programme satisfies all the elements of a compliant CVD policy: a published vulnerability reporting channel, defined response timelines, explicit safe harbour protection for good-faith researchers, and a commitment to address reported vulnerabilities. A bug bounty programme that only covers certain products in scope, or that discourages reporting of vulnerabilities that fall outside the bounty criteria, does not provide the unconditional CVD channel required by the CRA. Manufacturers should maintain a separate, universal CVD policy alongside any bug bounty programme.

What is the difference between a public and a private bug bounty programme?+

A public bug bounty programme is open to any researcher who agrees to the terms - it maximises the number of researchers looking at the product and the breadth of coverage. A private programme invites selected researchers only, resulting in fewer but often higher-quality reports from more experienced researchers. For CRA compliance purposes, either structure can satisfy the CVD requirement if all the required policy elements are in place. Many manufacturers run a private programme as a precursor to a public launch, using private phase findings to harden the product before broader researcher access.

Sector checklists covering Bug Bounty Programme

Smart Home DevicesSmart home devices, such as thermostats, smart speakers, lighting controllers and home security cameras, are among the most common products with digital elements in scope for the CRA. Thermostats and lighting controllers are default class, and Module A internal control is open to them (Article 32(1)). A smart speaker with a general purpose virtual assistant is Important Class I (Annex III, point 16). A home security camera, smart lock, baby monitor or alarm system is Important Class I (Annex III, point 17). So is a hub or software that centrally controls these security products.Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).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 Bug Bounty Programme fits into your complete CRA compliance programme.

View checklists →