Coordinated Vulnerability Disclosure Policy for Hardware Manufacturers
Build a usable hardware vulnerability disclosure policy with intake owners, safe testing boundaries and a security.txt example.
By CenitiaUpdated
Fact-checked against the law as of Reviewed by Vladimír Vician on How we check
A hardware vulnerability disclosure policy needs a working reporting channel, an accountable response owner and clear boundaries for safe research. Publishing a policy without monitoring the inbox leaves researchers with a document and your team without a reliable intake process.
The CVD policy template is a starting point for a small manufacturer. Its contacts, time targets and legal wording are placeholders. Replace them only with arrangements your team can actually maintain.
Decide what the policy covers
List the supported product families, firmware branches, mobile applications and manufacturer controlled backend services. Explain how to report an issue in a retired product or third party component. Avoid silently rejecting a report merely because the researcher used a different channel.
Separate the public policy from the internal incident procedure. A researcher needs contact details, requested information, permitted activity and an explanation of coordination. Your responders additionally need access to release owners, product identifiers, legal support and the reporting decision process.
The Cyber Resilience Act (Regulation (EU) 2024/2847) turns this into a product requirement for products placed on the market from 11 December 2027:
- Part II of Annex I requires the manufacturer to put in place and enforce a policy on coordinated vulnerability disclosure (point 5) and to provide a contact address for reporting vulnerabilities (point 6).
- Article 13(17) requires a single point of contact that users can easily identify. It must let users choose their preferred means of communication and must not be limited to automated tools.
- Annex II, point 2, requires the information supplied with the product to give that single point of contact and to say where the coordinated vulnerability disclosure policy can be found.
Article 14 reporting is a separate obligation with its own triggers and clocks. Receiving a researcher email does not by itself meet a reporting trigger. Use the text of Regulation (EU) 2024/2847 (Cyber Resilience Act) when defining those responsibilities.
Make the intake usable
Ask for product model, firmware version, affected interface, reproduction steps, observed impact and relevant logs. Tell researchers to remove credentials and personal information. Provide a way to arrange secure transfer if the evidence is sensitive.
Do not require a complete exploit as a condition of acknowledging a report. A reproducible observation can be enough to begin triage. If evidence is incomplete, ask focused questions: “Which firmware image did you test?” is more useful than “Please provide all details”.
An acknowledgement target is an operational commitment, not a legal definition of safety. Choose it after testing staff availability, weekends and leave cover. Publish an escalation route for unanswered reports and rehearse it from an external account.
Add security.txt without treating it as the policy
RFC 9116 defines security.txt, a machine-parsable file that tells researchers where to report vulnerabilities. The example below deliberately uses a reserved domain and cannot receive reports.
Contact: mailto:security@example.com
Expires: 2027-10-01T00:00:00Z
Preferred-Languages: en
Canonical: https://example.com/.well-known/security.txt
Policy: https://example.com/security-policy
Serve your actual file over HTTPS at /.well-known/security.txt. Contact and Expires are the two required fields, and Expires may appear only once. RFC 9116 recommends an Expires value less than a year in the future. The date in the example is an illustration: set your own, and assign someone to renew the file before it passes. Validate the deployed response and the linked policy. Publishing this example unchanged would create a broken reporting channel.
The RFC describes the file format. The file does not grant or deny permission to test, and it does not provide a complete disclosure agreement, guarantee safe harbour or decide your regulatory reporting obligations.
Define research boundaries carefully
Say whether testing is permitted on researcher owned devices, a dedicated test environment or other specifically authorised systems. Describe activities that can harm customers: availability testing against production, accessing someone else's data, persistent access and physical interference.
Have counsel review any legal assurance you intend to offer. A manufacturer cannot promise protection against every third party claim or jurisdiction. Never imply that a short template grants unlimited permission to test customer deployments.
Also explain compensation accurately. If there is no bounty programme, say so. Researchers should not need to guess whether acknowledgement, credit or payment is offered.
Walk one report through the process
In this fictional exercise, a researcher reports that an undocumented debug service is reachable on gateway firmware 2.4.0. The intake owner acknowledges receipt, creates a restricted ticket and asks for the exact image hash and network setup. Engineering checks whether the service is present in released builds. Security evaluates exploitability and affected installations.
The team records the evidence available at each time, the disclosure contact and the next update date. It separately checks whether any mandatory reporting trigger is met. No fictional exercise ticket is sent to a regulator.
When the issue is fixed, the team coordinates an advisory that identifies affected and corrected releases, practical mitigations and credits agreed with the researcher. Keep sensitive details restricted until the disclosure decision is made; record the reason for any delay rather than imposing an indefinite embargo.
Prove the process works
Before publishing the policy, send a harmless test message, check backup access, rehearse an out of hours escalation and confirm the mailbox renewal owner. Keep the exercise record with the policy version.
The gateway report in this article is invented. The article does not report results from a real intake channel or from research on any device.
CRA applicability and timing
Most Cyber Resilience Act obligations apply to products placed on the market from 11 December 2027; a product placed on the market earlier becomes subject to them only if it is substantially modified from that date (Article 69(2)). Article 14 reporting is already a current duty: it has applied since 11 September 2026 to every in-scope product, including products placed on the market before 11 December 2027 (Article 69(3)), and it continues after the support period ends. Check the product’s scope, your role and the transitional provisions. See the Commission page for manufacturers, the Commission page on reporting and the Commission guidance on the application of the Cyber Resilience Act (C/2026/6013).
Continue reading
Related guides
tutorial
Secure OTA Firmware Updates and the Evidence to Keep
Plan secure OTA test evidence for signatures, interrupted updates, recovery and downgrade controls against the CRA update requirements, with a small host demo.
6 min read
guide
CRA Scope for Connected Devices and Their Cloud Backends
Apply the CRA remote data processing tests to connected device architectures and record external cloud dependencies separately.
5 min read
guide
When a Firmware Update Needs New CE Evidence or Retesting
Assess firmware changes against existing CE evidence, notified body notification duties and the CRA substantial modification rules with a change impact record.
6 min read
tutorial
CycloneDX VEX for Embedded Firmware: a Worked Synthetic Example
Write a scoped CycloneDX VEX decision for embedded firmware: an unresolved in_triage record, a synthetic not_affected record with justification, and reassessment triggers.
5 min read
Put this into practice
Free tools & references
- CRA Readiness CheckerScore your product against the Cyber Resilience Act essential requirements.Open tool →
- EU Directive SelectorDescribe your product and find which EU directives and regulations apply.Open tool →
New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.