Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Responsible Disclosure?

Responsible disclosure is the practice of reporting a vulnerability privately to the affected organisation and allowing time for a fix before any public detail is released.

Illustration for the cybersecurity term Responsible Disclosure
Home / Blog / Cybersecurity Terms / What Is Responsible Disclosure?
17 November 2026

What Is Responsible Disclosure?

What Is Responsible Disclosure?

A researcher finds a flaw. They can tell the vendor quietly, publish it immediately, or sell it. Responsible disclosure is the first option with a deadline attached: report privately, give the organisation a reasonable period to produce a fix, then publish once users are protected. Most of the industry now prefers the term coordinated vulnerability disclosure, because “responsible” implies that anyone who chooses differently is behaving badly, and the reasons for publishing are sometimes good.

The model exists because neither extreme works. Silence leaves users exposed and lets vendors ignore the problem indefinitely. Immediate publication arms attackers before a patch exists. A deadline balances the two and, in practice, is the only thing that reliably makes a vendor act.

How the Process Runs

  1. Report. The researcher contacts the organisation through a published channel: a security address, a security.txt file as defined in RFC 9116, or a disclosure platform. The report describes the issue, the affected versions, reproduction steps, and the impact.
  2. Acknowledge. The organisation confirms receipt, ideally within a few working days, and assigns an owner.
  3. Triage and fix. Severity is assessed, a CVE is requested where appropriate, and a patch is developed and tested.
  4. Coordinate. Researcher and vendor agree a release date, and any downstream parties who ship the affected component are notified.
  5. Publish. The advisory goes out, the researcher receives credit, and technical detail follows after users have had time to update.

Ninety days is the common reference point, popularised by Google’s Project Zero, which adds a short grace period when a patch is imminent and shortens the clock when a flaw is being exploited in the wild. Other coordinators use forty-five days. The right number depends on the complexity of the fix and whether anyone is already being attacked with it.

The Standards Behind It

Two ISO documents set out the expectations. ISO/IEC 29147 covers vulnerability disclosure, meaning how an organisation receives reports and communicates about them. ISO/IEC 30111 covers vulnerability handling, meaning the internal process that turns a report into a fix. Together they describe what a mature programme looks like, and they are what auditors reference when asking whether you have one.

The NCSC published a Vulnerability Disclosure Toolkit in 2020 for UK organisations, setting out the three practical components: a way to be contacted, a published policy describing what researchers can expect, and a security.txt file so the first two can be found. Any organisation without those three is relying on a researcher being persistent enough to find a contact form.

The UK Legal Problem

British researchers face a difficulty their counterparts in several other countries do not. The Computer Misuse Act 1990 criminalises unauthorised access to a computer system, and it contains no defence for good-faith security research. A researcher who probes a service, finds a flaw, and reports it has, on a strict reading, committed an offence, and whether they are prosecuted depends on discretion rather than law. The CyberUp Campaign has pressed for a statutory defence for several years, and the Home Office has reviewed the Act, but at the time of writing no such defence has been enacted.

This is why a published policy matters so much. A vulnerability disclosure policy that states what testing is permitted and promises not to pursue legal action against researchers who follow it gives both sides something to rely on. Without one, the rational choice for a researcher who stumbles across a flaw in a UK service is often to say nothing.

What Good Behaviour Looks Like

Researchers should test only what is necessary to demonstrate the issue, stop as soon as it is proven, avoid accessing or copying other people’s data, never demand payment in exchange for silence, and respect the agreed timeline. Pulling a database to prove an injection flaw crosses a line that reporting a single record does not.

Organisations should publish a contact route, acknowledge quickly, keep the researcher informed, fix within the agreed window, credit the finder, and resist the urge to send a legal letter. Threatening a reporter is a reliable way to guarantee that the next person publishes without warning, and the reputational cost of that reaction usually exceeds the cost of the bug.

Disclosure sits alongside a bug bounty programme for organisations that pay, and alongside commissioned Penetration Test Services for the issues that no outsider will ever stumble across.

FAQ – Frequently Asked Questions

What Is the Difference Between Responsible and Full Disclosure?

Responsible or coordinated disclosure reports the issue privately first and allows an agreed period before publication. Full disclosure publishes immediately, on the argument that users deserve to know and that vendors only act under pressure. Most of the industry sits between the two: private reporting with a hard deadline, after which details are released whether or not a patch exists.

How Long Should a Vendor Get?

Ninety days is the most widely used benchmark, with a short extension when a fix is close and a shorter clock when the flaw is already being exploited. Complex issues in embedded or industrial products sometimes justify longer, because firmware updates reach devices slowly. The deadline should be stated clearly in the first report rather than negotiated later.

Am I Protected If I Report a Bug in the UK?

Not by statute. The Computer Misuse Act 1990 has no good-faith research defence, so unauthorised testing remains an offence even when the finder reports it honestly. Protection comes from the organisation’s own published policy, which may offer safe harbour for research conducted within its stated scope. Work outside a policy carries real legal risk, and advice is worth taking.

Do Researchers Get Paid for Responsible Disclosure?

Only where a bug bounty programme exists. Plain disclosure usually brings credit in an advisory rather than money. Demanding payment in exchange for withholding details is a different matter entirely and may constitute blackmail, regardless of how the request is phrased. Researchers who want payment should work through an established programme with published reward terms.

Related Terms

You May Be Interested In These

What Is Kubernetes Incident Analysis?

Cybersecurity Terms

17 November 2026

What Is Kubernetes Incident Analysis?

Read More
What Is a Human-Machine Interface?

Cybersecurity Terms

17 November 2026

What Is a Human-Machine Interface?

Read More