Security & Integrations
Connect everything. Expose nothing.
Designed for NERC CIP environments.
What we connect to
No equipment is off-limits.
Standard protocols work out of the box. For anything proprietary or legacy, our engineers build the connector.
01
Power and grid
The equipment that makes and moves power.
- SubstationsSEL relays, IEC 61850, DNP3
- TransformersDissolved gas analysis monitors
- Power electronics and storageInverters, UPS, DSTATCOMs, batteries
- Wind and solar plantsTurbine and plant controllers
02
Buildings and facilities
The equipment that keeps sites cool and running.
- Buildings and HVACDelta, Siemens, Johnson Controls
- Data centersSNMP for UPS and PDUs
- DrivesVFDs and motor controllers
- MetersRevenue and power quality
03
Systems you already use
The software around the equipment.
- PLCs, RTUs and data concentratorsRead-only, alongside what you run
- HistoriansAVEVA PI, Ignition, GE Digital
- Field service softwareSalesforce, ServiceNow, Maximo, SAP and more
Security
Built for teams that answer to NERC CIP.
NERC CIP obligations belong to the utility. 42Hz is designed to make them easier to meet, with encrypted connections, remote access that closes when the work is done, and a record of every access. [Engineering to confirm each item below before launch.]
Encrypted remote access.
Approved operators open the equipment screen from 42Hz. The connection is outbound and encrypted, uses single-use keys, reaches only that screen and closes on its own.
Last sync 2 s ago
Network security.
Your team sets the security rules, and 42Hz follows them. Data is encrypted with TLS 1.3, and both ends verify each other before anything moves. The connection is outbound only, through your IT team’s approved path or over cellular. Monitoring only reads from your equipment, and remote access stays off until you turn it on.
Access and audit.
Single sign-on, two-factor and role-based permissions. Every login, session and change is logged for your audits.
Your data.
Encrypted in transit and at rest, hosted in AWS, with optional tenant separation to ensure true isolation.
Trust center.
Our security program follows the SOC 2 framework, with controls monitored continuously.
Security reviews.
Send your questionnaire to [security@42hz.ai] and we’ll complete it and share our architecture and data-flow documents with your team.
Questions IT and controls teams ask.
Your team sets the security rules, and 42Hz follows them. Monitoring data is encrypted, and we can stay off your OT network entirely with cellular routers or work within your own network isolation. Either way, it only reads from your equipment. Remote access to equipment screens is separate: it uses outbound-only connections that open on demand, so the site opens no inbound ports for it.
Not unless you turn on 42Hz Control for specific units and users. Monitoring alone is read-only.
Yes, where a site turns it on. Operators sign in with a named account and two-factor sign-in, and can only open the screens they're approved for. The site can switch remote access off at any time, independently of monitoring.
On AWS, across multiple availability zones. Your data is stored in the US by default. With optional tenant isolation, it can be stored in the region of your choice.
Telemetry is collected within your VPC and queued for delivery, so nothing is lost. When the link comes back, it recovers automatically and fills the gap.