[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"framework:nist-800-53\u002Fsi-2":3},{"item":4,"lessons":18,"controls":69,"related":100},{"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","si-2","SI-2","Flaw Remediation",1770,"US National Institute of Standards and Technology (NIST)","**What it asks for.** The organisation must find, report and fix flaws in its systems, test security updates for effectiveness and side effects before installing them, install security-relevant updates within a defined time after release, and fold flaw remediation into configuration management.\n\n**In practice.** Good practice is a written patching standard with timelines tied to severity and exploitation status, an inventory that tells you what needs patching, and automated deployment with a short test ring before broad rollout. Auditors expect the standard, patch compliance reports over time, records of tested changes and documented exceptions with compensating controls. This is the same idea as continuous vulnerability management in CIS Control 7 and technical vulnerability management in ISO\u002FIEC 27001 Annex A.\n\n**Common gaps.** Typical gaps are patching operating systems well while third-party applications, firmware and network appliances lag, and exceptions that never expire. Many teams also cannot show how long remediation actually took against their own deadlines.","a. Identify, report, and correct system flaws;\n  b. Test software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation;\n  c. Install security-relevant software and firmware updates within [Assignment: organization-defined time period] of the release of the updates; and\n  d. Incorporate flaw remediation into the organizational configuration management process.\nDiscussion: The need to remediate system flaws applies to all types of software and firmware. Organizations identify systems affected by software flaws, including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security and privacy responsibilities. Organizations consider establishing a controlled patching environment for mission-critical systems. Security-relevant updates include patches, service packs, and malicious code signatures. Organizations also address flaws discovered during assessments, continuous monitoring, incident response activities, and system error handling. By incorporating flaw remediation into configuration management processes, required remediation actions can be tracked and verified.\n\nOrganization-defined time periods for updating security-relevant software and firmware may vary based on a variety of risk factors, including the security category of the system, the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw), the organizational risk tolerance, the mission supported by the system, or the threat environment. Some types of flaw remediation may require more testing than other types. Organizations determine the type of testing needed for the specific type of flaw remediation activity under consideration and the types of changes that are to be configuration-managed. Flaw remediation testing addresses both effectiveness of addressing security issues and for potential side effects on functionality, system and system component performance and operations. When implementing remediation activities, organizations consider the order and timing of updates to validate correct execution within the system environment, and to support system and component availability needs (i.e., implementing a staggered deployment strategy). In some situations, organizations may determine that the testing of software or firmware updates is not necessary or practical, such as when implementing simple malicious code signature updates. In testing decisions, organizations consider whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures.\n\nWhen implementing remediation activities, organizations consider the order and timing of updates to validate correct execution within the system environment, and to support system and component availability needs (i.e., implementing a staggered deployment strategy). Organizations verify that software and firmware updates come from authorized sources prior to downloading.","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":19,"list":20},1771,[21,25,29,33,37,41,45,49,53,57,61,65],{"slug":22,"title":23,"published_at":24},"greek-authority-fined-for-unlawful-publication-of-personal-data-on-transparency-portal","Greek Authority Fined for Unlawful Publication of Personal Data on Transparency Portal","2026-10-18T20:20:25.794+00:00",{"slug":26,"title":27,"published_at":28},"siteguard-waf-os-command-injection-exploited-for-root-access","SiteGuard WAF OS Command Injection Exploited for Root Access","2026-10-18T16:20:26.047+00:00",{"slug":30,"title":31,"published_at":32},"critical-drupal-rce-flaws-demand-immediate-patching","Critical Drupal RCE Flaws Demand Immediate Patching","2026-10-17T16:20:34.593+00:00",{"slug":34,"title":35,"published_at":36},"critical-beyondtrust-auth-bypass-actively-exploited-patch-immediately","Critical BeyondTrust Auth Bypass Actively Exploited — Patch Immediately","2026-10-16T22:21:05.267+00:00",{"slug":38,"title":39,"published_at":40},"critical-magento-rce-flaw-demands-immediate-patching","Critical Magento RCE Flaw Demands Immediate Patching","2026-10-16T22:20:34.131+00:00",{"slug":42,"title":43,"published_at":44},"beyondtrust-zero-day-highlights-critical-risk-of-unpatched-edge-devices","BeyondTrust Zero-Day Highlights Critical Risk of Unpatched Edge Devices","2026-10-16T22:20:18.59+00:00",{"slug":46,"title":47,"published_at":48},"active-exploitation-of-fortinet-and-beyondtrust-flaws-highlights-patch-urgency","Active Exploitation of Fortinet and BeyondTrust Flaws Highlights Patch Urgency","2026-10-16T20:21:00.599+00:00",{"slug":50,"title":51,"published_at":52},"openbsd-root-exploit-chains-decades-old-bug-to-bypass-kernel-protections","OpenBSD Root Exploit Chains Decades-Old Bug to Bypass Kernel Protections","2026-10-16T20:20:45.22+00:00",{"slug":54,"title":55,"published_at":56},"chinese-espionage-group-exploits-beyondtrust-zero-day-in-remote-support-tool","Chinese Espionage Group Exploits BeyondTrust Zero-Day in Remote Support Tool","2026-10-16T18:20:52.789+00:00",{"slug":58,"title":59,"published_at":60},"claude-code-desktop-flaw-enabled-html-based-credential-theft","Claude Code Desktop Flaw Enabled HTML-Based Credential Theft","2026-10-16T18:20:18.997+00:00",{"slug":62,"title":63,"published_at":64},"chinese-apt-exploits-beyondtrust-zero-day-to-harvest-credentials-and-exfiltrate-data","Chinese APT Exploits BeyondTrust Zero-Day to Harvest Credentials and Exfiltrate Data","2026-10-16T12:20:53.961+00:00",{"slug":66,"title":67,"published_at":68},"vodafone-spain-fined-400k-after-ignoring-known-vulnerability-for-months","Vodafone Spain Fined €400K After Ignoring Known Vulnerability for Months","2026-10-16T12:20:31.802+00:00",[70,75,80,85,90,95],{"slug":71,"name":72,"problem":73,"stories":74},"patch-management","Automated patch management","Known holes get closed in days, not months.",1494,{"slug":76,"name":77,"problem":78,"stories":79},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",1160,{"slug":81,"name":82,"problem":83,"stories":84},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",573,{"slug":86,"name":87,"problem":88,"stories":89},"network-segmentation","Network segmentation and microsegmentation","One compromised machine can no longer reach everything else.",195,{"slug":91,"name":92,"problem":93,"stories":94},"privileged-access-management","Privileged access management (PAM)","Admin accounts stop being one stolen password away from control of everything.",191,{"slug":96,"name":97,"problem":98,"stories":99},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them.",190,[101,107,112,117,123,128,134,139],{"family":102,"item":103,"code":104,"title":105,"together":106},"cis","7","Control 7","Continuous Vulnerability Management",1723,{"family":108,"item":109,"code":110,"title":110,"together":111},"itil","overview","ITIL",1041,{"family":102,"item":113,"code":114,"title":115,"together":116},"12","Control 12","Network Infrastructure Management",905,{"family":118,"item":119,"code":120,"title":121,"together":122},"nist-sp","800-40","SP 800-40","SP 800-40 Rev. 4: Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology",679,{"family":5,"item":124,"code":125,"title":126,"together":127},"ra-5","RA-5","Vulnerability Monitoring and Scanning",640,{"family":129,"item":130,"code":131,"title":132,"together":133},"gdpr","32","Article 32","Security of processing",522,{"family":102,"item":135,"code":136,"title":137,"together":138},"2","Control 2","Inventory and Control of Software Assets",467,{"family":5,"item":140,"code":141,"title":142,"together":143},"sc-7","SC-7","Boundary Protection",400]