Self-hosted Mac runner cleanup: keychains and profiles checklist
A self-hosted Mac runner can keep signing keys and profiles after a job ends. A checklist of what to delete, when, and what to check each week.
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.
A self-hosted Mac runner can keep signing keys and profiles after a job ends. A checklist of what to delete, when, and what to check each week.
Use the EPSS API date parameter for a single CVE, or the public daily archive for many. Steps to rebuild what you knew when you made a patch decision.
Vague or absolute answers about data handling are warning signs. Here are common red flag phrases from security vendors and a better follow-up for each.
RFC 9116 recommends signing security.txt with an OpenPGP cleartext signature and adding a Canonical field. What each does and how to set them up.
Beyond Contact and Expires, RFC 9116 defines Policy, Acknowledgments, Encryption, Preferred-Languages and more. What each does and which to add first.
The Expires field in security.txt must be present and tells researchers when your contact details go stale. What to set, what RFC 9116 says, how to renew.
security.txt (RFC 9116) tells researchers how to reach you from your website; SECURITY.md does it in your repo. Fields, location and a setup checklist.
Completion rate, hours logged and quiz scores say little about whether developers write safer code. Which metrics to retire and what to track instead.
QA and test engineers can add real security coverage with targeted training: abuse cases, authorization tests and using the OWASP Web Security Testing Guide.
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.