Compliance
UK PSTI Act Consumer IoT: Year-One Review
The UK PSTI Act's first year of enforcement reveals how consumer IoT vendors are struggling with minimum security requirements, password rules, and disclosure policies.
Mar 24, 20267 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 feedCompliance
NIST 800-53 security and privacy controls overview
A breakdown of NIST 800-53 Rev 5's control families, SBOM and supply-chain requirements, and why scanning tools like Anchore cover only a narrow slice of what compliance demands.
Mar 24, 20267 min read
Compliance
NIST 800-190 container security guide compliance
NIST 800-190 requires evidence across five container risk categories, not just image scans. Where Anchore-based pipelines fall short and how to close the gap.
Mar 24, 20267 min read
Compliance
NIST 800-218 / SSDF attestation requirements
What NIST SP 800-218 (SSDF) attestation actually requires, the CISA form's four claims, key OMB deadlines, and where Anchore's SBOM-first approach leaves gaps Safeguard closes.
Mar 24, 20267 min read
Compliance
Open Source Licensing Models Explained: Permissive, Copyleft, and Compliance Risk
Open source licensing models fall into a few families with very different obligations. Here is how permissive, copyleft, and source-available terms affect your compliance.
Mar 24, 20266 min read
Compliance
NIST SP 800-218A: SSDF Practices for Generative AI Models
NIST finalized SP 800-218A on July 26, 2024, augmenting the Secure Software Development Framework with practices specific to generative AI and dual-use foundation models.
Mar 23, 20266 min read
Compliance
DoD software factory reference design and secure software...
What a real DoD software factory requires under the DevSecOps Reference Design, where Anchore's scanning fits and falls short, and how continuous SBOM evidence enables cATO.
Mar 23, 20267 min read
Compliance
ATO and continuous ATO (cATO) for government software
ATO takes 6-18 months and expires the moment it's signed. Here's what continuous ATO (cATO) really requires, where container-only tools like Anchore fall short, and how Safeguard closes the gap.
Mar 23, 20267 min read
Compliance
STIG compliance scanning for hardened/Chainguard containe...
Chainguard images have near-zero CVEs, but shell-based scanners like Anchore flag them as STIG non-compliant. Here is why, and how to fix it.
Mar 23, 20267 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.