SOC 2
CC - Common Criteria (Security)

SOC 2 SOC2-CC2.1: CC2.1 Relevant, quality information to support internal control (COSO principle 13)

The organisation obtains or produces relevant, good-quality information and uses it so internal control can function. Points of focus: there is a process to decide what information the control components and objectives need; systems capture data from inside and outside the organisation; relevant data is turned into information; and that information stays produced on time, kept up to date, correct and whole, reachable when needed, secured, capable of verification and kept, and is reviewed for relevance. The 2022 revision adds five points: internal and external data flows are documented and used in control design; system components (infrastructure, software, data, external systems, endpoints and roles) are recorded and kept current as assets; information is classified by its characteristics, such as personal data, customer confidential data or intellectual property, so threats and controls can be identified; people running controls work from reports they can trust to be whole, correct, up to date and valid; and the physical location and custody of assets is tracked, especially where they sit outside the organisation's own premises, such as on vendor equipment or staff-owned phones.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

ISO/IEC 42001:2023 · 11 controls

  • 4.1 Understanding the organization and its context
  • 6.1.2 AI risk assessment
  • 7.5 Documented information
  • 7.5.3 Control of documented information
  • 9.1 Monitoring, measurement, analysis and evaluation
  • 9.3 Management review
  • A.4.3 Data resources
  • A.5.3 Documentation of AI system impact assessments
  • A.7.2 Data for development and enhancement of AI system
  • A.7.3 Acquisition of data
  • A.7.5 Data provenance
  • NIST-CSF-DE.AE-03 Information is correlated from multiple sources
  • NIST-CSF-GV.OC-01 The organizational mission is understood and informs cybersecurity risk management
  • NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
  • NIST-CSF-GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated
  • NIST-CSF-GV.OC-05 Outcomes, capabilities, and services that the organization depends on are understood and communicated
  • NIST-CSF-GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes
  • NIST-CSF-ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained
  • NIST-CSF-ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
  • NIST-CSF-ID.RA-09 The authenticity and integrity of hardware and software are assessed prior to acquisition and use
  • NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

PCI DSS 4.0 · 10 controls

  • 1.2.3 1.2.3 Accurate network diagram of CDE connections
  • 1.2.4 1.2.4 Accurate data-flow diagram for account data
  • 10.2.1.1 10.2.1.1 Logs capture individual user access to cardholder data
  • 10.2.2 10.2.2 Required details recorded for each auditable event
  • 5.1.1 5.1.1 Requirement 5 policies and procedures maintained and communicated
  • 8.3.8 8.3.8 Authentication policies communicated to users
  • 9.1.1 9.1.1 Requirement 9 policies and procedures maintained
  • 9.5.1.1 9.5.1.1 Current register of POI devices
  • 3.1.1 3.1.1 Requirement 3 policies and procedures maintained and in use
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking

NIST SP 800-53 Rev 5 · 7 controls

CIS Controls v8 · 6 controls

  • CIS-1.1 Establish and Maintain Detailed Enterprise Asset Inventory
  • CIS-12.4 Establish and Maintain Architecture Diagram(s)
  • CIS-3.2 Establish and Maintain a Data Inventory
  • CIS-3.8 Document Data Flows
  • CIS-8.12 Collect Service Provider Logs
  • CIS-8.2 Collect Audit Logs

ISO 27701:2019 · 5 controls

  • 5.2.1 Understanding the organization and its context
  • 5.5.5 Documented information
  • 5.7.1 Monitoring, measurement, analysis and evaluation
  • 6.5.2 Information classification
  • 7.4.3 Accuracy and quality

FedRAMP High · 4 controls

  • AU-3(1) Additional Audit Information
  • AU-6 Audit Record Review, Analysis, and Reporting
  • CA-7 Continuous Monitoring
  • SA-5 System Documentation

FedRAMP Moderate · 4 controls

  • AU-3(1) Additional Audit Information
  • AU-6 Audit Record Review, Analysis, and Reporting
  • CA-7 Continuous Monitoring
  • SA-5 System Documentation

HIPAA Security Rule · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

EU AI Act · 3 controls

  • EUAI-Art.11 Technical documentation
  • EUAI-Art.53 Obligations for providers of general-purpose AI models
  • EUAI-Art.72 Post-market monitoring by providers and post-market monitoring plan for high-risk AI systems

ISO 22301:2019 · 3 controls

  • 4.1 Understanding the organization and its context
  • 7.5.3 Control of documented information
  • 9.1 Monitoring, measurement, analysis and evaluation

ISO 27002:2022 · 3 controls

  • 5.12 Classification of information
  • 5.28 Collection of evidence
  • 5.9 Inventory of information and other associated assets

NIST SP 800-171 Rev 3 · 3 controls

CMMC 2.0 · 2 controls

DORA · 2 controls

  • DORA-Art.13 Learning and evolving
  • DORA-Art.45 Information-sharing arrangements on cyber threat information and intelligence

ISO 27001:2022 · 2 controls

  • 5.12 Classification of information
  • 5.9 Inventory of information and other associated assets

AICPA SOC 3 · 1 control

  • SOC3-COMMS Communication
  • CPS220-16 Management Information System and Data Framework
  • CPS230-P27 Comprehensive Assessment of the Operational Risk Profile
  • SEC04-BP02 Capture logs, findings, and metrics in standardized locations

C5 (Germany) · 1 control

  • C5-COM-04 Information on information security performance and management assessment of the ISMS
  • CFTC-SS-20 Production of System Safeguards Books and Records

NIST SP 800-172 · 1 control

  • 3.11.1e Threat-Aware Risk Assessment

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-CC2.1 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.

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.

Query this from an agent

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