← Controls / PM

PM-31 Continuous Monitoring Strategy

Program Management

Privacy New in Rev 5

Description

Develop an organization-wide continuous monitoring strategy and implement continuous monitoring programs that include: a. Establishing the following organization-wide metrics to be monitored: [Assignment: organization-defined metrics]; b. Establishing [Assignment: organization-defined monitoring frequencies] and [Assignment: organization-defined assessment frequencies] for control effectiveness; c. Ongoing monitoring of organizationally-defined metrics in accordance with the continuous monitoring strategy; d. Correlation and analysis of information generated by control assessments and monitoring; e. Response actions to address results of the analysis of control assessment and monitoring information; and f. Reporting the security and privacy status of organizational systems to [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency].

Supplemental Guidance

Continuous monitoring at the organization level facilitates ongoing awareness of the security and privacy posture across the organization to support organizational risk management decisions. The terms "continuous" and "ongoing" imply that organizations assess and monitor their controls and risks at a frequency sufficient to support risk-based decisions. Different types of controls may require different monitoring frequencies. The results of continuous monitoring guide and inform risk response actions by organizations. Continuous monitoring programs allow organizations to maintain the authorizations of systems and common controls in highly dynamic environments of operation with changing mission and business needs, threats, vulnerabilities, and technologies. Having access to security- and privacy-related information on a continuing basis through reports and dashboards gives organizational officials the capability to make effective, timely, and informed risk management decisions, including ongoing authorization decisions. To further facilitate security and privacy risk management, organizations consider aligning organization-defined monitoring metrics with organizational risk tolerance as defined in the risk management strategy. Monitoring requirements, including the need for monitoring, may be referenced in other controls and control enhancements such as, AC-02g, AC-02(07), AC-02(12)(a), AC-02(07)(b), AC-02(07)(c), AC-17(01), AT-04a, AU-13, AU-13(01), AU-13(02), CA-07, CM-03f, CM-06d, CM-11c, IR-05, MA-02b, MA-03a, MA-04a, PE-03d, PE-06, PE-14b, PE-16, PE-20, PM-06, PM-23, PS-07e, SA-09c, SC-05(03)(b), SC-07a, SC-07(24)(b), SC-18b, SC-43b, SI-04.

Changes from Rev 4

New control in Rev 5. Organization-wide continuous monitoring formalized.

Patterns that use this control (1)

Grouped by the emphasis each pattern gives it.

Compliance Mappings

ISO 27001:2022

4.46.27.47.59.19.210.110.2

NIST CSF 2.0

GV.OV-01GV.OV-02GV.SC-03GV.SC-09GV.SC-10ID.IM-02ID.IM-03

PRA Operational Resilience

PS6/21-1.1SS1/21-7.1

RBI CSF

Annex1.11ITGRCA.10

SAMA CSF

1.31.92.2

Qatar NIA

GV

CBUAE

CR-12

CBE CSF

CTO-11OVM-1

SA JS2

JS2-8.7

CBN CSF

Part2.4

BoG CISD

CISD-XVI

BoM CTRM

5.1

BCBS 239

Principle 1Principle 10

CPMI-IOSCO PFMI

CG.LE

FFIEC IS

II.C.20

NYDFS 500

500.11

ECB CROE

CROE.2.8.1CROE.2.8.2

SEBI CSCRF

CCIDE.CMGV.OV

CBEST

CBEST.6CBEST.10

TIBER-EU

TIBER.CLOSETIBER.REM

Lloyd's Minimum Standards

MS10.1

NAIC Insurance Data Security

4D

FCA SYSC 13

SYSC 13.5.3

Basel SCO60

SCO60.13