SOC 2
CC - Common Criteria (Security)

SOC 2 SOC2-CC1.5: CC1.5 Accountability for internal control responsibilities (COSO principle 5)

People are held answerable for the internal control duties assigned to them. Points of focus: structures and authority are used to communicate duties and apply corrective action; performance measures, incentives and rewards reflect control responsibilities and expected conduct across short and longer terms; those incentives are reviewed for continued relevance; pressures created by targets are weighed when assigning work and measuring performance; and performance of control duties, including conduct and competence, is evaluated with reward or discipline as warranted. The 2022 revision adds, for privacy engagements, a defined sanctions process used when staff breach privacy policies or cause a privacy incident through negligence.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

PCI DSS 4.0 · 14 controls

  • 1.1.2 1.1.2 Requirement 1 roles and responsibilities assigned
  • 11.1.2 11.1.2 Roles for security testing assigned and understood
  • 12.1.1 12.1.1 Overall information security policy established and disseminated
  • 12.4.2 12.4.2 Quarterly reviews that personnel follow security procedures
  • 2.1.2 2.1.2 Requirement 2 roles and responsibilities assigned
  • 3.7.8 3.7.8 Key custodians formally acknowledge responsibilities
  • 4.1.2 4.1.2 Requirement 4 roles and responsibilities assigned
  • 5.1.2 5.1.2 Requirement 5 roles and responsibilities assigned
  • 6.1.2 6.1.2 Requirement 6 roles and responsibilities assigned
  • 7.1.2 7.1.2 Requirement 7 roles and responsibilities assigned
  • 9.1.2 9.1.2 Requirement 9 roles and responsibilities assigned
  • 3.1.2 3.1.2 Assigned duties for Requirement 3 activities
  • 7.2.4 7.2.4 User accounts and privileges reviewed every six months
  • 8.1.2 8.1.2 Requirement 8 roles and responsibilities assigned

NIST SP 800-53 Rev 5 · 9 controls

ISO 27001:2022 · 6 controls

  • 5.2 Information security roles and responsibilities
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.4 Management responsibilities
  • 6.2 Terms and conditions of employment
  • 6.3 Information security awareness, education and training
  • 6.4 Disciplinary process

ISO 27002:2022 · 4 controls

  • 5.2 Information security roles and responsibilities
  • 5.4 Management responsibilities
  • 6.2 Terms and conditions of employment
  • 6.4 Disciplinary process
  • CPS220-02 Board Responsibility for the Risk Management Framework
  • CPS220-20 Annual Board Risk Management Declaration
  • CPS220-P23 Minimum Contents of the Risk Management Framework

FedRAMP High · 3 controls

  • PL-4 Rules of Behavior
  • PS-8 Personnel Sanctions
  • PS-9 Position Descriptions (PS-9)

FedRAMP Moderate · 3 controls

  • PL-4 Rules of Behavior
  • PS-8 Personnel Sanctions
  • PS-9 Position Descriptions (PS-9)

ISO 27701:2019 · 3 controls

  • 5.3 Leadership
  • 6.4 Human resource security
  • 6.4.2 During employment
  • CPS230-14 Board Setting of Senior Manager Roles and Responsibilities
  • CPS230-P31 Remediation of Material Operational Risk Weaknesses

APRA CPS 234 · 2 controls

  • CPS234-14 Definition of Information Security Roles and Responsibilities
  • CPS234-P19 Policy Direction to All Responsible Parties

C5 (Germany) · 2 controls

  • C5-HR-04 Disciplinary measures
  • C5-HR-05 Responsibilities in the event of termination or change of employment

HIPAA Security Rule · 2 controls

  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
  • NIST-CSF-GV.RR-04 Cybersecurity is included in human resources practices

NIST SP 800-66 Rev 2 · 2 controls

AICPA SOC 3 · 1 control

  • SOC3-CONTROL-ENV Control Environment

APPI · 1 control

  • SEC11-BP08 Build a program that embeds security ownership in workload teams
  • AUCDR-IS-6 Information security training and awareness program

CMMC 2.0 · 1 control

DORA · 1 control

EU AI Act · 1 control

ISO 22301:2019 · 1 control

  • 5.3 Roles, responsibilities and authorities

ISO/IEC 42001:2023 · 1 control

  • A.3.2 AI roles and responsibilities

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.5 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 74 it maps to, and the evidence behind each claim, over MCP and REST.