Why this environment matters
Security for refinery process historian gateways extends beyond passwords and network firewalls. The system collects high-volume plant data for analysis, reporting and engineering review, while a historian compromise can alter operational evidence, expose proprietary process information or become a bridge between business and control networks. NØNOS could be evaluated as an execution layer that verifies software identity, limits device access and avoids unnecessary long-lived state.
The security challenge
Energy and resource systems combine high-energy equipment, geographically distributed assets and operational technology that cannot be patched or restarted like an ordinary office computer. In refinery process historian gateways, the decisive risk is that a historian compromise can alter operational evidence, expose proprietary process information or become a bridge between business and control networks. Even strong perimeter controls may not help once authorised software, a vendor tool or a valid user session has been compromised. Internal permission boundaries must remain enforceable after initial access.
How the capsule model could help
For this system, NØNOS could use one-way or tightly scoped ingestion capsules, signed connectors and isolated analytics without broad control-network credentials. The design would combine zone-specific capabilities, isolated remote maintenance, minimal persistent administration state and a verified boot chain. The intended result would be a set of small trust boundaries instead of one large operating environment where every service inherits broad ambient access.
Deployment requirements
Deployment would require site-specific engineering, segregation from independent protection systems, deterministic performance testing, change control and compliance review. NØNOS would not replace certified relays or safety systems by default.
Current public-beta limitations, hardware support and application availability must be assessed before any pilot. Neither this use case nor an industry source establishes NONOS certification or a current customer deployment.
Who could buy or integrate it?
- Refinery operators buying data-integration and historian upgrades
- Historian software vendors qualifying secure collectors and connectors
- OT integration firms implementing refinery-to-enterprise data interfaces
Industry examples: AspenTech, AVEVA. These are research prospects, not represented as NONOS customers, partners or endorsers.