CriticalOTRetailThird-party access
Europe's refrigeration incidents expose a supplier-control blind spot
Confirmed reporting. On 4 November, the Commission, ENISA and EU response partners warned of incidents affecting commercial refrigeration systems in several member states since 11 October. A new wave occurred on 1–2 November; authorities advised immediate mitigation. The joint statement does not attribute the incidents to a named vendor or common root cause.
TPRM interpretation. A remote maintenance path into physical equipment can have consequences for stock, food safety and business continuity. A facilities integrator, controller manufacturer and operations team may each own part of the risk; no single questionnaire proves a safe fallback.
Control questionCan operations isolate vendor remote access without losing safe temperature control?
Evidence to requestController inventory, firmware/support status, network exposure, third-party access logs, local override procedure, cold-chain recovery test.
Recommended actions
- Identify connected refrigeration, building-management and other OT devices in supplier-operated environments.
- Confirm exposure, restrict direct internet access and apply relevant CSIRT/vendor guidance with operational approval.
- Test safe manual operation and escalation routes between maintenance provider, operations and incident response.
CriticalCitrixManaged services
28 NetScaler flaws: demand asset-level proof, not a generic patch email
Confirmed reporting. CERT-EU's 12 November advisory says Citrix addressed 28 memory flaws in NetScaler ADC and Gateway. CVE-2026-120868 (CVSS 9.3) affects default deployments; CVE-2026-107412 (CVSS 9.5) affects configured Gateway/AAA deployments. At publication Citrix reported no exploitation and no public proof of concept was confirmed.
TPRM interpretation. The urgent third-party question is not whether a service provider claims to be patched, but which customer-facing gateways it manages, which versions and configurations are affected, and when remediation is complete.
Control questionWhich internet-facing vendor-managed gateways serve critical operations?
Evidence to requestNamed appliance IDs, build/version and configuration, vendor bulletin mapping, patch time, verification output, downtime approval.
Recommended actions
- Request NetScaler applicability and remediation evidence from each managed-network, hosting and remote-access provider.
- Prioritise internet-facing Gateway and AAA devices; request proof of corrected releases.
- Maintain incident monitoring, but do not label these November CVEs actively exploited without new evidence.
HighAIAttack automation
AI-assisted exploitation compresses the vendor response window
Confirmed reporting. CERT-EU reported on 5 November observing threat actors using the AI-powered ARTEX penetration-testing framework to automate reconnaissance and exploitation of misconfigurations, including similar activity against its constituency.
TPRM interpretation. Externally exposed assets and supplier-operated control planes may be discovered and probed faster. This is a defensive urgency signal, not proof that any particular vendor has been breached by ARTEX.
Control questionCan the supplier demonstrate continuous exposure discovery and time-to-remediate?
Evidence to requestExternal attack-surface inventory, misconfiguration scan cadence, SLA exceptions, access-monitoring and incident escalation timings.
Recommended actions
- Prioritise externally exposed supplier infrastructure and shared service entry points.
- Require measurable discovery-to-fix targets, not only annual assessments.
- Rehearse a same-day escalation for exposed misconfigurations with high business impact.
HighCRAProduct vendors
CRA reporting is live — distinguish the regulatory clock from customer notification
Confirmed reporting. The Commission confirms that since 11 September 2026 manufacturers of products with digital elements must report qualifying severe incidents and actively exploited vulnerabilities through the CRA reporting framework. Main security requirements start in December 2027.
TPRM interpretation. Purchasers should not assume a manufacturer's statutory notification automatically reaches all affected customers. Supplier incident clauses need their own reporting route, owner and severity thresholds.
Control questionWhich products and vendors are in CRA scope, and who calls us first?
Evidence to requestSupplier role/scope inventory, customer notification clauses, contact tests, product vulnerability intake workflow.
Recommended actions
- Review CRA scope for critical hardware and software vendors.
- Exercise a 24-hour internal escalation for a vendor-reported vulnerability or severe incident.
- Keep regulatory reporting obligations separate from contractual customer notice.
HighDORAConcentration
Direct CTPP oversight does not transfer your accountability
Confirmed reporting. The European Supervisory Authorities' DORA oversight model places designated critical ICT third-party providers under Lead Overseers, with investigations, recommendations and possible sanctions. The EBA expressly says oversight complements, not replaces, financial entities' risk management responsibilities.
TPRM interpretation. Even a directly overseen provider needs customer-specific dependency mapping, subcontractor visibility, resilience testing and executable exit assumptions. Designation is not a certification of safety.
Control questionCan we describe every critical business process that relies on our designated provider?
Evidence to requestRegister of Information consistency, critical service mapping, subcontracting/exit documentation, tested recovery assumptions.
Recommended actions
- Reconcile the latest ICT supplier inventory with RoI and critical function mapping.
- Test continuity for a shared critical provider and its fourth parties.
- Escalate untested exit strategies to the management body.