SOC 2
CC - Common Criteria (Security)

SOC 2 SOC2-CC1.2: CC1.2 Board independence and oversight of internal control (COSO principle 2)

A governing body that is independent of management oversees how internal control is designed and how it performs. Points of focus: the board accepts defined oversight duties; it keeps and periodically reviews the skills it needs to question management and act; enough members are independent and objective; and where it lacks expertise in any of the five trust services categories (security, availability, confidentiality, processing integrity, privacy) it adds it through a committee or outside advisers.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 49 controls across 20 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 8 controls

NIST Cybersecurity Framework 2.0 · 7 controls

  • NIST-CSF-GV.OC-01 The organizational mission is understood and informs cybersecurity risk management
  • NIST-CSF-GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction
  • NIST-CSF-GV.OV-03 Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes
  • NIST-CSF-GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated
  • NIST-CSF-GV.RR-01 Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving

ISO 27701:2019 · 6 controls

  • 5.2 Context of the organization
  • 5.3 Leadership
  • 5.3.1 Leadership and commitment
  • 5.3.3 Organizational roles, responsibilities and authorities
  • 5.7.3 Management review
  • 6.2.1 Management direction for information security

ISO/IEC 42001:2023 · 5 controls

  • 4.2 Understanding the needs and expectations of interested parties
  • 5.1 Leadership and commitment
  • 5.3 Roles, responsibilities and authorities
  • 9.3 Management review
  • 9.3.1 General

C5 (Germany) · 3 controls

  • C5-COM-04 Information on information security performance and management assessment of the ISMS
  • C5-OIS-01 Information Security Management System (ISMS)
  • C5-OIS-02 Information Security Policy

APRA CPS 220 Risk Management · 2 controls

  • CPS220-02 Board Responsibility for the Risk Management Framework
  • CPS220-20 Annual Board Risk Management Declaration

APRA CPS 230 Operational Risk Management · 2 controls

  • CPS230-13 Board Accountability for Operational Risk Management
  • CPS230-8 Board Oversight, Approval of the BCP, Tolerance Levels and Service Provider Policy

APRA CPS 234 · 2 controls

  • CPS234-13 Board Responsibility for Information Security
  • CPS234-28 Escalation of Unremediated Testing Deficiencies

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

ISO 22301:2019 · 2 controls

  • 5.1 Leadership and commitment
  • 9.3 Management review

AICPA SOC 3 · 1 control

  • SOC3-CONTROL-ENV Control Environment

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-36 Internal Reporting and Review by Senior Management and the Board

DORA · 1 control

FedRAMP High · 1 control

FedRAMP Moderate · 1 control

ISO 27001:2022 · 1 control

  • 5.35 Independent review of information security

ISO 27002:2022 · 1 control

  • 5.35 Independent review of information security

NIS2 Directive · 1 control

  • Art.20.1 Management body approves the cybersecurity risk-management measures and oversees their implementation

NIST SP 800-218 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in CC - Common Criteria (Security)

You are reading one control. How much of SOC 2 have you already done?

SOC 2 SOC2-CC1.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of SOC 2 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 49 of 61 SOC 2 controls already carry evidence.

If you hold NIST SP 800-53 Rev 580.3% covered · 12 gapsIf you hold FedRAMP Moderate60.7% covered · 24 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.157.4% covered · 26 gapsIf you hold ISO 27001:202257.4% covered · 26 gapsIf you hold C5 (Germany)54.1% covered · 28 gapsIf you hold NIST Cybersecurity Framework 2.052.5% covered · 29 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 193 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 49 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll SOC 2 controls