Using CODEOWNERS to protect GitHub workflow files
How to use a CODEOWNERS file so changes to workflows need approval from a named reviewer, plus syntax traps like last match wins and skipped lines.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
How to use a CODEOWNERS file so changes to workflows need approval from a named reviewer, plus syntax traps like last match wins and skipped lines.
A walk through the review concerns in a published engineering guide, design to tests to comments, and the security questions you can attach to each one.
A CNAME says no other data should exist at a name, but a zone apex needs SOA and NS records. Why that conflict breaks DNS and the practical ways around it.
CloudTrail event history keeps 90 days of management events per Region. Learn what it misses and why you also need a trail or event data store.
A CloudFormation stack policy guards resources from accidental updates, but it is not access control. How it differs from IAM and when to use both.
Use CloudFormation dynamic references to pull secrets from Secrets Manager or Parameter Store instead of embedding them. Syntax limits and traps to avoid.
CloudFormation drift detection compares live resources with the template but skips unsupported resources, defaults, nested stacks and some properties.
How to choose between Delete, Retain, RetainExceptOnCreate and Snapshot for CloudFormation resources, including defaults and a trap with replacements.
Cloud Run services are private by default. Allowing unauthenticated calls makes sense for public sites and almost nothing else. Here is how to decide.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.