CyberKit

Responsible Disclosure

Also called coordinated disclosure.

Reporting a flaw privately and giving time to fix before going public.

What it is

A process where a researcher reports a vulnerability privately to the affected vendor and allows time to remediate before any public release. It coordinates the timing of fixes and disclosure to reduce harm.

Why it matters

Coordinated disclosure balances defenders' need to patch against the public's right to know, and it shapes when N-day details become available. Understanding the process matters when handling research findings or vendor advisories.

In practice

A researcher privately reports a bug, agrees on a remediation window with the vendor, and publishes details only after a patch ships.

What to look for

  • A published security contact or policy, such as security.txt.
  • Timelines agreed with the vendor.
  • Safe harbor language for researchers.

Common mistake

Ignoring reports without a process. Researchers may go public when nobody answers.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

Read next

Sources