Differentiator #1
Secure By Design
Across the publicly reported attacks on US water systems, nobody defeated sophisticated protections. Attackers found controllers reachable from the public internet, used passwords that were still the factory default or shared across a crew, and logged in through consumer remote-access software with no second factor.
Every one of those is a property of the architecture as much as of the utility. You can harden a conventional system a long way — and you should — but hardening cannot change what the system fundamentally is. Our platform removes the property instead of patching the instance:
-
Outbound-Only Connectivity
Field devices open connections outward to the platform and keep them open. Nothing at your utility listens for inbound connections — no port to forward, no service waiting for a login attempt, no address that answers a probe. A scanner sweeping the internet finds nothing to talk to.
-
Encryption On By Default
Traffic between your sites and the platform travels inside TLS, and the message itself is encrypted a second time with a per-device key. It cannot be switched off. That is the direct answer to unencrypted radio, where somebody within a few miles can listen to your telemetry and send commands your controllers accept as genuine.
-
Certificates, Not Passwords
Each device holds a certificate issued when it is deployed. It is never typed, never spoken, and never travels in a form anybody could reuse. There are no default device passwords to leave unchanged, and revoking access for a departing employee is an administrative action that takes effect immediately — not a trip to every site.
-
No Local Attack Surface
The device offers nothing to connect to locally: no USB, no Bluetooth, no Wi-Fi, no programming port. Cut the padlock at a remote site and open the panel, and there is still nothing to plug a laptop into. It is the only control that does not depend on the lock holding.
-
Per-Person Access, Fully Logged
Everyone gets their own login with role-based permissions — shared crew accounts are not needed to make it work. Every action is written to an audit trail, so you can answer who changed what, and when.
Nothing Listening
Nothing To Plug Into
Nothing To Steal And Reuse
Your Audit Findings, Answered
The problems a security audit typically turns up at a water system, and what each one becomes under this architecture.
- Equipment reachable from the internet
- Nothing listens, so there is nothing to find by scanning
- Default passwords on controllers or radios
- No device passwords to leave at their default
- One shared login the whole crew uses
- Per-person credentials; shared logins are not needed to make it work
- Access still active for somebody who left
- Revoke that person's credential; device credentials are unaffected
- Remote-access software with no second factor
- No inbound remote-access tool; access is through the platform, per person
- Unencrypted radio between sites
- Encrypted cellular; interception yields nothing usable
- A panel anyone could open and plug into
- Nothing to plug into; the lock stops being the only control
- Equipment that no longer receives firmware updates
- Supported equipment that updates itself, remotely, as fixes are released
- Nobody has tested a backup in years
- Configuration and programs are retained centrally and continuously
What still needs you. No architecture removes the need to do a few things well: phishing awareness, your business network and billing systems, physical protection of the equipment, and an emergency plan that lets you run manually. We would rather say so than pretend otherwise.
