# CA-07 Continuous Monitoring

NIST SP 800-53 control. Family: CA Security Assessment and Authorization. Function: detective. Baselines: low, moderate, high, privacy. Mapping licence: CC BY-SA 4.0.

Statement: Develop a system-level continuous monitoring strategy and implement continuous monitoring in accordance with the organization-level continuous monitoring strategy that includes: a. Establishing the following system-level metrics to be monitored: [Assignment: organization-defined system-level metrics]; b. Establishing [Assignment: organization-defined frequencies] for monitoring and [Assignment: organization-defined frequencies] for assessment of control effectiveness; c. Ongoing control assessments in accordance with the continuous monitoring strategy; d. Ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy; e. Correlation and analysis of information generated by control assessments and monitoring; f. Response actions to address results of the analysis of control assessment and monitoring information; and g. Reporting the security and privacy status of the system to [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency].
Guidance: Continuous monitoring at the system level facilitates ongoing awareness of the system security and privacy posture 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 generate risk response actions by organizations. When monitoring the effectiveness of multiple controls that have been grouped into capabilities, a root-cause analysis may be needed to determine the specific control that has failed. 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 information on a continuing basis through reports and dashboards gives organizational officials the ability to make effective and timely risk management decisions, including ongoing authorization decisions. Automation supports more frequent updates to hardware, software, and firmware inventories, authorization packages, and other system information. Effectiveness is further enhanced when continuous monitoring outputs are formatted to provide information that is specific, measurable, actionable, relevant, and timely. Continuous monitoring activities are scaled in accordance with the security categories of systems. Monitoring requirements, including the need for specific 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), 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, PM-31, PS-07e, SA-09c, SR-04, SC-05(03)(b), SC-07a, SC-07(24)(b), SC-18b, SC-43b, and SI-04.

## Enhancements (5)
- CA-07(01) Independent Assessment. Baselines: moderate, high
- CA-07(03) Trend Analyses
- CA-07(04) Risk Monitoring. Baselines: low, moderate, high, privacy
- CA-07(05) Consistency Analysis
- CA-07(06) Automation Support for Monitoring
Withdrawn by NIST: CA-07(02) (now in CA-02).
Each enhancement's statement: /api/v1/controls/CA-07?fields=enhancements

## Patterns that use it (34)
- Critical (19): SP-006 Wireless- Private Network Pattern; SP-011 Cloud Computing Pattern; SP-018 Information Security Management System; SP-023 Industrial Control Systems; SP-027 Secure LLM Usage; SP-028 Secure DevOps Pipeline Pattern; SP-029 Zero Trust Architecture; SP-030 API Security; SP-031 Security Monitoring and Response; SP-035 Offensive Security Testing; SP-038 Vulnerability Management and Patching; SP-043 Security Metrics and Measurement; SP-045 AI Governance and Responsible AI; SP-046 External Attack Surface Management; SP-047 Secure Agentic AI Frameworks; SP-049 AI in Security Operations (draft); SP-051 Tokenised Asset Security Architecture (draft); SP-053 Zero-Knowledge Proof Architecture (draft); SP-054 CBDC and Digital Currency Infrastructure (draft)
- Important (15): SP-001 Client Module; SP-002 Server Module; SP-007 Wireless- Public Hotspot Pattern; SP-013 Data Security Pattern; SP-015 Secure Remote Working; SP-017 Secure Network Zone Module; SP-026 PCI Full Environment; SP-032 Modern Authentication; SP-034 Cyber Resilience; SP-036 Incident Response; SP-037 Privileged User Management; SP-040 Post-Quantum Cryptography and Quantum Readiness; SP-042 Third Party Risk Management; SP-044 SaaS Identity Lifecycle Management; SP-048 Offensive AI and Deepfake Defence (draft)

## Clauses by framework (80 frameworks)
- iso_27001_2022: 9.1, 9.2, 9.3, 10.1, A.5.22, A.5.35, A.5.36, A.8.16. OSA's own, not in NIST's crosswalk: 9.2, 10.1, A.5.22, A.5.35, A.8.16
- iso_27002_2022: 5.22, 5.35, 5.36, 8.16
- cobit_2019: APO13, DSS01, MEA01, MEA02, MEA04
- pci_dss_v4: 12.4
- nist_csf_2: DE.AE-02, DE.AE-03, DE.CM-01, DE.CM-02, DE.CM-03, DE.CM-06, DE.CM-09, GV.OV-01, GV.OV-03, GV.PO-02, ID.IM-01, ID.IM-02, ID.IM-03, ID.RA-01, ID.RA-07, PR.PS-04, RC.RP-05. OSA's own, not in NIST's crosswalk: GV.OV-01, GV.OV-03, GV.PO-02, PR.PS-04, RC.RP-05
- cis_controls_v8: CIS 7, CIS 13, CIS 15.6
- soc2_tsc: CC1.1, CC1.1-POF3, CC2.2, CC2.3, CC4.2-POF1, CC4.2-POF2
- finos_ccc: CCC-C08
- iso_42001_2023: A.2.4, A.6.2.6
- iec_62443: 3-3 SR 6.2
- nis2: Art. 21(2)(f), Art. 32
- mas_trm: 7, 12
- pra_op_resilience: SS1/21-7.1, SS2/21-7.1
- bsi_grundschutz: DER.1
- anssi: Hygiene.3, Hygiene.29, Hygiene.31, Hygiene.39, SecNumCloud.13.7, SecNumCloud.19.2
- osfi_b13: B-13.1.3, B-13.3.3, B-13.4.2
- finma_circular: IV.C(66), IV.C(67), IV.C(68), IV.D(75), IV.D(76)
- gdpr: Art.32(1)(d), Art.35(11)
- dora: Art.6(4), Art.10(1), Art.10(2), Art.24(1)
- bio2: 5.22, 5.35, 5.36, 8.16
- rbi_csf: Annex1.21, ITGRCA.21, ITGRCA.30
- fisc: FISC.O2, FISC.O7
- lgpd_bcb: BCB.Art.6, BCB.Art.10, BCB.Art.19, LGPD.Art.50
- hkma_tme1: TME1.2.6, TME1.5.2, TME1.12.3
- mlps_2: 8.1.5.3, 8.1.7.2, 8.1.9.6
- dnb_good_practice: DNB.14.1, DNB.16.1, DNB.16.2
- cbb_tm: TM-5, TM-12, TM-16
- cbuae: CR-3, CR-10, CR-14
- nca_ecc: 1-7, 1-8, 2-12, 5-1
- qatar_nia: GV, OS, RM
- sama_csf: 1.3, 1.9, 2.2
- uae_ia: T7
- bog_cisd: CISD-COMP, CISD-II, CISD-III, CISD-ISMS, CISD-IV, CISD-VII
- bom_ctrm: 1.5, 3.1, 4.2, 5.3, 5.4
- cbe_csf: CD-1, GOV-3, OVM-3
- cbn_csf: Part2.2, Part2.3, Part3.5, Part6.1, Part6.2, Part7.2
- popia: s19
- sa_js2: JS2-7.3, JS2-7.6, JS2-7.7, JS2-9
- bcbs_239: Principle 7, Principle 8, Principle 10, Principle 12
- bot_cyber: Ch1.3, Ch3.1, Ch6.1, Ch10.1
- cpmi_pfmi: CG.DE, CG.LE, PFMI.P3, PFMI.P17
- eba_ict: 3.3.5, 3.3.6, 3.4.5, 3.4.6
- ecb_croe: CROE.2.2.1, CROE.2.4, CROE.2.8.1
- ffiec_is: II.A, II.A.2, II.C.4, II.D, III.A, III.B, IV.A, IV.A.3
- hipaa_sr: §164.308(a)(1)(i), §164.308(a)(1)(ii)(A), §164.308(a)(1)(ii)(B), §164.308(a)(1)(ii)(D), §164.308(a)(7)(ii)(D), §164.308(a)(8), §164.316(b)(2)(iii)
- iosco_cyber: DET-1, DET-2, LE-1, LE-2, SA-3, TEST-1
- nydfs_500: 500.2
- sebi_cscrf: AUDIT, CCI, DE.CM, GV.OV, RS.IM, SOC
- cmmc_2: CA
- nerc_cip: CIP-015-1
- nrc_73_54: 73.54(d), RG5.71-C-CA
- tsa_psd: SD-2 Sec C
- ferc_cip: Order 881, Order 893
- doe_c2m2: SITUATION
- api_1164: Sec 9, Sec 15
- awia: AWWA Sec 4, AWWA Sec 5
- iaea_nss: Sec 5.5, Sec 11
- cbest: CBEST.5, CBEST.7, CBEST.10
- tiber_eu: TIBER.BT, TIBER.REM
- pci_hsm: 10
- common_criteria: CEM
- isae_3402: Clause 2, Clause 5, Clause 6, Clause 10
- fca_sysc_13: SYSC 13.5.3, SYSC 13.7.5, SYSC 13.9.3, SYSC 13.G.3
- fda_21_cfr_11: §11.10(a)
- fda_cyber: 524B-2, 524B-4
- hitrust_csf: 00.b, 00.c, 03.b, 04.b, 06.c, 11.b, 12.c
- iso_27799: 5.2, 18.3
- lloyds_ms: MS8.12, MS10.2
- naic_ds: 4, 4-monitoring, 4A, 4E, 5, 7
- nhs_dspt: NDG-5.1, NDG-7.3, NDG-9.9
- pra_ss1_23: P4.1, P5.2
- solvency_ii: Art.45, Art.46, Art.47, EIOPA-ICT-4.2
- csa_ccm_v4: AA-02, AIS-03, LOG-03, LOG-10, SEF-05, STA-11, TVM-09, TVM-10
- csa_aicm: A&A-02, AIS-03, AIS-12, GRC-12, GRC-15, LOG-03, LOG-10, LOG-15, MDS-05, SEF-05, STA-11, TVM-09, TVM-10, TVM-13
- ccss_v9: 2.01.1, 2.01.3
- mica: Art.34(5), Art.43(1), Art.62(1), Art.94(1)
- basel_sco60: SCO60.5, SCO60.13, SCO60.23, SCO60.50, SCO60.51, SCO60.65, SCO60.71, SCO60.72, SCO60.73, SCO60.74
- bssc: GSP-15, NOS-10
- sec_custody_digital: SEC-CD-10, SEC-CD-13, SEC-CD-14
- dpdpa: Act.8(4), Act.10(2)(c), Rules.6(1)(g), Rules.13(1)-(2), Rules.Sch1.B.12
OSA's mapping for iso_27001_2022 and nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/CA-07
- Clauses only: /api/v1/controls/CA-07?fields=mappings
- Page for people: /controls/ca-07/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.