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.
Keep a per-rule ledger: findings reviewed, confirmed, dismissed, and the share confirmed. Use it to promote, tune or retire each rule on evidence.
Pinned packages are fine if each has an owner, a reason and an expiry date. Here is how to store the list in config, review it, and avoid silent drift.
Journals rotate, so keep a small separate install history on each device: what was installed, when, and any fallback. A field list and design notes.
Both can produce safe images. Jib builds without a Docker daemon and layers dependencies for you; a Dockerfile gives full control. A decision guide.
The JDK ships jdeprscan, a static tool that scans jars and classes for deprecated Java SE APIs. See how to run it, read it and what it cannot see.
Gradle dependency locking records resolved versions so builds are repeatable. How to turn it on in a template, use STRICT mode and update locks on purpose.
Istio PeerAuthentication modes explained: PERMISSIVE accepts plaintext, STRICT requires mTLS. A safe migration order and how to check what is left.
Two runs on the same commit should list the same components. Learn what legitimately changes between runs, what should not, and how to test repeatability.
Before auto-merge touches a service, confirm you can redeploy the previous build fast. These preconditions make a rollback real, not hopeful.
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.
