Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A vulnerability disclosure policy is the published document that tells security researchers how to report a flaw to your organisation and what they can expect in return.

What Is a Vulnerability Disclosure Policy?
Someone outside your organisation has found a security flaw in your website and wants to tell you. Where do they go? If the honest answer is a general enquiries form that routes to marketing, the report will probably never arrive, and the finder may conclude that publishing is the only way to get attention.
A vulnerability disclosure policy fixes that. It is a short, public document that states where to send a report, what is in scope, what testing is acceptable, how quickly you will respond, and what you commit to doing. It costs very little and it is the difference between learning about a problem from a researcher and learning about it from a journalist.
Add a security.txt file at /.well-known/security.txt, as defined in RFC 9116. It is a plain text file listing your contact address, a link to the policy, preferred languages, and an expiry date, and it is where tooling and experienced researchers look first.
The safe harbour clause carries more weight in Britain than elsewhere, because the Computer Misuse Act 1990 criminalises unauthorised access with no defence for good-faith research. A researcher who probes a UK service and reports what they find has, on a strict reading, committed an offence. The CyberUp Campaign has argued for a statutory defence for years, and the Home Office has reviewed the Act, but none has been enacted.
A published policy is therefore the closest thing to permission that a researcher can get. It defines what testing you authorise, which removes the “unauthorised” element for activity inside that boundary. Organisations without one are effectively telling researchers to take a legal risk with no reassurance, and many will reasonably decline. See responsible disclosure for how the wider process works.
If you manufacture, import, or distribute consumer connectable products for the UK market, this is no longer optional. The Product Security and Telecommunications Infrastructure Act 2022 and its associated regulations came into force on 29 April 2024 and impose three baseline security requirements. One of them is that you must publish information on how to report security issues, including a point of contact and the timescales for acknowledgement and status updates.
The other two are a ban on universal default passwords and a published statement of the minimum period for which security updates will be provided. The requirements draw on ETSI EN 303 645, the consumer IoT security standard, which sets out the same expectations in more detail. Enforcement sits with the Office for Product Safety and Standards, and penalties can reach £10 million or four per cent of worldwide turnover.
Publishing the policy is the easy part; honouring it is the work. Name an owner and a deputy so reports are not lost when someone is on leave. Acknowledge quickly, even if triage will take longer. Give the reporter a reference and keep them updated, because silence is what pushes people towards publication. Track reports through the same vulnerability management process as internal findings, with severity, owner, and target date. Request a CVE where the flaw affects software others deploy. Credit the finder unless they ask otherwise.
The NCSC publishes a Vulnerability Disclosure Toolkit that walks through all of this and includes template wording, which is a sensible starting point rather than drafting from scratch.
A disclosure policy says how to report and costs nothing beyond the staff time to handle reports. A bug bounty programme adds payment and usually a managing platform, which increases both volume and quality. Commissioned testing is different again: it finds what no outsider would stumble across, on a schedule you control. Most organisations should have the policy first, since it is the one that prevents a bad outcome on a day you were not expecting.
Our Penetration Test Services complement a disclosure policy by finding the issues that never reach a researcher’s screen.
A vulnerability disclosure policy tells people how to report issues and what to expect, with no payment involved. A bug bounty programme adds financial rewards, usually managed through a platform that handles triage and payment. Bounties attract far more submissions, including a great deal of noise, so most organisations publish a policy first and consider a bounty later.
For most organisations it is strongly recommended rather than mandatory. For manufacturers, importers, and distributors of consumer connectable products, it became a legal requirement on 29 April 2024 under the Product Security and Telecommunications Infrastructure Act 2022, alongside a ban on default passwords and a published security update period.
A plain text file published at /.well-known/security.txt, standardised as RFC 9116, that tells researchers where to send security reports. It lists a contact address, a link to your full policy, preferred languages, an optional PGP key, and an expiry date. Automated tooling checks for it, so it is often the first thing a finder looks for.
A request for a reward where none is offered is awkward but legitimate; a threat to publish or sell unless you pay is extortion and should be treated as a criminal matter. Your policy should state plainly whether rewards exist. Keep the conversation in writing, involve legal counsel early, and continue fixing the underlying issue regardless.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.