Make publication and repair separate decisions
Coordinated disclosure connects several parties' decisions about a vulnerability, its repair, and communication. The organization should know who can approve each decision and which dependencies affect the timetable. A fixed date alone does not operate that process.
Identify the people and systems involved
Record the reporter, program contact, affected product or application owner, and any supplier whose work is needed. Determine who can authorize technical investigation, accept a repair, approve a public statement, and maintain communication. One person may hold several roles, but the responsibilities should not be implied by an inbox address.
The CERT coordinated disclosure guide discusses the coordination process. Use the actual policy and circumstances for a particular case rather than treating general guidance as a guaranteed outcome.
Preserve the technical acceptance condition
Define what behavior must change and how the team will assess the result. A deployed patch, a repaired permission rule, and a completed retest are different observations. Record which one the team has established and what remains uncertain.
Where the finding crosses services or versions, identify the affected deployment paths. A repair in one environment does not establish that every dependent system has changed. Keep those limitations in the technical record used for communication decisions.
Agree how progress will be communicated
Establish a contact route and the next update commitment. A useful update can report a verified stage or a specific blocker without exposing credentials, sensitive user information, or unreviewed technical details. Keep the content appropriate to the recipient and the actual policy.
Do not infer a permission to publish from a permission to test. Similarly, a researcher-visible policy does not establish that a supplier has accepted a particular timetable. If coordination fails or responsibilities are unclear, escalate through the program's approved process rather than inventing an agreement.
Prepare the publication decision
Record what will be communicated, to whom, when, and under whose approval. Review whether sensitive details can be minimized while preserving the information readers need to understand and repair the issue. Make the distinction between the observed flaw and wider unverified consequences explicit.
This reference does not supply a universal safe-harbor promise or a mandatory timetable. The program's actual authority, commitments, and case-specific decisions need appropriate review.
Keep the program maintainable
After the case, update the scope, reporting information, ownership, and recurring process checks that the experience showed were weak. Review the advertised security.txt information under RFC 9116 and test that the intake route still works.
Continue reading
Cite this entry
Vulnerability Disclosure Programs. “Make publication and repair separate decisions.” Reviewed November 12, 2026.
https://vulnerabilitydisclosureprograms.com/disclosure-decisions/