Writing security acceptance criteria for user stories
How to add testable security acceptance criteria to ordinary user stories, with a pattern for access, input, data and logging that fits in a sprint.
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 add testable security acceptance criteria to ordinary user stories, with a pattern for access, input, data and logging that fits in a sprint.
Allow remote access to OT without a standing door: operator controlled, time limited, MFA, least privilege and logged, per CISA alerts and guidance.
Review a design across five areas: context, components, connections, code and configuration. Each gets short questions drawn from OWASP guidance.
Ship features that are safe out of the box. A practical checklist for defaults on access, exposure, secrets, logging and errors, based on OWASP guidance.
Ten settings to review on day one of a new repository: branch rules, reviews, owners, checks, signing, force push, secret protection and a PR template.
Pen test reports and architecture diagrams are sensitive. How to stage, redact and track access to security documents during a deal, step by step.
A grep friendly checklist of risky calls to search for in Python, JavaScript, Go, Java, Rust and C#, with the safer replacement for each in code review.
Both tool classes can flag a hardcoded password, but they work differently. Secrets scanning also checks git history and other places SAST skips.
A plain-language reading of OWASP's secrets management guidance: centralise, limit access, automate, log, plan break-glass, and keep secrets out of code.
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.