# NIST SP 800-53 Rev. 5 CM-11(1) — Alerts For Unauthorized Installations - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-11-1-alerts-for-unauthorized-installations - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › CM — Configuration Management - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `CM-11(1)`·medium·Component: **Configuration Management** ## What this control requires > Monitor and alert for unauthorized software installations using tools to detect and notify designated personnel, ensuring compliance and minimizing risks from malicious software. This control supports the Endpoint Detection and Response capability within the Configuration Management family. > > — NIST SP 800-53 Rev. 5, Control CM-11(1) ### In plain English Monitor and alert for unauthorized software installations using tools to detect and notify designated personnel, ensuring compliance and minimizing risks from malicious software. In practice, this means you can prove you security management-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **Configuration Management**, the assessor will trace your implementation back to the catalogue reference (Control CM-11(1)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Endpoint Protection **MDM.** Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token. **EDR.** Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h. #### Logging Monitoring **AWS.** Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation. **Azure.** Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR. **GCP.** Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM. ### Operational checklist - **Security.** Document the trigger, the owner and the cadence. - **Configuration.** Document the trigger, the owner and the cadence. - **Detection.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **Response.** Document the trigger, the owner and the cadence. - **Scope:** management, personnel, threat, alerts, protection, monitor, configuration, software. ## Evidence to collect - **Edr Scan.** `edr_scan` evidence EDR telemetry (CrowdStrike, Defender for Endpoint) confirms threat detection. Focus: Alerts For Unauthorized Installations. ## Common pitfalls - Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure. - Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days. ## Related controls in NIST SP 800-53 Rev. 5 - [**Control CM-8(9)** — Assignment Of Components To Systems](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-8-9-assignment-of-components-to-systems) - [**Control SI-15** — Information Output Filtering](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-15-information-output-filtering) - [**Control CM-8(1)** — Updates During Installation And Removal](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-8-1-updates-during-installation-and-removal) - [**Control SI-4(14)** — Wireless Intrusion Detection](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-4-14-wireless-intrusion-detection) - [**Control RA-3(4)** — Predictive Cyber Analytics](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ra-3-4-predictive-cyber-analytics) - [**Control CM-8(2)** — Automated Maintenance](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-8-2-automated-maintenance) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control CM-11(1)` Topics: endpoint securityedr xdrendpoint protectionlogging monitoringthreat intelligence ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [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): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.