GOV-12: Measures of Performance
Mechanisms exist to develop, report and monitor Security, Compliance & Resilience Program (SCRP) measures of performance.
Renumbered: Formerly GOV-05 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, GOV-12 was Forced Technology Transfer (FTT). That control is now GOV-13.
Control Question: Does the organization develop, report and monitor Security, Compliance & Resilience Program (SCRP) measures of performance?
General (30)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC1.1-POF3 CC1.2 CC1.5 CC1.5-POF2 CC1.5-POF5 CC2.1-POF4 CC2.2 CC4.1 CC4.1-POF2 CC4.2-POF1 CC5.3-POF6 |
| BSI Standard 200-1 | 4.3 |
| COBIT 2019 | EDM01.03 EDM05.01 EDM05.03 APO02.02 DSS06.01 MEA01.02 MEA01.03 |
| COSO 2013 | 2.0 5.0 14.0 16.0 |
| CSA CCM 4.1.0 | AIS-03 DCS-17 SEF-05 TVM-12 |
| IMO Maritime Cyber Risk Management | 3.3 |
| ISO 22301 2019 | 9.1 9.1(a) 9.1(b) 9.1(c) 9.1(d) |
| ISO 27001 2022 (source) | 9.1 9.1(a) 9.1(b) 9.1(c) 9.1(d) 9.1(e) 9.1(f) |
| ISO 27701 2025 | 9.1 |
| ISO 31000 2018 | 5.2 5.4.2 6.6 |
| ISO 42001 2023 | 5.1 9.3.2(d) 9.3.2(d)(1) 9.3.2(d)(2) 9.3.2(d)(3) |
| NIST AI 100-1 (AI RMF) 1.0 | GOVERN 1.5 MAP 5.2 MEASURE 1.0 MEASURE 1.1 MEASURE 1.2 MEASURE 4.0 MEASURE 4.3 |
| NIST AI 600-1 | GV-1.3-002 MS-2.7-004 |
| NIST 800-53 R4 | PM-6 |
| NIST 800-53 R5.2 | PM-06 |
| NIST 800-53B R5 (privacy) (source) | PM-06 |
| NIST 800-82 R3 | PM-06 |
| NIST 800-82 R3 LOW OT Overlay | PM-06 |
| NIST 800-82 R3 MODERATE OT Overlay | PM-06 |
| NIST 800-82 R3 HIGH OT Overlay | PM-06 |
| NIST 800-161 R1 | PM-6 |
| NIST 800-161 R1 Level 1 | PM-6 |
| NIST 800-161 R1 Level 2 | PM-6 |
| NIST 800-171 R3 (source) | 03.12.03 |
| NIST 800-171A R3 (source) | A.03.12.03[01] |
| NIST 800-207 | NIST Tenet 7 |
| NIST CSF 2.0 (source) | GV GV.OV GV.OV-01 GV.OV-03 GV.SC GV.SC-09 ID.IM-03 |
| NIST Privacy Framework 1.0 | GV.MT-P4 PR.PO-P5 PR.PO-P6 |
| SCF DPMP 2026 | 11.5 |
| TISAX ISA 6.0.3 | 1.2.1 |
US (5)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | PM-6 |
| USA Federal C2M2 2.1 | ASSET-5f THREAT-3f RISK-5f ACCESS-4f SITUATION-3d SITUATION-4f RESPONSE-5f THIRD-PARTIES-3f WORKFORCE-5f ARCHITECTURE-6f PROGRAM-2g PROGRAM-3f |
| USA Federal CERT RMM 1.2 | MA:SG1 MA:SG1.SP1 MA:SG1.SP2 MA:SG1.SP3 MA:SG1.SP4 MA:SG2 MA:SG2.SP1 MA:SG2.SP2 MA:SG2.SP3 MA:SG2.SP4 MA:GG1.GP1 MA:GG2 MA:GG2.GP2 |
| USA Federal FFIEC ITEH 2016 | II.D.1 |
| USA Texas DIR SCSC 2.2 2025 | PM-06 |
EMEA (12)
| Framework | Mapping Values |
|---|---|
| EMEA Germany BAIT 2017 | 2.5 4.9 |
| EMEA Germany C5 2026 | OPS-23.01B OPS-23.02B SIM-06.01B COM-04.01B COM-04.01AC COM-04.02AC.3 |
| EMEA Spain CCN-STIC 825 | op.mon.2 |
| EMEA EU DORA 2023 | Article 13.4 |
| EMEA EU DORA RTS 2024 | Article 2.2(c) Article 31.1(d) |
| EMEA EU EBA GL/2019/04 | 3.5.51 |
| EMEA EU NIS2 2022 | Article 21.2(f) |
| EMEA EU NIS2 Annex 2024 | 1.1.1(j) |
| EMEA Israel CDMO 2.0 | 4.2, Stage 5 Appendix D |
| EMEA LUX CCSF 20/750 2020 | 3.2.2-6 3.3.1-13.d |
| EMEA Saudi Arabia IoT CGIoT-1 2024 | 1-1-4 |
| EMEA Saudi Arabia OTCC-1 2022 | 1-4-2 1-7-2 |
APAC (9)
| Framework | Mapping Values |
|---|---|
| APAC Australia CCM 2026 | GOV-07 |
| APAC Australia ISM June 2026 | ISM-0724 |
| APAC India RBI Digital Payments 2021 | 5.0 |
| APAC India SEBI CSCRF 2024 | GV.OV.S3 GV.OV.S4 PR.IP.S10 |
| APAC Japan ISMAP | 4.6.2.1 |
| APAC Malaysia RMiT 2025 | 10.35(e) 12.3(f) |
| APAC New Zealand HISF MLHSP 2023 | HHSP46 HML46 |
| APAC New Zealand HISF Suppliers 2023 | HSUP38 |
| APAC Singapore MAS TRM 2021 | 4.5.3 |
Americas (2)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.12.03 |
| Americas Canada OSFI B-13 2022 | 1 1.2 2.8.1 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Cybersecurity & Data Protection Governance (GOV) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with GOV domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with GOV domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with GOV domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Governance-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ No formal Governance, Risk & Compliance (GRC) team exists. GRC roles are assigned to existing IT and/or cybersecurity personnel. ▪ Basic metrics are developed to provide operational oversight of a limited scope of cybersecurity and data protection controls.
Level 3 — Well Defined
Cybersecurity & Data Protection Governance (GOV) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with GOV domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with GOV domain capabilities are well-documented and kept current by process owners. ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, is appropriately staffed and supported to implement and maintain GOV domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ Technology is leveraged to enhance the efficiency and accuracy of governance, risk management and compliance operations (e.g., GRC platform). ▪ An implemented and operational capability exists to develop, report and monitor Security, Compliance & Resilience Program (SCRP) measures of performance.
Level 4 — Quantitatively Controlled
Cybersecurity & Data Protection Governance (GOV) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
Level 5 — Continuously Improving
Cybersecurity & Data Protection Governance (GOV) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes. ▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.
Assessment Objectives
- GOV-12_A01 cybersecurity / data privacy measures of performance are developed.
- GOV-12_A02 cybersecurity / data privacy measures of performance are monitored.
- GOV-12_A03 the results of cybersecurity / data privacy measures of performance are reported.
Evidence Requirements
- E-GOV-14 Measures of Performance (Metrics)
-
Documented evidence of formal measure of performance that are used to track the health of the cybersecurity & data protection program (e.g., metrics, KPIs, KRIs).
Security, Compliance & Resilience Governance
Technology Recommendations
Micro/Small
- Manually-generated metrics (spreadsheet-based dashboard)
- Basic security scorecard (patch %, training completion %, incident count)
Small
- Manually-generated metrics with structured reporting template
- GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.)
- Simple security dashboard (e.g., Power BI free tier, Google Looker Studio)
Medium
- Automated metrics via GRC or security tool integrations
- Security dashboard with defined KPIs/KRIs (e.g., Power BI, GRC platform reporting)
- GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.)
Large
- GRC platform with integrated metrics and dashboards
- Automated data collection from security tools (SIEM, vulnerability scanner, etc.)
- Defined measurement cadence aligned with board reporting schedule
Enterprise
- Enterprise GRC platform with automated metrics collection and reporting
- Security metrics integrated with business intelligence platform (e.g., Tableau, Power BI)
- Automated benchmarking against industry standards (e.g., CIS Benchmarks, CISA metrics)
- Real-time security posture dashboards for executive and board reporting