Observability becomes harder when the same log is both evidence and exposure.
Protecting sensitive material can remove the detail engineers need to diagnose a failed deployment.
Who you’d be doing this for
“I need the logs to explain failures, but I can’t accept finding out later that a key leaked.”
Shirin Bitar · Platform Security Engineer
Oversees build and deployment telemetry for an enterprise team with strict secret-handling requirements.
What is at stake
Final checks found seven secret-like strings in minified output, and the detector missed two of them. You have to weigh a missed secret against over-redaction that leaves logs useless for debugging.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- secret recall vs. diagnostic usefulness
- fixed launch vs. verification depth
- automated detection vs. human adjudication
- enterprise assurance vs. operational overhead
Why Vercel
At Vercel, this often matters where deployment diagnostics and enterprise trust meet.
Written with these in mind
Not your kind of problem? 7 more at Vercel, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.