Answers are grounded in this paper and cite their sources.
Vulnerability disclosure is a well-known process facilitating communication between finders and vendors. In contrast, vulnerability notification, a distinct practice focused on alerting network operators and end-users, remains less understood. Despite interventions from support organisations, large-scale vulnerability notification is often inefficient and lacks clear guidelines, making it challenging to establish trust and reach affected parties. In this work, we propose a new best practice to address the limitations of vulnerability notifications at scale, drawing on operational experience and community input, in collaboration with The Shadowserver Foundation. We explicitly differentiate vulnerability notification from vulnerability disclosure to help finders and vendors determine the applicability of our approach. We then introduce a workflow that provides a step-by-step guide to notification preparation, illustrated by two use cases: one for the finder and one for the vendor. This workflow includes scanning mechanisms to monitor mitigation progress and integrates seamlessly with existing disclosure guidelines. By reducing friction in tracking vulnerable systems and notifying responsible parties, we aim to streamline stakeholder communication, ultimately providing a practical guideline for finders and vendors to enhance Internet safety.
No takes yet. Share an insight, caveat, or question.
Chen et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: