Authority & scope

Define scope and test the reporting route before launch

Program in practice

A vulnerability disclosure program needs an authorized policy and a reporting route that reaches someone able to act. Publishing a contact address is only one part of that operating arrangement. Define the systems, conduct, and responsibilities before inviting reports.

Establish who can make the commitments

Identify the people responsible for the program and the systems they can authorize researchers to examine. Record which supplier-operated or connected services need a separate permission decision. Ownership of one domain does not automatically grant authority over every integration a researcher might encounter.

The CISA policy template is a useful primary reference for policy structure. Adapt decisions to the organization's actual authority and operating process rather than treating a template as an automatic grant of legal protection.

Make the target boundaries usable

Describe included and excluded systems in a way a researcher can apply to the actual target. Assign an owner to update that scope when domains, services, or suppliers change. A policy that lists a retired host while omitting its replacement can create uncertainty for both researchers and responders.

State the point where testing must stop, including how unexpected sensitive information or effects should be handled. Keep permission to test separate from the later decision to publish a finding. Avoid promises that the organization has not approved or cannot carry out.

Prove that a report can arrive

Test the intended reporting route with a labeled internal exercise. Confirm delivery, attachment handling, access by the responder, and the process for absence or escalation. A form that succeeds visually but never reaches the triage owner is not a functioning intake process.

If encrypted submission is offered, ensure the advertised material and handling process are usable. Record who maintains the route and who can restore it after an account, service, or key changes.

Publish discovery information accurately

RFC 9116 specifies security.txt and its fields. Use it to help people find the actual reporting information, not as a substitute for policy or authority. Maintain the advertised expiry and contact information according to the published format.

Rehearse the first handoff

The launch exercise should move a synthetic report from receipt to an identified triage and repair owner. Record what failed and repair the process before treating the policy as operational. This is a proposed tabletop procedure, not a claim that a named organization completed it.

Continue reading

Cite this entry

Vulnerability Disclosure Programs. “Define scope and test the reporting route before launch.” Reviewed November 12, 2026.
https://vulnerabilitydisclosureprograms.com/scope-and-intake/