Cross-Framework Mapping

OpenSSF ScorecardvsISO/IEC 23837 - Security Requirements for Quantum Key Distribution

See exactly how OpenSSF Scorecard controls map to ISO/IEC 23837 - Security Requirements for Quantum Key Distribution. Pre-computed mappings, identified gaps, and coverage analysis.

7
Controls Mapped
1
Gaps Found
38%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

OpenSSF Scorecard maps to ISO/IEC 23837 - Security Requirements for Quantum Key Distribution with 38% coverage across 3 directly mapped controls. Analysis of 8 OpenSSF Scorecard controls identifies 5 compliance gaps — primarily concentrated in Maintenance and Supply Chain Integration.

Source: TheArtOfService Knowledge Graph | 8 controls analysed | 706 frameworks | 324K+ cross-framework mappings

Control Mappings

Showing 7 of 7 mapped controls across 3 domains. Sign up to explore all 324K+ mappings across 706 frameworks.

Repository Governance(3 mappings)

OSSFSC-1Branch Protection, Code Review, and Repository Governance3 targets
23837-1.1Scope
27557-1Scope
27557-3Terms and definitions

Build and CI/CD Security(1 mappings)

OSSFSC-3Build, CI/CD Security, Workflow Permissions, Dangerous Patterns
23837-1.7.3Authentication and classical post-processing

Release Integrity and Provenance(3 mappings)

OSSFSC-6Signed Releases, Provenance, Trusted Publishing, Binary Artifacts3 targets
23837-1.2Normative references
23837-1.5.2Cryptographic module requirements
23837-1.5.3Network device testing requirements

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 706 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 706 framework browser
  • Cross-framework mappings (324K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between OpenSSF Scorecard and ISO/IEC 23837 - Security Requirements for Quantum Key Distribution?

OpenSSF Scorecard has 8 controls across its framework, while ISO/IEC 23837 - Security Requirements for Quantum Key Distribution covers 42 controls. Direct mapping analysis identifies 3 overlapping controls (38% coverage). The frameworks diverge most significantly in Maintenance and Supply Chain Integration, where 1 OpenSSF Scorecard controls have no direct ISO/IEC 23837 - Security Requirements for Quantum Key Distribution equivalent.

How many controls map between OpenSSF Scorecard and ISO/IEC 23837 - Security Requirements for Quantum Key Distribution?

Of 8 total OpenSSF Scorecard controls, 3 map directly to ISO/IEC 23837 - Security Requirements for Quantum Key Distribution controls — representing 38% coverage. The remaining 5 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping OpenSSF Scorecard to ISO/IEC 23837 - Security Requirements for Quantum Key Distribution?

5 OpenSSF Scorecard controls have no direct equivalent in ISO/IEC 23837 - Security Requirements for Quantum Key Distribution. The highest concentration of gaps is in Maintenance and Supply Chain Integration with 1 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between OpenSSF Scorecard and ISO/IEC 23837 - Security Requirements for Quantum Key Distribution?

The domain with the highest gap count is Maintenance and Supply Chain Integration (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.