Skip to main content

Supported Frameworks

The compliance engine is built on the Secure Controls Framework (SCF), release 2026.2 as a common-control backbone: you implement a control once, and it maps out to every framework that references it. That's why evidence collected for one framework automatically advances the others. The bundled catalog is over 1,500 controls mapped across 27 frameworks.

Framework catalog

All 27 frameworks below are mapped through the SCF 2026.2 backbone, so a single control satisfies every framework that references it:

FrameworkDomain
SOC 2 (AICPA Trust Services Criteria)Service-organization trust
CIS Controls v8.1Baseline cyber hygiene
ISO/IEC 27001:2022Information security management
ISO/IEC 27002:2022Security controls
ISO/IEC 27017:2015Cloud security controls
ISO/IEC 27018:2025Cloud PII protection
ISO/IEC 27701:2025Privacy information management
ISO/IEC 42001:2023AI management systems
CSA CCM 4.1.0Cloud controls matrix
NIST AI RMF (AI 100-1)AI risk management
NIST Privacy FrameworkPrivacy
NIST SP 800-53 Rev 5Security & privacy controls
NIST SP 800-171 Rev 2Controlled unclassified information
NIST SP 800-171 Rev 3Controlled unclassified information
NIST SSDF (SP 800-218)Secure software development
NIST CSF 2.0Cybersecurity framework
OWASP Top 10 (2025)Application security
PCI DSS 4.0.1Payment-card security
CMMC 2.0 Level 2Defense supply-chain maturity
HIPAAUS healthcare privacy & security
EU AI ActAI regulation
EU DORA (2023)Financial-sector operational resilience
EU GDPREU data protection
EU NIS2 (2022)EU network & information security
EU NIS2 Annex (2024)NIS2 sector annex
India DPDP Act, 2023India data protection
SEBI CSCRF (2024)India securities-market cyber resilience

Several of these also have dedicated, guided modules on top of the SCF mapping:

FrameworkDedicated module
India DPDP Act, 2023DPDP Act (India) Privacy — readiness, DPIA, SDF classification, vendor due diligence, breach workflow with statutory DPB / CERT-In deadlines
EU AI Act, NIST AI RMF, ISO 42001AI Governance — risk-tier classification, model discovery, prompt-injection testing, assessments

How mappings work in practice

  • One control, many frameworks. Marking an SCF control implemented updates the posture of every mapped framework at once — the compliance dashboard shows the per-framework effect.
  • Evidence reuse. Evidence attached in the Evidence Hub is control-mapped, so a single artifact (say, your access-review export) counts toward SOC 2, ISO 27001, and NIST CSF simultaneously.
  • Scan findings map to controls. Cloud, code, container, and Kubernetes findings link to the controls they affect, so technical drift shows up as compliance drift.
Start with one anchor framework

Pick the framework your customers or regulators actually ask for (commonly SOC 2 or ISO 27001), get it green, and let the SCF mappings pull the others along — rather than assessing everything at once.