How do runner groups limit who can use a self-hosted runner?
Runner groups decide which repositories can send jobs to a shared self-hosted runner. How the default group works and how to tighten access.
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.
Runner groups decide which repositories can send jobs to a shared self-hosted runner. How the default group works and how to tighten access.
Anyone with write access to a repository can read its Actions secrets through a workflow. Here is who that covers and how to shrink the group.
Read and Triage cannot touch Actions secrets; Write, Maintain and Admin can create, update and delete them. Why it matters and how to narrow exposure.
Share the lessons widely and keep secrets, live weaknesses and personal data restricted. A simple two layer approach to supply chain postmortem access.
Kafka Connect's REST API defaults to HTTP on port 8083 and manages connectors at runtime. Bind it, enable HTTPS, restrict the network, review access.
By default any repository admin can invite outside people. Learn the setting that narrows it to owners, who it applies to, and an intake process that fits.
Whoever can change the mirror can change what every build installs. How to restrict, separate and log edit rights on the mirror and the approved list.
Buyers ask who can change production because the pipeline is part of your supply chain. Show an access list, approval rules and a deploy log to answer.
The setting that controls how much a fix bot can do is itself a production change. How to restrict it, require a second person, and keep a record.
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.