Industrial customers ask hard security questions before they connect anything to a controller. This page is our opening answer.
Last updated: September 1, 2026
Hardware
TPM 2.0 hardware root of trust in every KNO1-PLC for device identity, secure key storage, and measured boot.
IEC 62443-ready design. The controller and platform are designed against the IEC 62443 industrial security framework; certification status is provided on request.
Read-only by design. In gateway mode, KNOCE does not issue control writes to the PLC or alter control logic. Deployment is designed around segmented, least-privilege connectivity — the gateway is placed on its own VLAN or firewall zone with outbound-only flows to the cloud.
Network architecture
The reference deployment, in one picture. Specifics are agreed with your OT security team per site.
The gateway initiates every connection; nothing on the internet initiates a connection to the gateway.
Raw operational data can remain on site; only what a customer's policy allows leaves, and it leaves encrypted.
Segmentation, firewall rules, and monitoring of the gateway zone are agreed with the customer's OT security team before commissioning.
Certification roadmap
"IEC 62443-ready" is a design statement, not a certificate. Here is where each item stands; this list is updated as testing completes.
TPM 2.0
On the KNO1-PLC today.
IEC 62443
Design aligned to IEC 62443-4-1 / 4-2. Formal certification: planned.
UL / CSA
Planned.
CE / FCC
Planned.
Hazardous location
Class I Div 2 / Zone 2: in evaluation for pressure-pumping deployments.
Environmental validation
Third-party IP69 / IP69K, temperature, vibration, and shock testing: planned.
Safety boundary
KNOCE software is a monitoring and supervisory-request layer. Protective functions — emergency shutdown, overpressure protection, interlocks — remain with certified hardware, independent of our software. Supervisory requests are validated, acknowledged, executed, and audited with attribution at every step.
Data in transit and at rest
Telemetry leaves the site over MQTT with TLS. Raw operational data can remain on-site; only detections and summaries need to leave when a customer's policy requires it.
Cloud data is encrypted at rest and segregated per customer. Identifiable data can respect regional residency requirements.
Customers own their raw operational data. De-identified telemetry is used to improve detection models under the terms of each customer agreement.
Access and operations
Role-based access with attributed actions: every alarm acknowledgement and supervisory request records who, when, and what.
Least-privilege administration, logged access to production systems, and defined response targets for platform incidents under partner and customer agreements.
License-keyed pipeline. The site pipeline runs against an encrypted license key that carries its cloud credentials without ever exposing them on site. Keys rotate without touching hardware, and each key dictates where a site's data may go.
Responsible disclosure
If you believe you have found a security vulnerability in a KNOCE product, the platform, or this website, please email info@knocesystems.com with "Security disclosure" in the subject line. We will acknowledge reports promptly, work with you to understand and resolve the issue, and will not pursue action against good-faith research conducted in accordance with this policy.