How we disclose
Quiet until it's fixed. Public once it is.
When our own open-source work turns up a flaw in other people's code, we hand it to the people who can fix it, with confidentiality and discretion, and we don't sit on it forever.
This is how we handle our own open-source research. Customer and contracted engagements follow the terms of the engagement.
Who hears first
The people who can fix it.
Each finding goes privately to the project's maintainers, or to the coordinator for its ecosystem, with the trace that shows where it is and why it matters.
Until it's fixed, we hold the details in confidence and work them through with the people fixing it.
How we handle it
Confidential, discreet, exact.
- Confidential. A finding goes to named people who can act on it. We don't name open issues in public.
- Discreet. No details, no hints, no countdowns in public before the fix. Until it ships, what the flaw is and where it lives stays with the people fixing it.
- Exact. What we send pins the flaw to the line, shows why it matters and spells out the fix.
- Honest about impact. We say exactly what an attacker would reach, and what stays out of reach. Every severity rating is earned.
When it goes public
Not forever. On a date.
We agree a disclosure date with the maintainers, once the fix has shipped and the people running the code have had time to update.
If a fix stalls, we set a deadline and publish after it. We give more time to a maintainer who is working on a fix. What we publish is written for defenders: what was wrong, what fixed it, and how to tell you're covered.
What we publish
One page per fix, on the record.
Disclosed findings are published, with what it was, what it affected, the fix, the timeline and the credit, as agreed with the maintainers.
Our public studies use releases already fixed upstream, so anyone can check every claim. The first is Grafana 8.3.0.
Open source
We choose what we read.
We point the swarm at the open-source code the world runs on, and report what it finds to the maintainers.
For that program, we pick projects by how many people they protect. It isn't by application.
Your code
Your findings are yours.
Findings from work we do for a client go to that client, under that client's terms, including flaws in the open-source code it runs. We never publish them without consent.
Reports describe code, never the people who wrote it.
A problem in HunterSwarm itself
One inbox.
Write to security@hunterswarm.com.
Grafana code quoted in our case study is Grafana's, unmodified. A flaw in that code goes to Grafana.