Intelligence for systems that move the physical world.
Notified-body provisions began applying in June 2026 and vulnerability-reporting provisions follow in September, while the regulation's general application remains December 2027.
The June 2026 announcement would combine OT threat detection, asset intelligence, firmware analysis, services, and a large integrator—creating immediate product-boundary, data, neutrality, and roadmap questions.
The April 2026 close moves a major cyber-asset intelligence platform inside ServiceNow and puts asset identity, exposure, workflow, data use, packaging, and remediation ownership on the diligence agenda.
The June 2026 announcement would combine OT threat detection, asset intelligence, firmware analysis, services, and a large integrator—creating immediate product-boundary, data, neutrality, and roadmap questions.
The April 2026 close moves a major cyber-asset intelligence platform inside ServiceNow and puts asset identity, exposure, workflow, data use, packaging, and remediation ownership on the diligence agenda.
The provider's annual report supplies threat, vulnerability, ransomware, assessment, and incident-response observations—but its populations and methods must remain attached to every reported number.
The January 2026 notice begins a revision of the central U.S. OT security guide while leaving Rev. 3 as the current final publication.
IEC PAS 62443-1-6:2025 addresses changed communication channels and organizational models without treating IIoT as a separate security universe.
The release spans multiple Siemens and Schneider Electric product families and demonstrates why asset identity, version, vendor guidance, exposure, process consequence, and maintenance feasibility must stay connected.
OT defense begins with identity, role, location, ownership, criticality, communication, dependency, version, configuration, exposure, and lifecycle. Collection methods have different coverage and operating risks.
Read the market record →Protocol decoding, baselines, threat content, packets, alerts, and cases matter only when teams can interpret process context, preserve evidence, and coordinate a response that does not create avoidable operational harm.
Read the market record →Vendor maintenance, engineering access, credentials, session paths, file transfer, emergency use, segmentation, and fail states need an explicit architecture and accountable owner at each boundary.
Read the market record →Exposure decisions, backups, configuration baselines, tested restoration, spares, incident authority, safety coordination, and product-support lifecycles determine whether a defense program can sustain the physical mission.
Read the market record →The proposed combination could alter ownership, packaging, data, services, partner relationships, and the OT security market architecture.
Industrial product suppliers and buyers need exact legal-role, product, conformity, reporting, support, and evidence records tied to the staged dates.
Buyers need current evidence for product identity, packaging, workflow, data governance, integrations, and organizational responsibility after the ownership change.
Readers should preserve sample, denominator, method, source population, and provider-research classification beside every reported finding.
Programs should preserve Rev. 3 as current final guidance while tracking the revision through explicit development states.
IIoT reviews need explicit device, gateway, edge, cloud, identity, data, update, supplier, and owner responsibilities.
The research connects the provider market, normalized capabilities, authority records, operating domains, and source limitations rather than presenting a score or universal winner.
Read the report →