Intake & triage

Move a report from intake to an owned repair

Program in practice

Triage should establish what is known, what needs controlled investigation, and who owns the next decision. A report can be important while still lacking the detail needed for reproduction. The response process should preserve that distinction without allowing the report to disappear.

Acknowledge the report and preserve its context

Retain the supplied target, timestamps, reproduction information, affected identity or role, and the reporter's contact preferences. Restrict sensitive material to the people who need it. Do not ask a reporter to expand testing beyond the program's approved boundaries merely to make triage easier.

An acknowledgement and a validated finding are different events. Communicate their actual meaning through the process rather than promising a resolution before the team has assessed the behavior.

Assign the technical question

For an illustrative access-control report, identify the expected permission rule and the minimum approved reproduction needed to assess it. Use synthetic data or a controlled environment where the question can be answered there. If the target is a supplier-operated service, involve the person authorized to coordinate that dependency.

The CERT coordinated disclosure guide provides primary process guidance. The organization's own scope, approvals, and evidence determine what a particular investigation may do.

Keep status and ownership separate

A useful record can distinguish received, under investigation, confirmed, duplicate, out of scope, repaired, awaiting retest, and unresolved. Each state still needs a responsible owner and a next action. A finding marked duplicate should point to the existing repair process rather than simply close the communication loop.

If a report cannot be reproduced, record the missing condition and the next investigation. A failure caused by unavailable access does not prove the claim false. Conversely, a persuasive narrative does not establish that the application performed the reported action.

Hand engineering a bounded repair record

Supply the affected behavior, accepted evidence, known impact, relevant constraints, and the criterion for accepting a change. Identify the engineering owner and the person responsible for communicating with the reporter. Keep those roles explicit when several teams or suppliers share the workflow.

Record the next communication decision

A technical investigation, a deployed repair, and an external update may occur at different times. Keep the owner of each decision visible and promise only response commitments the team can sustain. Use the planning worksheet and disclosure-decision guide to connect the technical work to the broader program without treating them as one automatic action.

Continue reading

Cite this entry

Vulnerability Disclosure Programs. “Move a report from intake to an owned repair.” Reviewed November 12, 2026.
https://vulnerabilitydisclosureprograms.com/triage-and-handoff/