@blamejs/exceptd-skills 0.19.19 → 0.19.20

package/data/zeroday-lessons.json

@@ -24960,7 +24960,7 @@
     "name": "D-Link DCS-2530L and DCS-2670L Devices Unspecified Vulnerability",
     "lesson_date": "2026-05-29",
     "attack_vector": {
-      "description": "an unauthenticated code-execution flaw (CWE-94) on the D-Link DCS-2530L/2670L network cameras. CISA KEV-listed 2025-08-05 with confirmed in-the-wild exploitation.",
+      "description": "an unauthenticated information-disclosure flaw on the D-Link DCS-2530L/2670L network cameras: the /config/getuser endpoint answers without authentication and returns the administrator password. CISA KEV-listed 2025-08-05 with confirmed in-the-wild exploitation.",
       "privileges_required": "none (unauthenticated network reach to the device/service)",
       "complexity": "low — KEV-listed, actively exploited; treat as weaponized",
       "ai_factor": "No AI involvement documented in discovery or weaponization."
@@ -24973,7 +24973,7 @@
         "adequacy": "Patch/replace is definitive; the gap is that the affected class is internet-exposed by function and (for consumer/EoL devices) often unpatchable, so network isolation is the load-bearing control."
       },
       "detection": {
-        "what_would_have_worked": "Monitoring for the IP camera web interface: exploit-shaped requests, device crashes/reboots, malicious firmware, and outbound botnet/C2 traffic from the device.",
+        "what_would_have_worked": "Monitoring the IP camera web interface for unauthenticated requests to /config/getuser from anything other than a known administration host, and for use of the camera administrator password on other systems — the flaw returns that credential without authentication, so its reuse elsewhere is the observable consequence.",
         "was_this_required": false,
         "framework_requiring_it": null,
         "adequacy": "Necessary to catch exploitation of devices not yet patched/replaced; edge devices are frequently recruited into botnets."
@@ -25014,7 +25014,39 @@
     },
     "ai_discovered_zeroday": false,
     "ai_discovery_source": "vendor_research",
-    "ai_assist_factor": "none"
+    "ai_assist_factor": "none",
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "Both framework gaps recorded against this D-Link camera entry are timing gaps — a 30-day flaw-remediation SLA, and an \"appropriate timescales\" phrase the packet calls undefined — applied to an internet-facing device whose flaw discloses the remote administrator password and which CISA KEV-listed on 2025-08-05 with confirmed exploitation and a public proof of concept. This control binds the response to the KEV clock instead of the patch cycle: from the listing date, every DCS-2530L and DCS-2670L must carry a verified mitigation, meaning the vendor firmware for that model and hardware revision where one exists, or documented isolation of the camera from untrusted networks where it does not. The packet gives affected_versions only as \"versions per vendor advisory\", so the fixed level has to be read from the vendor advisory this entry references for that exact model rather than inferred from a version comparison — there is no version string in the packet to compare against. Completion is measured on the running unit, not on the management console: live_patch_available is false and the packet records that the vendor patch typically requires a service restart or system reboot per the KEV requiredAction, so a camera that has received firmware but has not restarted onto it is still executing the vulnerable code and counts as exposed. Distinguishing test: for each camera produce the firmware version the unit itself reports after its restart, alongside the fixed level named in the vendor advisory — a fleet report showing the update as pushed or scheduled satisfies a 30-day SLA attestation while cameras that never restarted keep the administrator-password disclosure path open.",
+        "evidence": "Packet fields: cisa_kev true with kev_date 2025-08-05, active_exploitation confirmed, poc_available true, cvss 7.5, rwep_score 67, CWE-200; patch_available true, patch_required_reboot true, live_patch_available false; live_patch_notes — \"No live-patch tool registered for this entry at bulk-import time. Vendor patch typically requires service restart or system reboot per the KEV requiredAction.\" affected/affected_versions: \"D-Link DCS-2530L and DCS-2670L Devices — versions per vendor advisory\". vector: the devices contain a vulnerability that could allow for remote administrator password disclosure. framework_control_gaps: NIST-800-53-SI-2 — \"30-day flaw-remediation SLA inadequate for CISA-KEV-listed actively-exploited CVE. CISA due date is the operationally-meaningful clock — typically 14-21 days for new KEV listings\"; ISO-27001-2022-A.8.8 — the standard \"does not differentiate between routinely-disclosed CVEs and actively-exploited KEV-listed CVEs\", and framework_coverage records \"'Appropriate timescales' is undefined; the standard 30-day reading is unsafe for an unauthenticated, actively-exploited flaw on an internet-facing device\".",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "ISO-27001-2022-A.8.8"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-122",
+        "name": "EOL-ASSET-DECOMMISSION",
+        "description": "The packet states both halves this control turns on. patch_available is true, so a fixed firmware exists for this flaw; and the entry's own vector states the impacted products could be end-of-life and/or end-of-service and that users should discontinue product utilization, with the Essential Eight, UK CAF and NIS2 gaps all recording these D-Link cameras as end-of-life hardware for which retirement or isolation, not patching, is the complete action. Together those define the requirement: on a DCS-2530L or DCS-2670L whose hardware revision still has firmware carrying this fix, reaching that build is an interim state; on a unit with no fixed firmware, and on every unit once the model leaves vendor service, the terminal state is removal or replacement, because the camera then stands exposed not only to this administrator-password disclosure but to everything found in that firmware since its last build. Scope to what the packet names — DCS-2530L and DCS-2670L — and inventory those two models; the packet ties this credential-disclosure flaw to them and gives no mapping into other D-Link camera lines or other vendors' cameras, so treating every IP camera in the estate as an instance of this CVE manufactures replacement work against hardware no evidence implicates. Operationally: enumerate both models, record per unit whether the vendor advisory lists a fixed firmware for that hardware revision, put those units on the interim clock that opened with the 2025-08-05 KEV listing, and put the rest on a dated replacement schedule — a risk acceptance with no removal date leaves a device with a public proof of concept and confirmed exploitation in service indefinitely. Precondition on the interim half: no live-patch path is registered and the vendor fix typically requires a service restart or system reboot, so a unit updated but not restarted is not remediated. Precondition on the isolation half, which is the compensating measure the network-security gap describes: reachability has to be verified from an untrusted network and from outside, because a consumer camera commonly acquires its exposure through a port forward or UPnP mapping the topology diagram does not show, and \"the cameras are on the internal network\" is an assertion rather than a demonstration.",
+        "evidence": "Packet fields: vector — \"D-Link DCS-2530L and DCS-2670L devices contains an unspecified vulnerability that could allow for remote administrator password disclosure. The impacted products could be end-of-life (EoL) and/or end-of-service (EoS). Users should discontinue product utilization.\" patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes records the vendor patch typically requires service restart or system reboot per the KEV requiredAction; affected_versions only \"versions per vendor advisory\"; CWE-200; poc_available true; cisa_kev true with kev_date 2025-08-05 and active_exploitation confirmed. framework_control_gaps: AU-Essential-8-Patch — \"The patch pillar is moot for EoL/EoS D-Link cameras with no available firmware; only device replacement remediates, which Essential-Eight patching does not mandate\"; UK-CAF-B4 — \"Hardening cannot patch an end-of-life camera; the only compliant action is retirement\"; NIS2-Art21-network-security — \"Network-security measures must compensate for an end-of-life IP camera with no vendor fix, yet Article 21 doesn't compel decommissioning or isolating the internet-exposed DCS-2530L/2670L whose admin password is remotely disclosable.\"",
+        "gap_closes": [
+          "AU-Essential-8-Patch",
+          "UK-CAF-B4",
+          "NIS2-Art21-network-security"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-032",
+        "name": "PERIMETER-COMPROMISE-REBUILD-NOT-PATCH",
+        "description": "Scope what this control is for on this entry, because the primitive bounds it: the verified flaw is administrator-password disclosure from an unauthenticated endpoint on the DCS-2530L/2670L cameras, not code execution on them, so reachability during the exposure window is evidence that the credential could have been taken — not evidence that anything ran on the device. The framework gaps record the devices as internet-facing and internet-exposed, exploitation is confirmed and a proof of concept is public. What makes the control load-bearing rather than redundant here is the outcome the vector names — remote administrator password disclosure. Firmware that closes the disclosure path does not invalidate a credential already taken, so patch-in-place is the wrong default for any camera that was reachable from an untrusted network during the exposure window that opened before the 2025-08-05 KEV listing. Such a unit is handled as compromised rather than updated: reset it to a factory state and rebuild the configuration from a known-good record instead of carrying the existing configuration across the update, set a new administrative credential rather than restoring the previous one, and where the same administrative password was configured on other units, treat the disclosure from one as a credential for the rest and rotate accordingly. This is also why the least-privilege control cited against this entry passes its attestation while the exposure stands: the attacker never authenticates as any camera operator, so per-account privilege scoping is never consulted and the account model an access-control attestation examines is bypassed rather than abused; what failed is the authentication boundary itself, and the operator-side repair for that is credential replacement, not privilege reduction. Preconditions: rebuild presupposes a fixed firmware for that hardware revision to rebuild onto — where the packet's end-of-life statement means none exists for the model, the unit is a removal item and the credential rotation still has to happen; and a factory reset removes the device's own state, not an attacker's continued access to whatever the disclosed credential opens elsewhere, which has to be scoped and revoked separately. What follows from the disclosed credential rather than from execution: rotate the administrator password on every reachable unit and everywhere that password was reused, and treat the camera as replaceable rather than recoverable where its firmware cannot be brought to a build carrying the fix. A full rebuild is warranted where separately verified indicators of compromise exist on the unit — this CVE alone does not supply them, and recording it as though it did would spend replacement budget on evidence the entry does not carry.",
+        "evidence": "Packet fields: attack_vector — \"an unauthenticated information-disclosure flaw on the D-Link DCS-2530L/2670L network cameras: the /config/getuser endpoint answers without authentication and returns the administrator password. CISA KEV-listed 2025-08-05 with confirmed in-the-wild exploitation.\" vector — the devices contain a vulnerability that could allow for remote administrator password disclosure, and the impacted products could be end-of-life and/or end-of-service with users advised to discontinue product utilization. poc_available true; active_exploitation confirmed; patch_available true with patch_required_reboot true and live_patch_available false. framework_control_gaps: NIST-800-53-AC-6 — \"Least-privilege presumes a working authentication / authorization boundary. The KEV-listed exploit demonstrates the boundary is breakable from a baseline context\"; NIS2-Art21-network-security and ISO-27001-2022-A.8.8 both describe the affected units as internet-exposed / internet-facing devices.",
+        "gap_closes": [
+          "NIST-800-53-AC-6"
+        ]
+      }
+    ]
   },
   "CVE-2020-25079": {
     "name": "D-Link DCS-2530L and DCS-2670L Command Injection Vulnerability",
@@ -25823,7 +25855,38 @@
     },
     "ai_discovered_zeroday": false,
     "ai_discovery_source": "vendor_research",
-    "ai_assist_factor": "none"
+    "ai_assist_factor": "none",
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-042",
+        "name": "INCOMPLETE-PATCH-SEQUENCE-SEVERITY-MULTIPLIER",
+        "description": "The packet states the sequence outright: CVE-2025-53770 is a patch bypass for this CVE, and the updates for CVE-2025-53770 include more robust protection than the ones shipped for CVE-2025-49704. That makes this the first fix in an incomplete-patch sequence on the same SharePoint code-injection sink, and it explains the outcome the packet's Essential Eight gap records — an estate that met its patch cadence was still exposed, because the cadence was measured against a fix that had been defeated. Bound to this product, the requirement is that the vulnerability-management record for a SharePoint farm is not closed on the 49704 update: the target state is the build carrying the hardened 53770 protection, the risk score carried against the farm reflects that a bypass of the first fix already exists rather than the discrete rating of one entry, and any further defect announced against the same injection sink is triaged on the assumption that the sink rather than the individual entry point is the defect. The chain feeds the same judgement — the packet records this CVE as chainable with CVE-2025-49706, and its own attack-vector summary describes the chained result as unauthenticated remote code execution, so the 'authorized attacker' framing in the vendor text understates what the farm is actually exposed to and should not be used to down-rank it. Precondition: this control governs how the flaw is scored and tracked and deploys nothing. It reduces no exposure on a farm that has taken neither update, and it says nothing about what happened during the window — a farm that was reachable while exploitation was confirmed belongs on the incident path regardless of which update it now holds.",
+        "evidence": "Packet vector: 'Microsoft SharePoint contains a code injection vulnerability that could allow an authorized attacker to execute code over a network. This vulnerability could be chained with CVE-2025-49706. CVE-2025-53770 is a patch bypass for CVE-2025-49704, and the updates for CVE-2025-53770 include more robust protection than those for CVE-2025-49704.' attack_vector: code injection (CWE-94) on SharePoint Server as part of the ToolShell chain, yielding unauthenticated remote code execution, KEV-listed 2025-07-22 with confirmed in-the-wild exploitation. CVSS 9.8, RWEP 83, poc_available true. The AU-Essential-8-Patch gap states patch cadence was actively defeated here because the initial fix was bypassed by CVE-2025-53770, so meeting the SLA still left KEV-listed, ransomware-linked exploitation live until the hardened update landed.",
+        "gap_closes": [
+          "AU-Essential-8-Patch"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "The clock on this entry opened with the KEV listing on 2025-07-22 against confirmed in-the-wild exploitation, and the packet's own coverage records the standard 30-day reading of 'appropriate timescales' as exploitation acceptance for an actively-exploited flaw on an internet-facing enterprise server. Applied to SharePoint, the first operational consequence is a sourcing rule: the fixed build for each on-premises farm server must be taken from the vendor advisory this entry links, because the packet gives affected versions only as 'per vendor advisory' — the version range is not something to infer, and not something to carry over from another SharePoint entry. The second is where completion is measured. live_patch_available is false and the packet records that the vendor patch typically requires a service restart or system reboot per the KEV required action, so a farm server that has installed the update but has not been restarted is still serving requests from pre-fix code; on a farm that restart is also the step most likely to be deferred into a maintenance window, and a deferral recorded as patched is the specific way this remediation goes wrong. Precondition, and it is what makes this control insufficient on its own here: satisfying the clock with the 49704 update alone does not end exposure, because the packet records CVE-2025-53770 as a bypass of exactly that fix with more robust protection in its updates — so the state this control drives toward is the hardened update, and the interim hardening the packet names for on-premises SharePoint (AMSI enforcement) bounds exploitation rather than removing the injection path.",
+        "evidence": "Packet: cisa_kev true, kev_date 2025-07-22, active_exploitation confirmed ('KEV listing is CISA's confirmed-exploitation attestation'), CVSS 9.8, RWEP 83, poc_available true. patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes 'No live-patch tool registered for this entry at bulk-import time. Vendor patch typically requires service restart or system reboot per the KEV requiredAction.' affected and affected_versions: 'Microsoft SharePoint — see vendor advisory linked in verification_sources for affected version ranges' / 'versions per vendor advisory'. The NIST-800-53-SI-2 gap states the 30-day flaw-remediation SLA is far longer than the observed exploitation window and that the ToolShell SharePoint chain was mass-exploited within days of disclosure; the ISO-27001-2022-A.8.8 gap states 'appropriate timescales' is undefined and the standard 30-day reading is unsafe for an actively-exploited flaw on an internet-facing enterprise server; the UK-CAF-B4 gap names AMSI enforcement as compensating hardening the baseline does not mandate.",
+        "gap_closes": [
+          "ISO-27001-2022-A.8.8",
+          "NIST-800-53-SI-2"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-032",
+        "name": "PERIMETER-COMPROMISE-REBUILD-NOT-PATCH",
+        "description": "This control was written for perimeter appliances, and an on-premises SharePoint farm is not one — but the packet places this flaw on an internet-facing enterprise server under confirmed exploitation with a public PoC, which puts the farm in the same position the control exists to address: the update closes the code-injection sink and removes nothing an attacker installed through it. The packet's gaps name the residue directly — machine-key rotation and a web-shell hunt are recorded as the cleanup this class needs and as hardening the CAF baseline does not mandate — and the machine keys are why patch-in-place specifically fails here: an attacker who took them during the exposure window can keep presenting forged authenticated payloads to a fully patched farm, so reaching the fixed build closes the entry point while leaving the access intact. For this product the requirement is therefore that a farm reachable while exploitation was live is triaged as a compromise — forensic capture, web-shell hunt across the front ends, machine-key rotation, rebuild of anything that cannot be cleared, and rotation of credentials the farm held or that authenticated through it — rather than being closed on the patch record. It also settles which process owns the finding: the packet records ransomware-linked exploitation of this chain, so an exposed farm is an incident to classify and report on the jurisdictional clocks, not a patch ticket. Preconditions: this is the response half and prevents nothing — it depends on the update to stop re-entry through the same sink, and it applies only to farms reachable during the window. Rotating machine keys does not evict an attacker who already holds a web shell or other persistence on the host, which is why the rebuild half is stated rather than rotation alone; and a farm whose request and process logs for the window were not retained cannot demonstrate it was untouched, so a clean hunt against absent telemetry is not evidence of absence.",
+        "evidence": "Packet: active_exploitation confirmed, kev_date 2025-07-22, poc_available true, CWE-94, RWEP 83. attack_vector places the flaw on SharePoint Server as part of the ToolShell chain yielding unauthenticated remote code execution. The UK-CAF-B4 gap states CAF system-security baselines don't mandate the compensating hardening (AMSI enforcement, machine-key rotation) on-prem SharePoint needed once this code-injection was chained and its first patch bypassed, and that patch-alone left the ToolShell path open. The entry's NIS2-Art21-network-security coverage states the framework 'does not require the key-rotation/web-shell-hunt cleanup' this class needs. The NIS2-Art21-vulnerability-handling gap states that known ransomware-campaign use elevates this from routine vulnerability handling to a Significant Incident class under NIS2 Art.23(4), engaging disclosure clocks. The entry's ISO-27001-2022-A.8.8 and PCI-DSS-4.0-6.3.3 coverage both describe the exposure as an internet-facing server.",
+        "gap_closes": [
+          "UK-CAF-B4",
+          "NIS2-Art21-vulnerability-handling"
+        ]
+      }
+    ]
   },
   "CVE-2025-49706": {
     "name": "Microsoft SharePoint Improper Authentication Vulnerability",
@@ -27447,7 +27510,38 @@
     },
     "ai_discovered_zeroday": false,
     "ai_discovery_source": "vendor_research",
-    "ai_assist_factor": "none"
+    "ai_assist_factor": "none",
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-121",
+        "name": "MOBILE-ZERO-CLICK-HARDENING",
+        "description": "The packet's vector puts this in Apple iOS, iPadOS, macOS, watchOS and visionOS processing a maliciously crafted photo or video shared via an iCloud Link, and its NIS2 gap records the flaw as zero-click, compromising the device with no victim action, used for Paragon mercenary spyware. There is therefore no user decision anywhere on the delivery path to train, warn or gate — which is precisely why the cited system-security configuration control is recorded as unable to block it. Applied to this entry, the control means the cohort plausibly inside a mercenary-spyware targeting set runs in a reduced-attack-surface mode in which shared media, link previews and attachments are not rendered automatically, so a crafted photo or video arriving over an iCloud share does not reach the media-processing path without an explicit user action. Scope it to the five Apple families the entry names and to the high-risk cohort rather than the whole estate, since the mode costs normal functionality. Preconditions, and they are what make this a holding measure rather than a fix: the mode only helps if it was already on when the share arrived, so it must be a standing posture assigned before the next disclosure — turning it on after the 2025-06-16 KEV listing does nothing for a device already implanted during the window; it narrows the delivery path and removes nothing from the underlying flaw, which closes only when a device is running the vendor's fixed build and has restarted onto it (patch_required_reboot is true and live_patch_available is false); and it does not evict an implant already resident, so a device suspected of exposure is an incident, not a configuration item.",
+        "evidence": "Packet vector: \"Apple iOS, iPadOS, macOS, watchOS, and visionOS, contain an unspecified vulnerability when processing a maliciously crafted photo or video shared via an iCloud Link.\" NIS2-Art21-incident-handling gap: \"this zero-click flaw delivered via a crafted photo or video in an iCloud Link — used for Paragon mercenary spyware — compromises the device with no victim action\". UK-CAF-B4 gap: \"System-security configuration of a managed Apple fleet cannot block a zero-click media-processing exploit arriving over an iCloud share; the exposure closes only when Apple's patch reaches every device.\" cisa_kev true, kev_date 2025-06-16, active_exploitation confirmed, poc_available true, patch_available true, patch_required_reboot true, live_patch_available false.",
+        "gap_closes": [
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-056",
+        "name": "MOBILE-ENDPOINT-MDM-ENFORCED-KEV-SLA",
+        "description": "For this entry the control means the update carrying the fix is driven across every Apple device in the estate on the clock that opened with the 2025-06-16 KEV listing, with user deferral disallowed, rather than folded into a normal update ring — the packet's own flaw-remediation gap states the 30-day SLA is far longer than the observed exploitation window for a client flaw delivered by attacker-controlled content. Two details decide whether this actually lands. First, the population is the five Apple families the entry names — iOS, iPadOS, macOS, watchOS and visionOS — and the fixed build for each has to be read from the vendor advisory the packet points to, because the entry records affected versions only as \"Apple Multiple Products — versions per vendor advisory\"; an estate that enforces this on phones and laptops while the watch and headset families sit outside the managed-update path has not covered what the vector names. Second, completion is measured on the build each device is actually running, not on \"update pushed\" or \"downloaded\" in the management console: patch_required_reboot is true and the packet records that the vendor patch typically requires a service restart or system reboot per the KEV requiredAction, with no live-patch path, so a device that took the update and has not restarted is still executing vulnerable code and must be counted as exposed. Precondition: this control reaches only devices the management channel enrolls and can update. A personally-owned or unenrolled device carrying organizational data has the same completion measure and no enforcement lever, and belongs on the access-condition or removal path instead of on this one.",
+        "evidence": "NIST-800-53-SI-2 framework_coverage gap: \"The 30-day flaw-remediation SLA is far longer than the observed exploitation window for a KEV-listed, actively-exploited client memory-corruption flaw delivered by attacker-controlled content.\" ISO-27001-2022-A.8.8 gap: \"'Appropriate timescales' is undefined; the standard reading is unsafe for an actively-exploited mobile/desktop OS flaw, often part of a targeted-spyware chain against high-risk users.\" AU-Essential-8-Patch gap: \"Essential-Eight patch targets exceed the exploitation window for a KEV-listed zero-click Apple flaw already weaponised for targeted spyware before public disclosure.\" patch_available true; patch_required_reboot true; live_patch_available false; live_patch_notes: \"Vendor patch typically requires service restart or system reboot per the KEV requiredAction.\" affected_versions: \"Apple Multiple Products — versions per vendor advisory\". Vector names iOS, iPadOS, macOS, watchOS and visionOS.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "ISO-27001-2022-A.8.8",
+          "AU-Essential-8-Patch"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-043",
+        "name": "NATION-STATE-INITIAL-ACCESS-IR-ESCALATION",
+        "description": "The packet records this flaw as used for Paragon mercenary spyware and delivered zero-click through a crafted photo or video in an iCloud Link, so the intrusion it produces is a targeted implant, not a commodity malware infection — which is the distinction this control exists to force, and the reason the entry's incident-handling gap says response begins only after covert implantation. The hard part for this CVE is the trigger: the packet states there is no victim action, so there is no user report, no click to reconstruct and no user-visible artifact to escalate on. The runbook must therefore key on the exposure fact the packet does supply rather than on a detection signal it does not: any device in the targeted cohort that was running a build below the vendor fix at any point after the 2025-06-16 KEV listing is handled as a suspected targeted-implant case — forensic acquisition and evidence preservation, review of what the device's credentials and sessions could reach, and rotation of those credentials — instead of being closed the moment the update installs. Preconditions. Escalation prevents nothing; it bounds dwell time and scope after the fact. It pulls directly against the update clock, because the packet records that remediation requires a restart, and restarting or wiping a suspected device destroys volatile state — so the runbook has to decide acquisition-before-update per device, which is a decision that has to exist in writing before a disclosure, not be composed while the fleet is mid-update. And where the organization has no defensible list of who is inside the targeting set, this control has no population to run against and the cohort definition is the prerequisite work.",
+        "evidence": "NIS2-Art21-incident-handling gap: \"Incident-handling obligations assume a detectable trigger, but this zero-click flaw delivered via a crafted photo or video in an iCloud Link — used for Paragon mercenary spyware — compromises the device with no victim action, so response begins only after covert implantation.\" active_exploitation_notes records CISA KEV listing as the confirmed-exploitation attestation with in-wild observation possibly predating the 2025-06-16 dateAdded. attack_vector: \"a code-execution flaw (CWE-94, variant) reachable via attacker-controlled content (a zero-click delivery path in the documented in-the-wild use)\". patch_required_reboot true; live_patch_available false; active_exploitation confirmed.",
+        "gap_closes": [
+          "NIS2-Art21-incident-handling"
+        ]
+      }
+    ]
   },
   "CVE-2025-33053": {
     "name": " Microsoft Windows External Control of File Name or Path Vulnerability",
@@ -28431,7 +28525,30 @@
     },
     "ai_discovered_zeroday": false,
     "ai_discovery_source": "vendor_research",
-    "ai_assist_factor": "none"
+    "ai_assist_factor": "none",
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-025",
+        "name": "CONFIGURATION-SIDE-LIVE-PATCH-INVENTORY",
+        "description": "Craft CMS is the product, and this entry is unusual in that the packet names the configuration setting exploitation depends on: an install is vulnerable to remote code execution when the php.ini configuration serving it has register_argc_argv enabled. That makes a configuration-side mitigation path available which is independent of the Craft upgrade — and the upgrade is the slow path here, since the packet records patch_required_reboot true with the vendor fix typically requiring a service restart or system reboot per the KEV requiredAction. The control's requirement for this deployment: inventory every Craft CMS install with the effective register_argc_argv value of the PHP runtime that serves it, disable it on the web-serving runtime, and treat that as a deployable, tested mitigation held ready rather than something discovered during an incident. Distinguishing test: read the effective value back from the PHP process actually serving Craft on every host in the pool — not from a php.ini file on disk, and not from a configuration-management template — and confirm it is off; a secure-configuration attestation covering the operating system and web-server baseline passes cleanly while this flag stays on, which is precisely what the UK-CAF and Essential-Eight hardening gaps record. Preconditions, both load-bearing. The mitigation holds only where nothing in the deployment depends on the setting: command-line PHP tooling reads $argv, so the change must be scoped to the runtime handling web requests and verified there rather than cleared globally, or scheduled jobs break and the change gets reverted under pressure. And clearing the flag does not evict an attacker already resident — active exploitation is confirmed and the flaw is unauthenticated code execution on the web server, so an install that ran with the flag enabled while reachable needs a compromise assessment and rotation of the secrets that install holds, not a flag flip recorded as remediation. This is the holding measure for the window before the vendor release and its restart land; the least-privilege control cited on this entry gives nothing here, because the attacker never holds a Craft account and no privilege decision is ever consulted.",
+        "evidence": "Packet vector: 'Craft CMS contains a code injection vulnerability. Users with affected versions are vulnerable to remote code execution if their php.ini configuration has register_argc_argv enabled.' patch_required_reboot true; live_patch_available false; live_patch_notes: 'No live-patch tool registered for this entry at bulk-import time. Vendor patch typically requires service restart or system reboot per the KEV requiredAction.' active_exploitation confirmed; poc_available true; CVSS 9.8; RWEP 77. Cited gaps: NIS2-Art21-vulnerability-management ('exploitability here hinges on the register_argc_argv PHP runtime setting — a config-hardening step the process doesn't enumerate, so a patched-elsewhere host stays an unauthenticated RCE target'), UK-CAF-B4 ('secure-configuration baselines for the PHP runtime rarely flag register_argc_argv'), AU-Essential-8-App-Hardening ('application-hardening doesn't reach web-runtime php.ini flags'). NIST-800-53-AC-6 gap records that the exploit demonstrates the boundary is breakable from a baseline context.",
+        "gap_closes": [
+          "NIS2-Art21-vulnerability-management",
+          "UK-CAF-B4",
+          "AU-Essential-8-App-Hardening"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "For Craft CMS the packet gives an unauthenticated code-execution flaw on an internet-facing web application with a public proof of concept, KEV-listed 2025-06-02 with confirmed in-the-wild exploitation — the profile the cited 30-day flaw-remediation reading is least safe for. The control means the Craft upgrade runs on the KEV clock rather than the site's normal release train, and it means one specific piece of care with the fixed level: the packet records affected versions only as 'per vendor advisory', so the target build has to be taken from the vendor advisory linked in this entry's verification sources rather than assumed from a version the operator has to hand. Completion is measured on what the running site is executing, not on what was deployed. patch_required_reboot is true and the packet records the vendor fix as typically requiring a service restart or system reboot, so a host whose Craft files were updated while the PHP and web service kept running is still executing pre-fix code and must be counted as exposed — on a busy site that restart is the step most likely to be deferred, and a deferral recorded as patched is the specific way this remediation goes wrong. Distinguishing test: enumerate every Craft CMS install the organisation runs — production, staging and the marketing or campaign sites that tend to sit outside the main asset register — and produce the version each is serving; an attestation covering the primary site passes cleanly while a forgotten install keeps an unauthenticated RCE reachable from the internet. Precondition: this control governs the speed and completeness of reaching the fixed release. It does nothing for an install already exploited, and it does not reach the runtime setting the same exploit depends on, which is a separate control on this entry.",
+        "evidence": "Packet: CISA KEV 2025-06-02, active_exploitation confirmed, CVSS 9.8, RWEP 77, poc_available true. attack_vector: 'a code-injection flaw (CWE-94, the related earlier variant) enabling unauthenticated remote code execution on the web server.' patch_available true; patch_required_reboot true; live_patch_available false; live_patch_notes records the vendor patch typically requiring service restart or system reboot per the KEV requiredAction. affected / affected_versions given only as 'Craft CMS — see vendor advisory linked in verification_sources for affected version ranges'. Cited gaps: NIST-800-53-SI-2 ('30-day flaw-remediation SLA inadequate for CISA-KEV-listed actively-exploited CVE'), ISO-27001-2022-A.8.8 (standard does not differentiate routinely-disclosed CVEs from actively-exploited KEV-listed ones).",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "ISO-27001-2022-A.8.8"
+        ]
+      }
+    ]
   },
   "CVE-2023-39780": {
     "name": "ASUS RT-AX55 Routers OS Command Injection Vulnerability",
@@ -29006,7 +29123,39 @@
     },
     "ai_discovered_zeroday": false,
     "ai_discovery_source": "vendor_research",
-    "ai_assist_factor": "none"
+    "ai_assist_factor": "none",
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-030",
+        "name": "PERIMETER-DEVICE-ZERODAY-SLA-TIER",
+        "description": "Ivanti Endpoint Manager Mobile is the trust boundary for the mobile fleet in the sense this tier exists for: the packet's own gaps record its API as internet-facing and the manager as controlling every enrolled device, and its attack_vector records the exploited form as unauthenticated remote code execution on the EPMM management surface once this code injection is chained with the authentication bypass. That makes EPMM not a system sitting behind a perimeter but the thing the fleet authenticates to, which is why the standard cadence fails: the packet's own gaps name a 30-day flaw-remediation SLA and a 48-hour internet-facing target, both longer than the interval in which a public proof of concept against a 9.8 pre-auth remote code execution gets used. The requirement for this CVE is that EPMM sits in its own SLA tier whose clock started with the 2025-05-19 KEV listing and is counted in hours. One scoping caution the packet forces: it carries the affected range only as 'versions per vendor advisory', so the fixed level must be read from that advisory for the EPMM release actually in service rather than assumed, and the sweep covers every EPMM instance the estate runs — widen beyond EPMM only where a verified source identifies another product carrying the same Hibernate Validator implementation. The packet records no live-patch path and states that the vendor patch typically requires a service restart or system reboot per the KEV requiredAction, so an EPMM that has taken the update but has not restarted onto it is still executing the vulnerable code and is not remediated; completion is the version the running service reports. Precondition on the tier's isolation alternative, which is where this control is over-claimed on a device manager: isolating the vulnerable interface is only partly available here, because the packet's gap records the EPMM API as internet-facing and the device-facing paths that make it so are the ones the enrolled fleet depends on. Restricting the administrative surfaces and the source ranges permitted to reach the device API bounds who can attempt the chain; it does not remove the device-facing path, so it is a holding measure for the window before the update and its restart land, not a substitute for either.",
+        "evidence": "Packet: CWE-94; CVSS 9.8; RWEP 77; poc_available true; active_exploitation confirmed; cisa_kev true with kev_date 2025-05-19. attack_vector: 'code injection (CWE-94) yielding unauthenticated remote code execution on the EPMM management surface (chained with the authentication bypass). CISA KEV-listed 2025-05-19 with confirmed in-the-wild exploitation.' patch_available true; patch_required_reboot true; live_patch_available false; live_patch_notes: 'No live-patch tool registered for this entry at bulk-import time. Vendor patch typically requires service restart or system reboot per the KEV requiredAction.' affected and affected_versions both give the product as 'Ivanti Endpoint Manager Mobile (EPMM)' with versions 'per vendor advisory'. NIST-800-53-SI-2 gap: '30-day flaw-remediation SLA inadequate for CISA-KEV-listed actively-exploited CVE.' AU-Essential-8-Patch gap: 'The 48h internet-facing patch target trails active chaining of this EPMM RCE, whose compromise pivots to every mobile device the manager controls.' ISO-27001-2022-A.8.8 gap: the standard 'does not differentiate between routinely-disclosed CVEs and actively-exploited KEV-listed CVEs'. NIS2-Art21-network-security gap names the 'internet-facing EPMM API'.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "AU-Essential-8-Patch",
+          "ISO-27001-2022-A.8.8"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-134",
+        "name": "DEVICE-MANAGEMENT-GATEWAY-CONFIG-ENDPOINT-AUTH-INPUT-NEUTRALIZATION",
+        "description": "EPMM is the device-management gateway this control governs, and the defect sits on its API interface: the packet places a code-injection sink in the API component reachable through crafted API requests, arising from an insecure implementation of the Hibernate Validator open-source library as represented by CVE-2025-35036 — a request-supplied value reaching an expression-evaluation path. Bound to this product the control asks for two properties on that API. Each endpoint decides its caller's authorization itself, before the request body is processed at all, rather than inheriting a verdict from a front-end filter — which is exactly the arrangement that collapses when this injection is chained with the authentication bypass and the request arrives with no valid session; and request-supplied values never reach an evaluation path as expression text, so a parameter cannot select what the server evaluates. It also means no EPMM instance is left with its administrative API paths reachable from segments that have no operational need to reach them. This is why the least-privilege gap cited on this entry does not close the path: the packet's vector describes an authenticated attacker, but the exploited form it records is unauthenticated once chained, so per-account privilege scoping is never consulted and an AC-6 attestation passes cleanly while the endpoint stays reachable and evaluating. Distinguishing test on a staging EPMM: send each API endpoint an unauthenticated request whose parameter values carry expression syntax and confirm it is refused before the value is evaluated — not that EPMM administrators are correctly scoped, which this attacker never needed to be. Precondition: the endpoint-side authorization decision and the input handling are properties the vendor update establishes; this control states what to verify and does not implement it. Until that update and its restart land, restricting reachability bounds the population that can send the request while leaving the endpoint exploitable to anything within reach, and for the device-facing API that population includes any client that can present itself to it.",
+        "evidence": "Packet vector: 'Ivanti Endpoint Manager Mobile (EPMM) contains a code injection vulnerability in the API component that allows an authenticated attacker to remotely execute arbitrary code via crafted API requests. This vulnerability results from an insecure implementation of the Hibernate Validator open-source library, as represented by CVE-2025-35036.' attack_vector records the exploited form as unauthenticated remote code execution on the EPMM management surface when chained with the authentication bypass. NIST-800-53-AC-6 gap: 'Least-privilege presumes a working authentication / authorization boundary. The KEV-listed exploit demonstrates the boundary is breakable from a baseline context.' NIS2-Art21-network-security gap: 'Network-security controls do not compel restricting the internet-facing EPMM API whose expression-language injection RCE, chained with an auth bypass, hands over the MDM controlling an entire mobile fleet.' patch_available true with patch_required_reboot true and live_patch_available false.",
+        "gap_closes": [
+          "NIST-800-53-AC-6",
+          "NIS2-Art21-network-security"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-037",
+        "name": "FLEET-COMPROMISE-IR-PLAYBOOK",
+        "description": "The packet states the consequence plainly in its UK-CAF gap: a compromised EPMM becomes a fleet-wide command channel to every enrolled device. Code execution on the management surface means the attacker inherits the manager's own authority over that fleet — configuration profiles, certificates, application deployment and device-trust state — so the response has to be written for the enrolled devices and not only for the appliance. For this product the pre-rehearsed playbook is: revoke and reissue the certificates EPMM issued; invalidate device-trust state and re-enroll; diff every configuration profile and application-deployment policy against a known-good baseline across the window in which the instance was exposed, which opens no later than the 2025-05-19 KEV listing and earlier if the instance was reachable before it; set quarantine criteria for enrolled devices that took a profile or package during that window; and rotate credentials for every account that authenticated through EPMM. Applying the vendor update answers none of these questions. The fix removes the injection sink and leaves in place whatever was pushed to handsets through it, and a profile or certificate delivered by a compromised manager stays trusted by the fleet until it is explicitly revoked — which is the specific way this remediation is recorded as complete while the fleet is still carrying attacker-supplied configuration. Precondition: this is a response measure and not a preventive one, and it depends on the exposure window being establishable from records the compromised appliance itself may hold. Where EPMM's logging was local to the instance, the window cannot be bounded from the appliance alone and has to be reconstructed from an independent source, which is the argument for treating the enrolled fleet as in scope by default rather than scoping the response to the manager.",
+        "evidence": "Packet UK-CAF-B4 gap: 'Hardening the EPMM appliance does not remove an expression-language injection in its API, and the compromised MDM becomes a fleet-wide command channel to every enrolled device.' NIS2-Art21-network-security gap describes the chained RCE as handing over 'the MDM controlling an entire mobile fleet'; AU-Essential-8-Patch gap notes the compromise 'pivots to every mobile device the manager controls'. active_exploitation confirmed with poc_available true and cisa_kev true, kev_date 2025-05-19. patch_available true; live_patch_available false; live_patch_notes records that the vendor patch typically requires a service restart or system reboot per the KEV requiredAction.",
+        "gap_closes": [
+          "UK-CAF-B4"
+        ]
+      }
+    ]
   },
   "CVE-2025-4427": {
     "name": "Ivanti Endpoint Manager Mobile (EPMM) Authentication Bypass Vulnerability",
@@ -39231,7 +39380,31 @@
         "adequate": false,
         "gap": "Flaw remediation is structurally impossible: Zyxel has declared these DSL CPE devices end-of-life/end-of-service with no patch planned, so the standard remediate-within-SLA control has no path to closure short of hardware replacement."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-127",
+        "name": "UNSUPPORTED-NETWORK-DEVICE-ENUMERATION-AND-RETIREMENT",
+        "description": "The packet forecloses the interim half of this control before it begins: patch_available is false, the vector opens with the UNSUPPORTED WHEN ASSIGNED marker, and live_patch_notes records that no live-patch path exists for this EOL firmware and that the vendor's only guidance is to discontinue use of the device if it cannot be isolated from untrusted networks. So for these legacy Zyxel DSL CPE units there is no fixed build to reach and no patched state to record — every unit in service is a replacement item, and the requirement is an inventory naming each VMG4325-B10A and each related legacy Zyxel DSL CPE running firmware 1.00(AAFR.4)C0_20170615, with a dated removal date per unit rather than a remediation ticket that waits on firmware. Scope it to what the packet's affected and affected_versions name — VMG4325-B10A and the related legacy Zyxel DSL CPE builds sharing the same management-command codebase — because the packet maps this command-injection sink to that codebase and to no other Zyxel line, and sweeping every Zyxel device in the estate as an instance of this CVE manufactures replacement work against hardware no evidence implicates. Until a unit is gone, the only lever the packet leaves is the isolation the vendor names, and its precondition has to be stated rather than assumed: the injection is reached through the Telnet-exposed management command interface, so blocking Telnet at the WAN interface removes the path Censys observed on 1,500+ of these devices and the path GreyNoise saw scanned from January 2025 — but a DSL CPE exists to serve the LAN attached to it, and every client on that LAN still reaches the management interface with the default or service-account credentials the packet describes the attack using. For a unit serving a general user network there is no filter that removes the path, only isolation of that network from anything that matters. And because active exploitation is confirmed and Mirai variants recruited these routers into botnet infrastructure, a unit that was WAN-reachable during the exposure window is not made safe by filtering it now: the flaw yields OS command execution on the device itself, so it is a removal item rather than a reconfiguration item, and any credential that transited it should be rotated.",
+        "evidence": "Packet fields: patch_available false, live_patch_available false, patch_required_reboot true with no patch to apply; live_patch_notes — \"No live-patch path exists for this EOL firmware; the vendor's only guidance is to discontinue use of the device if it cannot be isolated from untrusted networks.\" The vector carries the UNSUPPORTED WHEN ASSIGNED marker and describes a post-authentication command injection in the management commands of the legacy DSL CPE Zyxel VMG4325-B10A firmware version 1.00(AAFR.4)C0_20170615, executed via Telnet; affected/affected_versions scope to VMG4325-B10A and related legacy Zyxel DSL CPE firmware builds sharing the same management-command codebase; CWE-78; cvss 8.8, rwep_score 70; poc_available false; cisa_kev true with kev_date 2025-02-11 and active_exploitation confirmed. active_exploitation_notes: GreyNoise observed mass scanning and exploitation attempts beginning January 2025 and Mirai botnet variants incorporated exploitation of this Telnet-based command injection, using it alongside CVE-2024-40890 to recruit EOL routers. framework_control_gaps: NIST-800-53-SI-2 records Zyxel declaring these devices end-of-life/end-of-service with no patch planned and no closure short of hardware replacement; NIST-800-53-CM-7 records Censys observing 1,500+ of these EOL devices with the Telnet management interface reachable directly from the WAN; UK-CAF-B4 records the Telnet management plane exposed to the untrusted WAN interface; ISO-27001-2022-A.8.8 records these units sitting outside the ISMS asset register.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "ISO-27001-2022-A.8.8",
+          "NIST-800-53-CM-7",
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "For this entry only the control's third branch is reachable. Its requirement is a verified mitigation — patch, live patch, or documented compensating controls — on the KEV clock, and the packet records patch_available false and live_patch_available false with no live-patch path for this EOL firmware, so the clock that opened with the 2025-02-11 KEV listing can only be answered by the compensating action the vendor names: isolate the device from untrusted networks, or discontinue use. That is precisely what the two frameworks cited here cannot express — Essential Eight's patch-within-48-hours-of-active-exploitation expectation is unmeetable because no patch exists, and NIS2 vulnerability handling assumes an eventual vendor fix that will never ship for this hardware — so the compensating action has to be recorded as the terminal deliverable against the KEV date, not as a temporary state pending firmware. Operationally, every affected unit needs a dated, evidenced record of either its removal or its Telnet management interface being unreachable from the WAN, produced against the listing date rather than left as an open remediation ticket. Distinguishing test, keyed on the exploitation path the packet documents: from outside the device's WAN interface, attempt a Telnet connection to each unit and issue a management command; anything that answers is within reach of the scanning and exploitation GreyNoise observed from January 2025, and a vulnerability-management report carrying this CVE as \"no patch available, risk accepted\" while the interface answers has recorded the exposure rather than mitigated it. Precondition: the isolation is a mitigation only while it holds, and it depends on a WAN-side filter surviving firmware resets, ISP re-provisioning and user reconfiguration on hardware the operator generally does not manage — which is why the vendor's own guidance ends at discontinuing use rather than at isolation.",
+        "evidence": "Packet fields: cisa_kev true with kev_date 2025-02-11 and active_exploitation confirmed; patch_available false; live_patch_available false; live_patch_notes — \"No live-patch path exists for this EOL firmware; the vendor's only guidance is to discontinue use of the device if it cannot be isolated from untrusted networks.\" attack_vector: an attacker with a Telnet session to a legacy Zyxel DSL CPE device, using default or otherwise-obtained service-account credentials, sends management commands containing embedded shell metacharacters that are passed unsanitized to the underlying OS shell. active_exploitation_notes: GreyNoise observed mass scanning and exploitation attempts against exposed Zyxel legacy DSL CPE devices beginning January 2025. framework_control_gaps: AU-Essential-8-Patch — \"Essential 8's patch-within-48-hours-of-active-exploitation guidance is unmeetable since no patch exists; the only compensating action is decommissioning or isolating the device from the internet\"; NIS2-Art21-vulnerability-management — \"NIS2 operators relying on this hardware have no vendor remediation SLA at all post-EOL; typical vulnerability-management timelines assume an eventual vendor fix that will never ship.\"",
+        "gap_closes": [
+          "AU-Essential-8-Patch",
+          "NIS2-Art21-vulnerability-management"
+        ]
+      }
+    ]
   },
   "CVE-2024-40890": {
     "name": "Zyxel DSL CPE OS Command Injection Vulnerability (CGI)",
@@ -39268,7 +39441,31 @@
         "adequate": false,
         "gap": "Boundary protection is absent by design: the CGI management program is reachable via HTTP POST from the untrusted WAN interface with no network-layer restriction."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-127",
+        "name": "UNSUPPORTED-NETWORK-DEVICE-ENUMERATION-AND-RETIREMENT",
+        "description": "The packet settles the patch question before the control begins: patch_available is false, the CVE text is marked UNSUPPORTED WHEN ASSIGNED, and the vendor's only recorded guidance is to discontinue use of the device if it cannot be isolated from untrusted networks. There is no fixed firmware to reach and therefore no interim state — for these units the terminal state is removal or replacement, and the enumeration half is what makes that actionable: inventory every Zyxel legacy DSL CPE in service with its model and running firmware, covering the related legacy models sharing the same CGI codebase that the packet's affected_versions name rather than only the VMG4325-B10A the vector headlines, since an estate that standardised on a sibling model would otherwise report clean. Each unit becomes a dated replacement item; a risk acceptance with no removal date leaves a KEV-listed device under confirmed mass exploitation in service indefinitely, and it stays exposed to everything else found in that abandoned firmware, not only this command injection. Precondition on the isolation half, which the vendor guidance itself makes conditional: the flaw is reached by an HTTP POST to the CGI management program, so removing WAN-side reachability of that interface takes the unit out of the internet-facing path the trackers observed from January 2025 — but a DSL CPE exists to serve the client network behind it, and every client on that network still reaches the CGI management surface, so for a unit serving a general user network isolation bounds who can reach the path rather than removing it. The post-authentication framing is not a barrier either: the packet places the session on a default or service account, so the precondition is credentials that ship with the device rather than anything an attacker must first steal. And because active exploitation is confirmed and the outcome is OS command execution on the device itself, a unit that was reachable during the window is not made safe by reconfiguration — it is replaced, and credentials that transited it are rotated.",
+        "evidence": "Packet: patch_available false, live_patch_available false, live_patch_notes 'No live-patch path exists for this EOL firmware; the vendor's only guidance is to discontinue use of the device if it cannot be isolated from untrusted networks.' vector begins '**UNSUPPORTED WHEN ASSIGNED**' and describes post-authentication command injection in the CGI program of the legacy DSL CPE Zyxel VMG4325-B10A firmware 1.00(AAFR.4)C0_20170615 via a crafted HTTP POST request; affected_versions extends to 'related legacy Zyxel DSL CPE firmware builds sharing the same CGI codebase'; affected records the session as an 'authenticated (default/service-account) session'. cisa_kev true, kev_date 2025-02-11, active_exploitation confirmed, CVSS 8.8, RWEP 70, CWE-78. active_exploitation_notes: GreyNoise and Mirai botnet trackers observed mass scanning/exploitation of exposed devices via crafted HTTP POST requests against the CGI management program beginning January 2025. The NIST-800-53-SI-2 gap states remediation is structurally impossible with no path to closure short of hardware replacement; the NIST-800-53-SC-7 gap states the CGI management program is reachable via HTTP POST from the untrusted WAN interface with no network-layer restriction; the ISO-27001-2022-A.5.21 gap states the devices are vendor-abandoned with no patch path.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "NIST-800-53-SC-7",
+          "UK-CAF-B4",
+          "ISO-27001-2022-A.5.21"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-038",
+        "name": "MITIGATION-ACTIVE-PATCH-PENDING-VERDICT-CLASS",
+        "description": "This control's three states resolve unusually on this entry, and that is the point of attaching it: state (a), binary patch deployed, is permanently unreachable. patch_available is false and live_patch_available is false with no live-patch path recorded for the abandoned firmware, so a Zyxel legacy DSL CPE that has been isolated from untrusted networks sits permanently in state (b) — compensating control active, no binary patch — and one that has not sits in state (c), full exposure, while its CGI management program answers HTTP POSTs from the WAN. The requirement here is that the compliance record says exactly that: an isolated VMG4325-B10A or sibling legacy unit must appear as a compensating-control state carrying a dated replacement action, never as remediated and never as an open-ended accepted risk, because unlike a patch-pending entry there is no future vendor event that converts the state — the only thing that closes it is the device leaving the estate. Precondition on what may be recorded as the compensating control: it has to be isolation actually in force and verified from outside, since 'the router sits behind the ISP connection' is an assertion about topology rather than evidence that the CGI interface is unreachable. The residual-risk statement attached to state (b) must also carry the two facts that bound it — LAN-side clients still reach the management surface, and the authenticating credential is a device default or service account — otherwise the record reads as containment while the exploited path remains available to anything on the client network.",
+        "evidence": "Packet: patch_available false, live_patch_available false, live_patch_notes recording no live-patch path for this EOL firmware and vendor guidance to discontinue use of the device if it cannot be isolated from untrusted networks; poc_available false but active_exploitation confirmed with kev_date 2025-02-11 (KEV ransomware use flagged Unknown). The NIS2-Art21-vulnerability-management gap states that operators relying on this hardware have no vendor remediation SLA at all post-EOL and that typical vulnerability-management timelines assume an eventual vendor fix that will never ship; the AU-Essential-8-Patch gap states the patch-within-48-hours-of-active-exploitation guidance is unmeetable since no patch exists and the only compensating action is decommissioning or isolating the device from the internet.",
+        "gap_closes": [
+          "NIS2-Art21-vulnerability-management",
+          "AU-Essential-8-Patch"
+        ]
+      }
+    ]
   },
   "CVE-2025-0994": {
     "name": "Trimble Cityworks Deserialization Vulnerability",
@@ -39895,7 +40092,38 @@
         "adequate": false,
         "gap": "Exploitation depends on obtaining admin credentials, frequently via the paired CVE-2018-19410 flaw; stronger identity-and-access controls (MFA, credential rotation) would blunt the chain."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-135",
+        "name": "CONTROL-PANEL-PLUGIN-USER-SURFACE-MUST-NOT-REACH-ROOT-OPERATIONS",
+        "description": "PRTG's sensor and notification management is the configuration surface this control governs, and the packet places the defect exactly there: parameters submitted through sensor or notification management — the packet names EXE/Script sensor parameters and notification 'Execute Program' actions — are passed unsanitized into an OS command, yielding execution on the PRTG core server and on any device the server manages. The missing boundary is not between an anonymous caller and the console; it is between holding PRTG System Administrator inside the application and running arbitrary OS commands as the account the PRTG core service runs under, across the monitored estate. Applied to this product, the control means the configuration fields that feed command execution accept a selection from an operator-curated set of programs and argument shapes rather than a free-form string composed at the console, and the process that executes them holds only the privileges monitoring genuinely requires rather than inheriting the reach of the monitoring platform. Distinguishing test: on a staging PRTG instance below 18.2.39, submit shell metacharacters in an EXE/Script sensor parameter and in a notification Execute Program action while authenticated as System Administrator, and observe whether an OS command runs — an attestation that every PRTG administrator is named, approved and periodically reviewed passes cleanly while this path is wide open, because the caller here is a legitimate administrator and no account model is being abused. That is the same reason the least-privilege gap recorded on this entry cannot be closed by tightening who holds the role. Precondition: the parameter handling itself is repaired by the vendor release — the packet records versions before 18.2.39 as affected — so this control states the property to verify and does not implement it. Until an instance is at or above that version, restricting who holds System Administrator bounds the population that can submit the parameters but does not close the path, because the packet's own exploitation account has attackers arriving with those credentials already in hand, frequently obtained through the companion pre-auth flaw CVE-2018-19410.",
+        "evidence": "Packet vector: 'An attacker who has access to the PRTG System Administrator web console with administrative privileges can exploit an OS command injection vulnerability (both on the server and on devices) by sending malformed parameters in sensor or notification management scenarios.' attack_vector names 'EXE/Script sensor parameters, notification \"Execute Program\" actions' passed unsanitized to an OS command 'yielding command execution on the PRTG core server or a monitored device'. affected_versions: '< 18.2.39'; patch_available true. The NIST-800-53-AC-6 gap: the console 'over-trusts authenticated administrators, allowing free-form OS-level parameter strings in sensor/notification configuration without least-privilege sandboxing of the executed command.' The AU-Essential-8-App-Hardening gap: those features 'are inherently high-risk command-execution surfaces that application-hardening guidance would restrict or disable where not required.' The ISO-27001-2022-A.8.9 gap: configuration management 'should validate/sanitize sensor and notification parameter fields rather than passing them unsanitized to OS command execution.' active_exploitation_notes place credential acquisition, 'often via the companion pre-auth flaw CVE-2018-19410', ahead of the injection.",
+        "gap_closes": [
+          "NIST-800-53-AC-6",
+          "AU-Essential-8-App-Hardening",
+          "ISO-27001-2022-A.8.9"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "The interval this control exists to compress is unusually visible on this entry: the flaw was disclosed against PRTG Network Monitor versions before 18.2.39 in 2018, and CISA added it to KEV on 2025-02-04, which the packet attributes to continued abuse of legacy, unpatched PRTG deployments. A KEV listing on a seven-year-old flaw is a statement that the population still running the vulnerable build is large enough to be worth an attacker's time, so the action here is an enumeration before it is a patch cycle: find every PRTG core server in service and record the version each runs, taking instances reachable from the internet first, since the packet's own vulnerability-management gap places the multi-year unpatched population in internet-exposed deployments. Every instance below 18.2.39 is on the clock that opened 2025-02-04. Measure completion on the version the running PRTG core service reports rather than on an installer having been executed; the packet records no live-patch path for this product, so the running service is the only thing whose version answers the question. Distinguishing test: query each PRTG core server for the version it is actually serving and confirm it is at or above 18.2.39 — a vulnerability-management report showing no PRTG findings because no PRTG server appears in it is the state this entry describes, not a clean result. Precondition: a public PoC exists and exploitation is confirmed, and the packet places command execution on the core server and on any device it manages, so an instance that ran a vulnerable build while its console was reachable by anyone holding or able to obtain System Administrator credentials is not remediated by the upgrade alone. Its configured sensors and notification actions are the objects the attacker writes to and should be compared against a known-good baseline rather than carried forward through the upgrade, and the devices the server manages belong in the blast radius rather than being assumed clean.",
+        "evidence": "Packet: cisa_kev true, kev_date 2025-02-04, active_exploitation confirmed, poc_available true, rwep_score 63 against cvss 7.2. affected_versions '< 18.2.39'; the vector records the issue as 'discovered in PRTG Network Monitor before 18.2.39'. active_exploitation_notes: attackers 'inject OS commands through sensor or notification configuration parameters for full RCE on the PRTG core server and any device it manages. Added to CISA KEV Feb 2025, reflecting continued abuse of legacy, unpatched PRTG deployments.' patch_available true, patch_required_reboot false, live_patch_available false, live_patch_notes null. The NIS2-Art21-vulnerability-management gap: 'A 2018-disclosed flaw remained unpatched and exploitable in internet-exposed PRTG deployments as of the 2025 KEV addition — patch-management processes failed over a multi-year window.'",
+        "gap_closes": [
+          "NIS2-Art21-vulnerability-management"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-036",
+        "name": "FLEET-CONTROL-PLANE-ADMIN-PRIVILEGE-TIER",
+        "description": "PRTG Network Monitor is a monitoring control plane whose administrative account, on the packet's own account of this exploit, converts into command execution on the core server and on every device the server manages. That places PRTG System Administrator in the tier this control exists to name rather than in the application-admin tier where a monitoring tool is usually filed, and the difference is the whole point: an identity-and-access attestation that treats it as one more application admin is measuring the wrong thing. For this deployment the requirement is that the PRTG console is reached through a privileged-access path rather than from an operator's daily workstation, that holding System Administrator is a separate identity from the same person's ordinary account and other administrative roles, and that the session is step-up authenticated rather than opened with a reusable password — because the packet's exploitation account is a credential-theft chain, in which attackers first obtain PRTG System Administrator credentials, frequently via the companion pre-auth flaw CVE-2018-19410, and only then reach the injection sink. Distinguishing test: from a general workstation segment, attempt to reach the PRTG console with a password alone and confirm it is refused; an estate where the monitoring platform's admin credential is a reusable password reachable from any desk already satisfies the precondition this exploit needs. Precondition, stated plainly because this is where the control is over-claimed: raising the bar at the console login bounds credential reuse, it does not repair the unsanitized parameter handling, and it is never consulted by a chain step that yields a live session or an API token rather than a password. It also does nothing against an administrator who is legitimately authenticated, since the packet's caller holds the role by design. It bounds the population that can attempt the escalation; it is not a substitute for reaching 18.2.39.",
+        "evidence": "Packet active_exploitation_notes: 'Actively exploited by attackers who first obtain PRTG System Administrator credentials (often via the companion pre-auth flaw CVE-2018-19410) and then inject OS commands through sensor or notification configuration parameters for full RCE on the PRTG core server and any device it manages.' vector requires 'access to the PRTG System Administrator web console with administrative privileges'. The UK-CAF-B2 gap: 'Exploitation depends on obtaining admin credentials, frequently via the paired CVE-2018-19410 flaw; stronger identity-and-access controls (MFA, credential rotation) would blunt the chain.' patch_available true with affected_versions '< 18.2.39'.",
+        "gap_closes": [
+          "UK-CAF-B2"
+        ]
+      }
+    ]
   },
   "CVE-2018-19410": {
     "name": "Paessler PRTG Network Monitor Local File Inclusion Vulnerability",
@@ -40195,7 +40423,40 @@
         "adequate": false,
         "gap": "Aviatrix Controller instances left reachable from the internet had no boundary protection to stop unauthenticated command injection against a cloud-network control plane."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "Aviatrix Controller is a multi-cloud network control plane, and the packet's timeline is what makes a KEV-tied clock the requirement rather than a cloud-infrastructure change window: exploitation ran January 7-10 2025 and surged after a public Nuclei detection template was released, with CISA listing the flaw on 2025-01-16. For this product the control means the upgrade to the fixed build — 7.1.4191 for the 7.1 line, 7.2.4996 for 7.2.x — is driven from the KEV listing, with completion measured per instance on the version the running controller reports. patch_required_reboot is false, which means no host reboot; it does not mean the fix is live the moment an upgrade is pushed, and a controller still answering /v1/api on a pre-fix version is exposed regardless of what the deployment record says. live_patch_available is false and live_patch_notes is empty, so there is no interim in-place fix to fall back on: reaching the fixed version is the only remediation the packet records. Distinguishing test: enumerate every Aviatrix Controller instance in the organisation — including any stood up by an application team outside the central cloud-platform inventory — and produce its running version; a patch attestation covering only the controllers the platform team already tracks passes cleanly while an unlisted instance keeps an unauthenticated command-injection endpoint reachable. Precondition: this control governs the speed and completeness of the upgrade only. It says nothing about an instance that was already exploited during the window the packet records, which is a separate response path.",
+        "evidence": "Packet: CISA KEV 2025-01-16, active_exploitation confirmed, CVSS 10, RWEP 75, poc_available true. Exploited in the wild from January 7-10 2025 with a sharp surge after a public Nuclei detection template was released. patch_available true, patch_required_reboot false, live_patch_available false, live_patch_notes null. affected_versions: before 7.1.4191; 7.2.x before 7.2.4996. Cited gaps: SI-2 (exploitation surged faster than routine remediation SLAs), ISO A.8.8 (periodic vuln-review cycles far slower than the days-long window), AU-Essential-8-Patch (mass exploitation within days, driven by public tooling).",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "ISO-27001-2022-A.8.8",
+          "AU-Essential-8-Patch"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-134",
+        "name": "DEVICE-MANAGEMENT-GATEWAY-CONFIG-ENDPOINT-AUTH-INPUT-NEUTRALIZATION",
+        "description": "The defect sits on Aviatrix Controller's own management API: /v1/api accepts list_flightpath_destination_instances and flightpath_connection_test, and the cloud_type and src_cloud_type parameters reach an OS command with shell metacharacters unneutralized, for a caller that never authenticates. Bound to this product the control means two things. First, each /v1/api operation authorizes its caller and neutralizes parameter content before the value reaches the command, so a caller-supplied string cannot select what the controller executes — this is the property the fixed build establishes, and the control states what to verify rather than implementing it. Second, no controller is left with that API reachable from a segment with no operational need to reach it; the packet's boundary gap records instances left reachable from the internet with nothing in front of them, and the NIS2 gap records segmentation isolating the controller's management API as frequently absent in this incident. Distinguishing test: from a general workstation VLAN and from an external address, attempt to reach /v1/api on a staging controller and confirm the connection is refused before the endpoint parses anything — 'the controller is in our cloud account' is a statement about topology, not a demonstration that the management API is unreachable from untrusted callers. Precondition, and this is where the reachability half is routinely over-claimed: restricting which segments can reach /v1/api bounds who can send the request, it does not close the injection. Any host inside a permitted segment still drives the endpoint to full unauthenticated command execution, and the lever is simply unavailable where the controller API must stay reachable for normal operation. It is a holding measure for the window before the fixed build lands, not a substitute for it.",
+        "evidence": "Packet vector/affected: shell metacharacters sent to /v1/api in cloud_type for list_flightpath_destination_instances, or src_cloud_type for flightpath_connection_test, fail neutralization and yield unauthenticated OS command execution (CWE-78). Cited gaps: NIST-800-53-SC-7 ('instances left reachable from the internet had no boundary protection to stop unauthenticated command injection against a cloud-network control plane'), UK-CAF-B4 ('secure configuration guidance for cloud-network control planes did not prevent an unauthenticated OS command injection sink from being internet-reachable'), NIS2-Art21-network-security (EU operators 'needed network segmentation isolating the controller's management API, which this incident showed was frequently absent').",
+        "gap_closes": [
+          "NIST-800-53-SC-7",
+          "UK-CAF-B4",
+          "NIS2-Art21-network-security"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-032",
+        "name": "PERIMETER-COMPROMISE-REBUILD-NOT-PATCH",
+        "description": "This is the case the control exists for, and the packet supplies both halves: an unauthenticated pre-auth command-execution flaw on a network control-plane device, and confirmed exploitation in which threat actors deployed XMRig cryptominers and Sliver C2 backdoors for persistence. Upgrading an Aviatrix Controller to 7.1.4191 or 7.2.4996 closes the injection sink; it removes nothing an attacker installed through it, so an instance that was reachable during the January 7-10 2025 window is not remediated by the upgrade and must not be closed on the patch record. For this product the response is to export and review the controller configuration, rebuild the instance from a known-good image, and rotate the cloud credentials and role trust the controller holds — the packet records Wiz Research finding that 65% of organisations running Aviatrix Controller have a lateral-movement path from it to administrative cloud control-plane permissions, which is the blast radius a resident Sliver implant inherits. Distinguishing test: for each controller, establish whether its /v1/api was reachable from an untrusted network at any point before the upgrade; where it was, treat it as an incident rather than a patch item. Precondition: rebuild-not-patch presupposes a known-good image and a configuration export the operator trusts, and it applies to instances with exposure during the window — it is not a blanket instruction to rebuild every controller. Where a rebuild genuinely cannot be scheduled, the honest state is a compromised-until-proven-otherwise instance under monitoring with its cloud credentials rotated, not a remediated one.",
+        "evidence": "Packet active_exploitation_notes: exploited in the wild from January 7-10 2025; 'threat actors used unauthenticated command injection to deploy XMRig cryptominers and Sliver C2 backdoors for persistence'; 'Wiz Research notes 65% of organizations running Aviatrix Controller have a lateral-movement path to administrative cloud control-plane permissions'. active_exploitation confirmed; poc_available true; patch_available true (before 7.1.4191 / 7.2.x before 7.2.4996). Cited gap NIST-800-53-SI-2 treats remediation as flaw removal on a clock, which does not reach attacker-installed persistence.",
+        "gap_closes": [
+          "NIST-800-53-SI-2"
+        ]
+      }
+    ]
   },
   "CVE-2025-21335": {
     "name": "Microsoft Windows Hyper-V NT Kernel Integration VSP Use-After-Free Vulnerability (CVE-2025-21335)",
@@ -40493,7 +40754,39 @@
         "adequate": false,
         "gap": "EU operators relying on BeyondTrust PRA/RS as a privileged-access gateway need vendor-supply-chain risk monitoring, not just internal patch cadence, since the compromise originated at the vendor."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-036",
+        "name": "FLEET-CONTROL-PLANE-ADMIN-PRIVILEGE-TIER",
+        "description": "BeyondTrust Privileged Remote Access and Remote Support are themselves the privileged-access control plane — the product exists so technicians reach other people's systems — and the packet's exploit precondition is an attacker who already holds administrative privileges on a PRA/RS site and uploads a crafted file the backend processes without OS-command sanitization, so commands run as the site user. Bound to this product the control means PRA/RS site administration is classified as its own privilege tier above application admin rather than collapsed into 'admin': a separate identity from any other administrative role, access only through a PAM jump host, per-session step-up, and just-in-time elevation with an approval workflow, so that holding an administrative session on the remote-support platform is a deliberately granted, time-bounded and individually attributable state instead of a standing role. What this incident adds to the tier is that it cannot enumerate human administrators only: the packet records the access arriving through a stolen BeyondTrust cloud API key used to reach 17 Remote Support SaaS tenants, so every API key carrying site-administrative capability — including keys the vendor holds against the customer's own tenant — needs a named owner, a scope, an expiry and a revocation path inside the same tier. Precondition, and it is the half this control is most often over-claimed on: jump-host routing, per-session step-up and just-in-time elevation constrain interactive administrator logons and do nothing to a machine-to-machine key presenting valid credentials to the API, because no session is ever opened for a step-up to interrupt. For that identity class the control reduces to enumeration, scoping and rotation, and a tenant that has recorded the vendor's key as simply 'vendor-managed' holds no lever at all until that key is listed as an administrative identity in its own right. Distinguishing test: produce the list of identities that can administer the PRA/RS site and confirm every non-human key on it has an owner and a revocation path — an attestation that every named BeyondTrust administrator authenticates with MFA passes cleanly while the documented access path stays open.",
+        "evidence": "Packet vector: 'A vulnerability has been discovered in Privileged Remote Access (PRA) and Remote Support (RS) which can allow an attacker with existing administrative privileges to inject commands and run as a site user.' affected: PRA and RS on-premises and SaaS deployments, where an attacker with existing administrative privileges uploads a malicious file processed without OS-command sanitization, executing commands as the site user. active_exploitation_notes: 'Exploited as a zero-day by the Chinese state-sponsored group Silk Typhoon in December 2024, chained with CVE-2024-12356 to steal a BeyondTrust API key and pivot into 17 Remote Support SaaS tenants, including the U.S. Treasury Department.' NIST-800-53-AC-6 gap: 'Least-privilege scoping alone does not stop an attacker who already holds legitimate admin credentials (via a stolen vendor API key) from injecting OS commands through the file-upload handler.' UK-CAF-B4 gap: 'Supply-chain and third-party PAM tooling assurance is insufficient when the vendor's own cloud API key can be silently compromised and used to reach customer tenants.'",
+        "gap_closes": [
+          "NIST-800-53-AC-6",
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-078",
+        "name": "ENDPOINT-MGMT-DEPLOYMENT-CHANNEL-INTEGRITY",
+        "description": "The primitive on this entry is OS command execution as the site user on a remote-support server, reached by uploading a file the backend processes without neutralizing embedded command sequences — so the exposed asset is the whole PRA/RS installation and everything it stores and hands out: session artifacts, technician-facing client downloads, and the site's own service configuration. Treat that content as a privileged distribution channel rather than as application data: file-integrity-monitor the PRA/RS installation and every directory from which it serves artifacts, alert on writes that do not reconcile to a recorded, approved administrator change or a vendor update, and hold the support server to KEV-priority patching as a management-plane asset in its own right. That patching half is concrete here rather than generic: the packet records the December 2024 fix in BT24-11 with all cloud instances patched by 2024-12-16 while self-hosted instances required manual patching, so a self-hosted site is remediated only by an operator action someone has to schedule, and an estate that read the vendor's cloud-side completion as its own is unpatched. This is also the control that still carries value after that fix lands, because the fix closes the injection path and removes nothing that was written or executed through it during the zero-day window. Precondition, and it decides whether the monitoring is worth anything on this product: the upload arrives inside an authenticated administrative session, so the presence of an administrator login is not evidence the write was sanctioned — the alert only distinguishes attacker activity when it is reconciled against change records, and a site with no change record to reconcile against produces an alert it cannot adjudicate. On remediation status, the packet registers no live-patch path, and its host-reboot flag says nothing about the service being restarted onto the fix, so completion is measured on the version the running PRA/RS site reports rather than on the update having been applied.",
+        "evidence": "Packet: CWE-78; CVSS 6.6; RWEP 50; poc_available false; active_exploitation confirmed; cisa_kev true with kev_date 2025-01-13. attack_vector: the attacker 'uploads a specially crafted file through the admin console; the backend fails to neutralize embedded OS command sequences, so the commands execute with the privileges of the site user.' affected_versions: 'RS/PRA 22.1.x and later prior to the December 2024 fix in BT24-11 (all cloud instances patched by 2024-12-16; self-hosted instances required manual patching)'. patch_available true; live_patch_available false; live_patch_notes null; patch_required_reboot false. NIST-800-53-SI-2 gap: 'This flaw was exploited as a zero-day by a nation-state actor before a patch existed, so patch-SLA-based remediation could not have prevented the initial Treasury compromise.' ISO-27001-2022-A.8.16 gap: 'Monitoring keyed to failed-auth and anomalous logins does not flag command injection issued through a legitimately-authenticated session riding a stolen vendor API key, so A.8.16 telemetry read the Treasury intrusion as normal privileged use.'",
+        "gap_closes": [
+          "ISO-27001-2022-A.8.16",
+          "NIST-800-53-SI-2"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-037",
+        "name": "FLEET-COMPROMISE-IR-PLAYBOOK",
+        "description": "A Remote Support / Privileged Remote Access site is a fleet control plane in the exact sense this control means — it holds standing access into every system its technicians support — and the packet documents the compromise propagating along that shape: a stolen BeyondTrust cloud API key reaching 17 Remote Support SaaS tenants, including the U.S. Treasury Department. Written in this product's terms and before it is needed, the playbook is: revoke and reissue every API key and site credential on notification of a vendor-side or tenant-side compromise; enumerate the support sessions, jump items and file transfers the site recorded across the suspected exposure window; rotate credentials for every account a technician used through the platform in that window, because those credentials transited a system on which an attacker was running commands as the site user; and fix quarantine criteria for the downstream endpoints that had a session in the window rather than negotiating them under time pressure. The trigger matters as much as the content here. The packet's compromise originated at the vendor and arrived at customers through a legitimately issued key, so the playbook has to be startable from a vendor advisory or a tenant notification and not only from the customer's own alerting — the customer-side telemetry, as the monitoring gap on this entry records, read the activity as normal privileged use. Precondition: this control bounds the damage of an intrusion that has already happened. It neither detects the command injection nor prevents it, and the rotation step is only complete if it covers the vendor-held key alongside the customer's own credentials — a rotation that reissues site passwords while leaving the vendor's cloud key in place leaves the documented access path intact.",
+        "evidence": "Packet active_exploitation_notes: 'Exploited as a zero-day by the Chinese state-sponsored group Silk Typhoon in December 2024, chained with CVE-2024-12356 to steal a BeyondTrust API key and pivot into 17 Remote Support SaaS tenants, including the U.S. Treasury Department. Ransomware status is unflagged in KEV for this entry.' affected: PRA and RS on-premises and SaaS deployments; commands execute as the site user. AU-Essential-8-Patch gap: 'Application patching alone does not address a vendor-side API key compromise; requires companion API-key rotation and access-anomaly monitoring.' NIS2-Art21-vulnerability-management gap: 'EU operators relying on BeyondTrust PRA/RS as a privileged-access gateway need vendor-supply-chain risk monitoring, not just internal patch cadence, since the compromise originated at the vendor.' ISO-27001-2022-A.8.16 gap records that the customer-side telemetry 'read the Treasury intrusion as normal privileged use'.",
+        "gap_closes": [
+          "AU-Essential-8-Patch",
+          "NIS2-Art21-vulnerability-management"
+        ]
+      }
+    ]
   },
   "CVE-2023-48365": {
     "name": "Qlik Sense HTTP Tunneling Vulnerability",
@@ -40673,7 +40966,31 @@
         "adequate": false,
         "gap": "EU operators of MiCollab as unified-communications infrastructure need emergency out-of-cycle patch processes for unauthenticated critical flaws, not standard change-management timelines."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "The interval this control has to compress on MiCollab is the one the packet measures: watchTowr's disclosure in December 2024, active exploitation of internet-facing NuPoint Unified Messaging endpoints within days of it, and the KEV listing on 2025-01-07 — days, against the change-management cycle a unified-communications platform is normally patched on, which is what this entry's flaw-remediation, internet-facing-patching and vulnerability-handling gaps each record. Applied here the requirement is an out-of-cycle emergency window rather than the next UC maintenance slot, and the population is every instance publishing the NuPoint Unified Messaging component, not only the one the asset register lists as the UC platform. The packet gives the vulnerable range as the NPM component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) and does not name a fixed build, so the target level has to be taken from the vendor advisory for the deployed release rather than assumed. patch_required_reboot is false, meaning no host reboot — not that the fixed code is live: live_patch_available is false and no live-patch path is recorded, so an instance counts as remediated only once the running NuPoint service is executing the fixed build. Priority follows the packet rather than the CVSS band alone — a public proof-of-concept, confirmed exploitation, a KEV ransomware association, and the packet's note that this traversal is frequently chained with CVE-2024-55550 make it a chain-entry item rather than a standalone UC patch ticket. And the update is not the whole of remediation: an instance that was internet-facing while the exploit was public has already had provisioning and configuration data read by an unauthenticated caller, and applying the fix closes the path without recalling what was taken, so material held there needs rotation rather than being closed on the patch record.",
+        "evidence": "Packet: patch_available true; affected_versions 'NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201)' with no fixed build named; cisa_kev true with kev_date 2025-01-07; active_exploitation confirmed, notes record exploitation against internet-facing MiCollab NuPoint Unified Messaging endpoints shortly after watchTowr's December 2024 disclosure, frequent chaining with CVE-2024-55550, and a CISA KEV ransomware association; poc_available true; cvss 9.1, rwep_score 72. patch_required_reboot false, live_patch_available false, live_patch_notes null. The NIST-800-53-SI-2 gap records the disclosure-to-KEV window as days, far shorter than typical enterprise patch-SLA cycles for UC platforms; AU-ISM-1546 records exploitation within days of disclosure. The vector states the exploit allows an attacker to view, corrupt, or delete users' data and system configurations.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "AU-ISM-1546",
+          "NIS2-Art21-vulnerability-management",
+          "ISO-27001-2022-A.8.8"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-129",
+        "name": "ENTERPRISE-ERP-MANAGEMENT-FUNCTION-AUTHENTICATION",
+        "description": "The path-sanitization boundary in front of MiCollab's NuPoint Unified Messaging component is where the product makes its access decision for everything behind it, and this CVE is that boundary failing: the packet has an unauthenticated caller sending a novel '..;/' sequence the sanitizer does not recognise, escaping the intended directory scope to reach internal AXIS2 SOAP services and read provisioning and configuration data or trigger limited administrative actions. Bound to this product, the control means those internal services — the AXIS2 SOAP endpoints and each administrative function reachable through them — authorize their own caller before acting rather than inheriting a verdict from the front-end path scoping, so that defeating the sanitizer yields a reachable endpoint instead of an executed administrative action; and that the NuPoint Unified Messaging component is not published to unauthenticated internet traffic, which this entry's own system-security gap names as the root cause. Distinguishing test: from an unauthenticated position outside the deployment, send the traversal sequence against a staging MiCollab and confirm the internal SOAP service refuses the caller rather than answering — an instance that passes a MiCollab user-account and role review still answers this request, because the attacker never authenticates as any MiCollab user and no account model is ever consulted. Preconditions, and they are load-bearing here. The caller-side authorization is a property the vendor update establishes; this control states what to verify, it does not implement it. Restricting reachability bounds who can send the sequence but closes nothing for anything inside the permitted segment, and that lever is unavailable where NuPoint Unified Messaging must stay published for remote users — which is precisely the deployment the packet describes as the exploited population — so it is a holding measure for the days between disclosure and the fix, not a closure. And because exploitation is confirmed and this read primitive is frequently chained with CVE-2024-55550, an instance reachable while the exploit was public has already disclosed provisioning data; restricting access afterwards does not recall it, so credentials and configuration held there need rotation.",
+        "evidence": "Packet vector: 'A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could allow an unauthenticated attacker to conduct a path traversal attack, due to insufficient input validation.' attack_vector: an unauthenticated attacker sends a request containing a novel '..;/' traversal bypass to the NuPoint Unified Messaging endpoint, escaping the intended directory scope to reach internal AXIS2 SOAP services and read provisioning/configuration data or trigger limited administrative actions. The NIST-800-53-SC-7 gap states the vulnerability is itself a boundary-bypass primitive whose traversal sequence was unrecognized by the application's path-sanitization boundary, so standard boundary-protection assumptions failed to hold; the UK-CAF-B4 gap states internet exposure of the NuPoint Unified Messaging component to unauthenticated traffic is itself the root cause and that segmentation should have limited exposure regardless of patch status. poc_available true; active_exploitation confirmed and frequently chained with CVE-2024-55550.",
+        "gap_closes": [
+          "NIST-800-53-SC-7",
+          "UK-CAF-B4"
+        ]
+      }
+    ]
   },
   "CVE-2020-2883": {
     "name": "Oracle WebLogic Server Unspecified Vulnerability (CVE-2020-2883)",
@@ -41616,7 +41933,39 @@
         "adequate": false,
         "gap": "Network security controls did not restrict firewall management-plane access to trusted administrative networks only."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-030",
+        "name": "PERIMETER-DEVICE-ZERODAY-SLA-TIER",
+        "description": "These units are perimeter firewalls and VPN concentrators — the device is the trust boundary, which is why a standard firmware-patch window is the wrong instrument for a traversal in their web management interface that a ransomware group was already using for initial access. For this CVE the tier requirement is that within the clock opened by the 2024-12-03 KEV listing, every affected unit either runs ZLD V5.39 or has its web management interface isolated from untrusted networks until it does. Scope is all four series the packet names, at each one's own affected range — ATP V5.00 through V5.38, USG FLEX V5.00 through V5.38, USG FLEX 50(W) V5.10 through V5.38 and USG20(W)-VPN V5.10 through V5.38 — because an estate standardised on the USG20(W)-VPN or the USG FLEX 50(W) reports clean against a sweep scoped to the ATP series the summary leads with. Completion is measured on the firmware version the unit is executing: the packet records patch_required_reboot true and live_patch_available false, so a unit that has had V5.39 uploaded but has not restarted onto it is still running the traversal-vulnerable code and counts as exposed, and a management console showing the firmware as staged is not evidence of remediation. The isolation branch is the one that needs its condition stated: pulling the web management interface off the internet removes the internet-reachable path the packet identifies as the exploitation precondition, but it does not fix the traversal — any caller inside whatever segment retains access still reaches it — and it is unavailable where administrators must reach the interface remotely, in which case the permitted set is a named administrative or jump network rather than 'reduced exposure'.",
+        "evidence": "Packet affected: 'Zyxel ATP, USG FLEX, USG FLEX 50(W), and USG20(W)-VPN series firewalls running ZLD firmware; the web management interface allows directory traversal to download or upload files via a crafted URL.' affected_versions: 'ATP series V5.00-V5.38', 'USG FLEX series V5.00-V5.38', 'USG FLEX 50(W) series V5.10-V5.38', 'USG20(W)-VPN series V5.10-V5.38', 'fixed in ZLD V5.39'. cisa_kev true with kev_date 2024-12-03; active_exploitation confirmed; poc_available true; rwep_score 77; cvss 7.5; patch_available true; patch_required_reboot true; live_patch_available false. The NIST-800-53-SI-2 gap records that 'Firmware patch-SLA cadence did not close the window before Helldown began using this flaw for initial access'; the AU-Essential-8-Patch gap records that 'Patch-applications control alone does not compensate for internet-exposed firewall management planes.'",
+        "gap_closes": [
+          "AU-Essential-8-Patch",
+          "NIST-800-53-SI-2"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-032",
+        "name": "PERIMETER-COMPROMISE-REBUILD-NOT-PATCH",
+        "description": "The packet says the crafted URL both downloads and uploads files, and that Helldown affiliates used this traversal as initial access into victim networks from around November-December 2024 — before and during the period operators were still scheduling firmware. That combination is what this control exists for: upgrading an ATP, USG FLEX, USG FLEX 50(W) or USG20(W)-VPN unit to ZLD V5.39 closes the traversal, but it does not delete a file that was already written to the device and does not invalidate a credential or configuration item that was already read off it. For these firewalls the control means any unit whose web management interface was reachable from an untrusted network while it ran an affected V5.00-V5.38 build is handled as a compromise rather than as a patch item: its configuration exported for offline review before anything is changed, the unit rebuilt from a known-good image and a known-good configuration instead of upgraded in place, and every credential the device held or brokered rotated at its source — local administrator accounts, VPN and remote-access users, directory bind accounts, pre-shared keys and device certificates. Distinguishing test: instead of asking whether the unit now reports V5.39, ask its filesystem and configuration whether anything was added or altered during the window it ran an affected build, and whether each credential it held carries a rotation date later than the end of that window. Precondition, and the reason this is a branch of the incident path rather than a replacement for it: rebuilding the device removes on-device persistence only. It does not evict an attacker who already used what the traversal yielded to move into the network — the packet records ransomware deployment into victim networks as the objective — so the internal investigation proceeds regardless of what state the firewall is in.",
+        "evidence": "Packet vector: the traversal in the web management interface 'could allow an attacker to download or upload files via a crafted URL'. attack_vector: 'An attacker sends a crafted URL to the ZLD web management interface that traverses outside the intended directory scope, allowing arbitrary file download or upload — used by Helldown ransomware affiliates as initial access into victim networks.' active_exploitation_notes: 'Used as an initial-access vector by the Helldown ransomware group from around November-December 2024 to compromise internet-exposed Zyxel firewall/VPN management interfaces before deploying ransomware into victim networks. CISA KEV flags ransomware use as Known.' active_exploitation confirmed; kev_date 2024-12-03; patch_available true with fixed build ZLD V5.39; patch_required_reboot true; live_patch_available false. The ISO-27001-2022-A.8.8 gap records that 'Technical vulnerability management on firewall firmware assumes scheduled updates, but Helldown ransomware operators used this directory-traversal for initial access within the patch window, so the standard's cadence-based timescale left the internet-exposed management interface exploitable.'",
+        "gap_closes": [
+          "ISO-27001-2022-A.8.8"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-134",
+        "name": "DEVICE-MANAGEMENT-GATEWAY-CONFIG-ENDPOINT-AUTH-INPUT-NEUTRALIZATION",
+        "description": "The management plane the packet names is the ZLD web management interface on these Zyxel firewalls, and the defect sits on it: a crafted URL escapes the intended directory scope and drives a file download or upload. Bound to this product, the control means every file-serving and file-accepting path on that interface authorizes its caller before the file operation is performed at all, and normalizes and validates the resolved path before any read or write executes, so a caller-supplied URL cannot select which file is served or overwritten; and that no ATP, USG FLEX, USG FLEX 50(W) or USG20(W)-VPN unit is left with that interface reachable from a network that has no operational need to reach it. The reachability half is the one the packet ties directly to exploitation — internet-exposed management interfaces are what Helldown affiliates compromised — so the administrative surface belongs on an administrative or jump network, with the WAN side of the management interface closed, rather than on the internet with a strong administrator password standing in for a boundary. Distinguishing test: on a staging unit, request each file path the management interface serves and submit each upload it accepts, from an unauthenticated caller on a segment with no administrative role, using a URL whose path resolves outside the intended directory, and confirm it is refused before anything is read or written. Precondition, and it is the one most often skipped: the caller authorization and path normalization are properties the vendor establishes in ZLD V5.39 — this control states what to verify, it does not implement it. Until a unit has restarted onto V5.39, restricting which segments can reach the management interface bounds who can send the crafted URL but leaves the endpoint fully exploitable to anything inside the permitted segment, and that restriction is unavailable wherever the interface must remain reachable for remote administration.",
+        "evidence": "Packet vector: 'A directory traversal vulnerability in the web management interface of Zyxel ATP series firmware versions V5.00 through V5.38, USG FLEX series firmware versions V5.00 through V5.38, USG FLEX 50(W) series firmware versions V5.10 through V5.38, and USG20(W)-VPN series firmware versions V5.10 through V5.38 could allow an attacker to download or upload files via a crafted URL.' cwe_refs CWE-22; affected_versions record the fix as 'fixed in ZLD V5.39'; patch_available true, patch_required_reboot true, live_patch_available false. The NIST-800-53-SC-7 gap records that 'Boundary protection was insufficient — the ZLD web management interface was reachable from the internet, the precondition for this exploitation chain'; the NIS2-Art21-network-security gap that 'Network security controls did not restrict firewall management-plane access to trusted administrative networks only'; the UK-CAF-B4 gap that 'System security lifecycle management allowed perimeter firewall management interfaces to remain internet-exposed.' active_exploitation_notes records Helldown compromising 'internet-exposed Zyxel firewall/VPN management interfaces'.",
+        "gap_closes": [
+          "NIST-800-53-SC-7",
+          "NIS2-Art21-network-security",
+          "UK-CAF-B4"
+        ]
+      }
+    ]
   },
   "CVE-2023-45727": {
     "name": "North Grid Proself Improper Restriction of XML External Entity (XXE) Reference Vulnerability",
@@ -42514,7 +42863,31 @@
         "adequate": false,
         "gap": "Essential Eight patch-applications guidance targets prompt remediation for exploited internet-facing services; a years-old MEDIUM CVE quietly returning to active-exploitation status falls outside routine patch-cadence triage."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "For this Jira entry the control means the remediation clock starts at the 2024-11-12 KEV listing, not at the CVSS 5.3 band that kept the CVE off high-severity-only remediation queues for the years the fixes had already existed. The mechanics are branch-specific and this is where the SLA is usually missed on Jira: the packet gives three separate fixed builds — before 8.5.14, 8.6.0-8.13.5 fixed in 8.13.6, and 8.14.0-8.16.0 fixed in 8.16.1 — so an estate pinned to the 8.5.x line closes this by reaching 8.5.14, and 'upgrade to the newest release' is a different change with a different approval path that instances on a long-term branch will not take inside the window. Completion is measured on the build the running instance reports, per Server instance and per Data Center node, not on the installer having run: live_patch_available is false, so there is no way to close the traversal on a process that is still executing pre-fix code, and patch_required_reboot false records only that no host reboot is needed — it does not mean the fix is live before the Jira process comes up on the new build. Speed matters beyond the patch record because of what the flaw yields: the packet has the unauthenticated read used to harvest servlet-mapping and configuration detail from web.xml ahead of follow-on attacks, and that material stays useful to the attacker after the upgrade lands, so an instance that was internet-facing during the exposure window needs the disclosed configuration reviewed rather than being closed on the version alone.",
+        "evidence": "Packet fields for CVE-2021-26086: cisa_kev true with kev_date 2024-11-12, active_exploitation confirmed, poc_available true, cvss 5.3 against rwep_score 67, patch_available true, patch_required_reboot false, live_patch_available false, live_patch_notes null. affected_versions gives the three fixed branches: before 8.5.14; 8.6.0 - 8.13.5 (fixed in 8.13.6); 8.14.0 - 8.16.0 (fixed in 8.16.1). The NIST-800-53-SI-2 gap states fixes existed years before the November 2024 KEV listing and that SI-2 SLAs commonly track vendor severity rather than active-exploitation status. active_exploitation_notes records active exploitation of unauthenticated file-read against internet-facing Jira Server/Data Center instances, used to harvest servlet-mapping and configuration detail from web.xml ahead of follow-on attacks, and that the entry is not flagged as ransomware-associated.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "ISO-27001-2022-A.8.8",
+          "NIS2-Art21-vulnerability-management",
+          "AU-Essential-8-Patch"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-074",
+        "name": "CVE-REGRESSION-WATCHER",
+        "description": "This entry is the case the watcher's trigger condition is written for, and it fires cleanly here: a CVE identifier assigned in 2021 appearing in current exploitation reporting and carrying a public proof-of-concept, three years after the fixed Jira branches shipped. What the triage must then resolve is specific to this product rather than the regression case the control was first written against — the finding is not a re-introduced defect but a Jira estate still running a pre-8.5.14, pre-8.13.6 or pre-8.16.1 branch, so the intake hit must be closed by resolving each instance's running branch against those three fixed builds rather than by checking whether the vendor shipped a fix. The distinguishing test is on the intake pipeline, not the host: replay a threat feed containing the 2024 exploitation reporting for this 2021 identifier and confirm it lands on the remediation queue. A pipeline that ingests only advisories for identifiers assigned in the current cycle, or that filters intake by CVSS band, never surfaces it at all — which is exactly how a fix that had been available for years went unapplied on internet-facing instances until CISA listed the CVE.",
+        "evidence": "Packet fields for CVE-2021-26086: the identifier is a 2021 assignment, kev_date is 2024-11-12, poc_available is true and active_exploitation is confirmed. The AU-Essential-8-Patch gap states that a years-old MEDIUM CVE quietly returning to active-exploitation status falls outside routine patch-cadence triage. The ISO-27001-2022-A.8.8 gap states that Jira's low CVSS kept it off many high-severity-only remediation queues despite the later KEV listing. affected_versions supplies the fixed branches the triage resolves against: 8.5.14, 8.13.6 and 8.16.1.",
+        "gap_closes": [
+          "AU-Essential-8-Patch",
+          "ISO-27001-2022-A.8.8"
+        ]
+      }
+    ]
   },
   "CVE-2014-2120": {
     "name": "Cisco Adaptive Security Appliance (ASA) Cross-Site Scripting (XSS) Vulnerability",
@@ -42840,7 +43213,30 @@
         "adequate": false,
         "gap": "CAF B4 secure configuration explicitly expects removal of unsupported internet-facing software; the real fix here is decommissioning, not patching."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-122",
+        "name": "EOL-ASSET-DECOMMISSION",
+        "description": "This entry is the case the control exists for and the packet states both halves. patch_available is true, so a build past the affected 'through 1.9.6' range exists and reaching it is available — but the packet's gaps describe an EOL, unmaintained web server that least-functionality controls should have listed as prohibited software, and the UK-CAF-B4 gap says the real fix is decommissioning rather than patching. Those facts define the requirement: on a host that must keep serving until it can be replaced, moving past 1.9.6 is an interim state; the terminal state is removal, because an unmaintained daemon is exposed not only to this traversal but to whatever is found in it next, and the packet records five years between disclosure and the 2024-11-07 KEV listing that finally forced attention. Scope to what the packet names — Nostromo nhttpd instances at or below 1.9.6 — and do not extend the removal work to other small HTTP daemons; the packet ties the traversal to the http_verify() authentication path in nhttpd on a non-chrooted instance and gives no mapping into any other server, so treating every lightweight web daemon in the estate as an instance of this CVE manufactures findings and replacement work against software no evidence implicates. Operationally: enumerate every nhttpd instance reachable from an untrusted network with its version, put each on a dated replacement schedule onto a maintained HTTP server, and for any instance that must stay in service in the meantime take the fixed build from the project rather than assuming a version number, and remove its reachability from untrusted networks. Precondition on the interim half: the packet registers no live-patch path, so replacing the binary on disk does not change what the listening process serves — the running daemon keeps executing the old image until it is restarted, and completion is the version the listener reports, not the version on the filesystem. And because active exploitation is confirmed and the outcome is remote code execution on a non-chrooted server, a host that was exposed is not remediated by the upgrade alone: what the web-server account could reach needs triage rather than being closed on the version record.",
+        "evidence": "Packet name: 'Nostromo nhttpd Directory Traversal Vulnerability'. affected: 'Nostromo nhttpd web server; directory traversal in the http_verify() authentication function of a non-chrooted server instance allows unauthenticated remote code execution.' affected_versions: 'through 1.9.6'. cwe_refs: CWE-22. cvss 9.8, rwep_score 63, poc_available true, active_exploitation confirmed, cisa_kev true with kev_date 2024-11-07. patch_available true, patch_required_reboot false, live_patch_available false, live_patch_notes null. The NIST-800-53-CM-7 gap: 'Least-functionality controls should have flagged an EOL, non-chrooted web server as prohibited software years before the 2024 KEV listing.' The UK-CAF-B4 gap: 'CAF B4 secure configuration explicitly expects removal of unsupported internet-facing software; the real fix here is decommissioning, not patching.' The NIS2-Art21-vulnerability-handling gap: 'requires an inventory that catches unsupported software still exposed to the internet; EOL nhttpd instances are exactly the blind spot this control targets.' The AU-Essential-8-App-Hardening gap: 'Application-hardening guidance would flag an unmaintained, non-chrooted HTTP daemon as prohibited attack surface.'",
+        "gap_closes": [
+          "NIST-800-53-CM-7",
+          "UK-CAF-B4",
+          "NIS2-Art21-vulnerability-handling",
+          "AU-Essential-8-App-Hardening"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-018",
+        "name": "SCANNER-PAPER-COMPLIANCE-TEST",
+        "description": "The A.8.8 gap on this entry records the paper-compliance outcome precisely: an EOL, unmaintained nhttpd instance evaded routine vulnerability-scanning cadences for five years before the KEV listing forced attention. The scans ran the whole time and reported clean — that clean report is what the ISMS recorded as conformance, and it is the artefact this control tests. For this CVE the operational test is whether the estate's scanning can name a running nhttpd at all: stand up an nhttpd instance at or below 1.9.6 on a staging host, run the exact scan profile the estate is attested with, and require the report to identify the daemon, its version, and this CVE. A scan cycle built around managed-package inventory and expected service ports produces nothing against a host serving nhttpd outside that inventory, and the absence of a finding is indistinguishable in the report from the absence of the software — which is the whole failure. Make the pass condition the positive identification, not the absence of an alert. Precondition and limit: this is a detection test, not a remediation. Finding the daemon does not remove it, and a finding that lands in a scanner queue rather than on the dated replacement schedule reproduces the five-year outcome in a different system of record. It also only covers hosts the scan can reach and is authorised to inspect; an nhttpd instance on a segment or a host outside the scan's scope is invisible to the test as well as to the scan, so scope coverage has to be demonstrated separately rather than assumed from a clean estate-wide result.",
+        "evidence": "The ISO-27001-2022-A.8.8 gap on this entry: 'A.8.8 technical vulnerability management requires ongoing visibility into internet-facing software; an EOL, unmaintained nhttpd instance evaded routine vulnerability-scanning cadences for five years before KEV listing forced attention.' Packet affected_versions: 'through 1.9.6'. affected: 'Nostromo nhttpd web server; directory traversal in the http_verify() authentication function of a non-chrooted server instance allows unauthenticated remote code execution.' cisa_kev true, kev_date 2024-11-07, active_exploitation confirmed with active_exploitation_notes citing 'ongoing internet-wide scanning and exploitation of exposed Nostromo nhttpd servers for remote code execution'.",
+        "gap_closes": [
+          "ISO-27001-2022-A.8.8"
+        ]
+      }
+    ]
   },
   "CVE-2024-8957": {
     "name": "PTZOptics PT30X-SDI/NDI Cameras OS Command Injection Vulnerability",
@@ -44107,7 +44503,39 @@
         "adequate": false,
         "gap": "SAP shipped a fix in 2019, but KEV addition in 2024 shows five years of unpatched exposure among internet-facing instances — patch-SLA enforcement failed long-term, not just at disclosure."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-133",
+        "name": "ECOMMERCE-PLATFORM-EXTENSION-UNTRUSTED-DESERIALIZATION-GUARD",
+        "description": "SAP Commerce Cloud (formerly Hybris) is the e-commerce platform this control governs, and the packet places the sink where the control says to look: not in core storefront code but in the platform's extensions — the packet's affected field names both the mediaconversion and virtualjdbc extensions, while the vector text mentions only virtualjdbc, so a review scoped to the vector's headline extension leaves the other one live. For this deployment the requirement is that neither extension passes request-supplied data to Java deserialization on any path an untrusted caller can reach, and that the patch and asset programmes enumerate the enabled extension set of each Commerce Cloud node as part of its code-execution surface rather than recording only the platform release. That enumeration is the load-bearing half here: exploitation yields arbitrary code execution with the 'Hybris' OS user's rights, so the blast radius is the application account that owns the storefront's data and integrations, and an inventory that lists 'SAP Commerce Cloud 1811' without listing which extensions that node loads cannot tell an assessor whether the vulnerable code is deployed. Distinguishing test: on a staging node of each affected release in the estate (6.4, 6.5, 6.6, 6.7, 1808, 1811, 1905), send a crafted serialized gadget-chain object to each interface the virtualjdbc and mediaconversion extensions expose, from a caller with no credentials, and confirm it is rejected before any deserialization runs — a paper attestation that the platform is patched, taken from a release banner while the extension set is never enumerated, passes cleanly while the object-injection sink stays reachable. Remediation is the SAP fix for the affected release, which the packet records as available; completion is measured on the extension code the running platform process is serving, since patch_required_reboot false records only that the host needs no reboot, not that a rebuilt artifact on disk is what the live process has loaded.",
+        "evidence": "Packet affected: 'SAP Commerce Cloud (formerly Hybris), mediaconversion and virtualjdbc extensions, vulnerable to unsafe Java deserialization enabling arbitrary code execution with \"Hybris\" OS user rights.' affected_versions: 6.4, 6.5, 6.6, 6.7, 1808, 1811, 1905. cwe_refs CWE-502; cvss 9.8; rwep_score 70; poc_available true; cisa_kev true with kev_date 2024-09-30; active_exploitation confirmed. patch_available true, patch_required_reboot false, live_patch_available false, live_patch_notes null. The ISO-27001-2022-A.8.8 gap records that 'Technical vulnerability management (asset + patch tracking) failed to catch a five-year-old vendor-patched flaw still present in production Commerce Cloud deployments'; the AU-Essential-8-Patch gap records that 'Essential Eight patch-application maturity presumes an asset inventory tracking the virtualjdbc extension that long-tail Commerce Cloud deployments plainly lacked.'",
+        "gap_closes": [
+          "ISO-27001-2022-A.8.8",
+          "AU-Essential-8-Patch"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-128",
+        "name": "APPSERVER-REMOTING-PROTOCOL-RESTRICTION",
+        "description": "The packet's attack vector puts this CVE squarely in the binary remoting-protocol class this control governs: the virtualjdbc extension exposes Java serialization over HTTP, RMI and JMXMP, the listener answers a caller that never authenticates, and the deserializer behind it is the vulnerable code — so a storefront WAF, TLS termination and web-tier hardening, which is what a Commerce Cloud deployment is usually audited against, never sit in front of the path that gets exploited. For this deployment the requirement is that the virtualjdbc and mediaconversion listeners accept connections only from the hosts that legitimately speak those protocols — the application-tier nodes and the administrative or integration hosts that actually use them — enforced by network ACL or host firewall rather than inferred from 'the Hybris cluster is internal', and that where an extension is not required by the deployment it is removed from the enabled extension set rather than left listening. Distinguishing test for this product: from a general user VLAN or an internet-facing segment against a staging node, open a connection to each RMI/JMXMP/HTTP serialization endpoint the two extensions expose and confirm the peer is dropped before the node reads any serialized content — an estate that passes storefront penetration tests and Commerce Cloud role audits while leaving the serialization listener reachable from any internal segment is still exposed to the unauthenticated gadget-chain path. Precondition, which is where this control is most often over-claimed: restricting reachability bounds who can send the payload, it does not remove the deserialization sink. Any host inside the permitted set still reaches it, so this is interim to applying the SAP fix on the affected release — and it is unavailable where an integration genuinely requires the listener to answer, in which case the permitted set is the named integration hosts and nothing else.",
+        "evidence": "Packet attack_vector: 'SAP Commerce Cloud's virtualjdbc extension exposes Java serialization over HTTP/RMI/JMXMP; an attacker sends a crafted gadget-chain serialized payload directly to the exposed listener to achieve remote code execution as the \"Hybris\" OS user.' The vector text records the flaw as 'unsafe deserialization used in SAP Commerce Cloud (virtualjdbc extension), versions 6.4, 6.5, 6.6, 6.7, 1808, 1811, 1905', and affected additionally names the mediaconversion extension. The NIST-800-53-SC-7 gap records that 'The virtualjdbc/JMXMP listener should never be reachable from untrusted networks, yet exploitation presumes direct network access to it — boundary protection was not enforced'; the UK-CAF-B4 gap records that 'Secure configuration guidance should have disabled or firewalled the legacy virtualjdbc extension where unused; long-tail exposure suggests this was not audited.' cvss 9.8, poc_available true, active_exploitation confirmed, patch_available true.",
+        "gap_closes": [
+          "NIST-800-53-SC-7",
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-018",
+        "name": "SCANNER-PAPER-COMPLIANCE-TEST",
+        "description": "What the packet documents is not a patch decision that went wrong but five years in which nobody's tooling reported the exposure: SAP shipped the fix in 2019 and the entry reached KEV in September 2024 against internet-facing Commerce Cloud instances that were never patched. For this CVE the control means a scan result of 'patched' derived from the Commerce Cloud platform release banner is paper compliance, because the vulnerable code lives in the virtualjdbc and mediaconversion extensions and exposure is decided by two facts a banner cannot carry — whether those extensions are in the node's enabled extension set, and whether their Java serialization listener answers from a segment the node should not be answering. The operational test has both parts: an authenticated inventory of the enabled extension set on every Commerce Cloud node, compared against the affected releases the packet names (6.4, 6.5, 6.6, 6.7, 1808, 1811, 1905) and against the version of the extension code the running platform process is actually serving rather than the artifact sitting on disk; and an unauthenticated reachability probe of the HTTP/RMI/JMXMP serialization listener from outside the application tier. A node that passes on its release string while the extension is loaded and the listener answers counts as unverified, not as compliant. This is also the test that distinguishes an asset register from an inventory: the packet's own gap describes long-lived deployments that no patch-verification process ever saw, and a scanner that cannot reach or authenticate to the Hybris node will report the same clean result for a node that does not exist, a node that is patched, and a node that has been exploitable since 2019.",
+        "evidence": "Packet active_exploitation_notes: 'An aged (2019) flaw added to CISA KEV in September 2024, indicating renewed/ongoing active exploitation against internet-facing SAP Commerce Cloud (Hybris) instances that were never patched — likely opportunistic scanning against long-lived unpatched deployments rather than a fresh campaign. Not flagged as ransomware.' kev_date 2024-09-30; cisa_kev true; active_exploitation confirmed; poc_available true; patch_available true; patch_required_reboot false; live_patch_notes null. The NIST-800-53-SI-2 gap records that 'SAP shipped a fix in 2019, but KEV addition in 2024 shows five years of unpatched exposure among internet-facing instances — patch-SLA enforcement failed long-term, not just at disclosure'; the NIS2-Art21-vulnerability-management gap records that 'A five-year-old known-fixed flaw remaining exploitable at scale indicates an absent asset-inventory/patch-verification process for SAP e-commerce infrastructure.' Extension scope from affected (mediaconversion and virtualjdbc) and affected_versions.",
+        "gap_closes": [
+          "NIS2-Art21-vulnerability-management",
+          "NIST-800-53-SI-2"
+        ]
+      }
+    ]
   },
   "CVE-2024-7593": {
     "name": "Ivanti Virtual Traffic Manager Authentication Bypass Vulnerability",
@@ -44255,7 +44683,30 @@
         "adequate": false,
         "gap": "The KEV due date is 3 days; a standard 30-day flaw-remediation SLA leaves internet-facing SharePoint exploitable for weeks after weaponization."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "For this SharePoint Server deserialization flaw the packet gives a 3-day KEV clock opening 2026-07-16 against the 30-day flaw-remediation SLA the entry records as inadequate, an available vendor update, and no live-patch path — so the requirement is that the update is driven as an out-of-band emergency change on the KEV clock rather than scheduled into the next maintenance window. Two things decide whether the deployment is real. The fixed build has to be taken per version from the MSRC guide the packet points to, because the entry carries affected versions only as \"Microsoft SharePoint Server (see MSRC guide for supported-version build numbers)\" — there is no single build number to compare against across an estate running more than one SharePoint version. And completion is measured on the build the running SharePoint service reports, not on the installer's exit code or an \"approved\" state in the management console: patch_required_reboot is false, which means no host reboot is demanded, not that the fix is live the moment the package installs — the entry's own Essential Eight gap records a deploy-and-reboot interval through which the pre-auth deserialization path on ports 80/443 stays open, so a server whose update is installed but whose SharePoint services have not been restarted onto the new build is still executing vulnerable code and must be counted as exposed until it has. Order the estate by internet reachability first, since that is where the packet records exploitation, but do not stop there: the flaw needs no authentication, and the packet records this class being chained into hands-on-keyboard intrusion, which puts internal instances within reach of an attacker who is already inside. Precondition: this control only compresses the clock. It does nothing for a server exploited before the update landed, which confirmed exploitation and a 3-day due date make a live possibility rather than a hypothetical — that case belongs to the rebuild control below.",
+        "evidence": "NIST-800-53-SI-2 gap: \"The KEV due date is 3 days (2026-07-16 to 2026-07-19); a standard 30-day flaw-remediation SLA leaves internet-facing SharePoint exploitable for weeks after weaponization.\" NIS2-Art21-patch-management gap: \"Routine patch cadence is insufficient against a 3-day KEV clock; emergency out-of-band patching is required.\" ISO-27001-2022-A.8.8 gap: \"Periodic technical-vulnerability review cannot match the same-day exploitation window observed for critical SharePoint RCE.\" AU-Essential-8-Patch gap: \"...patch maturity alone leaves the pre-auth deserialization path on ports 80/443 open through the deploy-and-reboot interval.\" affected_versions: \"Microsoft SharePoint Server (see MSRC guide for supported-version build numbers)\". patch_available true; patch_required_reboot false; live_patch_available false; live_patch_notes: \"No live-patching primitive for this product; the vendor update (no reboot required) is the remediation.\" active_exploitation_notes: KEV 2026-07-16 with a 3-day due date, confirmed active exploitation of internet-facing SharePoint servers, historically chained into web-shell drops and hands-on-keyboard intrusion.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "NIS2-Art21-patch-management",
+          "ISO-27001-2022-A.8.8"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-032",
+        "name": "PERIMETER-COMPROMISE-REBUILD-NOT-PATCH",
+        "description": "The packet's attack path for this CVE ends in code execution as the SharePoint service account, typically followed by a web-shell drop, with exploitation confirmed and a 3-day KEV due date — so for any SharePoint Server that was internet-reachable and below the fixed build during the exposure window, compromise is the default working assumption and the update is not the end of the response. The update closes the deserialization path; it removes nothing an attacker already wrote through it and it does not invalidate credentials or session material taken from the box. Applied here that means: preserve configuration and content for evidence, rebuild the server from a known-good baseline rather than patching in place, and rotate the SharePoint service account credential along with anything else that account could reach. The hunt keys on what the packet actually documents rather than on assumed signals — a web shell placed in the content the server serves, and code running under the SharePoint service identity — so look for files newly written into the server's web-serving directories during the window and for child processes spawned by the SharePoint service identity, not for exploit-tool signatures or process crashes. The exploit is a single crafted serialized request that the server processes through its normal request path: it produces no crash to alert on, and because the attacker never authenticates, it produces no authentication event either, so an estate whose logging is sign-in-centric has no record that it happened. Preconditions, and they are the ones this control is most often over-claimed past: rebuild-not-patch presumes a known-good baseline and a content restore point predating the exposure window — where the earliest backup falls inside that window, restoring reinstates whatever was planted and the artifact hunt is the only remaining check; and it presumes the estate can say which servers were reachable, and on which build, during the window. Where that record does not exist, the scope is every internet-facing instance, not the ones someone remembers.",
+        "evidence": "Packet attack_vector: \"An unauthenticated attacker sends a crafted serialized .NET payload to an internet-facing SharePoint endpoint; unsafe deserialization triggers a gadget chain that executes attacker code as the SharePoint service account, typically followed by a web-shell drop.\" active_exploitation_notes: \"Added to CISA KEV 2026-07-16 with a 3-day due date, indicating confirmed active exploitation of internet-facing SharePoint servers. Ransomware use is not yet confirmed but deserialization RCE on SharePoint has historically been chained into web-shell drops and hands-on-keyboard intrusion.\" UK-CAF-B4 gap: \"System-security assurance based on scheduled hardening reviews will not detect exploitation of an unauthenticated code-execution path in real time.\" AU-Essential-8-Patch gap: \"...patch maturity alone leaves the pre-auth deserialization path on ports 80/443 open through the deploy-and-reboot interval.\" active_exploitation confirmed; cvss 9.8; patch_available true; live_patch_available false.",
+        "gap_closes": [
+          "UK-CAF-B4",
+          "AU-Essential-8-Patch"
+        ]
+      }
+    ]
   },
   "CVE-2026-25089": {
     "name": "Fortinet FortiSandbox OS Command Injection Vulnerability (CVE-2026-25089)",
@@ -44556,7 +45007,30 @@
         "adequate": false,
         "gap": "The 3-day KEV due date reflects that this was exploited as a zero-day before any patch existed; a standard 30-day flaw-remediation SLA is far longer than the observed exploitation window."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-129",
+        "name": "ENTERPRISE-ERP-MANAGEMENT-FUNCTION-AUTHENTICATION",
+        "description": "The packet places this defect at exactly the layer this control governs: a missing authentication check (CWE-306) on a critical User Profiles administrative function in on-premises Microsoft SharePoint Server, reachable unauthenticated over the network via /_vti_bin/client.svc. The attack_vector shows the request-validation layer being stepped around rather than defeated — a crafted SOAP payload that omits the X-RequestDigest header and adds routing headers to reach an unvalidated code path — which is the pattern this control forbids: an administrative operation inheriting its authorization verdict from a validation layer that fronts it instead of deciding for itself. Bound to this product, the requirement is that each User Profiles administrative operation authorizes its caller inside its own code path, so a request that presents neither a digest nor a session cannot reach the operation at all, and that the farm's administrative surface is separated from the general-purpose client endpoint rather than sharing one entry point with it. This is also why the access-control gap cited on this entry cannot be closed operationally: the attacker never authenticates as any SharePoint principal, so per-account permission scoping is never consulted, and an access-control attestation showing every SharePoint administrator correctly assigned passes cleanly while this path stays open. Distinguishing test: on a staging farm at each of the three affected versions, issue unauthenticated SOAP requests to the User Profiles administrative endpoints through /_vti_bin/client.svc with the X-RequestDigest header omitted and the routing headers the packet describes added, and confirm each is refused before the operation runs. Preconditions: the endpoint-side authorization is a property the vendor update establishes — this control states what to verify, it does not implement it, and the packet records that update, which requires a reboot, as the remediation with no live-patching primitive available. Restricting which networks can reach the endpoint bounds the caller population only where the deployment permits it, and the packet's own boundary-protection gap records /_vti_bin/client.svc as an intended internet-facing service, so on a farm published to the internet that lever is unavailable and nothing stands between an untrusted caller and the missing check until the update and its reboot land.",
+        "evidence": "Packet fields: name = 'Microsoft SharePoint Server Missing Authentication for Critical Function Vulnerability'; cwe_refs = CWE-306; affected = 'On-premises Microsoft SharePoint Server: a missing authentication check on a critical User Profiles administrative function reachable unauthenticated via /_vti_bin/client.svc'; affected_versions = SharePoint Enterprise Server 2016, SharePoint Server 2019, SharePoint Server Subscription Edition; attack_vector = 'An unauthenticated attacker sends a crafted SOAP payload to /_vti_bin/client.svc targeting User Profiles administrative endpoints, omitting the X-RequestDigest header and adding routing headers to reach an unvalidated code path, elevating privileges over the network'; vector = 'Missing authentication for critical function in Microsoft Office SharePoint allows an unauthorized attacker to elevate privileges over a network'. Gap text used: ISO-27001-2022-A.5.15 = 'access control presumes authorisation is enforced at the function, but this flaw is a missing authentication check on a critical SharePoint operation reachable pre-auth over the network... a code defect A.5.15 cannot compensate for operationally'; UK-CAF-B4 = 'System security hardening cannot compensate for a code-level missing-authentication check on a critical administrative function reachable pre-auth'; NIST-800-53-SC-7 = 'Boundary protection does not help when the vulnerable /_vti_bin/client.svc endpoint is an intended internet-facing service'. Remediation state: patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes 'No live-patching primitive for this product; the vendor update requires a reboot and is the remediation'.",
+        "gap_closes": [
+          "ISO-27001-2022-A.5.15",
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "On this entry the KEV listing and the patch arrived together: the packet records confirmed in-the-wild exploitation as a zero-day before the July 14 2026 patch, and CISA adding it to KEV the same day with a three-day due date. The control's 'whichever is later' trigger therefore fires at patch availability, and its four-hour requirement is the only reading that matches an unauthenticated network privilege-elevation reachable pre-auth on an internet-facing service at CVSS 9.8. Applied to this product: every on-premises SharePoint Enterprise Server 2016, SharePoint Server 2019 and SharePoint Server Subscription Edition install is driven to its fixed build on the clock that opened 2026-07-14, counted per server rather than per farm, since a farm's patch record is not evidence about each server running the affected software. The packet records a vendor update that requires a reboot with no live-patching primitive, so a server that has installed the update but not completed its reboot is still executing the vulnerable code and must be counted as exposed rather than remediated; on servers carrying user-facing workloads the reboot is the step most likely to be deferred, and a deferral recorded as patched is the specific way this remediation goes wrong. Completion is measured on the build each server is actually running. Two things this control does not do, and both matter here. It gives nothing for the window before the fix: the flaw was exploited before any patch existed, so the 30-day flaw-remediation SLA the packet's gap describes was not merely slow, it had nothing to apply, and the coordinated-handling assumption of a disclosure-then-patch window that the EU gap names simply did not hold. And it does not evict an attacker already resident — the packet credits discovery to Mandiant incident responders and Google's FLARE team, stating the flaw was found inside active intrusions rather than routine research, so a farm that was network-reachable before the patch is a compromise-assessment and credential-rotation question, not something closed on the patch record.",
+        "evidence": "Packet fields: cisa_kev true, kev_date 2026-07-14; cvss 9.8; rwep_score 61; active_exploitation confirmed with active_exploitation_notes 'Confirmed exploited in the wild as a zero-day before the July 14 2026 patch; discovery credited to Mandiant incident responders and Google's FLARE team, indicating the flaw was found inside active intrusions rather than routine research. CISA added it to KEV the same day with a 3-day due date.'; affected_versions = SharePoint Enterprise Server 2016, SharePoint Server 2019, SharePoint Server Subscription Edition; patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes 'No live-patching primitive for this product; the vendor update requires a reboot and is the remediation'. Gap text used: NIST-800-53-SI-2 = 'The 3-day KEV due date reflects that this was exploited as a zero-day before any patch existed; a standard 30-day flaw-remediation SLA is far longer than the observed exploitation window'; AU-Essential-8-Patch = 'Essential 8 patch timelines (48 hours for internet-facing critical) still trail same-day active exploitation of an unpatched zero-day'; NIS2-Art21-vulnerability-handling = 'Coordinated vulnerability handling assumes a disclosure-then-patch window; an actively-exploited pre-patch zero-day gives operators no lead time to close exposure'. poc_available is false on this entry, so no public exploit code is claimed.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "AU-Essential-8-Patch",
+          "NIS2-Art21-vulnerability-handling"
+        ]
+      }
+    ]
   },
   "CVE-2026-15409": {
     "name": "SonicWall SMA1000 Appliances Server-Side Request Forgery Vulnerability",
@@ -44758,7 +45232,40 @@
         "adequate": false,
         "gap": "Boundary protection does not help when T3/IIOP management ports are exposed to the app tier or internet, which is common for WebLogic; the deserialization sink stays reachable."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-128",
+        "name": "APPSERVER-REMOTING-PROTOCOL-RESTRICTION",
+        "description": "WebLogic's T3 and IIOP listeners are exactly the binary remoting-protocol class this control governs: non-HTTP endpoints that answer and begin reconstructing an object before any authentication happens, on the same server whose HTTP tier is the only part most WebLogic deployments are audited against. The packet places the flaw in the Fusion Middleware Core component and has an unauthenticated network attacker reaching it over T3 or IIOP for full server takeover, so the operative question is not whether the deployed application enforces its roles but which hosts can open a T3 or IIOP connection at all. Bound to this product it means enumerating every WebLogic Server instance at 12.2.1.3.0, 12.2.1.4.0 or 14.1.1.0.0 — the three versions the packet names, including any the estate does not carry under the WebLogic name because it was installed as part of a larger Oracle deployment — and for each restricting the T3/IIOP listen ports to the admin server, cluster peers and application hosts that legitimately speak those protocols, enforced by network ACL or host firewall rather than inferred from 'WebLogic is internal', with the protocol disabled outright on instances that use neither. The distinguishing test for this product: from a general application or user VLAN on a staging deployment, open a T3 connection to the managed server's listen port and confirm it is dropped before the server reads the serialized payload — an estate that passes WebLogic account, role and password audits still exposes this path in full, because no credential is presented anywhere in the attack the packet describes. Precondition, and it is where this control is most often over-claimed: restricting reachability bounds who can send the object, it does not repair the deserializer. Any host inside the permitted set reaches the sink unchanged, and the measure is unavailable on instances where T3 or IIOP must remain reachable for clustering or remote clients — for those the only lever is the Oracle update.",
+        "evidence": "Packet affected: 'Oracle WebLogic Server (Fusion Middleware, Core component) reachable over the T3 or IIOP protocols by an unauthenticated network attacker; exploitation yields full server takeover.' affected_versions: 12.2.1.3.0, 12.2.1.4.0, 14.1.1.0.0. cwe_refs: CWE-502. The NIST-800-53-SC-7 gap records that boundary protection 'does not stop the flaw if the T3/IIOP admin ports are reachable from the app tier or internet; WebLogic management protocols are frequently left exposed, so segmentation alone leaves the deserialization sink live'. The ISO-27001-2022-A.8.8 gap records that technical-vulnerability management 'does not enforce protocol-level allowlisting of T3/IIOP', and the NIS2-Art21-vulnerability-management gap that the requirement 'does not mandate disabling or filtering the T3/IIOP protocols that carry the exploit, which is the only reliable compensating control when patching lags'. The UK-CAF-B4 gap names 'the exposed T3 port as the live entry point'. CISA KEV listed 2024-09-18, active_exploitation confirmed, poc_available true, CVSS 9.8, RWEP 75.",
+        "gap_closes": [
+          "NIST-800-53-SC-7",
+          "ISO-27001-2022-A.8.8",
+          "NIS2-Art21-vulnerability-management",
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-125",
+        "name": "SERVICE-INTERNAL-PROTOCOL-DESERIALIZATION-HARDENING",
+        "description": "This is the half of the problem that survives after network placement has been fixed as far as it can be. The packet's attack path is a crafted serialized Java object arriving over T3 or IIOP which WebLogic deserializes through a vulnerable gadget chain, executing attacker code as the server process — so the listener is a trust boundary, and treating it as an internal convenience is what makes a routable path into a takeover. Applied to this deployment the control means the T3/IIOP handler does not inherit its safety from where the server sits: constrain which types the protocol path is permitted to reconstruct so that content arriving on the port cannot select the gadget chain, and require peer authentication on every remoting protocol the instance has enabled rather than only the one the applications happen to use — a deployment that authenticates its T3 clients but leaves IIOP enabled and open has not closed the packet's stated path, which names both. The distinguishing test: from an unauthenticated host that can route to the T3 port of a staging instance, send a serialized object of a type the application protocol never legitimately conveys and confirm the connection is refused before the object is reconstructed — a WebLogic instance that passes a patch-level and role audit while reconstructing arbitrary types from unauthenticated peers still exposes this sink and the next one found in the same class libraries. Precondition, stated plainly because the corpus keeps getting this wrong: an operator-side type constraint bounds the chains already known. The packet says exploitation runs through 'a vulnerable gadget chain', and a constraint expressed as known-bad chains is defeated by the next chain in the same libraries — so this reduces what can be sent at the sink, it does not make the port safe to expose, and it is not a substitute for the Oracle update, which is what removes this chain.",
+        "evidence": "Packet attack_vector: 'An unauthenticated attacker sends a crafted serialized Java object over the WebLogic T3 or IIOP protocol; WebLogic deserializes it through a vulnerable gadget chain and executes attacker code as the server process, resulting in full takeover.' cwe_refs: CWE-502. Vector text: 'Easily exploitable vulnerability allows unauthenticated attacker with network access via IIOP, T3 to compromise Oracle WebLogic Server.' The NIST-800-53-SC-7 gap records that segmentation alone 'leaves the deserialization sink live'. poc_available true, active_exploitation confirmed, CISA KEV 2024-09-18, CVSS 9.8.",
+        "gap_closes": [
+          "NIST-800-53-SC-7"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "For this entry the clock runs from the 2024-09-18 KEV listing, because the population that matters is the WebLogic instances still sitting at 12.2.1.3.0, 12.2.1.4.0 or 14.1.1.0.0 long after the Oracle fix shipped — the packet's own SI-2 gap describes monthly and quarterly enterprise-middleware remediation cycles against a class mass-scanned within days of an Oracle CPU, and its Essential-Eight gap the same mismatch at a two-week to one-month cadence. The packet records a vendor fix available, no host reboot required, and no live-patch primitive, which is the exact combination that makes this remediation look finished before it is: with no in-process patching path, a managed server that is running has already loaded the pre-fix classes and keeps executing them until that server process is restarted onto the updated libraries. Completion is therefore measured on the version each running WebLogic process reports, never on a patch-inventory row and never on the 'no reboot required' note — the absence of a machine reboot is not the fix being live in the JVM. Where a managed server cannot be restarted inside the SLA, the interim state is restricting reachability of its T3 and IIOP listeners, recorded as an open item with a dated restart rather than as remediation. And because active exploitation is confirmed, a public PoC exists and the outcome the packet states is full server takeover, an instance whose T3 or IIOP listeners were reachable during the exposure window belongs on the incident path — the update does not remove what was already placed on the server.",
+        "evidence": "Packet: cisa_kev true, kev_date 2024-09-18, active_exploitation confirmed, poc_available true, rwep_score 75, cvss 9.8. patch_available true, patch_required_reboot false, live_patch_available false, live_patch_notes: 'No live-patching primitive for this product; the vendor update (no reboot required) is the remediation.' The NIST-800-53-SI-2 gap: 'Flaw-remediation SLAs run monthly/quarterly for enterprise middleware, but this class is mass-scanned within days of a Oracle CPU; the patch window vastly exceeds the observed exploitation window.' The AU-Essential-8-Patch gap: 'Application-patch maturity targets a 2-week/1-month cadence for internet-facing servers, still slower than the same-week weaponization seen for WebLogic deserialization chains.' affected states exploitation 'yields full server takeover'.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "AU-Essential-8-Patch"
+        ]
+      }
+    ]
   },
   "CVE-2022-21445": {
     "name": "Oracle ADF Faces Deserialization of Untrusted Data Vulnerability",
@@ -46898,7 +47405,37 @@
         "adequate": false,
         "gap": "Account-management controls do not detect that ESXi re-authorizes an AD group purely by name; deleting and re-creating 'ESXi Admins' re-grants full admin outside normal account provisioning review."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-036",
+        "name": "FLEET-CONTROL-PLANE-ADMIN-PRIVILEGE-TIER",
+        "description": "On an AD-integrated ESXi host the packet's grant path makes an ordinary directory operation equivalent to hypervisor root: the host gives full administrative access to members of a configured Active Directory group ('ESXi Admins' by default) matched by name, so whoever holds the AD permission to create a group with that name holds ESXi administration — which is what the packet describes the named actors doing, deleting and re-creating the group once they hold sufficient AD permissions. The control means that permission is classified and administered as a hypervisor-control-plane privilege in its own tier — just-in-time and approval-gated, held by an identity separate from routine directory administration, and enumerated explicitly rather than collapsed into 'admin' — instead of sitting inside general group-management delegation, where account-provisioning review never connects the operation to hypervisor access. That disconnect is the account-management gap this entry records. Scope the population from affected_versions, not from the headline product: ESXi 8.0 hosts reach the fix at ESXi 8.0 U3, ESXi 7.0 is recorded as having no patch with mitigation required, and VMware Cloud Foundation 4.x and 5.x AD-integrated ESXi is in scope on the same terms, so an estate that rolls 8.0 U3 and reports itself remediated leaves every 7.0 and Cloud Foundation host on the pre-fix grant path. Two preconditions decide whether this holds. patch_required_reboot is true and the packet records no live-patch path, with the vendor update requiring a reboot and being the remediation, so an 8.0 host that has taken the update but not rebooted is still running the name-matching code and must be counted as exposed. And on 7.0, where the packet states mitigation is required, repointing the host's configured admin group to a different name does not close the path — the host still matches by name, so an actor holding the AD permissions this attack already requires can create the new name just as easily. Only removing the host-administration grant from AD group membership removes the precondition, and a host that must retain AD user management stays exposed until it reaches a fixed build and reboots.",
+        "evidence": "Packet vector: a malicious actor with sufficient Active Directory permissions can gain full access to an ESXi host previously configured to use AD for user management by re-creating the configured AD group ('ESXi Admins' by default) after it was deleted from AD. affected: VMware ESXi (and vCenter-managed hosts) configured to use AD for user management, where the host grants full admin to members of a configured AD group matched by name. affected_versions: 'VMware ESXi 8.0 (fixed in ESXi 8.0 U3)', 'VMware ESXi 7.0 (no patch; mitigation required)', 'VMware Cloud Foundation 4.x / 5.x (AD-integrated ESXi)'. patch_required_reboot true; live_patch_available false; live_patch_notes: 'No live-patching primitive for this product; the vendor update requires a reboot and is the remediation.' The NIST-800-53-AC-2 gap states account-management controls do not detect that ESXi re-authorizes an AD group purely by name, so deleting and re-creating 'ESXi Admins' re-grants full admin outside normal account provisioning review. active_exploitation confirmed; Microsoft observed Storm-0506, Storm-1175, Octo Tempest and Manatee Tempest.",
+        "gap_closes": [
+          "NIST-800-53-AC-2"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-037",
+        "name": "FLEET-COMPROMISE-IR-PLAYBOOK",
+        "description": "The packet gives this entry an outcome, not just a flaw: Microsoft observed Storm-0506, Storm-1175, Octo Tempest and Manatee Tempest abusing it post-compromise to seize domain-joined ESXi hypervisors, ending in Akira and Black Basta deployment and mass-VM encryption, with CISA KEV flagging it 'Known' for ransomware. That is a hypervisor-control-plane compromise and the playbook has to exist before it happens, which is what the incident-handling and response-and-recovery gaps on this entry record as absent. Key the detection half on the behaviour the packet documents rather than on ransomware artefacts, which arrive after the encryption: deletion of the Active Directory group the host is configured to trust ('ESXi Admins' by default) followed by its re-creation, correlated with members of that group obtaining full administrative access on AD-integrated ESXi hosts. The pairing inside a short window is the distinguishing signal, because neither half is conclusive alone and nothing else is emitted — no exploit binary runs, no service crashes and no memory-corruption artefact appears; the host performs its configured group lookup and grants access exactly as designed, so file-integrity and signature-based endpoint tooling have nothing to match and a rule keyed on crashes or tool signatures would miss an attack behaving precisely as the packet describes. Size the response half to the blast radius the packet names — every VM on a seized host rather than one endpoint: invalidate the granted access and the host's AD integration, rotate credentials for every account that authenticated through an affected host during the exposure window, and rehearse recovery at fleet scale. Preconditions: this depends on directory security-event and ESXi host telemetry being collected and shipped off-host before the event, which is where a playbook written after the fact fails; and detection prevents nothing — it bounds the interval between the regrant and the encryption, and against the actors the packet names that interval is short.",
+        "evidence": "Packet active_exploitation_notes: flagged 'Known' for ransomware use in CISA KEV (added 2024-07-30); Microsoft observed Storm-0506, Storm-1175, Octo Tempest and Manatee Tempest abusing it post-compromise to seize domain-joined ESXi hypervisors, leading to Akira and Black Basta ransomware deployments and mass-VM encryption. attack_vector: after gaining a foothold with sufficient AD permissions, operators delete and re-create the 'ESXi Admins' group in Active Directory and the AD-joined host re-grants full administrative access by group name, giving hypervisor control to encrypt all hosted VMs. The NIS2-Art21-incident-handling gap states incident-handling controls do not flag AD-group re-creation as a hypervisor-takeover precursor, so the escalation goes unnoticed until ransomware fires; the UK-CAF-D1 gap states response-and-recovery planning does not anticipate hypervisor-layer admin regrant cascading into fleet-wide VM encryption, so no recovery path is pre-staged. rwep_score 79.",
+        "gap_closes": [
+          "NIS2-Art21-incident-handling",
+          "UK-CAF-D1"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-054",
+        "name": "BACKUP-TIER-NETWORK-ISOLATION",
+        "description": "This entry's backup gap states the failure directly: backups stored on the same hypervisor datastore are encrypted alongside the VMs when this ransomware-linked bypass fires, and the outcome the packet records is Akira and Black Basta mass-VM encryption once the actor holds full administrative access on an AD-integrated ESXi host. Applied here, the control means backup copies for VMs running on AD-integrated ESXi do not live on datastores those hosts present, and the backup tier's management and storage paths are not reachable using ESXi host administration — a separate credential path and a network position the hypervisor administrator does not inherit — so that seizing the hypervisor by re-creating the trusted AD group does not also hand over the recovery. Distinguishing test: from an account holding full administrative access on a staging AD-integrated host, attempt to enumerate, mount, alter or delete the backup repository for the VMs that host runs; anything reachable from that position is inside this CVE's blast radius, and a backup attestation showing only that jobs complete on schedule passes cleanly while every copy sits where the takeover reaches. Preconditions: this preserves a recovery path, it does not prevent the takeover and it does not repair the name-based grant that causes it. It also does nothing for a VM whose only protection is a snapshot on the datastore it runs from — that copy is inside the encrypted set by definition — and its value is bounded by whether restore has been exercised at the scale this flaw implies, an entire hypervisor's VM population rather than a single file.",
+        "evidence": "Packet AU-Essential-8-Backup gap: 'Essential-Eight backup guidance does not require offline/immutable copies resilient to an ESXi admin-takeover, so backups stored on the same hypervisor datastore are encrypted alongside the VMs when this ransomware-linked bypass fires.' active_exploitation_notes record Akira and Black Basta ransomware deployments and mass-VM encryption after actors seized domain-joined ESXi hypervisors; attack_vector ends in the attacker holding hypervisor control to encrypt all hosted VMs. cisa_kev true with kev_date 2024-07-30 and ransomware use flagged 'Known'; rwep_score 79. affected covers VMware ESXi (and vCenter-managed hosts) configured to use Active Directory for user management.",
+        "gap_closes": [
+          "AU-Essential-8-Backup"
+        ]
+      }
+    ]
   },
   "CVE-2023-45249": {
     "name": "Acronis Cyber Infrastructure (ACI) Insecure Default Password Vulnerability",
@@ -47186,7 +47723,22 @@
         "adequate": false,
         "gap": "Flaw remediation shipped as MS13-008, but the impacted IE is end-of-life; SI-2 does not force retirement of the unsupported browser that still renders attacker HTML."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-122",
+        "name": "EOL-ASSET-DECOMMISSION",
+        "description": "Both halves this control turns on are stated in the packet. patch_available is true — the flaw-remediation gap names MS13-008 as the fix that shipped — and the exploitation notes state that the impacted Internet Explorer is end-of-life and should be disconnected. So on a host still running Internet Explorer 6, 7 or 8, taking the update carrying this fix is an interim state; the terminal state is removing that browser from the host, because it remains exposed not only to this CDwnBindInfo use-after-free but to everything found in that rendering engine since its last servicing. Scope to what affected and affected_versions name: Internet Explorer 6, 7 and 8. The packet ties the use-after-free to the IE 6-8 rendering engine and gives no mapping into any other product, so treating every browser or HTML-rendering component in the estate as an instance of this CVE manufactures removal work against software no evidence implicates. Operationally: enumerate every host with IE 6, 7 or 8 installed, put each on a dated removal schedule measured against the 2024-07-23 KEV listing, and — because delivery here is a crafted page served from a site the victim trusts, which is how the December 2012 watering-hole compromise reached its targets — ensure that until removal completes IE 6-8 is not the browser handling untrusted web content, with browsing moved to a maintained one. That interim restriction is the disable-or-limit-legacy-browsers action the application-hardening gap names as missing, and its precondition must be stated: changing which browser is the default does not remove IE 6-8 from the host, so any application or workflow that launches it directly still reaches the same engine, and the restriction holds only where policy enforces it rather than user habit. Completion on the interim patch half is measured on the running host, not the update record: live_patch_available is false and the packet records that the vendor update requires a reboot and is the remediation, so a host that installed it without rebooting is still executing the vulnerable code. And because exploitation is confirmed with a public proof of concept and delivery is attacker-controlled web content, a host that browsed with IE 6-8 during the exposure window belongs on the incident path rather than being closed on the patch record — an update applied after the fact does not remove what a successful drive-by left behind.",
+        "evidence": "Packet fields: vector — \"Use-after-free vulnerability in Microsoft Internet Explorer 6 through 8 allows remote attackers to execute arbitrary code via a crafted web site that triggers access to an object that (1) was not properly allocated or (2) is deleted, as demonstrated by a CDwnBindInfo object, and exploited in the wild in December 2012.\" affected_versions: Internet Explorer 6, Internet Explorer 7, Internet Explorer 8; CWE-416; cvss 8.8, rwep_score 77; poc_available true; cisa_kev true with kev_date 2024-07-23 and active_exploitation confirmed. active_exploitation_notes — \"Exploited in the wild in December 2012 via watering-hole drive-by pages (notably the Council on Foreign Relations compromise) using a CDwnBindInfo use-after-free; re-added to CISA KEV 2024-07-23. The impacted Internet Explorer is end-of-life and should be disconnected.\" patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes — \"No live-patching primitive for this product; the vendor update requires a reboot and is the remediation.\" framework_control_gaps: NIST-800-53-SI-2 — \"Flaw remediation shipped as MS13-008, but the impacted IE is end-of-life; SI-2 does not force retirement of the unsupported browser that still renders attacker HTML\"; ISO-27001-2022-A.8.8 — \"does not compel removal of legacy IE 6-8 clients, leaving a client-side RCE surface active\"; NIS2-Art21-vulnerability-management — duties \"do not specifically mandate decommissioning end-of-life browsers that remain drive-by exploitable\"; UK-CAF-B4 — the principle \"lacks a control forcing retirement of end-of-life clients, so IE 6-8 keeps rendering attacker HTML from watering-hole sites long after MS13-008\"; AU-Essential-8-App-Hardening — \"Application-hardening (disable/limit legacy browsers, block untrusted script) is exactly the missing control that would have blunted the drive-by.\"",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "ISO-27001-2022-A.8.8",
+          "NIS2-Art21-vulnerability-management",
+          "UK-CAF-B4",
+          "AU-Essential-8-App-Hardening"
+        ]
+      }
+    ]
   },
   "CVE-2022-22948": {
     "name": "VMware vCenter Server Incorrect Default File Permissions Vulnerability",
@@ -47764,7 +48316,40 @@
         "adequate": false,
         "gap": "Least-functionality controls rarely disable unprivileged user namespaces (kernel.unprivileged_userns_clone), which is what grants the CAP_NET_ADMIN needed to reach the nf_tables path."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-130",
+        "name": "CONTAINER-HOST-NAMESPACE-ESCAPE-HARDENING",
+        "description": "The packet states this flaw's precondition rather than leaving it implicit: the local attacker needs CAP_NET_ADMIN before the netfilter nf_tables configuration path is reachable at all, and the packet's attack vector says that capability is often obtained through an unprivileged user namespace. For this CVE the control means unprivileged user-namespace creation (kernel.unprivileged_userns_clone) is disabled on every Linux host whose workloads do not genuinely require it, and each container is confined with an LSM profile plus a seccomp profile that does not hand it CAP_NET_ADMIN — because on a host still running a kernel without the nf_tables fix, that combination removes the entry condition while the reboot onto the fixed kernel is pending. On a container host the boundary claim itself is what is at stake: a confined workload able to create a user namespace holds CAP_NET_ADMIN inside it, creates an nft object referencing a set in a different table, deletes that table to free the set, and reclaims the dangling object as host root, so the confinement is not a boundary and the kernel is the only thing left. Distinguishing test: from a representative unprivileged container or an ordinary user session on a staging host running an affected kernel, create a user namespace and attempt the cross-table nft object/set configuration the packet describes, and confirm it is refused before the set can be freed. Two preconditions, both routinely skipped when this control is claimed. It closes only the user-namespace route — a process that already holds CAP_NET_ADMIN in the host's initial namespace (a container deliberately granted NET_ADMIN, a firewall or network-management daemon, a service account carrying the capability) reaches the identical path with unprivileged userns disabled, so that population must have the capability withdrawn or be counted as exposed until it reboots onto the fixed kernel. And it is unavailable on hosts that need unprivileged user namespaces to function — rootless container runtimes, build and CI hosts, sandboxes built on the same primitive — where the interim measure is detection plus the reboot, not this. Note also what is not available here: nf_tables is the host's own packet-filtering path, so unloading or blacklisting the subsystem is not the least-functionality answer the way an unused driver would be.",
+        "evidence": "Packet attack_vector: 'A local user obtains CAP_NET_ADMIN (often via an unprivileged user namespace), creates an nft object referencing a set in another table, deletes that table to free the set, and reclaims the dangling object to corrupt kernel memory and escalate to root.' The NIST-800-53-CM-7 gap records that 'Least-functionality controls rarely disable unprivileged user namespaces (kernel.unprivileged_userns_clone), which is what grants the CAP_NET_ADMIN needed to reach the nf_tables path'; the UK-CAF-B4 gap records that 'System-security assurance for Linux hosts seldom disables unprivileged user namespaces, the very setting that grants the CAP_NET_ADMIN this nf_tables use-after-free needs; CAF sets no requirement for that compensating control while the KEV-listed kernel LPE awaits a reboot'; the NIS2-Art21-patch-management gap records that patch-management obligations 'do not mandate the compensating control (disabling unprivileged userns) while kernel updates are pending.' An interim measure is needed because patch_available is true but patch_required_reboot is true and live_patch_available is false, with live_patch_notes stating 'No live-patching primitive for this product; the vendor update requires a reboot and is the remediation.' cisa_kev true (kev_date 2024-06-26), active_exploitation confirmed, poc_available true, rwep_score 73, cvss 7.8.",
+        "gap_closes": [
+          "NIST-800-53-CM-7",
+          "UK-CAF-B4",
+          "NIS2-Art21-patch-management"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-145",
+        "name": "ACTIVELY-EXPLOITED-OS-LPE-REMEDIATION-WINDOW-ENFORCEMENT",
+        "description": "This is a local privilege escalation in the Linux kernel's netfilter nf_tables subsystem, so for this CVE the control means the distro kernel update carrying the backported nf_tables fix is driven across every affected host on the clock that opened with the 2024-06-26 KEV listing, rather than folded into the next quarterly maintenance window — with completion measured against the kernel the host is actually executing, not against the kernel package a configuration-management console reports as installed. The packet makes that distinction load-bearing: patch_required_reboot is true and live_patch_available is false, with the entry recording that the vendor update requires a reboot and is the remediation, so a host that has taken the new kernel package but has not rebooted onto it still runs the vulnerable code and must be counted as exposed. On the multi-user and long-uptime hosts most exposed to a local escalation the reboot is precisely the step that gets deferred, and a deferral recorded as 'patched' is the specific way this remediation goes wrong. Scoping cannot be done by kernel version number alone: the packet records the defect as present since v3.16-rc1 and lists distro kernels prior to the backported nf_tables patch (RHEL/Ubuntu/SUSE) as a separate affected population, so a vendor kernel with a lower upstream base may already carry the backport while a higher-numbered one does not — each host has to be compared against the fixed build its own distro published for that kernel line. Enumerate first the hosts where the flaw's precondition is the normal operating state rather than an anomaly: shared and multi-user systems, CI and build runners, and container hosts, anywhere unprivileged local code runs by design. Priority follows the packet rather than the CVSS band — a 7.8 with a local vector reads as a deferrable endpoint item, while the packet records confirmed active exploitation, a public PoC and a KEV listing for a primitive that converts any code execution as a local user into root, which is what makes it a containment step for a chain rather than a standalone item.",
+        "evidence": "Packet fields: patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes 'No live-patching primitive for this product; the vendor update requires a reboot and is the remediation.' cisa_kev true with kev_date 2024-06-26; active_exploitation confirmed; active_exploitation_notes 'Added to CISA KEV 2024-06-26 as actively exploited. A use-after-free in the Linux kernel nf_tables (nft_object cross-table set reference) lets a local attacker with CAP_NET_ADMIN escalate to root. Ransomware association is unconfirmed.' poc_available true; cvss 7.8; rwep_score 73. Scope from affected ('Present since v3.16-rc1') and affected_versions ('Linux kernel >= 3.16-rc1 prior to the netfilter fix', 'distro kernels prior to the backported nf_tables patch (RHEL/Ubuntu/SUSE)'). The NIST-800-53-SI-2 gap records that 'Kernel patch-deployment cadence and reboot windows leave hosts exposed long after a working public LPE exists'; the AU-Essential-8-Patch gap that 'Patch-application timeframes for OS/kernel are measured in weeks, exceeding the exploitation window for a KEV-listed kernel LPE'; the ISO-27001-2022-A.8.8 gap that vulnerability management 'typically prioritizes remote flaws, deprioritizing a local kernel UAF that is in fact a ready root primitive for post-exploitation.'",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "AU-Essential-8-Patch",
+          "ISO-27001-2022-A.8.8"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-003",
+        "name": "KERNEL-EXPLOITATION-DETECTION",
+        "description": "On hosts that cannot yet take the reboot, and on the hosts where unprivileged user namespaces must stay enabled for rootless containers or build sandboxes, detection is the only interim measure left — and the packet describes the exploitation behaviour precisely enough to key on it instead of on a guess. The rule keys on the sequence the packet's attack vector states: an unprivileged uid creating a user namespace, followed within the same session lineage by nf_tables netlink configuration traffic that creates an nft object referencing a set belonging to a different table and then deletes that table, paired with the outcome the packet names — a privilege transition to uid 0 in a process descended from that non-root session. Both halves are needed. Netlink nf_tables configuration on its own is what ordinary firewall tooling does all day on a firewall or container host, and a uid-0 transition on its own arrives with no context; it is the pairing inside a short window, from a session that began unprivileged, that separates this exploit from routine administration. Note what will not see it: nothing is compiled, no kernel module is loaded, no setuid binary changes, and the attacker uses the kernel's normal configuration interface, so file-integrity monitoring and signature-matching endpoint tooling have no artifact to match, and a rule written against process crashes or named exploit tooling would miss an attempt that behaves exactly as the packet describes — with poc_available true, the exact sequence is public and need not resemble any particular tool. Preconditions: this requires host audit or eBPF telemetry already being collected and shipped off-host before the attempt, which on shared multi-user hosts is exactly where it is least often enabled, and a rule authored after the fact against telemetry nobody collected produces nothing. Detection also does not prevent the escalation and does not undo root already obtained — it bounds the window to alert-and-response time during the period before the host reboots onto the fixed kernel.",
+        "evidence": "Packet attack_vector: 'A local user obtains CAP_NET_ADMIN (often via an unprivileged user namespace), creates an nft object referencing a set in another table, deletes that table to free the set, and reclaims the dangling object to corrupt kernel memory and escalate to root.' active_exploitation confirmed and poc_available true. The interim window exists because patch_required_reboot is true and live_patch_available is false ('No live-patching primitive for this product; the vendor update requires a reboot and is the remediation'). The NIS2-Art21-patch-management gap records that 'Patch-management obligations do not mandate the compensating control (disabling unprivileged userns) while kernel updates are pending' — this control covers that pending window on the hosts where disabling unprivileged user namespaces is not available.",
+        "gap_closes": [
+          "NIS2-Art21-patch-management"
+        ]
+      }
+    ]
   },
   "CVE-2022-24816": {
     "name": "OSGeo GeoServer JAI-EXT Code Injection Vulnerability",
@@ -48134,7 +48719,39 @@
         "adequate": false,
         "gap": "Least-functionality controls rarely disable unprivileged user namespaces (user.max_user_namespaces), leaving the nf_tables attack surface reachable to any local user."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-002",
+        "name": "LIVE-PATCH-CAPABILITY",
+        "description": "Four of the framework gaps cited on this entry say the same thing in four vocabularies: the nf_tables fix requires a reboot and Linux fleets do not take reboots on a KEV clock, so a ransomware-associated privilege escalation with a reliable public exploit stays live between assessment cycles. This packet is one of the few where that gap has a direct answer, because live_patch_available is true — the notes record that distributions shipping kernel livepatch (Ubuntu Livepatch, Oracle Ksplice, kpatch) can apply the nf_tables fix without reboot. For this CVE the control means the livepatch capability is deployed and exercised on production Linux hosts before the next kernel KEV listing, not procured in response to one: a capability first attempted during an incident is not a capability. Completion must be measured on the kernel that is running, since the whole point of the control is decoupling remediation from the reboot — a host whose fixed kernel package is installed but which is still executing the pre-fix image is exposed, and a host carrying the livepatch is remediated even though its package version has not moved. Preconditions, and both matter operationally. The livepatch path exists only where the distribution ships a livepatch stream carrying this specific nf_tables fix; a custom-built kernel, an unsupported release, or a host without the livepatch service has no such path and must take the reboot the packet records, so the fleet has to be split into those two populations rather than assumed uniform. And a livepatch covers the kernel running now — the on-disk kernel still has to reach a build carrying the fix (upstream commit f342de4e2f33e0e39165d8639387aa6c19dff660), so the reboot is deferred by this control, not cancelled by it.",
+        "evidence": "Packet: live_patch_available true; live_patch_notes: 'Distributions shipping kernel livepatch (Ubuntu Livepatch, Oracle Ksplice, kpatch) can apply the nf_tables fix without reboot; disabling unprivileged user namespaces is an immediate mitigation.' patch_available true, patch_required_reboot true. CISA KEV 2024-05-30; active_exploitation confirmed with CISA flagging known ransomware use; poc_available true with a widely-shared public exploit described as a reliable post-compromise privilege-escalation primitive across many distributions. affected_versions: Linux kernel 3.15 through 6.8-rc1 (prior to commit f342de4e2f33e0e39165d8639387aa6c19dff660). Cited gaps: SI-2 (kernel patching lags a public exploit within the KEV window), AU-Essential-8-Patch (OS-patch timelines do not match rapid weaponization), NIS2-Art21-patch-management (SLAs lag observed ransomware-linked exploitation), UK-CAF-B4 (patch expectations assume a maintenance-reboot window fleets rarely hit promptly).",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "AU-Essential-8-Patch",
+          "NIS2-Art21-patch-management",
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-130",
+        "name": "CONTAINER-HOST-NAMESPACE-ESCAPE-HARDENING",
+        "description": "The packet states the reach path rather than leaving it implicit: an unprivileged local user, often via an unprivileged user namespace, crafts nf_tables rules that make nf_hook_slow() double-free on an NF_DROP verdict carrying a drop error resembling NF_ACCEPT, and lands as root. On a container host that is the escape case — a confined workload able to create a user namespace reaches the kernel's netfilter code and becomes host root, so the isolation the deployment is designed around is not a boundary and the kernel is the only thing left. For this CVE the control means unprivileged user-namespace creation is disabled on every host whose workloads do not genuinely require it (the least-functionality gap on this entry names user.max_user_namespaces as the setting nobody sets), and each container is confined by three separate mechanisms that are not substitutes for one another: a mandatory-access-control profile (AppArmor or SELinux), a seccomp profile restricting the syscalls the workload may issue, and the runtime capability policy that drops the capabilities it does not need. The third is the one that bears on this path and the one most often assumed to be covered by the second — seccomp filters syscalls and cannot drop a capability, so a workload can satisfy a MAC-plus-seccomp requirement and still hold the network-admin capability that the precondition below records as retaining the primitive. Drop it explicitly in the capability policy for every workload that does not administer networking. Distinguishing test: from inside a representative unprivileged container on a staging host, attempt to create a user namespace and then program an nf_tables rule set, and confirm the attempt is refused before any verdict reaches the vulnerable path — a fleet that passes image-scanning and RBAC audits while permitting unprivileged user-namespace creation is still handing every confined workload this primitive. Preconditions, stated plainly because this control is easy to over-claim. The packet says 'often via an unprivileged user namespace', not always: disabling the namespace removes the usual reach path, it does not repair nft_verdict_init(), so any local context that still reaches nf_tables rule creation — a workload that legitimately requires user namespaces, or one holding network-admin capability by design — retains the primitive. It also does nothing about an attacker already resident, and nothing about one who has already escalated. Treat it as the immediate mitigation the packet names for the window before the livepatch or the fixed kernel and its reboot land, not as closure.",
+        "evidence": "Packet attack_vector: 'An unprivileged local user (often via an unprivileged user namespace) crafts nf_tables rules that make nf_hook_slow() double-free on an NF_DROP verdict carrying a drop error resembling NF_ACCEPT, corrupting kernel memory to escalate to root.' live_patch_notes: 'disabling unprivileged user namespaces is an immediate mitigation'. Cited gap NIST-800-53-CM-7: 'Least-functionality controls rarely disable unprivileged user namespaces (user.max_user_namespaces), leaving the nf_tables attack surface reachable to any local user.' active_exploitation confirmed with known ransomware use; poc_available true; patch_required_reboot true; live_patch_available true.",
+        "gap_closes": [
+          "NIST-800-53-CM-7"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-018",
+        "name": "SCANNER-PAPER-COMPLIANCE-TEST",
+        "description": "On this CVE the usual vulnerability-management evidence — a scan reporting the installed kernel package version — is wrong in both directions at once, which is why the technical-vulnerability-management gap here is about under-tracking rather than about speed. patch_required_reboot is true, so a host that installed the fixed kernel package and has not rebooted reads as patched while it is still executing the vulnerable nf_tables code and is fully exploitable by any local user. live_patch_available is true, so a host carrying the Ubuntu Livepatch, Ksplice or kpatch fix reads as unpatched while its running kernel is actually fixed. An A.8.8 attestation built on either reading describes something other than the fleet's exposure. For this CVE the control means the scan is taken against the running kernel and its livepatch state, and the version judgement is made against the distribution's build carrying the backport of commit f342de4e2f33e0e39165d8639387aa6c19dff660 — not against upstream 6.8-rc1, because distribution kernels carry the fix on their own version numbers and an 'older than 6.8-rc1' rule misjudges every one of them. It must also treat a host that has only the mitigation the packet names, unprivileged user namespaces disabled, as mitigated rather than remediated, so the two states stay distinguishable on the report. Distinguishing test: stage one host with the fixed package installed but not rebooted and one host livepatched without the package upgrade, run the scan against both, and confirm the first is reported exposed and the second remediated; a scanner that gets either backwards is generating the compliance record while real exposure is unknown. Precondition: this is a measurement control. It remediates nothing on its own — its whole value is that the livepatch and reboot work driven by the other controls on this entry can be verified rather than assumed.",
+        "evidence": "Packet: patch_available true, patch_required_reboot true, live_patch_available true, live_patch_notes naming Ubuntu Livepatch, Oracle Ksplice and kpatch as able to apply the nf_tables fix without reboot and disabling unprivileged user namespaces as an immediate mitigation. affected_versions: Linux kernel 3.15 through 6.8-rc1 (prior to commit f342de4e2f33e0e39165d8639387aa6c19dff660). Cited gap ISO-27001-2022-A.8.8: 'Technical-vulnerability management on Linux fleets under-tracks kernel LPE flaws that require reboots to remediate.' CISA KEV 2024-05-30; active_exploitation confirmed with known ransomware use; poc_available true.",
+        "gap_closes": [
+          "ISO-27001-2022-A.8.8"
+        ]
+      }
+    ]
   },
   "CVE-2024-24919": {
     "name": "Check Point Quantum Security Gateways Information Disclosure Vulnerability",
@@ -50314,7 +50931,31 @@
         "adequate": false,
         "gap": "Identity-management control does not, by itself, mandate channel binding / EPA for legacy NTLM, leaving relayed authentication to Exchange viable."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-025",
+        "name": "CONFIGURATION-SIDE-LIVE-PATCH-INVENTORY",
+        "description": "For Microsoft Exchange Server the configuration-side path this control names is Extended Protection, and the packet makes it the load-bearing half rather than an optional extra: the affected condition is stated as Exchange Server where Extended Protection is not enforced, and the flaw-remediation gap records that applying the Exchange update is not enough on its own because Extended Protection must be actively enabled. Bound to this deployment that means every Exchange Server 2016 and 2019 host is inventoried by whether Extended Protection is enforced on the web endpoints that terminate authentication — Exchange Web Services first, because EWS is the endpoint the packet names as the relay target — and that this state is tracked, tested and driven as its own item rather than riding along with the CU14 upgrade project, since the packet describes CU14 as enabling Extended Protection by default rather than as the only route to it. Extended Protection is also exactly what the identity controls cited on this entry are missing: the packet's federated identity-management gap says the control does not by itself mandate channel binding for legacy NTLM, and channel binding at the EWS endpoint is what makes a relayed NetNTLM authentication fail instead of succeeding as the victim. Read the control's name carefully against this packet: live_patch_available is false, so enabling Extended Protection is a configuration change, not a vendor live-patch primitive, and it does not substitute for the remediation the packet records — applying the fixed release and rebooting. That is the precondition on treating this as closure: patch_required_reboot is true, so a server that took the February 2024 update but has not restarted is still running the vulnerable code. A second precondition is that Extended Protection bounds the relay into Exchange and does nothing about the step the attack begins with; the packet's network-security gap names disabling or segmenting NTLM and blocking authentication-coercion RPC as separate measures this control does not supply. And because active exploitation against internet-facing Exchange is confirmed, a server that was reachable while Extended Protection was off belongs on the incident path rather than being closed on the configuration change.",
+        "evidence": "Packet affected: 'Microsoft Exchange Server; when Extended Protection is not enforced, an attacker can relay a coerced NTLM authentication to Exchange Web Services and act as the victim (privilege escalation). Fixed by CU14 enabling Extended Protection by default.' affected_versions: 'Exchange Server 2016 and 2019 without Extended Protection (prior to Feb 2024 update / CU14)'. NIST-800-53-SI-2 gap: 'Applying the Exchange update is not enough on its own — Extended Protection must be actively enabled — so a standard patch-and-reboot SLA leaves the relay path open even on \"patched\" servers.' ISO-27001-2022-A.5.16-Federated gap: 'Identity-management control does not, by itself, mandate channel binding / EPA for legacy NTLM, leaving relayed authentication to Exchange viable.' NIS2-Art21-network-security gap names disabling/segmenting NTLM and blocking authentication-coercion RPC as what stops the relay chain. attack_vector: an attacker coerces a privileged account to authenticate (e.g. PetitPotam) then relays the NTLM credential to the Exchange EWS endpoint. Remediation state: patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes 'No vendor live-patch mechanism; remediation requires applying the fixed release and rebooting.' CWE-287, CISA KEV listed 2024-02-15, active_exploitation confirmed, poc_available true, CVSS 9.8, RWEP 80.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "NIST-800-53-IA-2",
+          "ISO-27001-2022-A.5.16-Federated",
+          "UK-CAF-B2"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-018",
+        "name": "SCANNER-PAPER-COMPLIANCE-TEST",
+        "description": "The paper-compliance shape this control exists to catch is precisely the failure the packet records for this CVE. A scanner that reads the Exchange build, sees the February 2024 update present and reports the server remediated has measured the one thing that does not settle the question: the condition the packet ties exploitation to is Extended Protection not being enforced, and that is a configuration state the build number does not carry. The operational test for this product is therefore per-server and per-endpoint — for every Exchange Server 2016 and 2019 host, produce the enforced/not-enforced state of Extended Protection on the web endpoints that accept authenticated traffic, Exchange Web Services first because the packet names EWS as the relay target, and treat a host that cannot produce that state as unverified rather than as compliant. The distinguishing test keys on the behaviour the packet documents rather than on a version string or a tool signature: on a staging Exchange server, coerce an account to authenticate and relay that NetNTLM authentication to the EWS endpoint — the exact sequence in the packet's attack vector, using the publicly available coercion and relay tooling its application-hardening gap names — and confirm the relayed authentication is refused rather than accepted as the victim. An estate whose patch report is green and whose user-application-hardening attestation covers Exchange passes both checks while that relay still succeeds, which is what makes the version-only scan and the hardening attestation paper compliance here. The same inventory must carry restart state alongside configuration state: the packet gives patch_required_reboot true with no live-patch path and states remediation requires applying the fixed release and rebooting, so a host that has installed the update and not restarted onto it is not remediated no matter what either check reports.",
+        "evidence": "Packet NIST-800-53-SI-2 gap: 'Applying the Exchange update is not enough on its own — Extended Protection must be actively enabled — so a standard patch-and-reboot SLA leaves the relay path open even on \"patched\" servers.' AU-Essential-8-App-Hardening gap: 'Application-hardening maturity does not enumerate Exchange Extended Protection or NTLM channel-binding, so a \"hardened\" server still relays a coerced NetNTLM authentication to EWS via public impacket/PetitPotam tooling; patching without enabling EPA leaves the relay path open.' affected_versions: 'Exchange Server 2016 and 2019 without Extended Protection (prior to Feb 2024 update / CU14)'. attack_vector: coerce a privileged account to authenticate (e.g. PetitPotam), relay the NTLM credential to the Exchange EWS endpoint; without Extended Protection the relay succeeds. patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes 'No vendor live-patch mechanism; remediation requires applying the fixed release and rebooting.' CISA KEV 2024-02-15, active_exploitation confirmed, poc_available true, CVSS 9.8, RWEP 80.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "AU-Essential-8-App-Hardening"
+        ]
+      }
+    ]
   },
   "CVE-2024-21412": {
     "name": "Microsoft Windows Internet Shortcut Files Security Feature Bypass Vulnerability",
@@ -51099,7 +51740,38 @@
         "adequate": false,
         "gap": "Identity-and-access-control assurance is undermined when authentication can be skipped entirely; B2 assumes the auth gate is reached for protected functions."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "Bound to this Ivanti EPMM and MobileIron Core entry, the control's clock opens at the 2024-01-18 KEV listing and closes only when each affected server has come up on the fixed release. Two things make that harder than the usual appliance ticket. First, the population is two separately-branded product lines: the packet gives Ivanti EPMM 11.10 and older on one side and MobileIron Core 11.7 and below on the other, so an inventory that queries for 'Ivanti EPMM' misses MobileIron Core-branded servers still in service, and those are the instances most likely to sit outside the current vendor-support relationship that drives patch notifications. Second, the packet records that remediation requires applying the fixed release and rebooting, with no live-patch mechanism available, so a server holding the fixed release staged but not yet restarted is still serving the bypass and must be counted as exposed rather than as patched — on an MDM server that reboot is the step most likely to be deferred, because taking it interrupts device check-in and enrollment. Priority follows the packet rather than a queue position: a public proof-of-concept, EPSS near 1.0, a KEV ransomware flag, and exploitation that began shortly after the public technical details make this a containment step whose delay is measured against attackers already operating, not a scheduled maintenance item.",
+        "evidence": "Packet fields for CVE-2023-35082: cisa_kev true with kev_date 2024-01-18, active_exploitation confirmed, cvss 9.8, rwep_score 82, poc_available true, patch_available true, patch_required_reboot true, live_patch_available false, and live_patch_notes 'No vendor live-patch mechanism; remediation requires applying the fixed release and rebooting.' affected_versions names both product lines: 'Ivanti EPMM 11.10 and older (11.9, 11.8, ...)' and 'MobileIron Core 11.7 and below'. active_exploitation_notes records CISA-confirmed exploitation in January 2024 against internet-facing EPMM / MobileIron Core MDM servers, a KEV ransomware flag, and EPSS ~1.0. The NIST-800-53-SI-2 gap states the flaw was exploited shortly after Rapid7's public details, faster than a routine flaw-remediation SLA closes an internet-facing MDM server.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "AU-Essential-8-Patch"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-129",
+        "name": "ENTERPRISE-ERP-MANAGEMENT-FUNCTION-AUTHENTICATION",
+        "description": "EPMM's authentication filter is where the product makes its authentication decision, and this CVE is that layer failing open: the packet has an unauthenticated attacker sending a request whose URI prefix bypasses the filter, so the restricted management-API functions behind it run without any access-control decision ever being taken for that request. Bound to this product, the control means each management-API function on EPMM and MobileIron Core authorizes its own caller rather than inheriting a verdict from the filter that fronts it, and the administrative portion of the surface is separated from the enrollment portion so an untrusted caller cannot present a request to that filter for administrative functions at all. This is also why the least-privilege and identity-side attestations an estate carries do not reduce this flaw: the attacker never authenticates as any EPMM operator, so per-account privilege scoping is never consulted and the account model an identity-and-access attestation examines is bypassed rather than abused. Distinguishing test: from a segment with no administrative need for the MDM console, send unauthenticated requests carrying the URI-prefix form to each management-API endpoint on a staging EPMM and confirm each is refused before the function runs — an attestation that every EPMM administrator authenticates at login passes cleanly while this path stays open. Precondition, and it is a hard one on this product: the endpoint-side authorization is a property the vendor fixed release establishes, not something an operator can add, and the packet records that the platform must by design remain internet-reachable for mobile enrollment. So restricting reachability bounds only the administrative portion of the surface; it cannot cover the enrollment path, and it gives nothing against a caller that can reach whatever must stay exposed. Until the fixed release and its reboot land, this control states what to verify rather than what to deploy.",
+        "evidence": "Packet fields for CVE-2023-35082: cwe_refs CWE-287, and attack_vector states that an unauthenticated attacker sends a crafted request whose URI prefix bypasses the authentication filter, reaching MDM management-API endpoints to read user PII and alter server configuration. The NIST-800-53-AC-3 gap states that access enforcement is defeated at the source — a crafted URI prefix bypasses the authentication filter, so the access-control decision point never runs for the sensitive API. The UK-CAF-B2 gap states that identity-and-access-control assurance is undermined when authentication can be skipped entirely, because B2 assumes the auth gate is reached for protected functions. The NIS2-Art21-network-security gap records that the device must be internet-reachable by design for mobile enrollment. patch_available is true with patch_required_reboot true and live_patch_available false.",
+        "gap_closes": [
+          "NIST-800-53-AC-3",
+          "UK-CAF-B2"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-037",
+        "name": "FLEET-COMPROMISE-IR-PLAYBOOK",
+        "description": "EPMM and MobileIron Core are the control plane for every mobile device they manage, and the packet places the attacker inside that control plane rather than merely at its door: unauthenticated access to restricted management-API endpoints, reading user PII and altering server configuration, chainable toward remote code execution, on a KEV entry flagged for known ransomware use. That is why the fixed release and its reboot do not by themselves resolve an instance that was internet-reachable during the exposure window — configuration the attacker changed through the bypass is carried forward by the upgrade, and PII already read is gone regardless of what version the server later reports. Bound to this platform, the playbook items are: audit EPMM server configuration and every configuration profile pushed to the fleet since the start of the exposure window against a known-good baseline; invalidate device-trust state and revoke certificates issued or pushed through the platform during that window; rotate credentials for any account that authenticated through the platform; and define, in advance, the criteria under which downstream managed devices are quarantined. This is the half of the response that still has value after the patch record reads clean, and it is what turns a technical-vulnerability finding on one server into the fleet-wide isolation decision the compromise actually requires.",
+        "evidence": "Packet fields for CVE-2023-35082: active_exploitation confirmed, kev_date 2024-01-18, and active_exploitation_notes stating that unauthenticated attackers reach restricted API endpoints to read user PII and make server changes, that it can be chained toward RCE, and that KEV flags known ransomware use. attack_vector describes the result as a foothold on the control plane for the entire managed mobile fleet. The ISO-27001-2022-A.8.8 gap states that technical-vulnerability management does not by itself force emergency isolation of an MDM control plane whose compromise exposes the entire managed fleet. patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes 'No vendor live-patch mechanism; remediation requires applying the fixed release and rebooting.'",
+        "gap_closes": [
+          "ISO-27001-2022-A.8.8"
+        ]
+      }
+    ]
   },
   "CVE-2024-0519": {
     "name": "Google Chromium V8 Out-of-Bounds Memory Access Vulnerability",
@@ -51531,7 +52203,38 @@
         "adequate": false,
         "gap": "Technical-vulnerability management provides no play for a KEV appliance zero-day with only a temporary mitigation, so exposed devices stayed reachable during active exploitation."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-030",
+        "name": "PERIMETER-DEVICE-ZERODAY-SLA-TIER",
+        "description": "Ivanti Connect Secure and Policy Secure are the VPN-concentrator class this tier names, and the defect is in the web component that faces unauthenticated internet clients by design — the device is the trust boundary, which is why a standard 14- or 30-day application SLA is the wrong instrument regardless of the 8.2 base score. For this CVE the tier means the clock opened at the 2024-01-10 KEV listing and closes only at the reboot of every affected unit, covering Connect Secure 9.x and 22.x and Policy Secure 9.x and 22.x — the packet names all four, and an estate standardised on Policy Secure while treating this as a Connect Secure advisory will sweep clean and stay exposed. The packet records a vendor fix with no live-patch mechanism and a reboot requirement, so a unit that has taken the fixed release but has not been rebooted onto it is still running the vulnerable web component and must be counted as exposed; on a remote-access gateway that reboot is also the step most likely to be deferred, because taking it drops every live session, and a deferral recorded as patched is the specific way this remediation goes wrong. The tier's alternative limb — isolation of the vulnerable interface — needs its precondition stated for this product rather than inherited from the firewall case: the vulnerable web component IS the remote-access service, so there is no segment to move it behind. The only forms isolation takes here are withdrawing remote access for the duration, or restricting the source addresses permitted to reach the gateway, and on a device whose purpose is terminating arbitrary remote workers the second is usually unavailable. Where neither is possible the honest record is an accepted exposure with the reboot dated, not a compensating control marked in place.",
+        "evidence": "Packet name: 'Ivanti Connect Secure and Policy Secure Authentication Bypass Vulnerability'. affected: 'Web component of Ivanti Connect Secure (ICS, formerly Pulse Connect Secure) 9.x and 22.x and Ivanti Policy Secure; directory traversal lets a remote attacker bypass control checks and access restricted resources without authentication.' affected_versions lists Connect Secure 9.x, Connect Secure 22.x, Policy Secure 9.x and Policy Secure 22.x. cisa_kev true, kev_date 2024-01-10, active_exploitation confirmed, poc_available true, rwep_score 82, cvss 8.2. patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes: 'No vendor live-patch mechanism; remediation requires applying the fixed release and rebooting.' The NIST-800-53-SC-7 gap: 'Boundary protection does not prevent the appliance itself, which is the boundary, from being bypassed via path traversal; the flaw lives in the very device meant to enforce the perimeter.' active_exploitation_notes records a mass-exploited zero-day chaining with CVE-2024-21887 for unauthenticated RCE.",
+        "gap_closes": [
+          "NIST-800-53-SC-7"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-038",
+        "name": "MITIGATION-ACTIVE-PATCH-PENDING-VERDICT-CLASS",
+        "description": "This entry is the case the three-state verdict exists for, and the packet supplies the evidence in its own gap text: the Essential-Eight objective was overtaken by zero-day mass exploitation before a patch existed, and the initial vendor guidance was a mitigation release file rather than a fix, while ISO A.8.8 had no play at all for a KEV-listed appliance zero-day carrying only a temporary mitigation. An estate in that condition is in state (b) — vendor mitigation loaded, no fixed build installed — and it must be reported as its own compensating-control state with a dated action item, never folded into a green 'patched per SLA' row. The residual risk in state (b) is specific rather than theoretical here: the mitigation is a rule applied to the same request path the flaw lives in, so a defect in it or an incomplete application on any unit reopens the pre-auth traversal, and it does nothing whatever about an appliance already exploited before the file was loaded — which, for a flaw the packet describes as mass-exploited as a zero-day, is a live possibility on any unit that was internet-reachable. State (a) for this CVE is reached only when the unit is on the fixed release and has been rebooted onto it, because the packet records no live-patch mechanism and a reboot requirement; a unit showing the fixed release with the reboot outstanding is still state (b) at best. Distinguishing test: pull the current verdict for every Connect Secure and Policy Secure unit and require each to name which of the three states it is in and the evidence for that state — an appliance register showing green flaw-remediation rows for units carrying only the mitigation file is recording compliance for an exposure under active mass exploitation.",
+        "evidence": "The AU-Essential-8-Patch gap on this entry: 'The patch objective was overtaken by zero-day mass exploitation before a patch existed — initial guidance was a mitigation.release XML, not a fix, leaving a control gap the SLA cannot cover.' The ISO-27001-2022-A.8.8 gap: 'Technical-vulnerability management provides no play for a KEV appliance zero-day with only a temporary mitigation, so exposed devices stayed reachable during active exploitation.' Packet: patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes 'No vendor live-patch mechanism; remediation requires applying the fixed release and rebooting.' active_exploitation confirmed; active_exploitation_notes: 'Mass-exploited zero-day (CISA-flagged ransomware-associated)'. cisa_kev true, kev_date 2024-01-10, rwep_score 82.",
+        "gap_closes": [
+          "AU-Essential-8-Patch",
+          "ISO-27001-2022-A.8.8"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-032",
+        "name": "PERIMETER-COMPROMISE-REBUILD-NOT-PATCH",
+        "description": "The packet describes exactly the conditions under which patch-in-place is the wrong default: a mass-exploited zero-day on an internet-facing gateway, CISA-flagged ransomware-associated, with the traversal chaining to CVE-2024-21887 command injection for unauthenticated RCE across the Connect Secure and Policy Secure fleet. The runbook for these appliances must therefore assume that any Connect Secure 9.x or 22.x or Policy Secure 9.x or 22.x unit reachable from the internet during the exposure window was compromised until evidence says otherwise, and default to capturing the running configuration for analysis, rebuilding the appliance onto the fixed release, and rotating every credential and certificate the device held or brokered — VPN user credentials and session material, the appliance's own administrative accounts, any directory or authentication-service account it bound with, and its device certificates. This is precisely what the two network-security gaps on the entry miss: NIS2's obligations and CAF's resilient-network expectations both treat the remote-access gateway as a trusted enforcement point, so once it reports the fixed version the framework's questions are answered — while an implant installed through the RCE chain survives the upgrade untouched and keeps the position the gateway grants. Preconditions, all three load-bearing: the rebuild only helps if the unit comes up on the fixed release and is rebooted onto it, since the packet records no live-patch path and a reboot requirement; a configuration restored wholesale from a backup taken after the exposure began can carry the attacker's changes back in, so it is reviewed rather than replayed; and rebuilding the appliance does nothing about access the attacker already converted into a foothold behind it, so the internal follow-on investigation and the credential rotation are part of this runbook rather than a later phase.",
+        "evidence": "Packet active_exploitation_notes: 'Mass-exploited zero-day (CISA-flagged ransomware-associated); a remote unauthenticated attacker uses directory traversal in the web component to bypass control checks and reach restricted endpoints, and chains with CVE-2024-21887 command injection for unauthenticated RCE across the Ivanti Connect Secure / Policy Secure fleet.' attack_vector: the traversal 'slips past the authentication/control checks, exposing restricted endpoints and priming the paired CVE-2024-21887 command injection for full RCE'. affected_versions: Connect Secure 9.x and 22.x, Policy Secure 9.x and 22.x. The NIS2-Art21-network-security gap: 'Network-security obligations treat the VPN concentrator as a trusted control, but this pre-auth bypass turns the enforcement point into the entry point, which the control does not anticipate.' The UK-CAF-B4 gap: 'Resilient-network expectations assume the remote-access gateway is trustworthy; they do not require compensating segmentation for a gateway that is itself the vulnerable, internet-facing asset.' patch_required_reboot true, live_patch_available false, live_patch_notes: 'No vendor live-patch mechanism; remediation requires applying the fixed release and rebooting.' rwep_score 82, poc_available true, cisa_kev true, kev_date 2024-01-10.",
+        "gap_closes": [
+          "NIS2-Art21-network-security",
+          "UK-CAF-B4"
+        ]
+      }
+    ]
   },
   "CVE-2024-21887": {
     "name": "Ivanti Connect Secure and Policy Secure Command Injection Vulnerability",
@@ -54106,7 +54809,41 @@
         "adequate": false,
         "gap": "System-security outcomes assume management interfaces enforce authentication; an unauthenticated file upload/download endpoint defeats that assumption without dedicated management-plane isolation."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-030",
+        "name": "PERIMETER-DEVICE-ZERODAY-SLA-TIER",
+        "description": "The SRX Series is a perimeter firewall — the trust boundary itself — and the packet describes an unauthenticated request to webauth_operation.php uploading and downloading arbitrary files through J-Web, with the write primitive chaining into pre-auth remote code execution via the PHPRC flaw the packet names as its chaining partner. That is the case this tier exists for, and this entry is also a clean demonstration of why a CVSS-keyed SLA misfiles it: the base score is 5.3, which routes the item to a routine queue, while the packet's own flaw-remediation gap records that the medium score understates a pre-auth upload/download primitive documented as part of a public RCE chain, and the entry's RWEP is 77. For this device the requirement is that remediation runs on the tier clock opened by the 2023-11-13 KEV listing — the fixed Junos release for whichever train is in service (21.2R3-S8, 21.4R3-S6, 22.1R3-S5, 22.2R3-S3, 22.3R3-S2, 22.4R2-S2 or 22.4R3, 23.2R1-S2 or 23.2R2) — or, where the maintenance window cannot be taken inside it, J-Web is made unreachable from untrusted networks until it can. Cover every train the packet names: an estate standardised on 22.4 or 23.2 is exposed at a different fixed build than one on 21.2, and a sweep scoped to a single train reports clean across the rest. Completion is measured on the release each chassis is actually running: the packet records no live-patch mechanism and remediation requiring the fixed release plus a reboot, so a device staged with the image but not rebooted onto it is still serving the unauthenticated endpoint. Precondition on the isolation alternative: restricting or disabling J-Web bounds who can reach webauth_operation.php, it does not repair the missing authentication check — anything inside a permitted management segment still reaches it unauthenticated — and it is unavailable where J-Web is the operational management path for the device. It is a holding measure for the window before the fixed release and its reboot land, not a closure.",
+        "evidence": "The packet records CISA KEV 2023-11-13, active_exploitation confirmed, poc_available true, CVSS 5.3 against RWEP 77. The NIST-800-53-SI-2 gap states the medium base score understates a preauth upload/download primitive documented as part of a public RCE chain and that CVSS-keyed patch SLAs deprioritize it wrongly; the AU-ISM-1546 gap states patching within the ISM window does not mandate restricting the exposed webauth_operation.php endpoint; the ISO-27001-2022-A.8.8 gap states technical-vulnerability management under CVSS-medium scoring deprioritizes this endpoint, delaying remediation of an actively-exploited preauth flaw. patch_available true, patch_required_reboot true, live_patch_available false with live_patch_notes recording that remediation requires applying the fixed release and rebooting. affected_versions lists 21.2 prior to 21.2R3-S8, 21.4 prior to 21.4R3-S6, 22.1 prior to 22.1R3-S5, 22.2 prior to 22.2R3-S3, 22.3 prior to 22.3R3-S2, 22.4 prior to 22.4R2-S2 / 22.4R3, and 23.2 prior to 23.2R1-S2 / 23.2R2.",
+        "gap_closes": [
+          "AU-ISM-1546",
+          "ISO-27001-2022-A.8.8",
+          "NIST-800-53-SI-2"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-134",
+        "name": "DEVICE-MANAGEMENT-GATEWAY-CONFIG-ENDPOINT-AUTH-INPUT-NEUTRALIZATION",
+        "description": "J-Web is the device-management gateway on the SRX Series, and webauth_operation.php is the file-accepting endpoint on it that makes no authorization decision at all — the packet's access-enforcement gap states outright that access enforcement is exactly what is missing, and that it is missing for both the upload and the download direction. Bound to this product, the control means that endpoint authorizes its caller before the request is processed at all, in both directions, so an unauthenticated caller can neither write a file onto the firewall nor read one off it; and that no SRX is left with J-Web reachable from a segment with no operational need to manage the device, least of all from the internet. The read direction deserves separate attention on a firewall and is the half most often dropped: the same unauthenticated endpoint returns arbitrary files from the device that holds the configuration, and the packet records the read primitive as exposing sensitive files, so treating this purely as an upload bug leaves the disclosure path uncounted and closes the finding while the configuration is still readable. Distinguishing test: from a segment with no management role, issue an unauthenticated upload and an unauthenticated download request against webauth_operation.php on a staging SRX and confirm each is refused before any file is written or returned — an estate that attests every J-Web administrator authenticates at login passes cleanly while this path stays wide open, because the attacker never presents a J-Web account and no access decision is ever consulted. Precondition: the endpoint-side authorization is a property the fixed Junos release establishes — this control states what to verify, it does not implement it. Until that release and its reboot land, restricting which segments reach J-Web bounds who can send the request but leaves the endpoint fully exploitable to anything inside the permitted segment, so a compromised jump host or workstation already in the management network satisfies the exploit's only precondition in full.",
+        "evidence": "The packet's affected field records the J-Web interface on Juniper Junos OS SRX Series with unauthenticated arbitrary file upload and download via webauth_operation.php, and the attack_vector states the request lacks an authentication check, that the write primitive chains with the PHPRC flaw for pre-auth RCE, and that the read primitive exposes sensitive files. The NIST-800-53-AC-3 gap states access enforcement is exactly what is missing — webauth_operation.php requires no authentication for both upload and download of files — and that until patching, no access policy compensates. The NIST-800-53-SC-7 gap states boundary protection that exposes J-Web is the precondition and that segmenting or disabling the management interface is the durable mitigation patch-only remediation ignores. The NIS2-Art21-network-security gap states network-security duties do not mandate management-plane isolation, so an exposed J-Web keeps the unauthenticated upload/download reachable, and the UK-CAF-B4 gap states an unauthenticated file upload/download endpoint defeats the assumption that management interfaces enforce authentication. patch_available true with patch_required_reboot true and live_patch_available false.",
+        "gap_closes": [
+          "NIS2-Art21-network-security",
+          "NIST-800-53-AC-3",
+          "NIST-800-53-SC-7",
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-032",
+        "name": "PERIMETER-COMPROMISE-REBUILD-NOT-PATCH",
+        "description": "The primitive here is an unauthenticated arbitrary file write onto a perimeter firewall, and the fixed Junos release removes the write path without removing anything already written through it. So for any SRX whose J-Web was reachable from an untrusted network during the exposure window, the default disposition is configuration extraction, rebuild from a known-good image, and rotation of the credentials and keys the device's configuration held or that transited it — not upgrade-in-place followed by closing the flaw-remediation ticket. Both primitives argue for it: the write half means a file placed on the device survives the upgrade intact, and the read half means the configuration was retrievable unauthenticated, so the material inside it must be treated as disclosed rather than as protected by reaching the fixed release. The packet records confirmed active exploitation, a public proof-of-concept, and this CVE as part of the J-Web pre-auth chain, which is what makes the upgrade-only disposition insufficient rather than merely conservative. Scoping precondition, which is where this control is most often over-applied: this disposition attaches to units whose J-Web was actually reachable during the window, not to every SRX in the estate — the packet's own note that this entry's EPSS is far below its sibling CVEs, reflecting narrower standalone weaponization, is a reason to establish reachability per unit rather than to rebuild a whole fleet. It is also worth stating what cannot be leaned on when establishing that: because the flaw itself grants an unauthenticated write to the device's filesystem, records held only on the device are not a trustworthy basis for concluding a unit was untouched, so absence of local evidence on a reachable unit is inconclusive rather than exculpatory. Rebuild does not prevent the exploitation and does nothing for a unit still on a vulnerable release; it is what makes the fixed release a genuine end-state on a unit that was exposed.",
+        "evidence": "The packet's attack_vector records an unauthenticated attacker uploading and downloading arbitrary files via J-Web, giving both a file-write primitive for RCE chaining and arbitrary-file read, and the vector records the resulting loss of integrity or confidentiality with possible chaining to other vulnerabilities. active_exploitation is confirmed with poc_available true, the entry is described as part of the Juniper J-Web pre-auth chain, and it was CISA KEV-listed 2023-11-13. patch_available true, patch_required_reboot true, live_patch_available false, with live_patch_notes recording that remediation requires applying the fixed release and rebooting. The packet also records EPSS 0.011 (61.7th percentile), far lower than the sibling CVEs, reflecting narrower standalone weaponization, and the NIST-800-53-SI-2 gap frames remediation of this entry purely in patch-SLA terms.",
+        "gap_closes": [
+          "NIST-800-53-SI-2"
+        ]
+      }
+    ]
   },
   "CVE-2023-29552": {
     "name": "Service Location Protocol (SLP) Denial-of-Service Vulnerability",
@@ -54558,7 +55295,30 @@
         "adequate": false,
         "gap": "Technical-vulnerability-management deprioritizes a 'medium' XSS, so the KEV-listed, actively-exploited flaw lingers unpatched on internet-facing webmail."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "This entry is the case where a severity-keyed patch queue and a KEV-keyed one give opposite answers, and the packet says so three times. It scores the flaw at CVSS 5.4, and its technical-vulnerability-management, flaw-remediation and Essential Eight patch gaps all record the same failure: a 'medium' stored XSS is deprioritized on score while the same packet carries a CISA KEV listing dated 2023-10-26 and exploitation by the Winter Vivern (TA473) espionage group against government webmail. The requirement here is that the KEV listing, not the CVSS band, sets the clock for every Roundcube Webmail installation the organization runs, and that the upgrade is to the fixed release on each installation's own branch — 1.4.15 for installs below 1.4.15, 1.5.5 for 1.5.x, 1.6.4 for 1.6.x — rather than letting a medium score route the ticket into a routine maintenance queue. The branch split is operationally load-bearing because an estate hosting several Roundcube instances will have them at different branch levels, and an instance left on a pre-1.5.5 1.5.x build is still serving the vulnerable rcube_washtml.php sanitizer no matter what the 1.6.x instance was upgraded to. The packet records no live-patch mechanism and states that remediation requires applying the vendor fixed release, so completion is measured on the release the running webmail actually serves rather than on a package or repository state: where long-lived PHP worker processes or a bytecode cache continue serving previously deployed code, the fixed sanitizer is not yet in effect for the sessions being served, and that instance is not remediated. Distinguishing test: query every Roundcube instance in the estate for the release it is serving and confirm each is at or above its own branch's fixed release; an attestation satisfied by upgrading one instance leaves the rest exposed to a flaw with confirmed in-the-wild use and, on this entry, public exploit code. Precondition: this bounds future exposure only. The packet has the attacker's JavaScript running inside the victim's authenticated Roundcube session to read and exfiltrate mail, so upgrading recalls nothing already taken, and a mailbox whose owner rendered a crafted message during the exposure window is an incident-response question rather than a patch-record one.",
+        "evidence": "Packet fields: name = 'Roundcube Webmail Persistent Cross-Site Scripting (XSS) Vulnerability'; cvss 5.4 against rwep_score 64; cisa_kev true, kev_date 2023-10-26; active_exploitation confirmed with active_exploitation_notes 'Exploited in the wild by the Winter Vivern (TA473) espionage group against government webmail targets: a crafted SVG in an HTML email ran JavaScript in the victim's Roundcube session to exfiltrate mail'; vector = 'Roundcube before 1.4.15, 1.5.x before 1.5.5, and 1.6.x before 1.6.4 allows stored XSS via an HTML e-mail message with a crafted SVG document because of program/lib/Roundcube/rcube_washtml.php behavior'; affected_versions = '< 1.4.15', '1.5.x < 1.5.5', '1.6.x < 1.6.4'; poc_available true; patch_available true, patch_required_reboot false (no host reboot recorded), live_patch_available false, live_patch_notes 'No vendor live-patch mechanism; remediation requires applying the vendor fixed release'. Gap text used: ISO-27001-2022-A.8.8 = 'Technical-vulnerability-management deprioritizes a medium XSS, so the KEV-listed, actively-exploited flaw lingers unpatched on internet-facing webmail'; NIST-800-53-SI-2 = 'Flaw-remediation timelines for webmail are often relaxed given the medium CVSS, yet a targeted APT exploited it promptly — the severity-driven patch prioritization under-weights active exploitation'; AU-Essential-8-Patch = 'Essential-Eight patch prioritization keyed to CVSS under-weights a medium stored-XSS, yet Winter Vivern weaponized this SVG-sanitizer bypass promptly against internet-facing Roundcube'.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "ISO-27001-2022-A.8.8",
+          "AU-Essential-8-Patch"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-040",
+        "name": "OWA-PER-REQUEST-SIEM-INGESTION",
+        "description": "The premise this control rests on holds in its strongest form on this entry: the packet's attack path generates no authentication event at all. The victim logs into Roundcube Webmail normally, views an HTML message whose crafted SVG bypasses the rcube_washtml.php sanitizer, and the attacker's JavaScript then reads and exfiltrates mail across that same already-authenticated session — so an authentication-event log shows one ordinary login and nothing else, which is precisely why the monitoring and incident-handling gaps on this entry describe the exfiltration as unobserved and late-detected. For this product the requirement is that Roundcube's per-request access logs — which mail-retrieval actions ran, against which message identifiers, in what order, at what rate, and on which session — are forwarded to a SIEM outside the webmail host and retained long enough to cover a campaign rather than a shift. The rule has to key on what an exploit doing exactly what the packet describes emits: a burst of message-fetch requests inside a single authenticated session beginning when a message is rendered, sequenced by mailbox contents rather than by anything a person clicked, with no new login and no credential event anywhere in the sequence. That is the observable; a rule keyed to failed logins, server process anomalies, or host-level file changes would see nothing here, because the server is not compromised — the session is, which is exactly the incident-handling gap the packet records. Preconditions. This is detection, not prevention: it does not repair the sanitizer, does not stop the script executing in the session, and does not recall mail already exfiltrated; what it bounds is the interval between the message being viewed and someone knowing. It works only on telemetry already being collected and shipped off-host before the message arrives, and per-request access logging on an internet-facing webmail host is the collection most often left rotating locally, so a query written after the fact returns nothing. Retention has to be sized against the threat the packet names — a targeted espionage group working government webmail is a campaign that outlasts a short local rotation window — and the control is a complement to reaching the fixed release on each branch, not a substitute for it.",
+        "evidence": "Packet fields: attack_vector = 'An attacker sends an HTML email whose crafted SVG document bypasses Roundcube's HTML sanitizer; when the victim views the message, attacker-controlled JavaScript executes in the webmail session and can read/exfiltrate mail'; affected = 'Roundcube Webmail — stored XSS via a crafted SVG in an HTML email due to rcube_washtml.php sanitizer behavior, allowing attacker JavaScript to run in the victim's session'; active_exploitation_notes = 'Exploited in the wild by the Winter Vivern (TA473) espionage group against government webmail targets: a crafted SVG in an HTML email ran JavaScript in the victim's Roundcube session to exfiltrate mail'. Gap text used: UK-CAF-C1 = 'Security-monitoring expectations focus on host/network telemetry, not on anomalous webmail DOM/script behavior, leaving this XSS-driven exfiltration unobserved'; NIS2-Art21-incident-handling = 'Incident-handling processes centered on server compromise miss session-level mail exfiltration triggered purely by viewing an email, so the breach is detected late or not at all'. That the weaponized message reaches the mailbox in the first place is the packet's NIST-800-53-SI-3 gap: 'Malicious-code protection (mail AV/anti-spam) does not inspect for sanitizer-bypassing SVG/HTML that yields client-side script execution, so the weaponized email passes content filtering.'",
+        "gap_closes": [
+          "UK-CAF-C1",
+          "NIS2-Art21-incident-handling"
+        ]
+      }
+    ]
   },
   "CVE-2023-20273": {
     "name": "Cisco IOS XE Web UI Command Injection Vulnerability",
@@ -56407,7 +57167,30 @@
         "adequate": false,
         "gap": "Technical-vulnerability management is periodic; a client-side zero-day exploited on open needs continuous endpoint monitoring beyond A.8.8's assessment cadence."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-144",
+        "name": "EMBEDDED-MEDIA-PARSER-LIBRARY-INVENTORY-AND-PATCH-PARITY",
+        "description": "The packet names the affected product as Adobe Acrobat and Adobe Acrobat Reader on Windows and macOS, and its affected_versions splits that into three separate update tracks: Acrobat/Reader DC at or below 23.003.20284, Acrobat/Reader 2020 at or below 20.005.30516, and Acrobat/Reader 2020 (Classic) at or below 20.005.30514. On a real estate those are separate products on separate update mechanisms, and per-user copies land outside managed software distribution, so this control means enumerating every Acrobat and every Reader install across all three tracks and both operating systems and confirming each reports a build above its own track's affected ceiling, rather than closing the flaw-remediation ticket when the single inventoried Reader package updates. Scope stops there. The packet ties the CWE-787 out-of-bounds write to Acrobat and Reader and gives no mapping into other PDF-handling software, so treating every PDF-capable binary on the estate as an instance of this CVE manufactures findings and removal work against renderers no evidence implicates; widen the inventory only where a verified source identifies another product carrying the same code. Drive the sweep on the clock that opened with the 2023-09-14 KEV listing rather than on the 2023-10-05 due date the packet's flaw-remediation gap records, because the packet states the flaw was exploited in the wild before Adobe's September 2023 fix existed, so the due date trails the exploitation it is supposed to bound. Distinguishing test: after the managed update lands, enumerate the Acrobat and Reader installs and produce each one's build, confirming none still sits at or below its own track's affected version. An estate that updates the inventoried Reader DC copy while a 2020 Classic install stays at 20.005.30514 still opens crafted PDFs into the out-of-bounds write, with a flaw-remediation attestation that reads clean. Preconditions: this reaches only copies the inventory can see and the operator can update, so an unmanaged per-user install is remediated by removing it, not by recording it as patched. The packet records no live-patch mechanism and states that remediation requires applying the vendor fixed release, so completion has to be measured on the build each install is actually executing rather than on a deployment task marked successful; a copy where the update is staged but the Acrobat or Reader process has not come up on the new build is still running the vulnerable parser. And because active exploitation is confirmed and delivery is an attacker-supplied file, a user who opened an untrusted PDF while their install was at or below the affected version belongs on the incident path rather than being closed on the patch record.",
+        "evidence": "Packet fields: affected = 'Adobe Acrobat and Adobe Acrobat Reader (Windows and macOS) processing a maliciously crafted PDF; out-of-bounds write reachable when the victim opens the file'; affected_versions = 'Acrobat/Reader DC <= 23.003.20284', 'Acrobat/Reader 2020 <= 20.005.30516', 'Acrobat/Reader 2020 (Classic) <= 20.005.30514'; cwe_refs = CWE-787; cisa_kev = true with kev_date 2023-09-14; active_exploitation = confirmed, with active_exploitation_notes 'Exploited in the wild as a zero-day before Adobe's September 2023 fix'; patch_available = true, live_patch_available = false, live_patch_notes = 'No vendor live-patch mechanism; remediation requires applying the vendor fixed release'; patch_required_reboot = false (no host reboot recorded). The 2023-10-05 KEV due date is the figure recorded in the packet's NIST-800-53-SI-2 gap ('the KEV due date (2023-10-05) trailed active exploitation, so SI-2 SLAs alone do not close the exposure'), which is also the ISO-27001-2022-A.8.8 gap's point that periodic technical-vulnerability management does not match a client-side zero-day exploited on open. poc_available is false on this entry, so no public exploit code is claimed.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "ISO-27001-2022-A.8.8"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-120",
+        "name": "DOWNLOAD-PROVENANCE-ENFORCEMENT",
+        "description": "Exploitation of this CVE requires the victim to open an attacker-supplied PDF: the packet's vector states that exploitation requires user interaction in that a victim must open a malicious file, and its attack_vector has the attacker delivering a crafted PDF whose opening triggers the out-of-bounds write and code execution in the current user's context. On any Acrobat or Reader install not yet above its track's fixed build, the delivery path is therefore the only lever the operator holds. Require an untrusted-origin marking on every PDF arriving by mail, web download, or untrusted file share, and require marked PDFs to open in Acrobat's reduced-privilege isolated render rather than the full parsing path that carries the CWE-787 write at the user's own privilege; the packet's application-hardening gap names exactly this pairing, disabling Acrobat's embedded JavaScript and opening untrusted PDFs in Protected View, as the compensating control the KEV entry does not mandate, and its EU vulnerability-handling gap names the attachment sandboxing and mail filtering that keeps the file from reaching the parser at all. The marking must survive the container: a PDF extracted from an archive, mounted from an image, or renamed has to still reach Acrobat marked untrusted, and the user-facing escape from the isolated render has to be blocked by policy rather than left as a click, since the whole exploit precondition is one user action. Distinguishing test: mail a PDF nested inside an archive to a managed workstation, extract it, open it, and confirm it lands in the isolated render rather than the full parser; an attestation that records the hardening policy as configured still lets a provenance-stripped PDF reach the vulnerable parser with full user privileges. Preconditions, and they are the load-bearing half here. This contains the render, it does not repair the write: the out-of-bounds write is still present in the binary, so this is a holding measure for the window before the fixed build lands, which on this entry is precisely the window that mattered because the packet records exploitation in the wild before Adobe's September 2023 fix existed. It holds only where the ingress path actually applies the marking, so a PDF arriving on removable media, pulled from an internal share the policy treats as trusted, or re-saved by the user loses the tag and opens into the full parser, and those paths need to be enumerated rather than assumed covered. And it does nothing for a workstation on which a crafted PDF has already been opened: active exploitation is confirmed and the outcome is code execution in the user's context, so that machine is an incident, not a configuration item.",
+        "evidence": "Packet fields: vector = 'Exploitation of this issue requires user interaction in that a victim must open a malicious file'; attack_vector = 'An attacker delivers a crafted PDF; opening it in a vulnerable Acrobat/Reader build triggers an out-of-bounds write and arbitrary code execution in the current user's context'; cwe_refs = CWE-787; active_exploitation = confirmed with active_exploitation_notes 'Exploited in the wild as a zero-day before Adobe's September 2023 fix'. The named compensating measures are taken from the packet's own gap text: AU-Essential-8-App-Hardening = 'Hardening endpoint applications (disabling Acrobat's embedded JavaScript / opening untrusted PDFs in Protected View) is the compensating control the KEV entry does not mandate; patch cadence alone left users exposed at open-time'; NIS2-Art21-vulnerability-handling = 'Requires timely handling but not the user-interaction-blocking controls (attachment sandboxing, mail filtering) needed to stop a document-delivered client RCE between disclosure and patch'; UK-CAF-B4 = 'System security expects patched software but does not force the endpoint isolation/EDR detection required for a memory-corruption RCE that fires on document open'. patch_available is true with live_patch_available false, so this control is stated as interim to the fixed release rather than as an alternative to it.",
+        "gap_closes": [
+          "AU-Essential-8-App-Hardening",
+          "NIS2-Art21-vulnerability-handling",
+          "UK-CAF-B4"
+        ]
+      }
+    ]
   },
   "CVE-2023-35674": {
     "name": "Android Framework Privilege Escalation Vulnerability",
@@ -56599,7 +57382,31 @@
         "adequate": false,
         "gap": "System security expects patched software but gives no mechanism to inventory and update a codec vendored into dozens of applications."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-144",
+        "name": "EMBEDDED-MEDIA-PARSER-LIBRARY-INVENTORY-AND-PATCH-PARITY",
+        "description": "The packet refuses to scope this to a browser and the inventory must not either. It records the flaw in libwebp below 1.3.2, states that everything embedding it is reachable through a crafted WebP image, and names Google Chrome below 116.0.5845.187 alongside Chromium-based browsers and Electron and native applications that bundle their own copy. That is the population this control requires enumerated, each install held to its own fixed build rather than to the browser's: Chrome at 116.0.5845.187 or later, each Chromium-based browser at the build its own vendor ships carrying the fix, and each Electron or native application at a build carrying libwebp 1.3.2 or later. Scoping the sweep to Chrome is the specific failure the packet's gaps describe — flaw remediation keyed to the browser misses the sprawl of applications shipping their own libwebp, and a vulnerability-management process scoped to OS and browser inventories never enumerates the embedded copies at all — so an estate standardised on a Chromium-based browser other than Chrome, or one whose desktop applications are Electron, produces a clean patch report while the decoder stays reachable from any rendered image. Do not widen past what the packet establishes: it ties the overflow to libwebp's VP8L Huffman-table decoding, so treating every image-handling or media-parsing binary in the estate as an instance of this CVE manufactures findings and update work against software no evidence implicates; widen only where a verified source names another product carrying this component. Precondition on completion, and it is the one most often mis-read here: patch_required_reboot is false, which means no machine reboot — it does not mean the fix is live. libwebp is mapped into a running process, so a browser or application that has received the new build keeps decoding through the copy already loaded until that process restarts, and the packet records no live-patch path. Measure each install on the version the running process is executing, not on what the software-distribution console reports as delivered. And because exploitation is confirmed and delivery is attacker-controlled content — a crafted HTML page, or any WebP image a vulnerable decoder renders — a host that rendered untrusted content while below the fixed build belongs on the incident path rather than being closed on the inventory.",
+        "evidence": "Packet affected: 'libwebp < 1.3.2 (and everything embedding it), reached via a crafted WebP image; Google Chrome prior to 116.0.5845.187 and numerous Chromium/Electron and native applications that decode WebP.' affected_versions: 'libwebp < 1.3.2', 'Google Chrome < 116.0.5845.187', 'Chromium-based browsers and Electron/native apps bundling libwebp < 1.3.2'. attack_vector: a crafted WebP image with malformed lossless (VP8L) Huffman coding tables overflows libwebp's BuildHuffmanTable, reachable via a crafted HTML page or any app that renders WebP. NIST-800-53-SI-2 gap: 'Flaw remediation must reach every application that statically or dynamically links libwebp, not just the browser; SI-2 patch tracking keyed to Chrome misses the sprawl of Electron/native apps that ship their own libwebp.' UK-CAF-B4 gap: 'System security expects patched software but gives no mechanism to inventory and update a codec vendored into dozens of applications.' AU-Essential-8-Patch gap: 'Patch maturity assumes a single vendor update path.' ISO-27001-2022-A.8.8 gap: technical-vulnerability management scoped to OS/browser inventories does not enumerate embedded libwebp. Remediation state: patch_available true, patch_required_reboot false, live_patch_available false, live_patch_notes 'No vendor live-patch mechanism; remediation requires applying the vendor fixed release.' CWE-787, CISA KEV 2023-09-13, active_exploitation confirmed, poc_available true, CVSS 8.8, RWEP 79, EPSS ~0.997.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "ISO-27001-2022-A.8.8",
+          "AU-Essential-8-Patch",
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-021",
+        "name": "TIER-3-DEPENDENCY-INVENTORY",
+        "description": "The reason the install inventory above cannot be built from an application list alone is the problem this control addresses. libwebp is not something an operator installs; it is a component vendored beneath products, and the packet's vulnerability-handling gap states outright that vulnerability management does not by itself require the SBOM or component inventory needed to find every product bundling the vulnerable codec. For this CVE that means component inventory has to reach the depth at which libwebp actually sits — statically linked into a native application, bundled inside an Electron runtime, or pulled in transitively by a framework the application depends on — and has to resolve to a version, because the only question that matters per artifact is whether the copy it ships is below 1.3.2. An SBOM that stops at the dependencies an application declares directly will not name libwebp at all for most of the affected population, which is how an estate can hold a complete and current application inventory and still not know where the vulnerable decoder is. Precondition, and it bounds what this control can be credited with: it produces knowledge, not remediation. It tells the operator which artifacts carry a copy below 1.3.2; each of those still has to reach a build carrying libwebp 1.3.2 or later from a vendor who may ship on a slower track than the browser, and the packet records no live-patch path, so each of those updated processes still has to be restarted before the fix is executing. Where a bundling application ships no updated build at all, the component inventory is what converts an invisible exposure into a decision the operator can actually take about that application rather than one they never knew they were carrying.",
+        "evidence": "Packet NIS2-Art21-vulnerability-management gap: 'Vulnerability management does not by itself require an SBOM/component inventory to find every product bundling the vulnerable codec, leaving unmanaged copies exposed to a crafted image.' ISO-27001-2022-A.8.8 gap: 'Technical-vulnerability management scoped to OS/browser inventories does not enumerate embedded libwebp in third-party software, so a supply-chain-wide image-decoder flaw stays unpatched in bundled copies.' affected: 'libwebp < 1.3.2 (and everything embedding it)'; affected_versions includes 'Chromium-based browsers and Electron/native apps bundling libwebp < 1.3.2'. patch_available true, live_patch_available false, live_patch_notes 'No vendor live-patch mechanism; remediation requires applying the vendor fixed release.' CISA KEV 2023-09-13, active_exploitation confirmed, poc_available true, CVSS 8.8, RWEP 79.",
+        "gap_closes": [
+          "NIS2-Art21-vulnerability-management",
+          "ISO-27001-2022-A.8.8"
+        ]
+      }
+    ]
   },
   "CVE-2023-36761": {
     "name": "Microsoft Word Information Disclosure Vulnerability",
@@ -58300,7 +59107,30 @@
         "adequate": false,
         "gap": "A.8.28 secure-coding controls should have caught the unescaped reflection of user-controlled URL parameters into the Classic Web Client; because the sink shipped to production and was exploited before the patch, the control failed at the code level rather than the deployment level."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "For this entry the clock has two starts and the estate has to be driven against the earlier one. Zimbra Collaboration 8 installs below 8.8.15 Patch 41 carry the Classic Web Client sink the packet describes — an unescaped URL parameter reflected into rendered HTML inside the authenticated webmail origin — and the packet places exploitation at 2023-06-29, roughly four weeks before the 2023-07-27 KEV listing and ahead of the vendor advisory. A KEV-tied SLA measured from 2023-07-27 alone therefore produces a remediation record for the tail of the campaign, not for the campaign. Applied to this product: enumerate every Zimbra Collaboration 8 mail server in service, drive each to 8.8.15 Patch 41, and measure completion on the version the running Zimbra services report after they restart. The packet records no live-patch path and states that applying Patch 41 restarts the Zimbra services though not the host, so an instance where the package landed but the webmail service was never restarted is still serving the vulnerable Classic Web Client and counts as exposed — patch_required_reboot being false says only that the machine stays up. Distinguishing test: request the Classic Web Client from each server and confirm the build it actually serves is at or above 8.8.15 Patch 41; an inventory row reading 'Patch 41 applied' beside a running service still answering on the prior build is precisely how this remediation gets recorded complete while the sink is live. Precondition, and the one most often missed here: the packet states the exploit steals mailbox data, cookies and auth tokens from the victim's session, and Patch 41 does nothing to a token already taken — a server reachable during the exposure window needs its webmail sessions invalidated and the credentials of users who could have clicked a crafted link rotated, rather than being closed on the patch record. Steering users toward a different client is not a substitute either: the Classic Web Client endpoint stays served by the same instance until the build carries the fix.",
+        "evidence": "Packet: cisa_kev true, kev_date 2023-07-27, active_exploitation confirmed, poc_available true, rwep_score 62 against cvss 6.1. active_exploitation_notes: 'Google TAG observed four distinct groups — including the Russia-aligned Winter Vivern — exploiting the flaw against government targets in Moldova and Tunisia starting 2023-06-29, at least two weeks before Zimbra's advisory.' affected: the ZCS Classic Web Client 'which reflects an unescaped URL parameter into rendered HTML, enabling cross-site scripting in the authenticated webmail origin'; affected_versions: 'Zimbra Collaboration 8 before 8.8.15 Patch 41'. patch_available true, patch_required_reboot false, live_patch_available false, live_patch_notes: 'No vendor live-patch mechanism; remediation requires applying Zimbra 8.8.15 Patch 41, which restarts Zimbra services but not the host.' attack_vector: attacker JavaScript runs in the webmail origin when an authenticated victim clicks a crafted link, 'allowing theft of mailbox data, cookies, and auth tokens'.",
+        "gap_closes": [
+          "AU-Essential-8-Patch",
+          "NIS2-Art21-patch-management",
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-072",
+        "name": "PRIMARY-SOURCE-INTAKE-VENDOR-BLOG-COVERAGE",
+        "description": "This entry extends the control's premise past vendor blogs to the vendor's own public source repository. The packet records that Zimbra's fix landed in public source on 2023-07-05 and that a later wave of attackers harvested it from there and exploited the flaw before 8.8.15 Patch 41 shipped — so for the interval between that push and the released patch, the authoritative signal that Zimbra 8 webmail was exploitable existed in a primary source while every advisory-driven feed the estate subscribes to was still silent. For an operator running Zimbra Collaboration 8 the requirement is concrete: treat the vendor's public commit stream for that product as a monitored intake source alongside the advisory page; make a security-relevant commit touching the webmail rendering path, with no accompanying advisory, open a case rather than wait for the bulletin; and start the internal remediation clock at the earlier of the two signals rather than at the advisory. Distinguishing test: take a fix the vendor published in source ahead of its own advisory and check whether the intake pipeline raised anything on the commit date — a pipeline whose Zimbra coverage is the advisory page alone produces nothing, which is exactly the result it produced in July 2023 while a second wave was already exploiting the harvested fix. Precondition, stated because this control is easy to over-credit: it shortens the interval between a public fix and the operator knowing, and it gives nothing at all for the first window the packet describes — 2023-06-29 through the 2023-07-05 push — during which the flaw was a zero-day with no fix in any source. That window is bounded by response and by session/credential invalidation after the fact, not by intake coverage.",
+        "evidence": "Packet active_exploitation_notes: 'A later wave harvested the fix from Zimbra's public GitHub (pushed 2023-07-05) and exploited it before the official 8.8.15 Patch 41 shipped', with initial exploitation from 2023-06-29 'at least two weeks before Zimbra's advisory'. The NIST-800-53-SI-10 gap in framework_control_gaps states that 'because the fix landed in public source on 2023-07-05 before the advisory, an SI-10 review keyed to vendor bulletins had no signal until attackers were already stealing tokens'. The NIS2-Art21-patch-management gap states 'a bulletin-driven patch process left webmail exploitable through the KEV 2023-07-27 window and until 8.8.15 Patch 41'. The AU-Essential-8-Patch gap states the two-week clock 'starts at fix availability' and that the flaw was exploited 'via the leaked commit before 8.8.15 Patch 41, so an on-time patcher was still exposed during the active campaign'.",
+        "gap_closes": [
+          "NIS2-Art21-patch-management",
+          "AU-Essential-8-Patch"
+        ]
+      }
+    ]
   },
   "CVE-2023-38606": {
     "name": "Apple Multiple Products Kernel Unspecified Vulnerability",
@@ -58848,7 +59678,39 @@
         "adequate": false,
         "gap": "A.8.8 technical vulnerability management presumes a triage-and-schedule flow, but an exploited WebKit zero-day demands emergency out-of-cycle patching; standard prioritization SLAs would leave a code-execution-on-page-load bug open far too long."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-056",
+        "name": "MOBILE-ENDPOINT-MDM-ENFORCED-KEV-SLA",
+        "description": "For this WebKit entry the control means the KEV-class update is driven onto managed Apple endpoints from the 2023-07-13 listing with user deferral disallowed, because user-side deferral is precisely the failure the packet records: devices with automatic Rapid Security Response or updates disabled stayed exploitable through ordinary browsing until the fix was installed by hand. Completion has to be measured on the build the device is actually running after its restart, not on the update being approved, downloaded, or reported as applied — the packet registers no live-patch mechanism for WebKit and states the fixed release or the corresponding Rapid Security Response requires a device restart, so a device holding the update but not yet restarted is still executing vulnerable WebKit and still renders attacker-controlled web content through it. Scope the enforcement to every product the packet names rather than to the device classes this control's estate definition covers: iOS and iPadOS at 16.6, macOS Ventura at 13.5 and Safari at 16.5.2 fall inside a normal Apple device-management ring, but tvOS 16.6 and watchOS 9.6 are separate fixed builds in the same affected list and need enumerating on their own rather than being assumed covered by the ring that reports on phones and Macs. The packet's affected field further extends the same WebKit defect to non-Apple products embedding WebKit for HTML processing; it names no specific one, so widen the inventory to a given third-party product only where a verified source identifies it as carrying the component, and reach that product's own fixed build rather than treating the Apple builds as covering it.",
+        "evidence": "Packet fields for CVE-2023-37450: cisa_kev true with kev_date 2023-07-13, active_exploitation confirmed, cvss 8.8, cwe_refs CWE-787, patch_available true, patch_required_reboot true, live_patch_available false. live_patch_notes: 'No live-patch mechanism for WebKit; remediation is installing the Apple fixed release (iOS/iPadOS 16.6, Safari 16.5.2, macOS Ventura 13.5, tvOS 16.6, watchOS 9.6) or the corresponding Rapid Security Response, which requires a device restart.' affected_versions lists iOS/iPadOS < 16.6, Safari < 16.5.2, macOS Ventura < 13.5, tvOS < 16.6, watchOS < 9.6; the affected field covers iOS, iPadOS, macOS, Safari, tvOS and watchOS and non-Apple products embedding WebKit for HTML processing. The NIST-800-53-SI-2 gap states that devices with automatic RSR/updates disabled remained exploitable through simple web browsing until the fix was manually installed after the 2023-07-13 KEV listing. The AU-Essential-8-Patch gap states that fleets of iPhones, iPads and Macs are hard to force-update within the 48-hour target.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "NIS2-Art21-patch-management",
+          "AU-Essential-8-Patch"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-057",
+        "name": "BROWSER-MANAGED-UPDATE-NO-DEFERRAL",
+        "description": "This CVE is a defect in the web engine itself, and the packet treats Safari as its own fixed build — Safari 16.5.2 is listed separately from macOS Ventura 13.5 — so on a managed Mac estate the browser has an update path that an OS-scoped deferral does not carry. The requirement here is that the channel delivering the Safari update and Apple's out-of-band Rapid Security Response is exempt from ring staging: the packet records that the fix shipped out of band rather than on the scheduled release cadence, and that organizations relying on managed update rings could not push it fast enough to close a bug reachable by any browsed page. A ring configured to hold releases for change-control review, with no security-channel exemption, keeps the estate on vulnerable WebKit for the duration of that hold while the rendering path stays fully exposed. Two preconditions on this control, both of which are how it gets over-recorded as the mitigation: it is an administrator-side lever only, so it does nothing on a device where the user has switched automatic updates off — the packet names that as a separate failure, and it belongs to the device-management enforcement path rather than to this one. And releasing the update into the ring is not the completion state: the packet records a required device restart with no live-patch mechanism, so a Mac that has taken Safari 16.5.2 or the Rapid Security Response but has not restarted is still running the pre-fix engine.",
+        "evidence": "Packet fields for CVE-2023-37450: affected_versions lists 'Safari < 16.5.2' and 'macOS Ventura < 13.5' as separate entries; live_patch_notes names both the fixed releases and 'the corresponding Rapid Security Response, which requires a device restart', with live_patch_available false and patch_required_reboot true. active_exploitation_notes records that Apple shipped the fix as an out-of-band Rapid Security Response and that CISA added the CVE to KEV on 2023-07-13. The NIS2-Art21-patch-management gap states that patch-management processes geared to scheduled vendor releases were outpaced by this actively-exploited WebKit zero-day, and that organizations relying on managed update rings could not push the emergency RSR fast enough to close a bug reachable by any browsed page. The NIST-800-53-SI-2 gap separately records devices with automatic RSR/updates disabled as remaining exploitable.",
+        "gap_closes": [
+          "NIS2-Art21-patch-management"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-126",
+        "name": "MOBILE-OS-MINIMUM-PATCH-LEVEL-ENFORCEMENT",
+        "description": "For the Apple devices in an estate that cannot yet reach iOS/iPadOS 16.6, Safari 16.5.2 or macOS Ventura 13.5, the fixed build has to function as an access condition — mail, VPN and document access denied to a device below it — rather than as a row on a patch-compliance dashboard, because until that device restarts onto the fixed build any page it renders reaches the WebKit defect. The distinguishing test is to enrol a device pinned below the fixed build and confirm the policy actually denies it access to protected resources; an estate that surfaces the stale build on a report while the device keeps its mail and document access has recorded the exposure rather than removed it. The precondition that matters on this CVE is which half of the control is load-bearing, and it is not the usual one: the packet's delivery path is a target lured to attacker-controlled web content, not a malicious application, so restricting untrusted or side-loaded application installation — the half this control normally leans on for the pre-fix window — does nothing here, and ordinary browsing on a fully compliant device reaches the flaw. The access condition therefore bounds what a compromised device can reach; it does not prevent the code execution, and it is a holding measure for the window before the fixed build and its required restart land. Because active exploitation is confirmed and the content is attacker-controlled, a device that browsed while below the fixed build belongs on the incident path rather than being closed when it later reports the fixed build.",
+        "evidence": "Packet fields for CVE-2023-37450: active_exploitation confirmed with kev_date 2023-07-13, patch_available true, patch_required_reboot true, live_patch_available false, and live_patch_notes naming iOS/iPadOS 16.6, Safari 16.5.2, macOS Ventura 13.5, tvOS 16.6 and watchOS 9.6 or the corresponding Rapid Security Response, which requires a device restart. attack_vector states that a target is lured to attacker-controlled web content and that processing it in WebKit triggers memory corruption leading to arbitrary code execution; active_exploitation_notes adds that exploitation requires luring a target to attacker-controlled web content (UI:R), consistent with targeted mobile-device attacks rather than mass exploitation, and that no detailed public PoC or technical writeup was released (poc_available false). The AU-Essential-8-Patch gap states that fleets of iPhones, iPads and Macs are hard to force-update within the 48-hour window. The ISO-27001-2022-A.8.8 gap states that standard prioritization SLAs would leave a code-execution-on-page-load bug open far too long.",
+        "gap_closes": [
+          "ISO-27001-2022-A.8.8",
+          "AU-Essential-8-Patch"
+        ]
+      }
+    ]
   },
   "CVE-2023-32046": {
     "name": "Microsoft Windows MSHTML Platform Privilege Escalation Vulnerability",
@@ -58909,7 +59771,30 @@
         "adequate": false,
         "gap": "A.8.8 technical-vulnerability management presumes a known fix to prioritize; for a zero-day EoP shipped and exploited on 2023-07-11, the control has nothing to act on until the update exists, so the exposure predates any compliant vulnerability-handling cycle."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-120",
+        "name": "DOWNLOAD-PROVENANCE-ENFORCEMENT",
+        "description": "The packet gives one delivery path for this flaw and nothing else: a user opens a crafted file delivered by email or the web, and the Windows MSHTML platform elevates the attacker to that user's privileges as one link in a wider chain. On an estate that has not yet taken the July 2023 cumulative update and its reboot, controlling how externally sourced files arrive and are handled is the only lever the operator holds, because the defective component is a Windows platform component sitting behind whatever handler opens the file. Apply the untrusted-origin marking at ingress — mail gateway, web download, untrusted file share — rather than relying on the handling application to infer origin, and require the marking to survive the container the file arrives in: extraction from an archive, mounting from an ISO or VHD, and renaming must all preserve it. Two scoping points matter here and both come from the packet rather than from habit. It does not name a file type, only 'a crafted file', so the marking has to cover externally sourced files generally instead of one application's document format. And affected_versions names Windows and Windows Server editions below the July 2023 update, so the population is both — a server where an administrator opens an attachment is in scope exactly as a workstation is. Distinguishing test: send an externally sourced file through each ingress path, nested inside an archive, and confirm it still reaches the endpoint marked untrusted; a policy attestation that the marking is enabled says nothing about whether it survived the archive, and a provenance-stripped file reaches the handler with the user's full privileges. Precondition, and it is why this is a holding measure rather than a fix: the marking bounds how an externally sourced file is treated, it does not repair the MSHTML platform defect, and it is never consulted where a user is permitted to clear the marking, where an ingress path applies none, or where the file arrives by a route the estate does not mediate. The vulnerable component stays in-path on every affected host until the update and its reboot land.",
+        "evidence": "Packet active_exploitation_notes: 'Exploitation is via a crafted file (e.g. delivered by email or web) that the user opens; opening it triggers the MSHTML platform flaw and elevates the attacker to the privileges of the current user, chaining into fuller compromise.' attack_vector repeats the crafted-file open as the trigger. affected: 'Microsoft Windows MSHTML platform — a flaw in the MSHTML component allows an attacker to elevate to the privileges of the current user when a crafted file is opened'; affected_versions: 'Windows and Windows Server editions prior to the July 2023 (2023-07-11) cumulative security update'. patch_required_reboot true, live_patch_available false, live_patch_notes: 'No live-patch mechanism for the MSHTML platform component; remediation requires installing the July 2023 Windows cumulative security update, which requires a reboot to complete.' The UK-CAF-B4 gap: hardening 'does not neutralize an MSHTML platform elevation reached by opening an attacker-supplied file; standard Windows hardening leaves the vulnerable component in-path until the July 2023 update lands.' The ISO-27001-2022-A.8.8 gap: 'for a zero-day EoP shipped and exploited on 2023-07-11, the control has nothing to act on until the update exists'.",
+        "gap_closes": [
+          "UK-CAF-B4",
+          "ISO-27001-2022-A.8.8"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "This is the case where the KEV clock and the patch clock open on the same day: the packet records Microsoft flagging CVE-2023-32046 as exploited in the wild when it shipped the fix on 2023-07-11 Patch Tuesday, and CISA adding it to KEV on 2023-07-11. No operator could have acted before the vendor, so the entire value of this control lies after that date — driving the July 2023 Windows cumulative security update across every affected Windows and Windows Server edition on the KEV clock rather than folding it into the next monthly rollup, which is the cadence the Essential Eight and the standard flaw-remediation SLA both permit. Completion is measured per host by the installed build against the fixed build for that SKU and by the restart having been taken: the packet records no live-patch mechanism for the MSHTML platform component and states the update requires a reboot to complete, so a host that installed the update and has not restarted is still executing the vulnerable MSHTML platform and must be counted as exposed. On servers that restart is the step most likely to be deferred into a maintenance window and then recorded as patched, which is the specific failure mode for this entry. Note also that poc_available is false here and it should not lower the priority — exploitation is confirmed, so the absence of a public exploit means only that the operator cannot reproduce what an attacker is already doing. Distinguishing test: for a sample of hosts reporting the July 2023 update as installed, compare uptime against the install time and confirm each has restarted since; a management-console row reading 'installed' against a host that has not rebooted is a compliance record written over a still-exploitable component. Precondition: this control compresses only the post-disclosure half of the exposure. The packet describes a flaw already being exploited on the day the fix shipped, so no remediation SLA — this one included — reaches the period before 2023-07-11; the delivery-path control is what bounds that half.",
+        "evidence": "Packet: cisa_kev true, kev_date 2023-07-11, active_exploitation confirmed, poc_available false, rwep_score 47 against cvss 7.8. active_exploitation_notes: 'Microsoft flagged CVE-2023-32046 as exploited in the wild when it shipped the fix on 2023-07-11 Patch Tuesday... No public PoC has been released. Added to KEV 2023-07-11.' patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes: 'No live-patch mechanism for the MSHTML platform component; remediation requires installing the July 2023 Windows cumulative security update, which requires a reboot to complete.' The AU-Essential-8-Patch gap: 'Essential Eight patch-OS timelines allow up to a month for such updates, but this was an exploited-in-the-wild zero-day on release day.' The NIST-800-53-SI-2 gap: 'because CVE-2023-32046 was a zero-day already exploited on the 2023-07-11 patch-release date, any SI-2 remediation window at all left an exposure the vendor could not have pre-empted.' The NIS2-Art21-patch-management gap: patch measures 'cannot compress the interval between weaponization and the July 2023 fix'.",
+        "gap_closes": [
+          "AU-Essential-8-Patch",
+          "NIS2-Art21-patch-management",
+          "NIST-800-53-SI-2"
+        ]
+      }
+    ]
   },
   "CVE-2023-32049": {
     "name": "Microsoft Windows Defender SmartScreen Security Feature Bypass Vulnerability",
@@ -59873,7 +60758,30 @@
         "adequate": false,
         "gap": "A.8.8 technical vulnerability management presumes a fix can be scheduled and applied, but for this DSP-driver OOB write on Samsung devices the fix availability depends on OEM SMR rollout, so vulnerability-management SLAs cannot guarantee remediation of the kernel escalation path."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-126",
+        "name": "MOBILE-OS-MINIMUM-PATCH-LEVEL-ENFORCEMENT",
+        "description": "The packet puts this flaw in Samsung's DSP kernel driver and puts remediation in the Samsung Mobile security maintenance release SMR Mar-2021 Release 1 or later — a build whose delivery the operator does not control, since it reaches a handset only through the OEM/carrier update channel. That is why every cited gap here is a patch-SLA gap: an estate can be fully compliant with its own patch policy and still be holding Samsung handsets running the vulnerable driver. Bound to this product, the control means the Samsung security-patch level functions as an access condition — mail, VPN and document access denied to any enrolled Samsung handset reporting a patch level below SMR Mar-2021 Release 1 — rather than as a row on a compliance report that stays red while the handset keeps its access. Completion is measured on the level the device is actually running: the packet records no live-patch mechanism for the DSP driver and an update that reboots the device, so a handset that has taken the SMR package but has not restarted onto it is still executing the vulnerable driver and counts as exposed. Scope to what the packet names — Samsung mobile devices prior to SMR Mar-2021 Release 1 — and widen to another vendor's handsets only where a verified source identifies a device carrying the same driver; the packet supplies no such mapping. Distinguishing test: enrol a Samsung handset pinned below SMR Mar-2021 Release 1 and confirm the policy actually denies it the protected resources, rather than confirming only that the stale patch level appears on a dashboard. Precondition, and it is the half most often over-claimed: withholding access bounds what a handset stuck below the fix can reach, it does not remove the out-of-bounds write. The packet's attack path is a local, already-privileged process issuing crafted requests to the driver, so the escalation happens entirely on the device — access gating neither prevents it nor evicts code already resident, and a handset suspected of running attacker code belongs on the incident path rather than the patch-level path. The gate also reaches only enrolled devices; an unenrolled or personally-owned Samsung handset touching organizational mail sits outside it entirely. And for a model or carrier variant the update channel never delivers an SMR build to, the packet records no remediation path at all — those handsets are replacement items on a dated schedule, not indefinite exception rows.",
+        "evidence": "The packet records patch_available true, live_patch_available false, patch_required_reboot true, and live_patch_notes stating that remediation requires installing the Samsung Mobile security maintenance release (SMR Mar-2021 Release 1 or later), which reboots the device; affected_versions is 'Samsung mobile devices prior to SMR Mar-2021 Release 1'. The NIS2-Art21-patch-management gap states that MDM update policies could not compel these handsets to update; the AU-Essential-8-Patch gap states the March 2021 fix was not universally deployable within any defined SLA because Samsung mobile firmware patching is gated by OEM/carrier delivery; the ISO-27001-2022-A.8.8 gap states A.8.8 presumes a fix can be scheduled and applied while here fix availability depends on OEM SMR rollout. CISA KEV listed 2023-06-29 with active_exploitation confirmed; RWEP 47, CVSS 6.7, poc_available false. The attack_vector records a local, already-privileged process issuing crafted requests to the DSP driver to corrupt kernel memory and escalate privileges.",
+        "gap_closes": [
+          "AU-Essential-8-Patch",
+          "ISO-27001-2022-A.8.8",
+          "NIS2-Art21-patch-management"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-056",
+        "name": "MOBILE-ENDPOINT-MDM-ENFORCED-KEV-SLA",
+        "description": "This is the delivery half of the same problem. The moment the OEM/carrier channel makes a build at or above SMR Mar-2021 Release 1 available for a given Samsung model variant, the management channel drives it on the KEV clock that opened 2023-06-29 rather than leaving it to whenever the handset's user acts on an update prompt, and deferral of the restart is disallowed by policy rather than left to the user. The restart is the load-bearing step and the one most often deferred: the packet records no live-patch mechanism for the DSP driver and an update that reboots the device, so a handset that has downloaded the SMR package and not restarted is still running the vulnerable driver, and a fleet report counting it as updated has recorded the exposure rather than removed it. Enforcement must therefore read the patch level the handset reports after restart, not the deployment state in the management console. The system-security gap on this entry is what makes this the whole of the remediation rather than one control among several: the packet states that no user-space hardening constrains a flaw inside the kernel-mode DSP driver and that only the Samsung SMR patch removes the out-of-bounds memory access — there is no configuration change, no permission tightening and no on-device setting that narrows this path, so getting the build installed and restarted is the only thing that closes it. Precondition: the management channel can only drive a build the OEM or carrier has actually released for that model variant. Where none has been released the SLA has nothing to enforce and the exposure stays open — that is the case the patch-level access condition has to cover instead, and treating the SLA as satisfied because no update was offered would mark an exposed handset compliant. It also assumes the handset is enrolled; devices outside enrolment are invisible to it.",
+        "evidence": "The packet records CISA KEV listing 2023-06-29 with active_exploitation confirmed, patch_available true, patch_required_reboot true, and live_patch_available false, with live_patch_notes recording no live-patch mechanism for the Samsung DSP kernel driver and remediation requiring the Samsung Mobile security maintenance release SMR Mar-2021 Release 1 or later, which reboots the device. The UK-CAF-B4 gap states that no user-space hardening constrains a flaw inside the kernel-mode DSP driver and that only the Samsung SMR patch removes the out-of-bounds memory access exploited as an LPE. The NIST-800-53-SI-2 gap states that SI-2 assumes timely vendor patch uptake but the SMR Mar-2021 fix reaches devices only through carrier/OEM update pipelines with long tails, leaving devices that never received it exposed long after the 2023-06-29 KEV listing.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "UK-CAF-B4"
+        ]
+      }
+    ]
   },
   "CVE-2023-32434": {
     "name": "Apple Multiple Products Integer Overflow Vulnerability",
@@ -62428,7 +63336,29 @@
         "adequate": false,
         "gap": "A.8.8 technical vulnerability management cannot enumerate SOHO routers outside the asset inventory, so the CWE-77 root command injection on the Archer AX21 is an untracked, actively-exploited exposure."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-030",
+        "name": "PERIMETER-DEVICE-ZERODAY-SLA-TIER",
+        "description": "The TP-Link Archer AX21 (AX1800) is the edge gateway for whatever network sits behind it, and the packet's defect is a pre-auth root remote code execution on that gateway: the country parameter of the write operation on /cgi-bin/luci;stok=/locale is passed to popen() without sanitization, so one unauthenticated POST executes commands as root on the device that is the trust boundary. A remediation tier measured in the weeks a general patch SLA allows does not fit that shape, and the packet says why in its own numbers — confirmed mass exploitation by Mirai variants, Condi and AndroxGh0st recruiting the router as root, a public proof of concept, and EPSS around 0.99999. For this device the control means a distinct tier: firmware 1.1.4 Build 20230219 or later deployed on the clock that opened with the 2023-05-01 KEV listing and its 2023-05-22 due date, or the vulnerable interface isolated until it is. Completion is measured per unit on the firmware version the router reports after it comes back up — live_patch_available is false and the packet records that installing 1.1.4 Build 20230219 reboots the device, so a unit that has taken the image but not restarted onto it is still executing the popen() sink and counts as exposed. Scope from what the packet's affected and affected_versions name: Archer AX21 (AX1800) below firmware 1.1.4 Build 20230219; widen only where a verified source identifies another model carrying the same vulnerable handler. Precondition on the isolation alternative, which is where this control is most often over-claimed: the vulnerable parameter sits on the router's web administration surface, so disabling WAN-side administration bounds who can reach it from the internet — but the packet records exploitation over the adjacent network as well as through an exposed web interface, and every client on the network this router exists to serve reaches that surface from the inside. For a unit serving a general user or household network there is no segment that removes the path, only isolation of that network from anything that matters, so isolation is a holding measure for the window before the firmware lands and not a closure. That is also why the enterprise-side expression of this tier is a reachability and firmware-version question asked of remote-work gateways, not a ticket that closes when a central console reports the push.",
+        "evidence": "Packet: CWE-77, vector states the country parameter of the write operation on the /cgi-bin/luci;stok=/locale endpoint 'was not sanitized before being used in a call to popen(), allowing an unauthenticated attacker to inject commands, which would be run as root, with a simple POST request'. affected_versions: TP-Link Archer AX21 (AX1800) firmware < 1.1.4 Build 20230219. cisa_kev true, kev_date 2023-05-01 with due 2023-05-22; active_exploitation confirmed, active_exploitation_notes record 'mass exploitation by multiple botnets (Mirai variants, Condi, AndroxGh0st) that recruit the router as root; EPSS ~0.99999' and that 'Exploitation over the adjacent/management network or an exposed web interface begins within days of PoC availability'. poc_available true, CVSS 8.8, RWEP 76. patch_available true, patch_required_reboot true, live_patch_available false, live_patch_notes 'No live-patch mechanism for the router firmware; remediation requires installing firmware 1.1.4 Build 20230219 or later, which reboots the device.' The AU-Essential-8-Patch gap records that the internet-facing patch SLA 'cannot be met on unmanaged home routers'; the UK-CAF-B4 gap records that the hardening baseline 'leaves a preauth root-RCE path open'.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "AU-Essential-8-Patch",
+          "UK-CAF-B4"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-032",
+        "name": "PERIMETER-COMPROMISE-REBUILD-NOT-PATCH",
+        "description": "The outcome the packet records for the Archer AX21 is command execution as root, and confirmed recruitment of the device into botnets — Mirai variants, Condi and AndroxGh0st — at an EPSS of roughly 0.99999. That combination is what makes patch-in-place the wrong default here. Installing firmware 1.1.4 Build 20230219 closes the popen() injection and reboots the unit, but the update is applied on top of a device an attacker held as root: the stored configuration and the administrative credential are carried across the upgrade, and root command execution was sufficient to alter either. For this router the control means a unit whose administration surface was reachable by an untrusted client or from the internet during the exposure window is handled as an incident case rather than a patch ticket — after the firmware update, reset it to factory defaults and rebuild the configuration from a known-good baseline instead of restoring the saved configuration file, set a new administrative credential, and rotate credentials and keys belonging to the network behind it. Preconditions and limits, stated because this control is the half that is easy to overstate: it does not close the injection — the firmware level and the reboot do that, and a rebuilt unit still running a pre-1.1.4 image is fully exploitable again on the next request. It applies to units that were exposed; a unit whose administration surface was never reachable by an untrusted party during the window is an ordinary patch item, and the packet gives no basis for treating every Archer AX21 as compromised. And a factory reset recovers nothing already exfiltrated and closes no session already intercepted, which is why the credential rotation rather than the reset is the load-bearing step. Scope to the model the packet names, Archer AX21 (AX1800) below firmware 1.1.4 Build 20230219, and widen only where a verified source identifies another model carrying the same handler.",
+        "evidence": "Packet: attack_vector 'An unauthenticated attacker sends a POST to /cgi-bin/luci;stok=/locale (country write operation); the country parameter is passed to popen() unsanitized, executing injected commands as root.' active_exploitation confirmed; active_exploitation_notes record 'Confirmed mass exploitation by multiple botnets (Mirai variants, Condi, AndroxGh0st) that recruit the router as root; EPSS ~0.99999 reflects near-certain ongoing exploitation.' poc_available true. patch_available true with live_patch_available false and live_patch_notes 'remediation requires installing firmware 1.1.4 Build 20230219 or later, which reboots the device'. The NIST-800-53-SI-2 gap records that the injection 'stayed exploitable across the fleet during the botnet surge that followed the 2023-05-01 KEV listing' — the population this control addresses. RWEP 76, CVSS 8.8, kev_date 2023-05-01.",
+        "gap_closes": [
+          "NIST-800-53-SI-2"
+        ]
+      }
+    ]
   },
   "CVE-2021-45046": {
     "name": "Apache Log4j2 Deserialization of Untrusted Data Vulnerability",
@@ -63700,7 +64630,21 @@
         "adequate": false,
         "gap": "Technical vulnerability management must prioritize local-privilege-escalation CVEs used by ransomware; scoring this 7.8 LPE below internet-facing RCEs leaves the SYSTEM-escalation path open across the endpoint fleet."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-145",
+        "name": "ACTIVELY-EXPLOITED-OS-LPE-REMEDIATION-WINDOW-ENFORCEMENT",
+        "description": "The packet places this in the Windows UAC certificate/consent dialog, which fails to enforce user privileges when a standard user views a publisher certificate, and the path it documents is entirely user-interface: trigger a consent dialog, open the publisher-certificate details, follow the certificate hyperlink to launch a browser as NT AUTHORITY\\\\SYSTEM, and spawn a SYSTEM shell from that browser, escalating without any exploit code. For this CVE the control means the November 2019 (or later) Windows cumulative security update is driven across the whole affected population the packet names — Windows 7, 8.1, 10 and Windows Server 2008, 2012, 2016 and 2019 — on the clock that opened with the 2023-04-07 KEV listing rather than folded into an ordinary monthly rollup, with completion measured by each host's installed build against the fixed build for its SKU rather than by 'approved' or 'downloaded' in the management console. The packet records no Microsoft hotpatch for this class and a remediation that requires that cumulative update and a reboot, so a host that has taken the update but has not restarted still presents the vulnerable dialog and must be counted as exposed. The second half of the control is the load-bearing one here: the escalation runs from an ordinary standard-user session through a dialog the operating system itself presents, so tightening account privilege does not contain it — which is exactly why the least-privilege gap cited on this entry can pass its attestation while the flaw stays fully exploitable, and why an endpoint baseline that treats UAC as the boundary is measuring something the packet says does not hold. Priority follows the packet rather than the CVSS band: a public PoC, confirmed exploitation, and a KEV ransomware:Known flag with documented post-compromise use to reach SYSTEM before payload deployment make this a containment step inside a ransomware chain, not a routine 7.8 endpoint item. Because the flaw requires local interactive access and is not remotely exploitable on its own, the population to enumerate first is hosts where non-administrative users log on interactively, since there the precondition the escalation needs is the normal operating state rather than an anomaly.",
+        "evidence": "Packet fields for this entry: CWE-269; CVSS 7.8; RWEP 68; poc_available true; active_exploitation confirmed; cisa_kev true with kev_date 2023-04-07. active_exploitation_notes: 'Added to CISA KEV on 2023-04-07 and flagged ransomware:Known. Used post-compromise by ransomware operators to escalate from a low-privileged foothold to SYSTEM before deploying payloads. Requires local interactive access; not remotely exploitable on its own.' patch_available true; patch_required_reboot true; live_patch_available false; live_patch_notes: 'No Microsoft hotpatch for this class at the time; remediation requires the November 2019 (or later) Windows cumulative security update and a reboot.' affected_versions: 'Windows 7 / 8.1 / 10 and Windows Server 2008/2012/2016/2019 without the November 2019 cumulative update'. attack_vector describes the standard user following the certificate hyperlink to launch a browser as NT AUTHORITY\\\\SYSTEM and spawning a SYSTEM-level shell 'without any exploit code'. The NIST-800-53-AC-6 gap records that least-privilege enforcement 'assumes the UAC boundary holds'; the UK-CAF-B4 gap records that Microsoft treats UAC as not a security boundary; the ISO-27001-2022-A.8.8 gap records that scoring this 7.8 LPE below internet-facing RCEs leaves the SYSTEM-escalation path open across the endpoint fleet.",
+        "gap_closes": [
+          "NIST-800-53-AC-6",
+          "AU-Essential-8-Patch",
+          "NIS2-Art21-patch-management",
+          "ISO-27001-2022-A.8.8"
+        ]
+      }
+    ]
   },
   "CVE-2023-26083": {
     "name": "Arm Mali GPU Kernel Driver Information Disclosure Vulnerability",
@@ -63847,7 +64791,29 @@
         "adequate": false,
         "gap": "A.8.8 technical vulnerability management had a fix available (Patch 24), but the ongoing TA473 campaign shows the real exposure was the gap between the released patch and its application on internet-facing webmail."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "This Zimbra entry is a case where CVSS-keyed and KEV-keyed prioritization give opposite answers. The base score is 6.1 — a reflected XSS, the shape of finding that lands in a quarterly web-application queue — while the packet records Winter Vivern / TA473 using it across 2022 and 2023 against European government and military Zimbra webmail to steal credentials and mailbox contents, with CISA listing it on 2023-04-03. Bound to this product, the control means the clock on an internet-facing Zimbra Collaboration Suite instance starts at the KEV listing or patch availability, whichever is later, and stops when the mailbox service is actually running 9.0.0 Patch 24 or later — not when a change ticket is raised or a package is staged. The packet is precise about what running means here and it is easy to get wrong in both directions: patch_required_reboot is false, so no host reboot is being coordinated, but the recorded remediation is a mailbox-service restart, so an instance where the package was applied and the mailbox service never restarted is still reflecting the parameter unsanitized and is not remediated. Scope to what the packet names — Zimbra Collaboration Suite 9.0 prior to 9.0.0 Patch 24 — rather than to webmail generally. The two patch-window gaps on this entry say the same thing from different sides: the fix existed and the exposure was the interval before it was applied on internet-facing webmail. The application-hardening gap matters here as an exclusion — it rules out the control a framework would otherwise reach for, since browser and webmail hardening does not stop script the server itself reflects from the trusted origin, which is why the response clock rather than endpoint hardening is the control that carries this entry. Precondition: nothing available to the operator short of Patch 24 removes the unsanitized reflection, so this SLA governs how fast the estate gets there and offers nothing during the window before it does. And because exploitation is confirmed and the payload runs inside the victim's own authenticated session, an instance that was internet-reachable while unpatched is not closed by the upgrade — the packet records credential and mailbox theft as the outcome, so session invalidation, credential rotation for users who could have followed such a link, and a review of what those mailboxes held belong inside remediation rather than being deferred to a separate incident question.",
+        "evidence": "The packet records CVSS 6.1 against RWEP 61, CISA KEV 2023-04-03, active_exploitation confirmed and poc_available true; active_exploitation_notes record Winter Vivern / TA473 using the reflected XSS through 2022-2023 against unpatched Zimbra webmail at European government and military organizations, sending targeted emails whose links ran JavaScript to steal webmail credentials and messages. patch_available true, patch_required_reboot false, live_patch_available false, with live_patch_notes recording remediation as updating to Zimbra Collaboration Suite 9.0.0 Patch 24 or later — a mailbox-service restart, not a host reboot; affected_versions is Zimbra Collaboration Suite 9.0 prior to 9.0.0 Patch 24. The AU-Essential-8-App-Hardening gap states application hardening does not stop server-reflected XSS delivered from the trusted webmail origin and that only the Zimbra patch removes the unsanitized reflection; the ISO-27001-2022-A.8.8 gap states the real exposure was the gap between the released patch and its application on internet-facing webmail; the NIS2-Art21-patch-management gap states the XSS was exploited against European government Zimbra instances that stayed unpatched after 9.0.0 Patch 24 shipped.",
+        "gap_closes": [
+          "AU-Essential-8-App-Hardening",
+          "ISO-27001-2022-A.8.8",
+          "NIS2-Art21-patch-management"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-040",
+        "name": "OWA-PER-REQUEST-SIEM-INGESTION",
+        "description": "This control's name comes from Exchange but its subject is webmail per-request telemetry, and the Zimbra campaign in this packet is the same shape it was written against. The packet describes a logged-in user following a link to their own Zimbra /public/launchNewWindow.jsp, the server reflecting the script into the trusted origin, and attacker JavaScript then reading and exfiltrating mail inside that user's existing session. None of that generates an authentication event — the user logged in normally, and everything afterwards is that user's own session issuing ordinary webmail requests — so an estate whose Zimbra logging is authentication-only holds no record of the intrusion at all. The requirement is that the Zimbra webmail tier forward per-request access logs, not just authentication events, to a collector off the mail server, with retention spanning a campaign the packet records as running across 2022 and 2023. What to key on is what the packet actually describes: requests to /public/launchNewWindow.jsp carrying script in their parameters, paired with the mailbox reads and message retrieval that follow in the same session from the same source. Both halves are needed. A script-shaped parameter on that endpoint alone may be a scanner probing it, and mailbox reads alone are what webmail does all day; it is the pairing inside one session that matches the path the packet documents. Note what will not see this: the request arrives over a valid session and no login anomaly, no malware artifact and no server-side process change accompanies it, so authentication-event alerting and host anti-malware have nothing to match, and a rule written against failed logins or unusual sign-in geography would miss an attempt behaving exactly as the packet describes. Precondition: this is detection, not prevention — it does not stop the script executing and does not recover mail already exfiltrated. It also depends on the telemetry having been collected and shipped off the mail server before the campaign arrived; a rule authored afterwards against logs nobody retained produces nothing. It bounds the window to alert-and-response time during the interval before 9.0.0 Patch 24 and its mailbox-service restart land, and complements reaching that build rather than substituting for it.",
+        "evidence": "The packet's attack_vector records an attacker sending a logged-in webmail user a link to their own Zimbra /public/launchNewWindow.jsp with a script payload in the parameters, the server reflecting it unsanitized into the trusted origin, and the attacker's JavaScript stealing credentials and mailbox contents; the affected field places the unsanitized reflection at /public/launchNewWindow.jsp and describes the result as unauthenticated reflected XSS in the webmail origin. active_exploitation_notes record TA473 running this against European government and military organizations through 2022-2023 to steal webmail credentials and messages, with poc_available true and CISA KEV listing 2023-04-03. The ISO-27001-2022-A.8.8 gap states the real exposure was the gap between the released patch and its application on internet-facing webmail. live_patch_notes record remediation as Zimbra Collaboration Suite 9.0.0 Patch 24 or later with a mailbox-service restart.",
+        "gap_closes": [
+          "ISO-27001-2022-A.8.8"
+        ]
+      }
+    ]
   },
   "CVE-2013-3163": {
     "name": "Microsoft Internet Explorer Memory Corruption Vulnerability",
@@ -64504,7 +65470,28 @@
         "adequate": false,
         "gap": "A.8.8 technical-vulnerability management often leaves aging ColdFusion deployments off the actively-tracked inventory, so this known-exploited deserialization RCE could sit unpatched on a public server past the KEV due date."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "For Adobe ColdFusion the two clocks a normal remediation process keeps apart collapsed onto one day: the packet records CISA adding this to KEV on 2023-03-15, the same day Adobe shipped the fix, and notes that this indicates exploitation was already underway. A response measured in hours from that day is the only patch-side clock that had any window at all, and it is precisely what the cited routine cadences do not carry. Bound to this product, completion means the fixed update is the code actually running: ColdFusion 2018 Update 16 for instances at or below 2018 Update 15, and ColdFusion 2021 Update 6 for instances at or below 2021 Update 5, with the ColdFusion service restarted afterwards. Read patch_required_reboot carefully here — it is false, which means no host reboot is needed, not that the fix is live on install. The packet's own remediation note requires restarting the ColdFusion service, and live_patch_available is false, so there is no path that avoids that restart; an instance that installed the update and left the service running is still executing the pre-fix code and must be counted exposed until the restart. Measure per ColdFusion installation rather than per site: a host serving several applications through one ColdFusion instance is one remediation, and an application inventory that tracks web properties rather than ColdFusion installations will miss instances on both the 2018 and 2021 tracks, which update independently. Scope from what the packet's affected and affected_versions name — ColdFusion 2018 at or below Update 15 and ColdFusion 2021 at or below Update 5 — and widen only where a verified source identifies another product carrying the same code path. Residual to state plainly rather than let the SLA imply otherwise: this compresses the post-patch window only. The packet records exploitation preceding the fix, so even a same-day clock from 2023-03-15 covers nothing before it, and an internet-facing instance that was reachable before that date is a compromise-assessment case rather than a clean patch record.",
+        "evidence": "Packet: CWE-284, vector 'Adobe ColdFusion versions 2018 Update 15 (and earlier) and 2021 Update 5 (and earlier) are affected by an Improper Access Control vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue does not require user interaction.' affected_versions: 'Adobe ColdFusion 2018 <= Update 15 (fixed in Update 16)', 'Adobe ColdFusion 2021 <= Update 5 (fixed in Update 6)'. cisa_kev true, kev_date 2023-03-15; active_exploitation_notes state the entry was 'Added to CISA KEV 2023-03-15, the same day as the Adobe fix, indicating exploitation was already underway.' patch_available true, patch_required_reboot false, live_patch_available false, live_patch_notes 'No live-patch mechanism; remediation requires applying Adobe ColdFusion 2018 Update 16 or 2021 Update 6 and restarting the ColdFusion service.' CVSS 8.6, RWEP 72, poc_available true. The NIST-800-53-SI-2 gap records that a routine cadence 'was too slow' and that 'any multi-week patch SLA left an internet-facing ColdFusion server open to unauthenticated RCE'; the NIS2-Art21-patch-management gap records that routine patch management 'does not force emergency patching of legacy web-application servers... warranting out-of-band action the routine process omits'.",
+        "gap_closes": [
+          "NIST-800-53-SI-2",
+          "NIS2-Art21-patch-management"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-032",
+        "name": "PERIMETER-COMPROMISE-REBUILD-NOT-PATCH",
+        "description": "The packet records that CISA documented a federal agency's public-facing ColdFusion servers compromised through this flaw, and it names both halves of the primitive: unauthenticated arbitrary code execution and arbitrary file read in the ColdFusion service context. Both halves determine what remediation has to mean. The execution half is what leaves a persistent artifact written through a path the application legitimately exposes; the read half hands over datasource credentials, configuration and any key material the ColdFusion service account can read, and nothing about applying an update reverses a read. Applying ColdFusion 2018 Update 16 or 2021 Update 6 and restarting the service closes the improper-access-control path to the deserialization sink, and removes nothing already written through it. So for an internet-facing ColdFusion instance that was reachable during the pre-patch window — which on this entry's own timeline is a broad population, since the KEV listing and the vendor fix landed together on 2023-03-15 with exploitation already underway — the default response is a compromise assessment and rebuild rather than patch-in-place: inventory the files under the web root and the ColdFusion installation against what a deployment accounts for, rebuild from a known-good image where one exists, and rotate every credential the service account could read, including datasource passwords. Preconditions and limits. This does not close the flaw; the update plus the service restart does, and the packet records no live-patch path, so an instance assessed but left on 2018 Update 15 or 2021 Update 5 is exploitable again immediately. It applies to instances that were internet-facing or otherwise reachable by an untrusted caller during the window, not to every ColdFusion installation in the estate. And the assessment has to be a file-inventory-against-deployment exercise rather than a scan: an artifact written through a legitimate application path is bespoke, so signature-based anti-malware and authentication logging have nothing to match, and an authentication log is silent by construction for a flaw whose whole point is that no authentication took place.",
+        "evidence": "Packet: affected records 'an improper-access-control flaw permits deserialization of untrusted data, allowing unauthenticated arbitrary code execution and arbitrary file read in the ColdFusion service context'; attack_vector repeats the unauthenticated deserialization path 'yielding arbitrary code execution and file read in the service context'. active_exploitation confirmed; active_exploitation_notes state 'CISA later documented (in a June 2023 advisory) that a federal agency's public-facing ColdFusion servers were compromised via this flaw' and that the KEV listing on 2023-03-15 landed the same day as the Adobe fix, indicating exploitation was already underway. poc_available true, CVSS 8.6, RWEP 72. patch_available true, live_patch_available false, live_patch_notes 'remediation requires applying Adobe ColdFusion 2018 Update 16 or 2021 Update 6 and restarting the ColdFusion service'. The AU-Essential-8-Patch gap records that the 48-hour window 'was already breached on release: exploitation preceded the fix, so patch-timeliness alone could not protect exposed ColdFusion servers by the 2023-03-15 KEV date.'",
+        "gap_closes": [
+          "AU-Essential-8-Patch"
+        ]
+      }
+    ]
   },
   "CVE-2023-23397": {
     "name": "Microsoft Office Outlook Privilege Escalation Vulnerability",
@@ -64565,7 +65552,30 @@
         "adequate": false,
         "gap": "A.8.22 network segregation would have isolated user endpoints so a coerced SMB connection could not exit to an attacker server, but flat networks allow the outbound authentication; without segregation and SMB egress control, A.8.8 patching alone left the forced-auth leak reachable on unpatched clients."
       }
-    }
+    },
+    "new_control_requirements": [
+      {
+        "id": "NEW-CTRL-001",
+        "name": "CISA-KEV-RESPONSE-SLA",
+        "description": "For this CVE the mitigation the clock runs against is not one artifact. The KEV listing and the Microsoft March 2023 Outlook security update arrived together, so the patch arm is available from hour zero — but the packet's remediation note pairs that update with three named mitigations (block outbound TCP 445, add users to the Protected Users group, enforce SMB signing), and this control is what makes those the deployable alternative for any client that cannot take the update inside the clock. Scope is the Outlook for Windows estate the packet's affected_versions name — Microsoft 365 Apps and Office 2013, 2016, 2019 and LTSC 2021 below the March 2023 build — not Microsoft 365 Apps alone, since an estate standardised on a perpetual Office release is affected at its own pre-update build. Completion must be measured on Outlook itself: patch_required_reboot false means no machine reboot, and the packet states the Office update requires restarting Outlook, so a workstation that installed it while Outlook stayed open is still running the vulnerable reminder-processing path and is not remediated. Preconditions on the compensating half, which is where this gets recorded as done while the path stays open: blocking outbound TCP 445 stops the coerced authentication reaching an SMB server on the internet, but the UNC path in the reminder can name any destination the client can route to, so an attacker with an interior foothold still collects the hash — that internal case is the segregation problem, not something the egress rule covers. Protected Users membership removes NTLM only for the accounts placed in it, so the general user population keeps leaking Net-NTLMv2 until the update lands or SMB signing is enforced on the services that would accept the relay. And none of the three, nor the update, recovers a hash captured before they were in place.",
+        "evidence": "Packet: cisa_kev true with kev_date 2023-03-14, active_exploitation confirmed, CVSS 9.8, RWEP 65, poc_available true. patch_available true, patch_required_reboot false, live_patch_available false, with live_patch_notes stating 'No live-patch mechanism; remediation requires the Microsoft March 2023 Outlook security update, plus recommended mitigations (block outbound TCP 445, add users to Protected Users group, enforce SMB signing). Applying the Office update requires restarting Outlook but not the host.' affected_versions: 'Microsoft Outlook for Windows (Microsoft 365 Apps, Office 2013/2016/2019/LTSC 2021) before the March 2023 security update'. attack_vector: a crafted reminder with a UNC path in PidLidReminderFileParameter forces the client to send the user's Net-NTLMv2 hash to an attacker SMB server with no interaction. The NIST-800-53-SC-7 gap records that blocking outbound SMB (TCP 445) is Microsoft's primary mitigation but that default enterprise egress rules rarely deny 445; the UK-CAF-B2 gap records that B2 cannot distinguish the relayed session from the legitimate user without disabling NTLM or enforcing MFA/signing.",
+        "gap_closes": [
+          "AU-Essential-8-Patch",
+          "NIST-800-53-SC-7",
+          "NIS2-Art21-network-security",
+          "UK-CAF-B2"
+        ]
+      },
+      {
+        "id": "NEW-CTRL-043",
+        "name": "NATION-STATE-INITIAL-ACCESS-IR-ESCALATION",
+        "description": "The packet's attribution is the trigger this control names by actor: confirmed in-the-wild zero-day exploitation from as early as April 2022 by APT28 (Fancy Bear / Forest Blizzard) against government, military, energy and transportation targets in Europe — roughly eleven months of collection before the KEV listing on 2023-03-14. Bound to Outlook, that changes what remediation means: the flaw's output is the user's Net-NTLMv2 hash delivered to an attacker-controlled SMB server with no interaction and then relayed to impersonate the victim, so what survives the March 2023 update is authentication material already taken, not a code path still open. The runbook must therefore treat a mailbox that received a message whose reminder carried a UNC path in PidLidReminderFileParameter during the exposure window as an intrusion lead rather than a patch-compliance exception: rotate credentials for the affected accounts, and hunt for authentication that arrived by relay rather than from the user's own workstation. Escalating under the nation-state path rather than a commodity-malware path is the packet's own justification — a state-aligned espionage group operating against those sectors uses a relayed session to move, so the commodity path's expectation of a malware artifact to find produces a clean result on a compromised estate. Preconditions: this is the response half and it prevents nothing — further leaks stop only when the update and the packet's named mitigations land. It also depends on mail retention covering the exposure window and on authentication telemetry that was already being collected when the relay happened; where neither survives, the honest output is that the exposure cannot be bounded, which is the finding rather than an all-clear.",
+        "evidence": "Packet: active_exploitation confirmed, with active_exploitation_notes stating exploitation in the wild as a zero-day from as early as April 2022 by the Russia-aligned APT28 (Fancy Bear / Forest Blizzard) against government, military, energy and transportation targets in Europe, CISA KEV addition 2023-03-14, and PoCs released immediately (poc_available true). attack_vector: the hash is relayed to impersonate the victim. The AU-Essential-8-Patch gap states that even the March 2023 patch does not retroactively protect credentials leaked before it; the NIS2-Art21-network-security gap states that a patch-only response around the KEV 2023-03-14 date misses the credentials already captured by APT28.",
+        "gap_closes": [
+          "AU-Essential-8-Patch"
+        ]
+      }
+    ]
   },
   "CVE-2023-24880": {
     "name": "Microsoft Windows SmartScreen Security Feature Bypass Vulnerability (CVE-2023-24880)",