iac.htora.dev · security templates

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

  1. Code is pushed: to any repository in the organisation.
  2. Scanning runs: secrets, dependencies, code.
  3. A block or an alert: push protection stops known secret formats.
  4. Responders see it: through a signed webhook to the collector.
PlatformUsesThe part that catches people
GitHubOrganisation security settings with the GitHub provider, and a signed webhook that sends security alerts to your collectorThe organisation settings resource manages every setting it covers, so in a real organisation read the plan before applying.

Run the quick start

Download providersterraform init
Previewterraform plan
Applyterraform 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.

Read the full pageDownload PDF

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.