A developer accidentally includes a cloud API token in a commit. Which repository control is meant to catch this at commit time?
Choose an answer to check it. Afterward, select any option to review its explanation.
A honeytoken is a decoy planted to detect someone misusing it. It does nothing to prevent a real token from being committed by mistake.
A web application firewall filters HTTP traffic in front of a running web server. It never sees developer commits, so it cannot stop a token from being committed.
Secrets scanning evaluates committed code for secrets such as keys and API tokens, and push protection blocks them from entering the repository. It targets exactly this mistake.
Dependency detectors also run in the pipeline, which makes them tempting, but they inventory the libraries a project pulls in. They do not look for credentials pasted into the code.
id q26fcf2b521