NIST SP 800-161 Rev 1 161R1-PM-2: Information Security Program Leadership Role

What else in your programme already covers this

This control maps to 25 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.

APRA CPS 234 · 2 controls

CPS234-13 Board Responsibility for Information Security
CPS234-14 Definition of Information Security Roles and Responsibilities

C5 (Germany) · 2 controls

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

ISO 22301:2019 · 2 controls

5.1 Leadership and commitment
5.3 Roles, responsibilities and authorities

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.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders

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

APRA CPS 230 Operational Risk Management · 1 control

CPS230-13 Board Accountability for Operational Risk Management

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

Azure Security Benchmark · 1 control

GS-1 Align organization roles, responsibilities and accountabilities

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-GRC-06 Governance Responsibility Model

DORA · 1 control

DORA-Art.5 Governance and organisation

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

NIST SP 800-172 · 1 control

3.6.1e Establish Security Operations Center (SOC)

NIST SP 800-53 Rev 5 · 1 control

NIST800-PM-2 PM-2 Information Security Program Leadership Role

NIST SP 800-66 Rev 2 · 1 control

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

PCI DSS 4.0 · 1 control

12.1.4 12.1.4 Executive ownership of information security formally assigned

SOC 2 · 1 control

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

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 NIST SP 800-161 Rev 1 have you already done?

NIST SP 800-161 Rev 1 161R1-PM-2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-161 Rev 1 your existing evidence covers. Hold C5 (Germany) and 94 of 191 NIST SP 800-161 Rev 1 controls already carry evidence.

If you hold C5 (Germany)49.2% covered · 97 gaps If you hold NIST SP 800-171 Rev 338.2% covered · 118 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.137.2% covered · 120 gaps If you hold NIST SP 800-17221.5% covered · 150 gaps If you hold AWS Well-Architected Security Pillar20.9% covered · 151 gaps If you hold DORA17.3% covered · 158 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 C5 (Germany) pair alone.

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