j3ffyang·Oct 14Keeping secrets out of GitSecrets, credentials, and keys belong on the local disk and nowhere else — not in a commit, not in a push, not in a branch, not in a pull…
Provahona·Oct 5Automating GitHub Tokens for Claude with 1Password Service AccountsWhat failed, and what I settled on, while automating tokens for Claude
Shubham Anandani·Oct 3Migrating to Microsoft Entra Verified IDA neutral playbook for issuing and verifying user-owned credentials with open standards, and wiring the verification step into an existing…
Dean J Murphy·Sep 28Using DuckDB SecretsHow to Stop Leaking Your Credentials to Your Git RepoA response icon1A response icon1
Muhammadpahrizal·Sep 19From Static Passwords to Dynamic Database Credentials with HashiCorp VaultAlmost every production app need credentials to access their database.
Gauvin David Delubio·Sep 17The Credentialed DegenerateWhy being accomplished, educated, and a little unconventional can make you more human
Amanda Lewis·Sep 9Building Permits: Security, Sandboxes, and Guardrails for Enterprise AI BuildersAn AI development tool without guardrails is like an excavator on a job site with no safety perimeter.A response icon1A response icon1
CognycopIA Nexhowl - Estúdio Laboratório·Sep 3The Advantage of Looking QualifiedWho Deserves It, and Who Can Prove It
Shubham Anandani·Aug 25Revocation Is the Hard PartIssuing is easy; keeping credentials current without leaking who asked is the challenge.
Robert Broeckelmann·Aug 19Holder of Key vs. Proof of Possession: Two Sides of Cryptographic IdentityThis post is also published on the IyaSec blog.
