Azure Security Benchmark GS-1: Align organization roles, responsibilities and accountabilities

What else in your programme already covers this

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

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

CCM-CEK-02 CEK Roles and Responsibilities
CCM-GRC-01 Governance Program Policy and Procedures
CCM-GRC-05 Information Security Program
CCM-GRC-06 Governance Responsibility Model
CCM-HRS-09 Personnel Roles and Responsibilities

PCI DSS 4.0 · 5 controls

1.1.2 1.1.2 Requirement 1 roles and responsibilities assigned
12.1.3 12.1.3 Security roles defined and acknowledged by all personnel
12.1.4 12.1.4 Executive ownership of information security formally assigned
2.1.2 2.1.2 Requirement 2 roles and responsibilities assigned
3.1.2 3.1.2 Assigned duties for Requirement 3 activities

APRA CPS 234 · 4 controls

CPS234-13 Board Responsibility for Information Security
CPS234-14 Definition of Information Security Roles and Responsibilities
CPS234-19 Information Security Policy Framework
CPS234-P19 Policy Direction to All Responsible Parties

NIST SP 800-181 · 3 controls

NICE-OG-WRL-003 Cybersecurity Workforce Management
NICE-OG-WRL-007 Executive Cybersecurity Leadership
NICE-OG-WRL-014 Systems Security Management

NIST SP 800-53 Rev 5 · 3 controls

NIST800-PM-1 PM-1 Information Security Program Plan
NIST800-PM-2 PM-2 Information Security Program Leadership Role
NIST800-PS-9 PS-9 Position Descriptions

C5 (Germany) · 2 controls

C5-OIS-01 Information Security Management System (ISMS)
C5-OIS-02 Information Security Policy

FedRAMP High · 2 controls

PL-1 Policy and Procedures
PS-9 Position Descriptions (PS-9)

FedRAMP Moderate · 2 controls

PL-1 Policy and Procedures
PS-9 Position Descriptions (PS-9)

ISO 27701:2019 · 2 controls

5.3.3 Organizational roles, responsibilities and authorities
6.3.1 Internal organization

NIST Cybersecurity Framework 2.0 · 2 controls

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
NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

NIST SP 800-161 Rev 1 · 2 controls

161R1-PM-2 Information Security Program Leadership Role
161R1-PM-29 Risk Management Program Leadership Roles

NIST SP 800-171 Rev 3 · 2 controls

03.15.01 Policy and Procedures
03.15.02 System Security Plan

NIST SP 800-218 · 2 controls

SP800-218-PO.2.1 Roles and Responsibilities for Secure Development
SP800-218-PO.2.3 Obtain Management Commitment to Secure Development

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-39 Designate an Information System Security Officer and Make the Role Known

APEC Cross-Border Privacy Rules (CBPR) System · 1 control

CBPR-PR-26 Information security policy

AWS Well-Architected Security Pillar · 1 control

SEC11-BP08 Build a program that embeds security ownership in workload teams

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

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

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-1 Written security and access policy

Authorised Economic Operator (AEO) Programmes - Global Standards · 1 control

AEO-6 Cargo Security

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

CFTC-SS-2 Enterprise Risk Management and Governance Category

CIS Controls v8 · 1 control

CIS-17.5 Assign Key Roles and Responsibilities

HIPAA Security Rule · 1 control

164.308(a)(2) Assigned Security Responsibility (Standard)

ISO 27001:2022 · 1 control

5.2 Information security roles and responsibilities

ISO 27002:2022 · 1 control

5.2 Information security roles and responsibilities

ISO/IEC 42001:2023 · 1 control

A.3.2 AI roles and responsibilities

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(2) Assigned Security Responsibility (Standard)

SOC 2 · 1 control

SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)

UK Cyber Essentials · 1 control

CE-SCOPE.2 Cloud Services in Scope

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.

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark GS-1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free