Full Report
Dispel announced the launch of Dispel Zero Trust Engine for OEMs, a solution purpose-built for OEMs and machine... The post Dispel Zero Trust Engine for OEMs to secure remote industrial service, standardize access, strengthen compliance appeared first on Industrial Cyber.
Analysis Summary
# Industry News: Dispel Launches Zero Trust Engine for OEMs to Secure Remote Industrial Service
## Summary
Dispel has launched the Dispel Zero Trust Engine for OEMs, a remote access platform for equipment manufacturers and machine builders that deliver remote service to their industrial customers. The product replaces the mix of VPNs, jump hosts, shared credentials, and customer-specific tools that OEMs typically accumulate, and it offers tiered deployment options for different security and regulatory needs. ABB is already using the platform under its ABB Care service offering.
## Key Details
- **Date:** October 19, 2026 (announcement; CEO blog post published the same Monday)
- **Companies Involved:** Dispel (vendor), ABB (named customer and partner)
- **Category:** Product launch, with a referenced partnership
## The Story
Dispel announced the Zero Trust Engine for OEMs, a product aimed at equipment manufacturers and machine builders who provide remote service to their customers' industrial assets. The company says the platform already supports remote service at several OEMs, including ABB, which has a global partnership with Dispel for secure remote access under ABB Care.
The launch is framed around a problem Dispel says is growing: third-party remote access is becoming a major risk in manufacturing. The announcement cites Verizon's 2026 Data Breach Investigations Report, which says 61% of manufacturing breaches involve a third party, compared with a 48% cross-industry average. It also cites a Gartner Market Guide for CPS Secure Remote Access, which describes a shift from "secure connectivity" to "secure operations."
Dispel argues that OEMs face several practical problems:
- Standing VPNs and jump hosts create always-on exposure.
- Each customer often requires a different access tool.
- Shared credentials make it hard to trace who connected.
- Manual approvals slow response when downtime is costly.
- Inconsistent logging makes incident reconstruction difficult.
- Security reviews are increasingly delaying contracts.
The product's core components include:
- **Tiered Connection Suite:** Browser Connect, Virtual Desktop, or a local application, all through one platform.
- **Disposable, session-based infrastructure:** Aims to remove persistent attack surface.
- **Session controls:** Scoped, time-bound, automatically recorded sessions, with just-in-time access and MFA enforced by default.
- **Real-time topology:** Visibility across facilities, gateways, and devices.
- **Add-on capabilities:**
- *Dispel Intelligence* provides dynamic risk scoring during sessions.
- *Dispel Identity* uses government ID and biometric verification to tie high-risk sessions to a named individual.
- *Dispel Compliance* continuously checks against NERC CIP, IEC 62443, and NIS2.
- **Deployment tiers:**
- *Foundation:* Multi-tenant, cloud-based.
- *Premium:* Single-tenant, dedicated per customer.
- *Advanced:* On-premises or hybrid, extending into customer-owned infrastructure.
- **Entry options:** Rapid-Deploy SaaS for quick pilots, or a white-labeled platform that OEMs can run as their own.
*Note: The source article is truncated, so pricing, availability details, and some deployment specifics are not included here.*
## Business Impact
### For the Companies Involved
- **Dispel** gains a productized offering aimed at a specific buyer, OEMs, and a named reference customer in ABB, which adds credibility in industrial markets.
- The white-label option could open a channel model in which OEMs resell or brand the platform, extending Dispel's reach beyond direct sales.
- **ABB** gets a standardized remote service platform for its global installed base, which it says supports faster response and more reliable digital service delivery.
### For Competitors
- Remote access vendors focused on OT, such as those offering jump-host replacements and industrial VPN alternatives, face a competitor that is packaging compliance evidence, identity verification, and multi-deployment options in one offering.
- The white-label and multi-tenant models could pressure competitors that sell only to end-user asset owners and do not address OEM operating models.
- Because the product is positioned around OEM service workflows, it may compete with in-house or customer-mandated tools more than with other security vendors.
### For Customers
- **OEM customers (asset owners)** may benefit from session recording, named-user identity verification, and faster compliance evidence. The announcement claims this could shorten security reviews from weeks to same-day answers, though that claim is vendor-stated.
- **Plant operators and utilities** may see fewer incompatible vendor tools and more consistent access controls, though they will still need to validate the platform against their own requirements.
- Biometric identity verification may raise privacy and HR questions that customers and OEMs will need to address with legal and labor-relations teams.
### For the Market
- The announcement reflects a broader move toward purpose-built remote access for OT and cyber-physical systems, as opposed to general IT remote access tools.
- It highlights supply-chain and third-party access as a central manufacturing risk, which could push more OEMs and asset owners to require zero trust remote access in contracts.
- Regulatory alignment with NERC CIP, IEC 62443, and NIS2 suggests that compliance-driven demand will be a major factor in adoption.
## Technical Implications
- **Eliminating standing access:** Session-based, disposable infrastructure is meant to remove always-on VPN paths, which reduces the attack surface that attackers can map. This is a core zero trust principle applied to OT remote access.
- **Identity and attribution:** Named-user verification, combined with recording, addresses the shared-credential problem and supports forensic reconstruction.
- **Continuous risk assessment:** Dynamic risk scoring during sessions, not just at login, is a step toward adaptive access control. Its effectiveness will depend on the signals used and how they are tuned for OT environments.
- **Deployment flexibility:** The Foundation, Premium, and Advanced tiers reflect different segmentation and data-residency needs, including on-premises deployment for environments with strict operational requirements.
- **Integration questions:** Real-world value will depend on how the platform works with existing OT networks, legacy protocols, safety systems, and customer-owned gateways. The article does not provide details on these integrations.
## Strategic Analysis
- **Market Positioning:** Dispel is positioning itself as an OEM-focused platform in the OT secure remote access category, with ABB as a flagship reference. The emphasis on white-labeling suggests an effort to become infrastructure for OEM service businesses, not just a tool used by them.
- **Competitive Advantage:** Combining access control, session recording, identity verification, risk scoring, and compliance evaluation in one platform could reduce the number of tools OEMs need. The multi-tier deployment model may also help with varied customer requirements.
- **Challenges:**
- Many customers already require their own remote access tools, so OEMs may still need to support multiple systems.
- Biometric identity verification may create privacy, regulatory, and adoption barriers in some regions.
- Vendor claims about faster compliance and contract approvals are not independently verified in the article.
- Adoption by OEMs will depend on migration effort from existing VPN and jump-host setups.
- Competitors in OT remote access and identity are likely to respond with similar bundles.
## Industry Reactions
- **Vendor and partner commentary:**
- Charles Bennett (ABB) said the partnership supports faster service response, real-time support, and a secure foundation for remote digital services.
- Ben Burke (Dispel) said OEMs should not need "a patchwork of tools" to scale service and meet SLAs.
- **Third-party references:** The article cites Verizon's 2026 DBIR and a Gartner Market Guide. These are supporting context, not endorsements of the product.
- **Independent analyst opinion:** None is included in the available text.
- **Market response:** Not reported in the available text.
## Future Outlook
- **Predictions and expectations:**
- Expect more OEMs to ask for standardized, compliance-ready remote access in procurement and contract terms.
- Expect OT remote access vendors to add more identity, compliance, and OEM-focused features.
- The white-label model may encourage other platform announcements from OEMs or service vendors.
- **What to watch for:**
- Additional OEM customers beyond ABB and whether they publicly name the platform.
- Independent validation of the claimed security and compliance outcomes.
- Pricing and availability details, which were not included in the available text.
- How the platform handles integration with legacy OT, air-gapped sites, and customer-mandated tools.
- Regulatory or privacy scrutiny of biometric identity verification.
## For Security Professionals
The announcement addresses a real and common weakness: third-party remote access to industrial equipment. Security teams should consider the following:
- **Inventory your remote access paths.** Many OT environments have undocumented VPNs, jump hosts, and vendor-owned tools. Identifying them is a useful first step regardless of which product is chosen.
- **Evaluate session-based access.** Ephemeral sessions, time limits, and default MFA are reasonable controls to look for in any OT remote access solution.
- **Require attribution.** Shared accounts should be eliminated where possible. Named-user access and reliable session recording improve incident response and accountability.
- **Check compliance mapping.** If you operate under NERC CIP, IEC 62443, or NIS2, verify any vendor's compliance claims against your own audit requirements.
- **Pressure-test vendor claims.** Ask for independent evidence, architecture reviews, and references from similar environments. Vendor statements about faster contract approvals and reduced risk should be validated.
- **Plan for vendor access as a supply-chain risk.** Whether or not you adopt this platform, third-party access should be governed by policy, monitored, and included in your risk assessments.