| name | CA-7_continuous-monitoring |
| description | Develop a system-level continuous monitoring strategy and implement continuous monitoring in accordance with the organization-level continuous monitor |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","ca-7","ca"] |
| tech_stack | ["any"] |
| cwe_ids | [] |
| chains_with | ["AC-2","AC-6","AC-17","AT-4","AU-6","AU-13","CA-2","CA-5","CA-6","CM-3"] |
| prerequisites | [] |
| severity_boost | {"AC-2":"Chain with AC-2 for comprehensive security coverage","AC-6":"Chain with AC-6 for comprehensive security coverage","AC-17":"Chain with AC-17 for comprehensive security coverage"} |
CA-7 Continuous Monitoring
High-Level Description
Family: Assessment, Authorization, and Monitoring (CA)
Framework: NIST SP 800-53 Rev 5
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-2g, AC-2(7), AC-2(12)(a), AC-2(7)(b), AC-2(7)(c), AC-17(1), AT-4a, AU-13, AU-13(1), AU-13(2), CM-3f, CM-6d, CM-11c, IR-5, MA-2b, MA-3a, MA-4a, PE-3d, PE-6, PE-14b, PE-16, PE-20, PM-6, PM-23, PM-31, PS-7e, SA-9c, SR-4, SC-5(3)(b), , , , , and .
