# NIST800 171 3.11.2 — Vulnerability Monitoring and Scanning

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_nist800171_3112_dae543d842-nist800-171-3112-vulnerability-monitoring-and-scanning
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [NIST SP 800-171 Readiness](https://support.icompaas.com/support/solutions/c_gen_nist800171) › [Risk Assessment](https://support.icompaas.com/support/solutions/folders/f_gen_cgennist800171_riskassessment)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

NIST800 171 · Control 3.11.2 · Priority: critical · Component: Risk Assessment

### What this control covers

This control mandates monitoring and scanning the system for vulnerabilities at defined intervals and when new vulnerabilities are identified. It includes remediating vulnerabilities within specified response times and updating the system's vulnerability scanning practices to reflect newly discovered vulnerabilities. This control supports the Vulnerability Scanning capability within the Risk Assessment (3.11) family.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

**VM Manager** (OS patch + config management) and **Artifact Registry vulnerability scanning** integrate with Cloud Build to block vulnerable images.

#### Google Workspace

Forward the **Admin, Login, Drive, Token and Mobile** audit logs to Cloud Logging (Workspace BigQuery export). Alert on impossible-travel logins, OAuth-scope grants for high-risk scopes, and external Drive sharing of sensitive labels.

#### GitHub

**Dependabot** security updates + version updates, plus **CodeQL** for SAST and a renovate bot for major-version drift management.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `vapt_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Pen-test and vulnerability scan reports substantiate attack-surface coverage. Focus: Vulnerability Monitoring and Scanning.

### Quick checklist

-   Response — Management / Assessment
-   System — Management / Assessment
-   Risk — Management / Assessment

### Related articles on this site

-   [NIST 800-171 3.11.2 Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.](https://support.icompaas.com/support/solutions/articles/62000229328-nist-800-171-3-11-2-scan-for-vulnerabilities-in-organizational-systems-and-applications-periodically-)
-   [CMMC 2.0 RM.2.142 Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.](https://support.icompaas.com/support/solutions/articles/62000229710-cmmc-2-0-rm-2-142-scan-for-vulnerabilities-in-organizational-systems-and-applications-periodically-an)
-   [Ensure Track All Code Changes Using a Version Control System](https://support.icompaas.com/support/solutions/articles/62000234895-ensure-track-all-code-changes-using-a-version-control-system)
-   [Ensure Implement Automated Code Vulnerability Scanning](https://support.icompaas.com/support/solutions/articles/62000235045-ensure-implement-automated-code-vulnerability-scanning)

## Related compliance guidance

- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): The CUI requirements CMMC Level 2 assesses, the SPRS score, POA&M rules and the phased DFARS rollout.
- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): The federal catalogue 800-171 is derived from — useful when a contract also cites a FedRAMP baseline.