Keep the investigation where the next person finds it.
An incident or a near miss is a record too: what happened, who owns it, the products and CVEs involved, and when to check back, with the evidence on its CVE frozen the day it opened. Anyone in your organisation finds it again by searching your records, a year later, in another team. New evidence on its CVE reaches you while it is open, and the check-back date sends one reminder.
Close it with a new version that says what you found. What it said while open stays readable. Keep it to named people when it has to be: then only its author, your organisation's owner and the people you share it with can find it.
When an investigation needs more than the public record, two escalation paths sit right inside it: 1. Automated deep code analysis ($49.99 per run) checks your pasted call stack, manifest or repository reference against the CVE's held ranges and weakness class using our Sovereign AI model and formats the result to freeze into the chain; 2. Send me an expert · contact us routes the CVE, your investigation chain and your notes to our specialist desk.