Security Guides
TLP labels explained: RED, AMBER, GREEN and CLEAR
TLP 2.0 labels tell recipients how far threat intelligence may be shared. A short guide to RED, AMBER, AMBER+STRICT, GREEN and CLEAR with sharing examples.
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
How to throttle password reset and OTP endpoints in an API
Reset and one time passcode endpoints need tighter limits than general rate limits: per account throttles, attempt caps and cost controls. Here is how.
Oct 18, 20263 min read
Security Guides
A 60-minute threat modeling workshop for developers
Run a 60-minute threat modeling session using four questions, a data flow sketch and STRIDE prompts. Includes timings, roles and the outputs to capture.
Oct 18, 20263 min read
Security Guides
Threat modeling a medical device: what FDA expects to see
FDA recommends threat modeling across the whole medical device system, with stated assumptions and supply chain risks. What the model should contain.
Oct 18, 20263 min read
Security Guides
Threat modeling in sprint planning: a 15 minute routine
A short routine that adds threat modeling to sprint planning without a separate workshop: pick the stories that matter, ask four questions, log the outcome.
Oct 18, 20263 min read
Security Guides
Threat modeling in four questions, with no special tools
Threat modeling can start with the Manifesto's four plain questions: what are we working on, what can go wrong, what will we do about it, did we do enough.
Oct 18, 20263 min read
Security Guides
Four questions or five steps: which threat modeling frame to use
The Manifesto four questions and the Microsoft five steps cover the same ground. Choose by what your team will run, not by which sounds more official.
Oct 18, 20263 min read
Security Guides
Four threat modeling anti-patterns and how to avoid them
The Threat Modeling Manifesto names four anti-patterns: the hero modeler, admiration for the problem, overfocus and the quest for a perfect representation.
Oct 18, 20263 min read
Security Guides
Threat modeling a REST API: a worked example with trust boundaries
A worked threat model for a small REST API: draw the data flow, mark trust boundaries, apply STRIDE to each flow and turn results into tickets.
Oct 18, 20264 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.