Production
Org-wide Secret Remediation
Leading a team of 5 to find and remove hardcoded secrets across the organization, with zero production impact.
- Role
- SDE 1 – Backend (Java)
- Company
- Standard Chartered Research and Technology (SOLV)
- Period
- Jan 2024 – Present
- Stack
- gitleaks · entropy scanning · AWS Secrets Manager · Ansible Vault
5
engineers led
0
production incidents
3
config sources kept in parity (service repo, Ansible v1, Ansible v2)
Production metrics · 30-day window · Sep 2026
Context
Credentials had accumulated in source repos and deployment config over years: database passwords, API keys, tokens.
Design
- Discovery: scan every repository with gitleaks, then a second entropy-based pass to catch secrets the default rules miss.
- Remediation:
- Replace each secret with a
${placeholder}in service config and an encrypted variable in Ansible Vault, or move it to AWS Secrets Manager. - Keep the service repo, Ansible v1 and Ansible v2 in parity, so no environment breaks.
- Ship one PR per service.
- Replace each secret with a
- Tracking & handoff: a central tracker of every secret, its new home and its status, handed to DevOps for rotation. Removing a secret from the latest commit does not un-leak it; rotation does.
- Team: split by domain groups, with a shared playbook and review checklist, and daily status on the tracker.
Key decisions & trade-offs
Results
- Hardcoded secrets removed across the organization’s services, SDKs, infra and mobile repos, with zero production impact.
- A repeatable process: tracker + playbook + rotation handoff.
Tech used
- gitleaks
- AWS Secrets Manager
- Ansible Vault
- Git
- GitHub