Supported compliance standards

CIS Software Supply Chain Security benchmark

The CIS Software Supply Chain Security benchmark provides prescriptive guidance for establishing a secure configuration posture for Software Development Platforms and Pipelines.

CIS Benchmarks are best practices for the secure configuration of a target system. In this case, the target system is the software supply chain.

Visit CIS Software Supply Chain Security benchmark for further details.

OWASP Software Component Verification Standard

The Software Component Verification Standard (SCVS) is a community-driven effort to establish a framework for identifying activities, controls, and best practices, which can help in identifying and reducing risk in a software supply chain.

Visit OWASP Software Component Verification Standard for further details.

OpenSSF FLOSS

The OpenSSF FLOSS Best Practices is a set of recommendations from the Open Source Security Foundation (OpenSSF) Best Practices Working Group to help open source developers create and maintain more secure software.

The best practices criteria are divided into three levels, for an incremental adoption:

• Passing focuses on best practices that well-run FLOSS projects typically already follow. Getting the passing badge is an achievement; at any one time only about 10% of projects pursuing a badge achieve the passing level.

• Silver is a more stringent set of criteria than passing but is expected to be achievable by small and single-organization projects.

• Gold is even more stringent than silver and includes criteria that are not achievable by small or single-organization projects.

Visit OpenSSF FLOSS Best Practices Badge for further details.

OpenSSF Scorecard

OpenSSF Scorecards is an automated tool that assesses a number of important heuristics ("checks") associated with software security and assigns each check a score of 0-10. You can use these scores to understand specific areas to improve in order to strengthen the security posture of your project. You can also assess the risks that dependencies introduce, and make informed decisions about accepting these risks, evaluating alternative solutions, or working with the maintainers to make improvements.

Visit OpenSSF Scorecards for further details.

ESF Securing the Software Supply Chain DEV

The ESF Securing the Software Supply Chain - Recommended Practices for Developers is a set of guidelines aimed at improving the security of software development by reducing the risk of supply chain attacks.

The set of recommended principles are framed in 5 top-level sections:

• Secure product criteria and management

• Develop Secure Code

• Verify Third-Party Components

• Harden the Build Environment

• Deliver Code

By following these guidelines, software developers can reduce the risk of supply chain attacks and ensure the security and integrity of their software.

Visit ESF Securing the Software Supply Chain. Recommended Practices for Developers for further details.

Post-quantum cryptography (PQC) standards

These standards map your cryptographic inventory to the post-quantum transition mandates. They require a cryptographic inventory (CBOM) as input — supplied with --cbom or computed on demand. Each checks that a cryptographic inventory exists and that no quantum-vulnerable cryptography remains relative to the regime's timeline. See Quantum-Safe Compliance & CBOM for the requirements behind them.

NIST IR 8547 - Transition to Post-Quantum Cryptography Standards

NIST IR 8547 sets the timeline for retiring quantum-vulnerable public-key cryptography: deprecated by 2030 and disallowed after 2035. Hybrid (classical + PQC) constructions are permitted during the transition.

Visit NIST IR 8547 PQC Transition for further details.

NSA CNSA 2.0

The NSA Commercial National Security Algorithm Suite 2.0 mandates pure post-quantum algorithms for national security systems — default by 2030 and exclusive by 2033, with hybrid constructions not approved as an end state.

Visit NSA CNSA 2.0 for further details.

EU PQC Roadmap

The EU Coordinated Implementation Roadmap for the transition to post-quantum cryptography expects governance and a cryptographic inventory from 2026, high-risk use cases migrated by 2030, and all systems by 2035, with hybrid constructions encouraged during the transition.

Visit EU PQC Roadmap for further details.

PCI DSS 4.0 (Post-Quantum)

PCI DSS 4.0 requirement 12.3.3 mandates a documented, periodically-reviewed cryptographic cipher-suite inventory. PCI DSS sets no post-quantum deadline, so quantum-vulnerable cryptography is surfaced as advisory migration debt rather than a dated failure. This is a PQC-scoped subset, not a full PCI DSS assessment.

Visit PCI DSS 4.0 PQC for further details.

DORA (Post-Quantum)

The EU Digital Operational Resilience Act (Art. 9) requires ICT cryptographic controls and a key-management/encryption policy — implying a cryptographic inventory. DORA sets no post-quantum deadline, so quantum-vulnerable cryptography is surfaced as advisory migration debt. This is a PQC-scoped subset, not a full DORA assessment.

Visit DORA PQC for further details.

NIS2 (Post-Quantum)

The EU NIS2 Directive (Art. 21) requires policies on the use of cryptography and encryption — implying a cryptographic inventory. NIS2 sets no post-quantum deadline, so quantum-vulnerable cryptography is surfaced as advisory migration debt. This is a PQC-scoped subset, not a full NIS2 assessment.

Visit NIS2 PQC for further details.