Home/Refreshers/Pipeline security findings in front of responders: refresher
Pipeline security findings in front of responders
Secret scanning, push protection, and dependency alerts switched on and sent to the SIEM, so a leaked key is an incident.
Remember
- Code is pushed: to any repository in the organisation.
- Scanning runs: secrets, dependencies, code.
- A block or an alert: push protection stops known secret formats.
- Responders see it: through a signed webhook to the collector.
| Platform | Uses | The part that catches people |
|---|---|---|
| GitHub | Organisation security settings with the GitHub provider, and a signed webhook that sends security alerts to your collector | The organisation settings resource manages every setting it covers, so in a real organisation read the plan before applying. |
Run the quick start
| Download providers | terraform init |
| Preview | terraform plan |
| Apply | terraform apply |
Watch out
- A leaked key found by push protection costs nothing.
- The webhook also reports when someone switches a scanner off or makes a repository public, which is how a quiet exposure usually starts.
Check it worked
Push a test token to a branch. Push protection blocks it. Bypass the block, and the alert reaches your collector.