{"data":{"id":"PM-31","name":"Continuous Monitoring Strategy","family":"PM","family_name":"Program Management","withdrawn":false,"description":"Develop an organization-wide continuous monitoring strategy and implement continuous monitoring programs that include:\na. Establishing the following organization-wide metrics to be monitored: [Assignment: organization-defined metrics];\nb. Establishing [Assignment: organization-defined monitoring frequencies] and [Assignment: organization-defined assessment frequencies] for control effectiveness;\nc. Ongoing monitoring of organizationally-defined metrics in accordance with the continuous monitoring strategy;\nd. Correlation and analysis of information generated by control assessments and monitoring;\ne. Response actions to address results of the analysis of control assessment and monitoring information; and\nf. 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.","enhancements":[],"baseline_low":false,"baseline_moderate":false,"baseline_high":false,"nist_800_53":{"rev5":{"id":"PM-31","name":"Continuous Monitoring Strategy","description":"Develop an organization-wide continuous monitoring strategy and implement continuous monitoring programs that include:\na. Establishing the following organization-wide metrics to be monitored: [Assignment: organization-defined metrics];\nb. Establishing [Assignment: organization-defined monitoring frequencies] and [Assignment: organization-defined assessment frequencies] for control effectiveness;\nc. Ongoing monitoring of organizationally-defined metrics in accordance with the continuous monitoring strategy;\nd. Correlation and analysis of information generated by control assessments and monitoring;\ne. Response actions to address results of the analysis of control assessment and monitoring information; and\nf. Reporting the security and privacy status of organizational systems to [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency].","discussion":"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.","related_controls":["AC-02","AC-06","AC-17","AT-04","AU-06","AU-13","CA-02","CA-05","CA-06","CA-07","CM-03","CM-04","CM-06","CM-11","IA-05","IR-05","MA-02","MA-03","MA-04","PE-03","PE-06","PE-14","PE-16","PE-20","PL-02","PM-04","PM-06","PM-09","PM-10","PM-12","PM-14","PM-23","PM-28","PS-07","PT-07","RA-03","RA-05","RA-07","SA-09","SA-11","SC-05","SC-07","SC-18","SC-38","SC-43","SI-03","SI-04","SI-12","SR-02","SR-04"],"baseline_low":false,"baseline_moderate":false,"baseline_high":false,"baseline_privacy":true,"new_in_rev5":true,"changes_from_rev4":"New control in Rev 5. Organization-wide continuous monitoring formalized."}},"compliance_mappings":{"iso_27001_2022":["4.4","6.2","7.4","7.5","9.1","9.2","10.1","10.2"],"iso_27002_2022":[],"cobit_2019":[],"pci_dss_v4":[],"nist_csf_2":["GV.OV-01","GV.OV-02","GV.SC-03","GV.SC-09","GV.SC-10","ID.IM-02","ID.IM-03"],"cis_controls_v8":[],"soc2_tsc":[],"finos_ccc":[],"iso_42001_2023":[],"iec_62443":[],"asd_e8":[],"nis2":[],"apra_cps_234":[],"mas_trm":[],"pra_op_resilience":["PS6/21-1.1","SS1/21-7.1"],"bsi_grundschutz":[],"anssi":[],"osfi_b13":[],"finma_circular":[],"gdpr":[],"dora":[],"bio2":[],"rbi_csf":["Annex1.11","ITGRCA.10"],"fisc":[],"lgpd_bcb":[],"hkma_tme1":[],"mlps_2":[],"dnb_good_practice":[],"cra":[],"swift_cscf":[],"cbuae":["CR-12"],"qatar_nia":["GV"],"sama_csf":["1.3","1.9","2.2"],"bog_cisd":["CISD-XVI"],"bom_ctrm":["5.1"],"cbe_csf":["CTO-11","OVM-1"],"cbn_csf":["Part2.4"],"sa_js2":["JS2-8.7"],"bcbs_239":["Principle 1","Principle 10"],"cpmi_pfmi":["CG.LE"],"ecb_croe":["CROE.2.8.1","CROE.2.8.2"],"ffiec_is":["II.C.20"],"nydfs_500":["500.11"],"sebi_cscrf":["CCI","DE.CM","GV.OV"],"nerc_cip":[],"nrc_73_54":[],"tsa_psd":[],"ieee_1686":[],"ferc_cip":[],"doe_c2m2":[],"api_1164":[],"awia":[],"iaea_nss":[],"pci_pts":[],"fips_140":[],"cbest":["CBEST.6","CBEST.10"],"tiber_eu":["TIBER.CLOSE","TIBER.REM"],"pci_hsm":[],"common_criteria":[],"isae_3402":[],"fca_sysc_13":["SYSC 13.5.3"],"fda_21_cfr_11":[],"fda_cyber":[],"hitrust_csf":[],"iso_27799":[],"lloyds_ms":["MS10.1"],"naic_ds":["4D"],"nhs_dspt":[],"pra_ss1_23":[],"solvency_ii":[],"owasp_masvs_v2":[],"csa_ccm_v4":[],"csa_aicm":[],"ccss_v9":[],"mica":[],"basel_sco60":["SCO60.13"],"bssc":[],"sec_custody_digital":[],"dpdpa":[]},"attack_techniques":[],"metadata":{"last_reviewed":"2026-10-03","review_notes":"Generated from NIST SP 800-53 Rev 5 with compliance mappings extracted from framework-coverage data 2026-10-02: iso_27001_2022 clauses taken from NIST's SP 800-53 Rev 5 to ISO/IEC 27001:2022 crosswalk (OLIR, v1.0.0). OSA had none. 2026-10-03: nist_csf_2 GV.OV-02, GV.SC-03, GV.SC-09, GV.SC-10, ID.IM-02, ID.IM-03 added from NIST's CSF 2.0 to SP 800-53 Rev 5.2.0 crosswalk (OLIR entry 186), which OSA's mapping now takes as its base. 2026-10-03: privacy baseline added, from NIST SP 800-53B Release 5.2.0.","mapping_status":"complete"},"function":"preventative","used_by_patterns":["SP-018"]}}