FedRAMP High
CA - Assessment, Authorization, and Monitoring

FedRAMP High CA-7(4): Continuous Monitoring | Risk Monitoring (CA-7(4))

Continuous Monitoring | Risk Monitoring. Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes the following: (a) Effectiveness monitoring; (b) Compliance monitoring; and (c) Change monitoring

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events
  • NIST-CSF-GV.OV-03 Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed
  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
  • NIST-CSF-ID.RA-08 Processes for receiving, analyzing, and responding to vulnerability disclosures are established
  • NIST-CSF-ID.RA-09 The authenticity and integrity of hardware and software are assessed prior to acquisition and use

CIS Controls v8 · 5 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-15.5 Assess Service Providers
  • CIS-15.6 Monitor Service Providers
  • CIS-7.1 Establish and Maintain a Vulnerability Management Process
  • CIS-8.2 Collect Audit Logs

NIST SP 800-53 Rev 5 · 5 controls

SOC 2 · 4 controls

  • SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

PCI DSS 4.0 · 2 controls

  • 11.4.6 11.4.6 Service provider segmentation testing every six months
  • 12.3.2 12.3.2 Targeted risk analysis for each customized-approach requirement
  • CPS220-P47 Minimum Assessment Required by the Framework Review
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities
  • CFTC-SS-2 Enterprise Risk Management and Governance Category

CMMC 2.0 · 1 control

ISO 27002:2022 · 1 control

  • 5.36 Compliance with policies, rules and standards for information security

NIS2 Directive · 1 control

  • Art.21.2.f Policies and procedures to assess the effectiveness of the cybersecurity risk-management measures

NIST SP 800-172 · 1 control

  • 3.14.2e Monitor Organizational Systems with Specialized Capabilities
  • CA-7(4) CA-7(4) Continuous Monitoring | Risk Monitoring
  • CA-7(4) CA-7(4) Continuous Monitoring | Risk Monitoring
  • CA-7(4) CA-7(4) Continuous Monitoring | Risk Monitoring
  • 53A-3.4 Analyze Assessment Report Results

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.

Other controls in CA - Assessment, Authorization, and Monitoring

You are reading one control. How much of FedRAMP High have you already done?

FedRAMP High CA-7(4) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High controls already carry evidence.

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. 6 were rejected on the C5 (Germany) pair alone.

Query this from an agent

The graph holds this control, the 37 it maps to, and the evidence behind each claim, over MCP and REST.