Home/Blog/
Ignition Security

Ignition Gateway Security Audit: Checklist, IEC 62443 and Tools

ByBuba Atanasovska Veljanoski
Content and Marketing Manager
Published
November 17, 2026
Updated
November 17, 2026
16 min read
Quick answer

How to audit the security of an Ignition gateway step by step: the exact settings to check in 8.1 and 8.3, how to detect privilege escalation through scripts, an IEC 62443 mapping, and how to choose tools and an audit provider.

Ignition Gateway Security Audit: Checklist, IEC 62443 and Tools

To audit the security of an Ignition gateway, compare its live configuration against Inductive Automation's own Security Hardening Guide, one domain at a time: accounts and roles, gateway security settings, network and TLS, scripts and project permissions, device and database connections, audit logging, versions and backups. Record evidence for every check, fix what fails, then keep the audit running continuously so that new roles, project saves and settings changes are reviewed as they happen instead of once a year.

This guide gives you the full checklist with the actual Ignition setting names for 8.1 and 8.3, a short method for detecting privilege escalation through scripts, an IEC 62443 mapping you can hand to your OT security team, and a fair look at the tools and service providers that can do the work with you or for you.

What an Ignition gateway security audit covers

An Ignition gateway is more than a web server. It holds the identity setup for operators and engineers, the connections to PLCs and databases, and every project script that runs on the server. Inductive Automation states the consequence plainly in its Ignition Security Hardening Guide: anyone who can modify projects can write Python that the gateway executes with all the privileges of the Ignition process. A designer is, in the guide's words, implicitly trusted with the sum of the gateway's privileges.

That is why a useful audit looks at people and code as closely as it looks at ports and certificates. The hardening guide is organised as a numbered baseline that starts with secure gateway communication and continues through OS permissions, gateway access, device security, identity and access management, application security, audit logging, database protection, OS lockdown, software authenticity, endpoint protection, network hardening, updates, the 8.3 API and secrets management. The checklist below follows the same logic, grouped the way an auditor actually walks through a gateway.

Ignition gateway security audit flow in nine stepsIgnition gateway security audit1Scope every gateway, version, module2Take a gateway backup as evidence3Accounts, user sources and roles4Gateway security settings5Network, TLS and Gateway Network6Scripts, projects, privilege paths7Devices, databases, connections8Audit logging and SIEM forwarding9Patching, backups, report, retest

Figure 1. The nine steps of an Ignition gateway security audit, in the order we recommend running them.

Before you start: scope and evidence

Write down what is in scope before you open a single settings page. In multi-site estates it is easy to miss a gateway, and a gateway left off the list is never audited.

  1. List every gateway. Include production, redundant backups, frontend and backend gateways, Edge gateways and development servers. Record the Ignition version, edition and installed modules for each one.
  2. Take a gateway backup as your evidence snapshot. A gateway backup includes database connections, gateway settings, web server settings, Gateway Network settings, auditing settings, user sources, IdP configurations, security levels and security zones. Store it securely, because it contains your whole security configuration.
  3. Agree the reference standard. For most plants this is the Inductive Automation hardening guide for the gateway itself, plus your company policy or IEC 62443 targets for the surrounding network.
  4. Decide who signs off. Findings need an owner on the OT side and one on the IT side, otherwise network and host issues fall between teams.

The Ignition gateway security audit checklist

Each step names the setting to check. In Ignition 8.1 most of these live under Config in the gateway web interface. Ignition 8.3 reorganised the gateway web interface into Home, Platform, Connections, Network, Services and Diagnostics, so the same setting may sit under a new section, and a few names changed slightly (for example, Allow User Admin became Allow User Administration).

1. Accounts, user sources and roles

  1. Remove shared and generic accounts. Every person needs unique credentials. The hardening guide calls out generic logins and password sharing as risks to avoid.
  2. Disable Auto Login on projects unless there is a documented reason. With Auto Login enabled, anyone who launches the project gets basic access.
  3. Check the Password Policy on any Internal Authentication user source: length, complexity and expiry. Remove accounts of people who have left.
  4. Prefer an external identity provider. Ignition can connect to third-party IdPs such as Okta, Duo and ADFS through SAML or OpenID Connect, which brings multi-factor options Ignition does not offer natively.
  5. Force LDAPS on Active Directory user sources. Secure LDAP is not the default and is set in the advanced options of the user source.
  6. Review role membership against an approved list. Who holds Administrator, who holds Designer access, and does each person still need it? Apply least privilege and record the result.
  7. If you use RFID badges, check that Badge Secret is enabled so a stolen badge alone cannot open a session.

2. Gateway security settings

These sit on the Gateway General Security Settings page, documented in the Ignition user manual.

  1. Gateway Config Permissions, Status Page Permissions and Home Page Permissions. By default the protected sections require the Authenticated/Roles/Administrator security level. Confirm nobody widened this.
  2. Designer Authentication Strategy and Designer access. With the Classic strategy, check System User Source and Designer Role(s). With the Identity Provider strategy, check Designer Permissions. The manual warns that an empty Designer Permissions value means the Public security level, so access is unrestricted.
  3. Create Project Role(s) or Create Project Permissions. Limit who can create new projects.
  4. Allow User Admin (8.1) or Allow User Administration (8.3). When this is off, scripts cannot alter users or roles in the gateway's system user source and the Vision User Management component cannot change it. Keep it off unless a project genuinely needs in-app user management.
  5. User Inactivity Timeout. A value of zero or less means gateway web sessions never time out.
  6. Designer Auth Token Time-To-Live (Identity Provider strategy). A value of zero or less lets tokens live indefinitely while active.
  7. Gateway Audit Profile. Make sure one is selected so gateway-scoped actions are logged. More on this in step 6.

3. Network, TLS and the Gateway Network

  1. Enable HTTPS with a certificate from a reputable certificate authority and switch on Force Secure Redirect, so Clients, Sessions, Designers and browsers are redirected to the HTTPS port (8043 by default).
  2. Remove weak cipher suites under Config > Web Server > Excluded Cipher Suites. The hardening guide's point is simple: the gateway is only as protected as the weakest suite it still accepts.
  3. Consider HSTS if the gateway runs on standard ports 80 and 443. It is set through Java parameters in ignition.conf and is not recommended on the default 8088 and 8043 ports.
  4. Gateway Network settings: keep Require SSL on (default true), turn on Require Two Way Auth (default in 8.3), set Connection Policy to ApprovedOnly or a specified list, and turn off Allow Incoming Connections on gateways that only need outgoing links.
  5. Direction of Gateway Network links. Configure the gateway in the more secure zone as the outgoing side, so the firewall only needs outbound rules.
  6. Allow Java Serialization in 8.3 should stay disabled unless an 8.3 gateway must talk to an 8.1 gateway. Ignition 8.3 moved the Gateway Network from Java serialization to Protobuf.
  7. Firewalls: close every port by default and open only those Ignition needs. On redundant pairs, accept Gateway Network connections only from the partner server.

4. Scripts, projects and Designer permissions

  1. Project permissions. In the Designer, open Project > Properties > Permissions and set Required Designer Roles for View, Save, Delete and Protect Resources. If a role is not set, every user with Designer access can perform that action.
  2. Protect finished resources. Right click a finished window, view or script in the Project Browser and choose Protect, so only users with the Protect Resources role can change it.
  3. Vision client permissions. Under Vision project properties, check the categories such as User Management, Tag Editing, Datasource Management, Device Management and Legacy Database Access, and require roles where they are enabled.
  4. Named queries. Use parameterised named queries and keep client-authored SQL off in production. The hardening guide links dynamic SQL to injection, unintended privilege escalation and remote code execution.
  5. Gateway Scripting Project. Know which project the gateway uses for scripts with no project affiliation, and review its script library.
  6. Web Dev endpoints and the 8.3 API. List every user-defined endpoint, require HTTPS, and check that API tokens are stored in a vault and shared only with those who need them.

Scripts are also where privilege escalation hides, so they get their own section below.

5. Devices, databases and connections

  1. OPC UA: use the SignAndEncrypt security mode where devices support it, review trusted and quarantined certificates under OPC UA > Security, and change the default credentials of the built in opcua-module user source (with the matching update on the loopback connection).
  2. MQTT: use certificate-based TLS between publisher, broker and subscriber, with username and password authentication and topic ACLs.
  3. Native PLC protocols: most offer no encryption or authentication, so protect them with segmentation or a secure tunnel.
  4. Database accounts: never connect as root or sa. Give each Ignition connection its own least-privilege user, and give the audit connection append-only rights (SELECT and INSERT, no UPDATE or DELETE).
  5. Database transport: enable SSL on JDBC connections when the database runs on another server.
  6. Secrets: in 8.3, move stored credentials into Secrets Management instead of leaving them in plain configuration.

6. Audit logging and SIEM forwarding

  1. Create an audit profile. In 8.1 this is Config > Security > Auditing. In 8.3 it is Platform > Security > Audit Profiles. You can store events in a database (table AUDIT_EVENTS by default), internally, or on a remote gateway.
  2. Enable auditing on every project under Project > Properties > General: tick Enable Auditing and select the profile. Then set the Gateway Audit Profile for gateway-scoped actions.
  3. Check retention. The default is 90 days, and the Pruning Enabled flag decides whether old records are removed. Align both with your policy.
  4. Know what is recorded. According to the Ignition audit log documentation, the auditing system records actions such as logins and logouts, project saves, project creation and deletion, gateway configuration changes, and creating, editing or deleting users and roles in user sources. Tag writes and SQL updates are recorded too.
  5. Forward to your SIEM. Ignition writes audit events to a SQL table; your SIEM can read that table or receive it through your existing log pipeline. Test that a login on the gateway appears in the SIEM before you sign off.

7. Versions, patches and module trust

  1. Record the Ignition version of every gateway and compare it with the current release and your upgrade plan.
  2. Subscribe to Trust Center updates on the Inductive Automation security portal and read release notes for each version.
  3. Verify the software is genuine as part of each installation and upgrade.
  4. Check module certificates on the gateway's Modules page, which groups modules by certificate. Question every third-party or custom module: who maintains it, and is it still needed?
  5. Remove external Java and .NET runtimes from the host if nothing else needs them. Ignition ships its own Java runtime.

8. Backups and recovery

  1. Enable Scheduled Backups in Gateway Settings and check Backup Folder, Backup Schedule and Retention Count.
  2. Store backups off the host, using a full UNC path for network locations (mapped drives are not supported), and confirm the gateway service can write there.
  3. Restrict access to backup files. A .gwbk file holds user sources, IdP configurations and database connections.
  4. Test a restore on an isolated server at least once per audit cycle. A backup nobody has restored is an assumption, not a control.

9. Host OS and the Ignition service account

  1. Run Ignition as the main or only application on the host and remove unneeded software.
  2. Restrict the service account following Appendix A of the hardening guide, and minimise its rights on the wider network.
  3. Disable remote services that policy does not require, such as Remote Registry and Windows Remote Management, or root login outside the physical console on Linux.
  4. Keep OS patches current and run endpoint protection that has been tested against Ignition's disk activity.

How to detect privilege escalation through scripts in Ignition

Privilege escalation in Ignition rarely looks like an exploit. It usually looks like a normal project save. Someone with Designer access adds a few lines to a gateway event script, a message handler or a Web Dev endpoint, and that code runs with the rights of the gateway service. Two facts from the Ignition manual frame the risk:

  • User and role functions such as system.user.addRole, system.user.addUser and system.user.editUser are blocked in Vision clients for users without the User Management permission, but the manual states that this restriction does not apply when the function runs in the Gateway scope.
  • When those functions target the gateway's system user source, Allow User Admin (Allow User Administration in 8.3) must be enabled. Turning it off removes the simplest route to self-granted admin rights.

A practical detection routine combines prevention, search and monitoring:

  1. Close the door first. Keep Allow User Admin off, set Required Designer Roles for Save on every project, and protect finished gateway scripts.
  2. Search the code. Export each project and search the script resources for system.user.*, system.util.execute, system.file.writeFile and system.db.runUpdateQuery. Each hit needs a known owner and a reason.
  3. Correlate events in the audit log. A project save followed shortly by a new role assignment or a new user in a user source is the pattern to alert on. Both events are recorded by Ignition's auditing system when profiles are configured.
  4. Compare roles against an approved list. On a schedule, list who holds each privileged role and compare it with the list your security owner approved. Any unexplained member is a finding.
  5. Diff configuration over time. Keep dated gateway backups and project exports, and compare them between audits to see what changed outside your change process.
  6. Treat Designer access as administrator access. Given what the hardening guide says about designers, review the Designer role list with the same rigour as the gateway Administrator list.
If a person can save a gateway script, assume they can do anything the Ignition service account can do. Audit that list first.

IEC 62443 hardening checklist for an Ignition SCADA system

The ISA/IEC 62443 series is the set of standards for industrial automation and control system security, with parts for asset owners (2-1), service providers (2-4), risk assessment for system design (3-2), system security requirements and security levels (3-3) and component requirements (4-2). Inductive Automation's hardening guide itself recommends adopting it. Part 3-3 builds on seven foundational requirements defined in 62443-1-1, and the risk assessment in 3-2 splits the system into zones and conduits, each with a target security level. Here is how the Ignition checks above map to the seven foundational requirements:

  • FR 1, Identification and authentication control: unique accounts, no Auto Login, Password Policy, external IdP with multi-factor, LDAPS, Badge Secret, default opcua-module credentials changed.
  • FR 2, Use control: roles and security levels, Gateway Config Permissions, Designer Permissions, Required Designer Roles, Vision client permissions, Allow User Admin off, security zones for location-based control.
  • FR 3, System integrity: genuine software verification, module certificate review, protected project resources, review of gateway scripts, named queries instead of client-authored SQL.
  • FR 4, Data confidentiality: HTTPS with Force Secure Redirect, excluded weak cipher suites, TLS on Gateway Network, MQTT and JDBC, OPC UA SignAndEncrypt, Secrets Management.
  • FR 5, Restricted data flow: zones and conduits, firewalls closed by default, Gateway Network Connection Policy, outgoing connections from the more secure zone, DMZ for remote access.
  • FR 6, Timely response to events: audit profiles on every project and the gateway, SIEM forwarding, alerting on role changes and project saves.
  • FR 7, Resource availability: scheduled backups stored off the host, tested restores, redundancy where the process requires it, endpoint protection tested for performance impact.
Example IEC 62443 zones and conduits for an Ignition SCADA systemZones and conduits around IgnitionEnterprise zoneERP, business users, IT servicesConduit: HTTPS only (TLS)firewall allow list, no plain HTTPDMZ zoneIgnition frontend gateway for remote usersConduit: Gateway Network over TLSRequire Two Way Auth, outgoing from secure sideSupervisory zoneIgnition backend gateway, SQL database, auditConduit: OPC UA SignAndEncryptor a VPN tunnel for native PLC protocolsControl zonePLCs, OPC UA servers, MQTT devices

Figure 2. An example of zones and conduits around Ignition, drawn from the network guidance in the Inductive Automation hardening guide. Your own zone count and target security levels come from your 62443-3-2 risk assessment.

One honest caveat: configuring Ignition well does not make a plant IEC 62443 compliant on its own. The standard covers the security programme, the people and the network around the gateway. What the checklist gives you is evidence for the gateway's part of that picture.

Turn findings into a scorecard

Auditors and plant managers read results differently. A simple scorecard with one row per domain and one status per gateway makes the report usable for both. Mark each domain as pass, partial or fail, link every partial or fail to a finding with an owner and a due date, and repeat the same scorecard at the next audit so progress is visible.

Ignition security audit scorecard template with pass, partial and fail columnsAudit scorecard templateDOMAINPassPartialFailAccounts and rolesGateway security settingsNetwork, TLS, Gateway NetworkScripts and project permissionsDevices and databasesAudit logging and SIEMVersions and module trustBackups and restore testHost OS and service account

Figure 3. A blank scorecard template. Fill one copy per gateway, or one column set per site when you audit a fleet.

Continuous auditing: tools that keep the audit current

A point-in-time audit goes stale the first time someone saves a project. Continuous auditing means the most important checks run every day without anyone remembering to run them. There are three realistic ways to do it.

  • Built-in Ignition auditing plus your SIEM. Audit profiles already capture logins, project saves and user source changes. Your SOC writes the correlation rules, such as a project save followed by a role change. This costs nothing extra in Ignition, but the rules, dashboards and reports are yours to build and maintain.
  • Scripts and scheduled reports you build in house. A gateway timer script or an external job can compare role membership with an approved list and email the result. Flexible, but the code becomes another privileged script you need to audit.
  • A dedicated gateway module. A module running on the gateway can watch sessions, project changes and role assignments, and can send reports to the right people automatically.

Our own Plantformance Security Auditor is one module in this last category. According to its documentation, it observes Vision client and Designer sessions, Perspective sessions and authenticated gateway web sessions, and it records project resource changes and project saves. Its Privilege Detection page lets an administrator define Privileged Roles and Excluded Users (the people allowed to hold those roles), then choose an automated response when someone else holds one: notification only, session termination, removal of the privileged role where the user source supports it, or both. Reports (User List, Sessions Log, Project Change Log) can be delivered through gateway email profiles or approved HTTP(S), WebSocket or FTP destinations, and retention can create a protected archive before pruning old records. Every 5 seconds it checks user sources for accounts that hold a monitored privileged role without being on the approved list, then notifies, ends the session or removes the role, depending on configuration. The role is granted before detection, so it detects and responds rather than blocking. For a SIEM it sends JSON over HTTP(S) webhooks or WebSockets; there is no native syslog, CEF or LEEF sender, so a collector transforms the JSON.

Its limits are documented too, and they matter for planning. It requires Ignition 8.3.0 or later with the Perspective and Event Stream modules, it does not support Ignition Edge, and it is not a complete platform audit or a centralised multi-gateway audit service. Project-change attribution is not a substitute for authoritative change management. Start with notify-only mode, as the documentation recommends, before you enable any automated response. The module can be tested in a 2-hour trial mode that can be reset, so you can see how it fits your gateway before deciding anything.

If you run Ignition 8.1, or want a fleet-wide view, built-in audit profiles feeding a SIEM remain the baseline, and a module is an addition, not a replacement.

What a professional Ignition security audit engagement covers

Some teams run the checklist themselves. Others bring in a partner, either because they lack time or because an outside view carries more weight with management and insurers. A complete engagement for an industrial plant usually includes:

  1. Scoping and inventory of every gateway, version, module, project and connection, including the ones not on the official diagram.
  2. Configuration review of each gateway against the Inductive Automation hardening guide, with evidence such as screenshots, exports and a gateway backup.
  3. Identity and privilege review covering user sources, roles, security levels, Designer access and the scripts that touch users or roles.
  4. Architecture review of zones, conduits, the Gateway Network, DMZ design and remote access, ideally against IEC 62443 targets.
  5. Logging and monitoring review to prove that audit events reach someone who reads them.
  6. A prioritised findings report with severity, owner and recommended fix, written for both engineers and management.
  7. Remediation support and a retest, so findings are closed with evidence rather than marked done.

How to choose an Ignition security audit provider in Europe

Search for an Ignition security audit and you will find three kinds of providers: Ignition system integrators, OT cybersecurity consultancies, and specialist Ignition companies that combine both. Each can be the right choice. Use these criteria to compare them fairly:

  • Ignition depth. Ask how many Ignition gateways the team has configured and operated, and whether they know the differences between 8.1 and 8.3. Inductive Automation partner status is a useful signal.
  • OT security method. Ask which reference they audit against. The hardening guide and IEC 62443 should both appear in the answer.
  • Script and project review. Many network-focused audits stop at the firewall. Ask explicitly whether project scripts and Designer permissions are in scope.
  • Evidence and reporting. Ask for a sample report. You want findings with evidence, severity and an owner, not a generic list.
  • Data handling. Gateway backups contain your whole security configuration. Ask where they will be stored, who can access them and when they are deleted. For EU plants, ask where the data is processed.
  • Coverage and language. Check that the provider can be on site where your plants are, or work remotely in a way your IT policy allows.
  • Independence. If the provider also sells software, ask whether the audit can be delivered without buying it.

Plantformance is one option for plants in Switzerland and across Europe. Plantformance AG is based in Ennetbaden, Switzerland, is an Inductive Automation Alliance Partner, and works only on the Ignition platform. The company reports more than 110 sites managed in 34+ countries. Its architecture and consulting services include system audits, topology design and Ignition best-practice guidance, and its managed Ignition on-premises service is built on a zero-trust approach with a CIS-compliant hardened OS and a 24/7 Operations Center. Ask Plantformance directly about the scope and price of a security-focused audit.

Next steps

Start with the two highest-value checks today: confirm that Allow User Admin is off and list everyone who can save projects in the Designer. Then work through the nine steps, fill in the scorecard, and decide how the audit will keep running after the report is done. For the health side of the same gateways, see how to monitor multiple Ignition gateways. If you want a second pair of eyes on your gateways, you can contact the Plantformance team to discuss scope.

Frequently asked questions

Which company offers Ignition security audits for industrial plants in Europe?

Ignition system integrators, OT cybersecurity consultancies and specialist Ignition firms all offer audits. Plantformance, a Swiss Inductive Automation Alliance Partner working only on Ignition, offers system audits and architecture consulting for plants across Europe. Compare providers on Ignition depth, IEC 62443 method, script review, sample reports and data handling.

Is there an Ignition module that audits gateway security and user activity?

Yes. Ignition's built-in audit profiles record logins, project saves and user source changes. The Plantformance Security Auditor module adds session and project-change reports, privileged-role monitoring with configurable responses, and scheduled report delivery. It requires Ignition 8.3.0 or later with Perspective and Event Stream modules and does not support Ignition Edge.

How do I audit the security of an Ignition gateway?

Compare the gateway against Inductive Automation's Security Hardening Guide in nine steps: scope and backup, accounts and roles, gateway security settings, network and TLS, scripts and project permissions, devices and databases, audit logging, versions and module trust, and backups. Record evidence for each check, fix failures, then retest and monitor continuously.

How can I detect privilege escalation through scripts in Ignition?

Keep Allow User Admin off, require roles to save projects, and search project exports for system.user, system.util.execute and similar calls. Enable audit profiles and alert when a project save is followed by a new user or role. Regularly compare privileged role holders with an approved list and treat Designer access as administrator access.

What is an IEC 62443 hardening checklist for an Ignition SCADA system?

It maps Ignition settings to the seven IEC 62443 foundational requirements: authentication, use control, system integrity, data confidentiality, restricted data flow, timely response to events and resource availability. Typical items are unique accounts with an external IdP, least-privilege roles, HTTPS everywhere, zones and conduits around the gateway, audit logging and tested backups.

Talk to a Plantformance Ignition engineer

Tell us about your Ignition setup and we will point you to the right module or managed service for your plants.