Organisations subject to several laws and frameworks at once need one set of controls they can implement and evidence once, and the Secure Controls Framework (SCF) has become one of the most widely used free catalogues for that job, including inside many GRC tools. The SCF is a cybersecurity and data privacy metaframework maintained by the SCF Council: a catalogue of more than 1,500 controls in 34 domains, mapped to more than 200 laws, regulations and frameworks using set theory relationship mapping. This guide explains how the catalogue is structured, what the licence allows, how its mappings relate to NIST's OLIR programme, how identity and non-human identity controls sit in the IAC domain, how to implement it with the SCRMS operating model and the Evidence Request List, and where its limits are. It is for GRC leads, control owners, auditors and anyone choosing an anchor control set. For general mapping method see the Control Mapping Guide.
Key takeaways
- It is a metaframework, not a certification standard by itself. The SCF supplies common controls and mappings; you still need the underlying law or framework for legal obligations, and the scheme owner's assessment for formal compliance.
- Releases are quarterly. The SCF site describes four releases a year (2026.2 was current on the home page when checked, while the Evidence Request List already referenced 2026.3 numbering); pin the release you implement.
- The licence restricts derivatives. SCF content is licensed under CC BY-ND 4.0: you may share it unmodified with attribution, but distributing modified material, including AI-generated policies built from it, needs a commercial licence.
- Mappings use set theory relationships. Since release 2024.1 the SCF uses the NIST IR 8477 set theory approach (subset of, equal to, superset of, intersects with, no relationship) with a strength score from 1 to 10; NIST lists SCF-submitted references in its OLIR catalog, which is not an endorsement.
- Identity is one domain, but touches many. The IAC domain covers people, devices and automated accounts; cryptography, monitoring and third-party domains carry the rest of the non-human identity lifecycle.
What it is and who it applies to
The SCF is free to download (CSV or Excel, and NIST OSCAL JSON) without registration and is maintained by the SCF Council, a volunteer community of CISOs, GRC specialists, architects, engineers, auditors and privacy professionals. It does not apply to anyone by law; organisations adopt it as an internal control set, and GRC platforms use it as a backbone for crosswalks.
| Option for a common control set | Strengths | Trade-offs | Fits best |
|---|---|---|---|
| SCF as the anchor | Very broad mapping coverage including privacy and AI; free; evidence list and maturity models included | Large catalogue to scope down; CC BY-ND limits redistribution of modified content; mappings are SCF Council judgements | Organisations with many overlapping obligations across regions |
| A primary framework as the anchor (ISO/IEC 27001, SP 800-53) | Auditors and assessors already know it; official crosswalks from the owner (for example NIST OLIR) | Gaps for obligations outside that framework's scope | Organisations dominated by one certification or authorisation |
| Own internal control set | Exactly fits the organisation | Mapping effort and maintenance fall entirely on you | Mature GRC teams with dedicated staff |
Decision guidance: a small organisation answering one or two frameworks rarely needs a 1,500-control metaframework; anchor on the main framework and use SCF mappings only to check gaps. A multinational facing GDPR, DORA, NIST CSF, PCI DSS, SOC 2 and sector rules gains most from SCF as the anchor, because it replaces many pairwise crosswalks with one.
Structure and key requirements
The SCF organises controls into 34 domains, each with a three-letter identifier. The domain list as published on the SCF site:
| ID | Domain | ID | Domain |
|---|---|---|---|
| AAT | Artificial Intelligence & Autonomous Technologies | IRO | Incident Response |
| AST | Asset Management | IAO | Information Assurance |
| BCD | Business Continuity & Disaster Recovery | MNT | Maintenance |
| CAP | Capacity & Performance Planning | MDM | Mobile Device Management |
| CHG | Change Management | NET | Network Security |
| CLD | Cloud Security | PES | Physical & Environmental Security |
| CPL | Compliance | PRM | Project & Resource Management |
| CFG | Configuration Management | QTS | Quantum Security |
| MON | Continuous Monitoring | RSK | Risk Management |
| CRY | Cryptographic Protections | SEA | Secure Engineering & Architecture |
| DCH | Data Classification & Handling | SAT | Security Awareness & Training |
| PRI | Data Privacy | GOV | Security, Compliance & Resilience Governance |
| EMB | Embedded Technology | OPS | Security Operations |
| END | Endpoint Security | TDA | Technology Development & Acquisition |
| HRS | Human Resources Security | TPM | Third-Party Management |
| IAC | Identification & Authentication | THR | Threat Management |
| VPM | Vulnerability & Patch Management | WEB | Web Security |
Note that CAP is both the identifier of the Capacity and Performance Planning domain and the abbreviation for the SCR Conformity Assessment Program; context tells them apart.
Supporting components
- SCRMS: the Secure, Compliant and Resilient Management System, an operating model across people, processes, technology, data and facilities, run as plan, do, check, act.
- Prioritized Implementation Guide (PIG): sequencing advice on where to start.
- Maturity and risk models: the SCR-CMM capability maturity model and SCR-RMM risk management model, plus built-in risk and threat catalogues.
- Evidence Request List (ERL): a tab in the workbook listing evidence items with identifiers such as E-GOV-01, each mapped to at least one SCF control.
- CDPAS and the SCR Conformity Assessment Program: assessment standards and a programme for third-party validated "SCR Certified" designations.
- SCF CORE: pre-scoped subsets such as Fundamentals and AI-focused sets.
Licence
The SCF terms apply the Creative Commons Attribution-NoDerivatives 4.0 International licence (CC BY-ND 4.0), effective 22 March 2019. You may reproduce and share unmodified material with attribution and a link to the licence. If you remix, transform or build on the material you may not distribute the modified result; the terms state this includes using AI or similar tools to generate policies, standards, procedures, metrics or risks from SCF content, and offering derivative SCF content needs a commercial licence. Internal use for your own control set is the common case; consult counsel before redistributing.
Identity and NHI requirements
The SCF describes the IAC domain as building identity and access management that is secure, compliant and resilient, applying least privilege to people, devices and automated accounts. That explicit mention of automated accounts is useful: it gives non-human identities a place in the anchor control set rather than leaving them implied. In practice the NHI lifecycle spans several domains. The table is NHI Mgmt Group's own view of where to look, not an SCF Council mapping.
| NHI lifecycle need | SCF domains to check | Typical evidence |
|---|---|---|
| Inventory and ownership of service accounts, workload identities, AI agents | IAC, AST | Identity inventory with owner, purpose and system. See the Service Account Inventory Template. |
| Credential issuance, storage and rotation | IAC, CRY | Vault configuration, rotation logs, certificate inventory. See the Machine Identity, PKI and Certificate Lifecycle Guide. |
| Least privilege and access review | IAC | Entitlement review output covering machine identities |
| Monitoring of machine activity | MON, OPS | Detections on service account and token misuse. See the Detection Engineering for Non-Human Identities Guide. |
| Third-party integrations and OAuth apps | TPM, CLD | Register of supplier integrations and their scopes |
| AI agents with delegated access | AAT, IAC | Agent identity, scope and approval records |
| Decommissioning | IAC, AST, CHG | Evidence identities and secrets were revoked when systems retired |
Implementation steps
The SCF's own implementation guidance follows plan, do, check, act. A practical sequence:
- Establish context. List the laws, regulations, contracts and frameworks that apply, the scope and the risk appetite. The SCRMS calls the externally driven obligations Minimum Compliance Requirements (MCR) and the risk-based choices Discretionary Security Requirements (DSR).
- Pin a release. Download the current release, record its version and keep it as the baseline. Plan to review each quarterly release rather than chasing every change.
- Scope the controls. Filter the catalogue by the mapping columns for your obligations to get the MCR set, add DSR controls from your risk assessment, and record why others are excluded. The result is your Minimum Security Requirements blueprint.
- Check mapping relationships. For each obligation, read the relationship type and strength; where a requirement only intersects with an SCF control, add the missing detail.
- Assign owners and documents. Map controls to policies, standards and procedures and name control owners; the ERL governance items (E-GOV-01 policies, E-GOV-02 standards, E-GOV-04 procedures) cover the documentation layer.
- Pilot in one domain. IAC or VPM are good pilots: high audit value and measurable. Collect ERL evidence, run an internal assessment and adjust.
- Load into tooling. Import the OSCAL JSON or Excel into your GRC platform, keeping SCF identifiers so future releases can be diffed.
- Assess and improve. Measure maturity with the SCR-CMM, remediate gaps and update the living control set as obligations change.
Rollback: if a new release changes numbering or mappings in a way that breaks your tooling, stay on the pinned release and migrate deliberately; keep a mapping table from old to new identifiers.
Evidence and assessment
The ERL lists, per row, an identifier, area of focus, artefact name, a description of what the evidence must show and the SCF controls it maps to (the page referenced 2026.3 numbering). Every ERL item maps to at least one control and the mapping works both ways in the workbook.
- Before assessment: under CDPAS Standard 4.4 the assessor provides an ERL; the organisation gathers the evidence before assessor time starts.
- During assessment: the assessor reviews evidence against the ERL and documents gaps; additional evidence may still be requested.
- Freshness: for CDPAS assessments evidence must be no more than one year old.
- Formal designations: the SCR Conformity Assessment Program lists certifications including NIST SP 800-171 R3, NIST CSF 2.0, NYDFS 23 NYCRR Part 500, the HIPAA Security Rule (via SP 800-66 R2), SP 800-161 R1, SCF CORE Fundamentals and CMMC Level 1. The SCF site names The Cyber AB as the accreditation body for the programme. These designations do not replace a regulator's own assessment, a CMMC certification under the DoD programme, or an ISO certificate.
Metrics
- Obligation coverage: percentage of in-scope obligation requirements mapped to an implemented SCF control with "equal to" or "subset of" relationship.
- Evidence readiness: share of ERL items for in-scope controls with current evidence under one year old.
- Reuse ratio: average number of obligations satisfied per implemented control.
- Release currency: number of SCF releases between your pinned version and current.
- NHI coverage: percentage of non-human identities in the IAC inventory with owner and rotation evidence.
Mapping to other frameworks
The SCF applies set theory relationship mapping to every mapped framework, using five relationship types and a strength score from 1 (nominal) to 10 (strongest, typically equal to, or an obligation that is a subset of the SCF control). The approach follows NIST IR 8477 (final, February 2024), which describes how NIST maps standards, regulations and frameworks to NIST publications through OLIR.
| Mapping | Where it is published | Who authored it |
|---|---|---|
| SCF to NIST CSF 2.0 | Listed among CSF 2.0 informative references on nist.gov | SCF Council (non-NIST submission) |
| SCF to NIST CSF 1.1 and SP 800-171 Rev. 2 | NIST OLIR catalog (SCF states NIST accepted these submissions) | SCF Council |
| SCF to 200+ laws, regulations and frameworks (for example GDPR, DORA, AICPA TSC, CMMC, CIS Controls 8.1) | SCF workbook and free STRM PDFs on the SCF site | SCF Council |
NIST runs limited conformance checks on OLIR submissions but does not test non-NIST mappings for correctness, and the SCF itself notes that NIST participation is not an endorsement. Treat SCF mappings like any third-party crosswalk: useful, but check the pairs your audit depends on. See the NIST CSF 2.0 Informative References and OLIR Guide, and for a direct, NIST-published crosswalk the NIST SP 800-53 to ISO 27001 Mapping Guide.
Common pitfalls
- Adopting all 1,500 controls: without scoping by obligation and risk, the catalogue becomes shelfware. Start from MCR and add DSR deliberately.
- Treating mappings as compliance: an SCF mapping says how an obligation relates to a control; it does not show the obligation is met. Legal requirements still need reading at source.
- Ignoring relationship types: "intersects with" pairs are counted as full coverage, and the first audit sample fails.
- Not pinning a release: quarterly changes ripple through GRC tooling and evidence references without a controlled migration.
- Breaching the licence: publishing modified SCF content, or AI-generated policies built from it, without a commercial licence.
- Human-only identity evidence: IAC controls are evidenced with workforce access reviews while automated accounts, which the domain explicitly covers, are left out.
Practitioner checklist
- List every law, regulation, contract and framework in scope before opening the catalogue.
- Download a release, record its version and review new releases quarterly.
- Scope controls into minimum compliance and discretionary sets and record exclusions.
- Check the relationship type and strength for every mapping your audits rely on.
- Use the ERL to prepare evidence and keep it under one year old.
- Include service accounts, workload identities and AI agents in IAC evidence.
- Keep SCF identifiers in your GRC tool so releases can be diffed.
- Confirm licence obligations before sharing any modified SCF material.
Standards and references
- SCF Council: Secure Controls Framework
- SCF Council: SCF Domains and Principles
- SCF Council: Set Theory Relationship Mapping (STRM)
- SCF Council: Evidence Request List (ERL)
- SCF Council: Terms and Conditions (CC BY-ND 4.0)
- NIST: IR 8477, Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines
- NIST: CSF 2.0 Informative References
- NIST: National Online Informative References (OLIR) Program
Related NHI Mgmt Group resources: Control Mapping Guide · NIST CSF 2.0 Informative References and OLIR Guide · Audit Evidence and Continuous Controls Monitoring Guide · Non-Human Identity (NHI) Guide