How We Handle a Security Disclosure From a Stranger
A working note on handling security disclosures — what matters, what does not, and where projects usually go sideways.
Somebody asks about handling security disclosures roughly once a fortnight, usually after a decision has already been half made. Here is the answer we give on the call, written down so you can read it first.
Why handling security disclosures keeps coming up
It sits between two teams. Engineering assumes the business has decided; the business assumes engineering will pick something sensible.
Nobody owns it, so it gets settled by whoever is loudest in the last meeting before the deadline.
What this looks like in practice
In projects like these the shape repeats. Someone maps the current process, finds three painful steps, and discovers only one of them justifies real engineering.
A team we would typically advise starts with the step generating the most back-and-forth email. Not the most interesting one.
The first version covers the common case and a human handles the rest. That is the design, not a compromise.
Mistakes teams make with handling security disclosures
- Treating launch as the finish line. Most of the cost arrives afterwards.
- No named owner. Unowned work drifts, then the technology takes the blame.
- Designing for the rare case. Build the common path first.
- Skipping measurement. If nobody can tell whether it worked, you will keep paying regardless.
- Picking the tool first. That is the last decision, not the first.
How we approach it technically
Start with the data model. Most bad decisions here are downstream of a schema that made an assumption nobody revisited.
Then the failure modes. Then the interface. Interfaces are cheap to change; schemas and contracts are not.
Alert on rate of change rather than fixed thresholds. Quiet degradation is the failure that costs customers without waking anyone.
How we work through it
- List what breaks today, with dates and examples.
- Separate the problems that cost money from the ones that cost patience.
- Pick one from the money column.
- Write the smallest change that addresses it, and the way you would undo it.
- Ship behind a flag, to real users, this month.
- Review in two weeks with numbers, not impressions.
The list in step one does more work than people expect. Half the perceived problems disappear once they have to be written with a date attached.
Practical guardrails
- Instrument before you optimise. Guessing at bottlenecks costs more than measuring them.
- Keep a rollback path for anything touching customer data.
- Document the decision, not just the result.
- Set a review date ninety days out.
- Cap spend and volume in code, not on the invoice.
The honest trade-offs
Going fast now usually means paying interest later. That is fine if you know the rate and have a date to refinance.
Going slow now to avoid rework only pays off if the requirements hold. Early on, they rarely do.
Common misconceptions
“We need the best available option.” You need the option your team can operate at 2am. Those are rarely the same.
“We will fix it properly later.” Sometimes true. Write down what later means or it never arrives.
“This is a one-off.” Anything a customer touches becomes a product, with support attached.
Frequently asked questions
How long does handling security disclosures usually take?
A narrow first version is normally four to six weeks. Anything quoted at three months with no shippable slice in between is a risk, not a plan.
What is the most common mistake with handling security disclosures?
Scoping too wide. Covering every case in version one delays feedback and inflates cost with no matching benefit.
Do we need a dedicated team for this?
Not at the start. One owner with a few hours a week plus a small build team is enough until the first version proves value.
How do we know whether it worked?
Pick the number before you build: hours saved, error rate, response time or conversion. Compare a two-week window before and after.
What should we do first?
Write one sentence describing the outcome of handling security disclosures, then map the workflow it touches. Both take an afternoon and remove most of the guesswork.
Conclusion
The useful move on handling security disclosures is almost always the smaller one. Ship a narrow slice a real user can touch this month, measure it, then decide what deserves the next four weeks.
Everything gets easier once something is live.
Related reading and next steps
- the $299 AI audit — how we run this kind of work.
- All Augere Labs services.
- More writing from the team.
Want a second opinion on handling security disclosures for your setup? Book a 30-minute call. We will say plainly if it is not worth building.
FAQ
Frequently asked questions
How long does handling security disclosures usually take?+
A narrow first version is normally four to six weeks. Anything quoted at three months with no shippable slice in between is a risk, not a plan.
What is the most common mistake with handling security disclosures?+
Scoping too wide. Covering every case in version one delays feedback and inflates cost with no matching benefit.
Do we need a dedicated team for this?+
Not at the start. One owner with a few hours a week plus a small build team is enough until the first version proves value.
How do we know whether it worked?+
Pick the number before you build: hours saved, error rate, response time or conversion. Compare a two-week window before and after.
What should we do first?+
Write one sentence describing the outcome of handling security disclosures, then map the workflow it touches. Both take an afternoon and remove most of the guesswork.
Building something similar?
Let's talk in 30 minutes.