Architecture
Containerised and Hardened by Design
nz_controller runs on a modern Enterprise Linux 9 host that sits in front of the legacy Netezza appliance. The controller host is fully patched, hardened per SOC2 requirements, and is the only system that communicates with the Netezza appliance. Support engineers connect to the controller — never directly to the appliance.
This architecture achieves something that previously seemed incompatible: you can maintain full support capability for a legacy Netezza system running vulnerable old software, while satisfying modern security and compliance requirements. The vulnerable system is isolated. The access point is hardened.
The controller host can be deployed on-premises alongside the Netezza appliance, or in a cloud VPC with an appropriate network path. The Netezza appliance requires no changes — it does not know nz_controller exists.
Deployment Architecture
Support Engineer (Browser)
↓ HTTPS
nz_controller Host — Enterprise Linux 9
SOC2-compliant · Fully patched · Hardened
SOC2 Compliant
↓ Internal Network Only
Legacy Netezza Appliance
Striper / Mako / CP4D — no direct external access
Network Isolated
Deployment Options
On-premises alongside the appliance
Cloud VPC with VPN/private link to appliance