Secure coding · 3 min read
Secrets in git history: finding them before someone else does
Deleting a key in a later commit does not remove it. The only response that counts is rotation, and the only prevention that works runs before the commit lands.
Secure coding
What this covers
These posts cover secure development practice: fixing vulnerability classes at the framework level instead of one endpoint at a time, keeping secrets out of git, and wiring security checks into CI so the same finding does not return next quarter.
The cheapest security fix is the one a framework applies for you. These posts are about moving controls down the stack — into base queries, input objects, gateway policy and CI — so correctness stops depending on a developer remembering.
2 posts in Secure coding.
Secure coding · 3 min read
Deleting a key in a later commit does not remove it. The only response that counts is rotation, and the only prevention that works runs before the commit lands.
Secure coding · 3 min read
A forty-item security checklist gets ticked without being read. Seven questions, asked only when they apply, get answered honestly.
Scope and a fixed quote within two working days. First consultation is free.