Designed for operational technology environments
Fieldiq is designed with NERC CIP operational technology controls in mind. Unidirectional data flow, network segmentation support, least-privilege access controls, and TLS encryption throughout — appropriate for ICS/OT integration at electric utilities.
Security controls
These controls reflect Fieldiq's current architectural design. Security documentation is available under NDA for utility procurement review.
Telemetry flows from field assets and SCADA to Fieldiq only. No inbound connections from Fieldiq to OT networks. Alert write-back uses a separate controlled path with explicitly defined firewall rules.
Fieldiq's architecture supports deployment in a DMZ between OT and IT networks. Integration documentation includes network topology diagrams and firewall rule specifications for common utility network architectures.
All data transmitted between field sensors, SCADA/historian systems, and Fieldiq processing infrastructure uses TLS 1.2 minimum. Certificate management and rotation procedures are documented.
Role-based access with minimum necessary privileges. Fieldiq service accounts are configured with read-only access to telemetry sources. Write-back accounts are scoped to specific SCADA alarm points only.
All access to field asset data and alert operations is logged with timestamp, user identity, and action. Logs are retained for 12 months and are available for utility security audit review.
Third-party software components are tracked and documented. A software bill of materials (SBOM) is available on request for utilities with CIP-013 supply chain review requirements.
NERC CIP context
Fieldiq is designed with NERC CIP operational technology controls in mind. This means our architecture reflects the network segmentation, access control, and audit logging requirements that CIP-005, CIP-007, and CIP-013 impose on BES Cyber System components and associated access points.
Fieldiq is not certified as a NERC CIP compliant system, and we do not claim certification. Whether Fieldiq deployments require CIP treatment as BCS or EACMS at your utility depends on your compliance program's scoping decisions, the specific assets monitored, and your system's connectivity to BES Cyber Assets. Asset reliability engineers should engage their compliance team as part of any deployment evaluation.
Fieldiq provides security documentation, architecture diagrams, and SBOM on request to support your utility's internal compliance evaluation.
Fieldiq does not provide legal or compliance advice. This page reflects our architectural design intent, not a compliance assessment. Consult your utility's compliance team for CIP applicability determinations.Security documentation available under NDA
Fieldiq provides detailed security documentation — architecture diagrams, firewall rule specifications, access control models, and SBOM — to utilities conducting procurement security reviews. Contact us to begin the documentation exchange process.