NIST SP 800-53 Rev 5 NIST800-PM-12: PM-12 Insider Threat Program

What else in your programme already covers this

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

CIS Controls v8 · 4 controls

CIS-13.1 Centralize Security Event Alerting
CIS-17.1 Designate Personnel to Manage Incident Handling
CIS-17.4 Establish and Maintain an Incident Response Process
CIS-17.5 Assign Key Roles and Responsibilities

CMMC 2.0 · 4 controls

AT.L2-3.2.3 Insider Threat Awareness
AU.L2-3.3.1 System Auditing
IR.L2-3.6.1 Incident Handling
RA.L2-3.11.1 Risk Assessments

ISO 27001:2022 · 4 controls

5.24 Information security incident management planning and preparation
5.26 Response to information security incidents
6.1 Screening
6.6 Confidentiality or non-disclosure agreements

ISO 27002:2022 · 4 controls

5.24 Information security incident management planning and preparation
5.26 Response to information security incidents
6.1 Screening
8.16 Monitoring activities

NIST Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria
NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
NIST-CSF-RS.AN-08 An incident's magnitude is estimated and validated
NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

PCI DSS 4.0 · 4 controls

12.10.1 12.10.1 Incident response plan ready for activation
12.10.2 12.10.2 Annual review and testing of the incident response plan
12.10.3 12.10.3 Incident response personnel available 24/7
12.10.6 12.10.6 Plan evolved from lessons learned and industry developments

SOC 2 · 4 controls

SOC2-CC3.3 CC3.3 Considering fraud risk (COSO principle 8)
SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
SOC2-CC7.4 CC7.4 Responding to security incidents

FedRAMP High · 2 controls

AT-2(2) Insider Threat
SR-2(1) Supply Chain Risk Management Plan | Establish SCRM Team (SR-2(1))

FedRAMP Moderate · 2 controls

AT-2(2) Insider Threat
SR-2(1) Supply Chain Risk Management Plan | Establish SCRM Team (SR-2(1))

ISO 27701:2019 · 2 controls

6.13.1 Management of information security incidents and improvements
6.3.1 Internal organization

NIST SP 800-161 Rev 1 · 1 control

161R1-PM-12 Insider Threat Program

NIST SP 800-172 · 1 control

3.9.2e Insider Threat Program

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-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 NIST800-PM-12 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 1014 NIST SP 800-53 Rev 5 controls already carry evidence.

If you hold ISO 27001:202216.1% covered · 851 gaps If you hold ISO 27002:202210.8% covered · 904 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.110.2% covered · 911 gaps If you hold CIS Controls v810.1% covered · 912 gaps If you hold NIST SP 800-171 Rev 310.1% covered · 912 gaps If you hold C5 (Germany)9.6% covered · 917 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. 342 were rejected on the ISO 27001:2022 pair alone.

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