Skip to main content

GOV-09: Steering Committee & Program Oversight

GOV 7 — High Govern

Mechanisms exist to align security, compliance and resilience capabilities with business requirements through a steering committee or advisory board, comprised of key cybersecurity, data protection and business executives, which meets formally and on a regular basis.

Renumbered: Formerly GOV-01.1 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, GOV-09 was Define Control Objectives. That control is now GOV-03.3.

Control Question: Does the organization align security, compliance and resilience capabilities with business requirements through a steering committee or advisory board, comprised of key cybersecurity, data protection and business executives, which meets formally and on a regular basis?

General (19)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC1.2 CC1.2-POF1 CC1.2-POF2 CC1.2-POF3 CC1.2-POF4 CC1.3-POF1 CC1.3-POF3 CC1.5-POF3 CC1.5-POF4 CC1.5-POF5 CC2.2-POF4 CC2.2-POF12 CC2.3-POF3 CC3.1-POF11 CC3.4-POF3 CC4.2 CC4.2-POF1 CC4.2-POF2
BSI Standard 200-1 4.1.1 4.1.2 4.3 4.4 7.4 7.5 8.4
COBIT 2019 EDM05.01 EDM05.02 EDM05.03 APO01.06 APO14.01 DSS06.01 MEA01.04 MEA03.02 MEA04.03
COSO 2013 1.0 2.0
IMO Maritime Cyber Risk Management 3.3
ISO 22301 2019 5.1 5.1(a) 5.1(b) 5.1(c) 5.1(d) 5.1(e) 5.1(f) 5.1(g) 5.1(h) 9.3.1 9.3.2 9.3.2(a) 9.3.2(b) 9.3.2(c) 9.3.2(c)(1) 9.3.2(c)(2) 9.3.2(c)(3) 9.3.2(d) 9.3.2(e) 9.3.2(f) 9.3.2(g) 9.3.2(h) 9.3.2(i) 9.3.2(j) 9.3.2(k) 9.3.3.1 9.3.3.1(a) 9.3.3.1(b) 9.3.3.1(c) 9.3.3.1(d) 9.3.3.2 9.3.3.2(a) 9.3.3.2(b)
ISO 27001 2022 (source) 4.4 5.1 5.3 5.3(a) 5.3(b) 9.3.1 9.3.2(a) 9.3.2(b) 9.3.2(c) 9.3.2(d) 9.3.2(d)(1) 9.3.2(d)(2) 9.3.2(d)(3) 9.3.2(d)(4) 9.3.2(e) 9.3.2(f) 9.3.2(g) 9.3.3 10.1
ISO 27017 2015 5.1 7.2.1
ISO 27018 2025 5.4
ISO 27701 2025 5.1 9.3.1 9.3.2 9.3.2(a) 9.3.2(b) 9.3.2(c) 9.3.2(d) 9.3.2(e) 9.3.3
ISO 31000 2018 5.2 5.4.2 5.4.3
ISO 42001 2023 9.2.2(c) 9.3.1 9.3.2 9.3.2(a) 9.3.2(b) 9.3.2(c) 9.3.2(d) 9.3.2(d)(1) 9.3.2(d)(2) 9.3.2(d)(3) 9.3.2(e)
NAIC Insurance Data Security Model Law (MDL-668) 4.E(1) 4.E(2) 4.E(2)(a) 4.E(2)(b) 4.E(3)
NIST AI 100-1 (AI RMF) 1.0 GOVERN 2.3 MAP 3.5 MAP 5.2
NIST AI 600-1 GV-1.3-004
NIST 800-171 R3 (source) 03.12.03
NIST 800-171A R3 (source) A.03.12.03[01]
NIST CSF 2.0 (source) GV.RM-01 GV.RM-03 GV.RR-01 GV.OV GV.OV-01 GV.OV-02 GV.OV-03 GV.SC GV.SC-01 GV.SC-03 GV.SC-09 ID ID.RA PR PR.IR
TISAX ISA 6.0.3 1.2.1
US (10)
Framework Mapping Values
USA Federal DHS CISA TIC 3.0 3.UNI.PEPAR
USA Federal C2M2 2.1 RISK-1f PROGRAM-2a PROGRAM-2c PROGRAM-2d
USA Federal CERT RMM 1.2 ADM:GG2.GP10 AM:GG2.GP10 COMM:GG2.GP10 COMP:GG2.GP10 CTRL:GG2.GP10 EC:GG2.GP10 EF:SG3 EF:SG4 EF:SG4.SP1 EF:SG4.SP2 EF:GG1.GP1 EF:GG2 EF:GG2.GP2 EF:GG2.GP10 EXD:GG2.GP10 FRM:GG2.GP10 HRM:GG2.GP10 ID:GG2.GP10 IMC:GG2.GP10 KIM:GG2.GP10 MA:GG2.GP10 MON:GG2.GP10 OPD:GG2.GP10 OPF:GG2.GP10 OTA:GG2.GP10 PM:GG2.GP10 RISK:GG2.GP10 RRD:GG2.GP10 RRM:GG2.GP10 RTSE:GG2.GP10 SC:GG2.GP10 TM:GG2.GP10 VAR:GG2.GP10 GG2.GP10
USA Federal FTC Act 1938 45(a)(1)
USA Federal GLBA CFR 314 2023 314.4(a)(2)
USA Federal NSF RIG 2025 5.3.7.2
USA Federal SEC Cybersecurity Rule 2023 17 CFR 229.106(b)(1)(iii) 17 CFR 229.106(c)(1) 17 CFR 229.106(c)(2) 17 CFR 229.106(c)(2)(i) 17 CFR 229.106(c)(2)(iii) Form 8-K Item 1.05(a)
USA Federal FCA CRM 2023 609.930(b)(1) 609.930(b)(2)
USA Federal FINRA 2007 248.201(e)(1) 248.201(e)(2)
USA New York DFS 23 NYCRR500 2023 Amd 2 500.4(b) 500.4(b)(1) 500.4(b)(2) 500.4(b)(3) 500.4(b)(4) 500.4(b)(5) 500.4(b)(6) 500.4(d) 500.4(d)(1) 500.4(d)(2) 500.4(d)(3) 500.4(d)(4)
EMEA (17)
Framework Mapping Values
EMEA CHE FINMA Circular 2023/1 IV.A-23 IV.A-24 V-101 V-103
EMEA Germany BAIT 2017 1.1 1.2 1.2(a) 1.2(b) 1.2(c) 1.2(d) 1.2(e) 1.2(f) 2.1 2.2 2.3 2.4 2.5 4.3
EMEA Spain Royal Decree 311 2022 Article 12(1)(d)
EMEA EU DORA 2023 Article 5.2 Article 5.2(a) Article 5.2(b) Article 5.2(c) Article 5.2(d) Article 5.2(e) Article 5.2(f) Article 5.2(g) Article 5.2(h) Article 5.2(i)(i) Article 5.2(i)(ii) Article 5.2(i)(iii)
EMEA EU DORA RTS 2024 Article 28.2 Article 28.2(a) Article 28.2(c) Article 28.2(d) Article 28.2(d)(ii) Article 39.2(a)
EMEA EU EBA GL/2019/04 3.2.1.2 3.2.1.3 3.2.1.4
EMEA EU NIS2 2022 Article 21.2(f)
EMEA EU NIS2 Annex 2024 1.1.1(k)
EMEA UK CAF 4.0 A1.a A1.c
EMEA UK DEFSTAN 05-138 2024 1101 1103 1202
EMEA UK DEFSTAN 05-138 - L1 2024 1202
EMEA UK DEFSTAN 05-138 - L2 2024 1101 1103 1202
EMEA UK DEFSTAN 05-138 - L3 2024 1101 1103 1202
EMEA Israel CDMO 2.0 2.A
EMEA Saudi Arabia IoT CGIoT-1 2024 1-1-4
EMEA Saudi Arabia ECC-1 2018 1-1-1 1-2-3 1-4-1
EMEA Saudi Arabia SAMA CSF 1.0 2017 3.1.1.1 3.1.1.2 3.1.1.3 3.1.1.3.a 3.1.1.3.b 3.1.1.3.c 3.1.1.4 3.1.1.4.a 3.1.1.4.b 3.1.1.4.c 3.1.1.4.d 3.1.1.5 3.1.1.6 3.1.1.7 3.1.1.8 3.1.1.9 3.1.1.9.a 3.1.1.9.b 3.1.1.9.c
APAC (14)
Framework Mapping Values
APAC Australia CCM 2026 GOV-01 GOV-08
APAC Australia ISM June 2026 ISM-0725 ISM-1998 ISM-1999 ISM-2002 ISM-2003 ISM-2005 ISM-2006
APAC Australia Prudential Standard CPS230 2023 16(a) 17 18 24 27(a)
APAC Australia Prudential Standard CPS234 2019 13.0
APAC India DPDPA 2023 8(6) 18(2) 23(1) 26(a) 26(b) 26(c) 27(1)(a) 27(1)(b) 27(1)(c) 27(1)(d) 27(1)(e) 27(2) 27(3) 28(1) 28(2) 28(3) 28(4) 28(5) 28(6)
APAC India RBI PA 2025 Annex 1.1.7.1 Annex 1.1.7.2
APAC India SEBI CSCRF 2024 GV.OV.S2 GV.RR.S1 GV.RR.S3 GV.RR.S4
APAC Japan ISMAP 4.4.1.1 4.4.1.3 4.4.5.3 4.5.3.1 4.6.3.1 4.6.3.2 4.6.3.3
APAC Malaysia RMiT 2025 8.2 8.2(b) 8.3 8.4 8.4(b) 8.7 8.7(a) A10-A1(a)
APAC New Zealand HISF MLHSP 2023 HHSP12 HML12 HML21
APAC New Zealand HISF Suppliers 2023 HSUP10 HSUP19
APAC New Zealand NZISM 3.9 3.2.9.C.01
APAC Singapore CCOP CII 2026 3.1.1 3.1.2 3.1.2(b)
APAC Singapore MAS TRM 2021 3.1.1 3.1.2 3.1.5 3.1.7 3.1.7(a) 3.1.7(b) 3.1.7(c) 3.1.7(d) 3.1.7(e) 3.1.7(f) 3.1.7(g)
Americas (4)

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. ▪ Organizational leadership maintains an informal process to review and respond to trends.

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 align security, compliance and resilience capabilities with business requirements through a steering committee or advisory board, comprised of key cybersecurity, data protection and business executives, which meets formally and on a regular basis.

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

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. GOV-09_A01 an executive steering committee, or advisory board, is formed and is comprised of key cybersecurity, technology, risk, privacy and business executives.
  2. GOV-09_A02 the executive steering committee, or advisory board, coordinates cybersecurity, technology, risk, privacy and business alignment through formal meetings held per an organization-defined frequency.

Evidence Requirements

E-GOV-09 Charter - Cybersecurity Steering Committee

Documented evidence of an executive steering committee, or advisory board, that is formed to perform oversight of cybersecurity management decisions and is comprised of key cybersecurity, technology, risk, privacy and business executives.

Security, Compliance & Resilience Governance
E-GOV-10 Charter - Data Privacy Steering Committee

Documented evidence of an executive steering committee, or advisory board, that is formed to perform oversight of privacy management decisions and is comprised of key cybersecurity, technology, risk, privacy and business executives.

Security, Compliance & Resilience Governance
E-GOV-11 Charter - Audit Committee

Documented evidence of an executive steering committee, or advisory board, that is formed to perform oversight of internal and external audit management decisions and is comprised of key cybersecurity, technology, risk, privacy and business executives.

Security, Compliance & Resilience Governance
E-GOV-12 Charter - Risk Committee

Documented evidence of an executive steering committee, or advisory board, that is formed to perform oversight of risk management decisions and is comprised of key cybersecurity, technology, risk, privacy and business executives.

Security, Compliance & Resilience Governance
E-GOV-13 Charter - Data Management Board (DMB)

Documented evidence of the organization's Data Management Board (DMB) charter and mission.

Security, Compliance & Resilience Governance
E-PRM-06 Quarterly Business Review (QBR)

Documented evidence of a Quarterly Business Review (QBR), or similar process, to provide recurring status reports on the current state of the cybersecurity and data protection program.

Resource Management

Technology Recommendations

Micro/Small

  • Third-party advisors (subject matter experts)
  • Virtual CISO (vCISO) service
  • Fractional security advisor

Small

  • Third-party advisors (subject matter experts)
  • Virtual CISO (vCISO) service
  • Informal security advisory committee

Medium

  • Steering committee / advisory board
  • Quarterly security committee meetings with documented minutes
  • Cross-functional representation (IT, Legal, HR, Operations)

Large

  • Formal steering committee / advisory board
  • Documented charter with defined roles and meeting cadence
  • Board-level cybersecurity reporting

Enterprise

  • Formal steering committee / advisory board
  • Board-level Cybersecurity Committee or subcommittee
  • Chief Information Security Officer (CISO) with board-level access
  • Independent security advisor / external audit committee

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.