The Ignition Security Hardening Guide is Inductive Automation’s set of implementation recommendations for deploying Ignition securely: Gateway configuration, authentication and authorization, TLS, network placement, and operational practices. It’s being revised for Ignition 2027.
Treat the guide as a minimum. Your own security policy, risk assessment, and architecture decisions take precedence over our general advice. Where a different control, technology, or approach fits your environment better, use it and follow the spirit of the guide rather than the letter. External controls, such as a firewall rule, a reverse proxy, or a network segment that accomplishes the same goal may be a valid substitute for an Ignition control such as a Gateway setting.
Changes for 2027:
We are moving the guide to the Online User Manual rather than a separate PDF.
We are adding a Security Hardening Checklist: a short, ordered set of steps that takes a Gateway from its initial install state to a secure baseline. This will be the same as the configuration assessed for EU Cyber Resilience Act (CRA) conformity. EU customers deploying Ignition 2027 will be expected to complete it before go-live. See the CRA post for context. This should be valuable for all customers running Ignition in production environments.
The current guide remains the recommended practice for 8.1 and 8.3.
We value feedback. If there’s a control you’ve had to figure out on your own, a section that’s unclear, or something that the guide doesn’t cover well, reply here or email ignition-security@inductiveautomation.com. Responses here will be reviewed as part of the revision.