LAB
Leaked Credential, End to End
A developer committed AWS credentials to the `payments-api` repository four commits ago, and the file is still tracked on the team's Git server. Detect the exposure with gitleaks, revoke the credential, purge it from every commit with `git filter-repo`, and discover that the remote is still dirty the moment that separates fixing your copy from fixing the exposure. You will finish by adding a pre-commit hook and a CI gate, then proving they work by trying to reintroduce a credential.
Intermediate
•
60m
Secrets Management
DevSecOps