Vulnerability disclosure policy template for product teams

Hephaestus Technology8 min read

A vulnerability disclosure policy template gives security researchers and customers a clear, public way to report security flaws in your product, and tells them what you will do in return. For product companies selling in the EU it is no longer optional: the Cyber Resilience Act requires manufacturers to "put in place and enforce a policy on coordinated vulnerability disclosure", and the UK's product security regime already requires connected-product makers to publish how to report issues. Below is a ten-section template you can copy, with a short note on why each section is there.

Key takeaways

  • The CRA requires a coordinated vulnerability disclosure policy and a contact address for reports.
  • The UK has required consumer connectable products to publish how to report security issues since 29 April 2024.
  • A good policy states scope, how to report, response timelines, safe-harbour terms and how you will disclose fixes.
  • Publish a security.txt file so researchers and tools can find your contact and policy automatically.
  • A policy only works if someone triages reports; name an owner and connect it to your CRA reporting process.

Why does a small product company need a disclosure policy?

Because the law now expects one, and because researchers will find your bugs whether or not you invite them. The CRA's vulnerability handling requirements in Annex I Part II say manufacturers must:

  • "put in place and enforce a policy on coordinated vulnerability disclosure" (point 5);
  • "take measures to facilitate the sharing of information about potential vulnerabilities", including by providing a contact address for reporting them (point 6);
  • publicly disclose information about fixed vulnerabilities once a security update is available (point 4).

Annex II also requires the user information supplied with a product to include a single point of contact for vulnerability reports and where the disclosure policy can be found. These product requirements apply from 11 December 2027, but the CRA's 24-hour reporting of actively exploited vulnerabilities has applied since 11 September 2026, and a working intake channel is how you find out about exploitation early. Our explainer on Cyber Resilience Act reporting covers that duty.

In the UK, the regulations for consumer connectable products, in force since 29 April 2024, require manufacturers to publish information on how to report security issues. The ETSI consumer IoT standard says the same: provision 5.2-1 of EN 303 645 requires a publicly available policy with contact information and timelines for acknowledgement and status updates.

What should the policy include?

Ten sections cover what regulators, standards and researchers expect. The structure below draws on the CISA VDP template, the ETSI provision and the CRA requirements.

# Section Why it is there
1 Introduction and commitment Sets a welcoming tone and shows you take reports seriously
2 Scope Tells researchers which products, versions and services are covered
3 How to report Meets the CRA contact address requirement
4 What to include in a report Saves triage time
5 What you can expect ETSI 5.2-1 asks for acknowledgement and status-update timelines
6 Guidelines for researchers Protects users and data during testing
7 Safe harbour Encourages good-faith research
8 Disclosure and credit Covers coordinated disclosure and CRA point 4
9 Out of scope Prevents wasted effort on both sides
10 Policy history and contact Shows the policy is maintained

What does the template look like?

Copy the text below, replace everything in square brackets, and have it reviewed by someone who knows your products and, ideally, a lawyer.

Vulnerability Disclosure Policy, [Company name]

1. Our commitment. [Company] makes [product types]. We welcome reports from security researchers, customers and anyone else who believes they have found a security vulnerability in our products or services. We will work with you to understand and fix the issue.

2. Scope. This policy covers: [product names and model numbers]; their firmware and companion apps [app names]; and the cloud services they rely on [domains or API endpoints]. Products past their support end date are listed at [link]; we still want to hear about issues in them.

3. How to report. Email [security@yourdomain] or use [web form URL]. If you want to encrypt your report, use our key at [link]. Reports may be submitted anonymously.

4. What to include. The product and firmware or app version; a description of the issue and its potential impact; steps to reproduce it; and any proof-of-concept code. English is preferred but not required.

5. What you can expect. We will acknowledge your report within [3] business days, give you an initial assessment within [10] business days, and update you at least every [14] days until the issue is resolved. We will tell you when a fix is available.

6. Guidelines. Please test only against devices and accounts you own or have permission to use. Do not access, change or delete other people's data; if you encounter it, stop and tell us. Do not degrade our services or run denial-of-service tests. Give us a reasonable time to fix the issue before public disclosure.

7. Safe harbour. If you act in good faith and follow this policy, we will consider your research authorised, we will not pursue or support legal action against you for it, and we will say so if a third party takes action.

8. Disclosure and credit. We aim to release a fix and publish a security advisory within [90] days of your report, and we will agree a disclosure date with you. With your permission, we will credit you in the advisory. [We do / do not currently offer financial rewards.]

9. Out of scope. Social engineering of our staff; physical attacks on our premises; reports from automated scanners without a demonstrated impact; and issues in third-party services we do not control, which we will help you route to the right vendor.

10. Policy history. Version [1.0], published [date]. Questions about this policy: [security@yourdomain].

What does each part of the template need from you?

A few sections need decisions, not just text:

  • Response times (section 5). CISA's template commits to acknowledgement within 3 business days (CISA). Choose numbers your team can actually meet on a bad week, then meet them.
  • Safe harbour (section 7). This wording follows the CISA template's authorisation language. It expresses your intent but cannot bind third parties or override the law, so take advice before publishing.
  • Disclosure timeline (section 8). Ninety days is a common convention, not a legal requirement. The CRA requires you to publish information on fixed vulnerabilities after an update is available, but allows publication to be delayed in justified cases until users have had the chance to apply the patch.
  • Scope (section 2). Include companion apps and cloud services, because under the CRA the back end your device needs is part of the product.

How do you make the policy easy to find?

Publish it on a stable URL such as yourdomain/security, link it from product documentation and packaging, and add a security.txt file. RFC 9116 places this at /.well-known/security.txt, served over HTTPS. Two fields are mandatory, Contact and Expires, and a Policy field can point to your disclosure policy. A minimal example:

Contact: mailto:security@yourdomain.example
Expires: 2027-11-30T23:59:59Z
Policy: https://yourdomain.example/security
Preferred-Languages: en

Keep the Expires date current. A stale file tells researchers no one is watching.

What has to happen behind the policy?

A named owner and a short process. A policy that sends reports to an unmonitored inbox is worse than none. At minimum:

  1. Route the security address to at least two people.
  2. Log every report with a date, product, version and status.
  3. Triage within your stated timelines, and decide whether there is evidence of active exploitation, which triggers the CRA's 24-hour early warning.
  4. Fix, test and ship the update, then publish an advisory.
  5. Review the policy once a year and when you launch a new product.

This process is one item on our wider Cyber Resilience Act checklist, alongside the SBOM and support period. For an early-stage team putting it together from scratch, our worked example of product security for a hardware startup shows where it fits.

Frequently asked questions

Is a vulnerability disclosure policy a legal requirement?

In the EU, the Cyber Resilience Act requires manufacturers of products with digital elements to have a coordinated vulnerability disclosure policy and a reporting contact, for products placed on the market from 11 December 2027. In the UK, consumer connectable product makers have had to publish how to report security issues since 29 April 2024.

Do I need a bug bounty to have a disclosure policy?

No. A disclosure policy sets out how to report issues and what you will do; a bug bounty adds payment. Many small companies start with a policy and public credit, and add rewards later if budget allows.

What is security.txt?

It is a plain text file at /.well-known/security.txt, defined in RFC 9116, that tells researchers how to contact you about security issues. Contact and Expires are mandatory fields, and a Policy field can link to your disclosure policy.

How fast must we respond to a vulnerability report?

No law sets a single acknowledgement time, but ETSI EN 303 645 expects your policy to state timelines, and CISA's template uses 3 business days. If the report shows active exploitation, the CRA's 24-hour early warning clock may already be running.

Should the policy cover products we no longer support?

It is good practice to accept reports for them and say clearly which products are past their support end date. You may not ship a fix, but you can still warn users and, if the issue is actively exploited, you may still have reporting duties.

Building a connected product and want a second opinion on its security plan? Book a free 30-minute call with our team.

Cover photo by cottonbro studio on Pexels.

Hephaestus Technology

We help founders and businesses validate, build and launch products across software, AI and hardware, from offices in Ho Chi Minh City, Dublin and Delaware. See how we work.

Tell us what
you're building.

A free 30-minute call. You'll get an honest view of the idea, the risks we see and what we'd do first, whether or not we end up working together.