A key the working tree no longer tells the truth about
ClaimsPortal keeps an AWS key pair in an env file that is committed. A later commit deletes another secrets file. The key in that deleted file is still in git history, and a rejected bearer token is written to the log.
Found. The scan reports the committed key, the history that still holds a deleted secret, the token in the logs, and the absence of a scanner that would stop the next one.
Fix. Rotate the key with the team that uses it, plan the history clean-up, and add a scan that runs before a commit is accepted.
AWS_ACCESS_KEY_ID=AKIA************MPLE