security
Safeguard articles tagged "security" — guides, analysis, and best practices for software supply chain and application security.
71 articles
Griffin AI vs Sourcegraph Cody for Security Use
Cody's codebase-wide context is valuable for security review. Griffin AI adds reachability, taint, and policy grounding that Cody doesn't target.
One Policy Set, Four Enforcement Points
Different gates with different rules create gaps and developer friction. A unified policy engine evaluates one definition at PR, build, admission, and runtime.
Nginx and CVE-2023-44487: How to Fix HTTP/2 Rapid Reset
CVE-2023-44487, the HTTP/2 Rapid Reset attack, is a protocol-level DoS. Nginx resists it with default settings, but a loose keepalive config can still be abused. Here's the fix.
Data Pipeline Platform Migration Security
Moving from one orchestration platform to another surfaces hidden trust relationships. A security-first migration plan for Airflow, Dagster, and Prefect transitions.
Automating License Policy: Blocking AGPL At PR
License risk that surfaces at release time is already too late. PR-time license policy turns an open-ended legal review into an automated, predictable check.
Signed Artifact Policy Enforcement In 2026
Signing artifacts is necessary but not sufficient. The policy that verifies signatures, attestations, and trust roots is what turns signing into a security control.
Zig's Memory Safety Model: A Security Analysis for Systems Programmers
Zig offers memory safety features that C lacks but does not go as far as Rust. For security-critical code, understanding where Zig sits on the safety spectrum matters.
Griffin AI vs Claude Prompt Caching: Security
Claude's prompt caching gives you 90% discount on cached tokens. Security workloads have massive cacheable surface area. Griffin AI takes advantage; direct API use often does not.
MCP Server Capability Policy Enforcement
MCP servers expose tools that AI agents can call directly. Capability policy decides which tools each agent gets, with the same rigor as any other supply chain gate.
OSS Trademark Policies: Security Angle
Trademarks matter in open source security because they are the signal of authentic origin. When trademark policies fail, typosquatting, impostor forks, and compromised builds follow.
Pydantic v2 Security Implications
Pydantic v2 rewrote the core in Rust and changed validation semantics. Here is what that means for security-sensitive code, from input coercion to ReDoS exposure.
Maintainer Burnout: Security Implications
Exhausted maintainers are not just a welfare problem. They are a security problem. Burnout is a precondition for social engineering, delayed patches, and hostile takeovers.
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.