Security Guides
A CVE shows no fix yet: what to do while you wait
When a CVE page says not fixed, you still have options: confirm exposure, mitigate, isolate, monitor and set a review date. A practical plan.
Oct 18, 20263 min read
Resources
Supply Chain Security, in plain English.
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.
Filter
Articles
RSS feedSecurity Guides
Nonprofit security in the first 90 days with no IT staff
A 90 day plan for a nonprofit with no security staff: what to do in month one, two and three, using free guidance from CISA, the FTC and CIS.
Oct 18, 20263 min read
Security Guides
Node.js permission model: a seat belt, not a sandbox
The Node.js permission model limits file, network and process access for trusted code. What its flags do and why it cannot contain malicious code.
Oct 18, 20263 min read
Security Guides
What the no-new-privileges container flag blocks and what it does not
The no-new-privileges option stops container processes from gaining privileges through setuid binaries. Learn how to set it and where it falls short.
Oct 18, 20264 min read
Security Guides
NIST zero trust: the seven tenets of SP 800-207 in plain language
The seven tenets of zero trust from NIST SP 800-207, explained in plain words with a practical question for each one that you can ask about your own setup.
Oct 18, 20263 min read
Security Guides
NIS2 vulnerability handling and disclosure: what is required
NIS2 asks for vulnerability handling and disclosure inside secure development, and national CSIRTs act as coordinators. What teams need to have in place.
Oct 18, 20263 min read
Security Guides
NIS2 patch management: when you may skip a patch, and how to record it
EU implementing rules expect timely, tested patches from trusted sources, and documented reasons when a patch is skipped. How to write the policy.
Oct 18, 20263 min read
Security Guides
Next.js server-only, taint and NEXT_PUBLIC: keeping secrets off the client
Three ways to keep private data out of the browser in Next.js: the NEXT_PUBLIC prefix rule, the server-only package and React taint APIs. What each does.
Oct 18, 20263 min read
Security Guides
Next.js Server Actions are public endpoints: check auth inside
A Server Action can be called with a direct POST, so a page level login check does not protect it. Verify authentication and ownership inside every action.
Oct 18, 20263 min read
Stay informed
Weekly insights on software supply chain security, delivered to your inbox.
Self-healing security runs on Safeguard.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.