FedRAMP High
RA - Risk Assessment

FedRAMP High RA-5: Vulnerability Monitoring and Scanning

Scan for vulnerabilities monthly (FedRAMP); OS/network weekly, web app monthly, database monthly; remediate within FedRAMP timeframes (HIGH critical 15d, high 30d).

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

What else in your programme already covers this

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

PCI DSS 4.0 · 10 controls

  • 11.3.1 Internal vulnerability scans quarterly
  • 11.3.1.1 Address non-high vulnerabilities per TRA
  • 11.3.1.2 Authenticated internal scans
  • 11.3.1.3 Internal scans after significant changes
  • 11.3.2 External vulnerability scans quarterly by ASV
  • 11.3.2.1 External scans after significant change
  • 12.6.1 Formal security awareness program implemented
  • 6.4.1 For public-facing web applications, new threats and vulnerabilities are addressed on an ongoing basis and these applications are protected against known attacks as follows: • Reviewing public-facing web applications via manual or automated application
  • 6.3.1 Security vulnerabilities are identified and managed as follows: • New security vulnerabilities are identified using industry-recognized sources for security vulnerability information, including alerts from international and national computer emergency response teams (CERTs). • Vulnerabilities
  • 6.3.3 All system components are protected from known vulnerabilities by installing applicable security patches/updates as follows: • Patches/updates for critical vulnerabilities (identified according to the risk ranking process at Requirement 6.3.1) are installed within one

CIS Controls v8 · 7 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.5 Use Up-to-Date and Trusted Third-Party Software Components
  • CIS-16.6 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities
  • CIS-7.1 Establish and Maintain a Vulnerability Management Process
  • CIS-7.5 Perform Automated Vulnerability Scans of Internal Enterprise Assets
  • CIS-7.6 Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets
  • CIS-7.7 Remediate Detected Vulnerabilities

C5 (Germany) · 4 controls

  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept
  • C5-OPS-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests
  • C5-OPS-22 Testing and Documentation of known Vulnerabilities
  • C5-PSS-02 Identification of Vulnerabilities of the Cloud Service

ACSC Essential Eight · 3 controls

  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
  • NIST-CSF-ID.RA-03 Internal and external threats to the organization are identified and recorded

NIST SP 800-218 · 3 controls

  • ASD37-02 Patch applications (Essential)
  • ASD37-19 Patch operating systems (Essential)
  • DS-2 Ensure software supply chain security
  • PV-5 Perform vulnerability assessments

CMMC 2.0 · 2 controls

DORA · 2 controls

ISO 27701:2019 · 2 controls

  • 6.15.2 Information security reviews
  • 6.9.6 Technical vulnerability management

NIST SP 800-53 Rev 5 · 2 controls

  • ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions

APRA CPS 234 · 1 control

  • CPS234-P17 Active Maintenance of Capability Against Change
  • AUCDR-IS-4 Formal vulnerability management program

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 1 control

  • 8.8 Management of technical vulnerabilities
  • 03.11.02 Vulnerability Monitoring and Scanning

NIST SP 800-172 · 1 control

  • 3.12.1e Penetration Testing by Independent Agents

SOC 2 · 1 control

  • SOC2-CC7.1 Detection and monitoring procedures for security events are in place

UK Cyber Essentials · 1 control

  • CE-SU.3 Critical and High Updates within 14 Days

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 RA - Risk Assessment

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

FedRAMP High RA-5 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 63 it maps to, and the evidence behind each claim, over MCP and REST.