[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"framework:nist-800-53\u002Fca-7":3},{"item":4,"lessons":18,"controls":68,"related":98},{"family":5,"item":6,"code":7,"title":8,"citations":9,"publisher":10,"summary_md":11,"official_text":12,"official_attribution":13,"official_url":14,"link_label":15,"note":16,"updated_at":17},"nist-800-53","ca-7","CA-7","Continuous Monitoring",55,"US National Institute of Standards and Technology (NIST)","**What it asks for.** The organisation must develop a continuous monitoring strategy and run a programme that defines metrics, monitoring and assessment frequencies, ongoing control assessments, correlation and analysis of results, response actions and reporting of security and privacy status.\n\n**In practice.** Doing this well means choosing a set of meaningful metrics, such as patch latency, MFA coverage, critical vulnerability age and control test results, collecting them automatically where possible and reporting them to management on a regular cycle. Auditors expect the monitoring strategy, dashboards or reports, and evidence that poor results led to action. This supports the ongoing evaluation expected by ISO\u002FIEC 27001 clause 9 and NIS2 governance duties.\n\n**Common gaps.** Many programmes report activity counts rather than control effectiveness. Metrics are collected but not linked to decisions or remediation.","Develop a system-level continuous monitoring strategy and implement continuous monitoring in accordance with the organization-level continuous monitoring strategy that includes:\n  a. Establishing the following system-level metrics to be monitored: [Assignment: organization-defined system-level metrics];\n  b. Establishing [Assignment: organization-defined frequencies] for monitoring and [Assignment: organization-defined frequencies] for assessment of control effectiveness;\n  c. Ongoing control assessments in accordance with the continuous monitoring strategy;\n  d. Ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy;\n  e. Correlation and analysis of information generated by control assessments and monitoring;\n  f. Response actions to address results of the analysis of control assessment and monitoring information; and\n  g. Reporting the security and privacy status of the system to [Assignment: organization-defined organization-defined personnel or roles] [Assignment: organization-defined organization-defined frequency].\nDiscussion: 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.\n\nAutomation 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_smt.g), [AC-2(7)](#ac-2.7), [AC-2(12)(a)](#ac-2.12_smt.a), [AC-2(7)(b)](#ac-2.7_smt.b), [AC-2(7)(c)](#ac-2.7_smt.c), [AC-17(1)](#ac-17.1), [AT-4a](#at-4_smt.a), [AU-13](#au-13), [AU-13(1)](#au-13.1), [AU-13(2)](#au-13.2), [CM-3f](#cm-3_smt.f), [CM-6d](#cm-6_smt.d), [CM-11c](#cm-11_smt.c), [IR-5](#ir-5), [MA-2b](#ma-2_smt.b), [MA-3a](#ma-3_smt.a), [MA-4a](#ma-4_smt.a), [PE-3d](#pe-3_smt.d), [PE-6](#pe-6), [PE-14b](#pe-14_smt.b), [PE-16](#pe-16), [PE-20](#pe-20), [PM-6](#pm-6), [PM-23](#pm-23), [PM-31](#pm-31), [PS-7e](#ps-7_smt.e), [SA-9c](#sa-9_smt.c), [SR-4](#sr-4), [SC-5(3)(b)](#sc-5.3_smt.b), [SC-7a](#sc-7_smt.a), [SC-7(24)(b)](#sc-7.24_smt.b), [SC-18b](#sc-18_smt.b), [SC-43b](#sc-43_smt.b) , and [SI-4](#si-4).","From NIST SP 800-53 Rev. 5, a work of the US government in the public domain.","https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Fsp\u002F800\u002F53\u002Fr5\u002Fupd1\u002Ffinal","Open SP 800-53 at NIST",null,"2026-10-18T15:18:43.663+00:00",{"total":9,"list":19},[20,24,28,32,36,40,44,48,52,56,60,64],{"slug":21,"title":22,"published_at":23},"pwnescape-linux-kernel-flaw-allows-guest-vms-to-read-host-memory","PwnEscape: Linux Kernel Flaw Allows Guest VMs to Read Host Memory","2026-10-15T22:20:53.307+00:00",{"slug":25,"title":26,"published_at":27},"unpatched-contractor-system-leads-to-mass-fbi-personnel-data-breach","Unpatched Contractor System Leads to Mass FBI Personnel Data Breach","2026-10-09T20:20:40.03+00:00",{"slug":29,"title":30,"published_at":31},"shinyhunters-exploits-third-party-vendor-zero-day-to-breach-fbi-systems","ShinyHunters Exploits Third-Party Vendor Zero-Day to Breach FBI Systems","2026-10-09T18:20:41.265+00:00",{"slug":33,"title":34,"published_at":35},"unpatched-ahsaycbs-backup-flaws-weaponized-for-crypto-mining","Unpatched AhsayCBS Backup Flaws Weaponized for Crypto Mining","2026-10-09T12:20:56.625+00:00",{"slug":37,"title":38,"published_at":39},"flax-typhoon-iot-botnet-targets-critical-infrastructure-via-unpatched-vulnerabilities","Flax Typhoon IoT Botnet Targets Critical Infrastructure via Unpatched Vulnerabilities","2026-10-09T08:21:29.924+00:00",{"slug":41,"title":42,"published_at":43},"poellm-botnet-exploits-exposed-ai-infrastructure-to-mine-crypto-on-3400-servers","PoeLLM Botnet Exploits Exposed AI Infrastructure to Mine Crypto on 3,400+ Servers","2026-10-07T18:21:48.858+00:00",{"slug":45,"title":46,"published_at":47},"critical-buffer-overflow-in-lwip-smtp-client-threatens-critical-infrastructure","Critical Buffer Overflow in lwIP SMTP Client Threatens Critical Infrastructure","2026-10-06T19:20:21.791+00:00",{"slug":49,"title":50,"published_at":51},"unpatched-oracle-peoplesoft-system-enables-shinyhunters-breach-via-fbi-contractor","Unpatched Oracle PeopleSoft System Enables ShinyHunters Breach via FBI Contractor","2026-10-06T18:20:56.804+00:00",{"slug":53,"title":54,"published_at":55},"netscaler-fortimail-0-days-exploited-amid-ransomware-arrests","NetScaler & FortiMail 0-Days Exploited Amid Ransomware Arrests","2026-10-05T16:22:03.667+00:00",{"slug":57,"title":58,"published_at":59},"clingstun-linux-backdoor-exploits-dozens-of-flaws-via-stealthy-stun-protocol","ClingSTUN Linux Backdoor Exploits Dozens of Flaws via Stealthy STUN Protocol","2026-10-05T14:20:55.456+00:00",{"slug":61,"title":62,"published_at":63},"warlock-exploits-unpatched-sharepoint-to-deploy-ransomware-via-lotl-techniques","Warlock Exploits Unpatched SharePoint to Deploy Ransomware via LotL Techniques","2026-10-03T16:20:37.796+00:00",{"slug":65,"title":66,"published_at":67},"antino-backdoor-abuses-microsoft-365-for-stealthy-c2-in-asia-espionage-campaign","Antino Backdoor Abuses Microsoft 365 for Stealthy C2 in Asia Espionage Campaign","2026-10-02T18:20:59.758+00:00",[69,74,79,84,89,94],{"slug":70,"name":71,"problem":72,"stories":73},"patch-management","Automated patch management","Known holes get closed in days, not months.",33,{"slug":75,"name":76,"problem":77,"stories":78},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",27,{"slug":80,"name":81,"problem":82,"stories":83},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",22,{"slug":85,"name":86,"problem":87,"stories":88},"network-segmentation","Network segmentation and microsegmentation","One compromised machine can no longer reach everything else.",8,{"slug":90,"name":91,"problem":92,"stories":93},"identity-threat-detection","Identity threat detection and response (ITDR)","Attackers who log in with real, stolen credentials get noticed.",7,{"slug":95,"name":96,"problem":97,"stories":93},"ot-security","OT and industrial control system security","Factory, building and utility control systems get visibility and protection.",[99,105,110,115,120,125,131,136],{"family":100,"item":101,"code":102,"title":103,"together":104},"cis","7","Control 7","Continuous Vulnerability Management",42,{"family":100,"item":106,"code":107,"title":108,"together":109},"12","Control 12","Network Infrastructure Management",40,{"family":5,"item":111,"code":112,"title":113,"together":114},"si-2","SI-2","Flaw Remediation",36,{"family":100,"item":116,"code":117,"title":118,"together":119},"13","Control 13","Network Monitoring and Defense",30,{"family":121,"item":122,"code":123,"title":123,"together":124},"itil","overview","ITIL",29,{"family":126,"item":127,"code":128,"title":129,"together":130},"nist-sp","800-40","SP 800-40","SP 800-40 Rev. 4: Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology",21,{"family":5,"item":132,"code":133,"title":134,"together":135},"sc-7","SC-7","Boundary Protection",20,{"family":137,"item":138,"code":139,"title":140,"together":141},"gdpr","32","Article 32","Security of processing",17]