FreeIgnition® MRI: every risk in your gateway, found and ranked in five business days.Get yours →
Home / Articles / What an inspection finds Ignition MRI

What we find when we inspect an Ignition gateway.

Our sample Ignition MRI is written for Pinecrest Regional Water District, a fictional utility. The names and counts are invented, but every finding is a type our scan detects in real gateway backups. The report ranks 23 findings across all nine areas the MRI checks. The main ones are below.

Artek engineering team · October 2026

Security

  • Three web endpoints handed any file on the server to whoever asked. Each read a file path straight from the request, with no login and no limit on which folder it could reach. Looking files up by an ID and requiring a login closes it.
  • Two passwords were typed into the script library. Anyone with Designer access can read them, and they travel inside every backup. They belong in a Secret Provider.
  • Active Directory sign-in ran over plain LDAP, so every login sent a domain password across the network in readable form. LDAPS on port 636 fixes it.
  • Fourteen database calls built SQL by pasting values into the query, and eleven named queries did the same with text parameters. That is the pattern behind SQL injection. Typed parameters fix it.
  • The gateway connected to its databases as the administrator account, so a successful injection would have full control of the database server.
  • The gateway version was inside the range of a published security advisory. Filling in one blank permission setting closed a second advisory in minutes.

Scripts that fail quietly

  • A nightly data purge was written but never scheduled. Its own comment said to run it from a gateway timer, no timer called it, and the tables it was meant to trim kept growing.
  • Six operator buttons did nothing when pressed. Their scripts were set to run in the client, which Perspective scripts never do, and no error appeared on screen or in any log. Two of them acknowledged alarms.
  • 214 error handlers hid failures instead of logging them. A script that fails silently looks the same as one that works until someone checks the data.

Performance

  • The same polling timer ran in three projects at once, so every poll of every lift station happened three times, and the three copies raced to write the same tags.
  • 38 query tags hit the database every five seconds, all day: about 657,000 queries a day, whether or not anyone was looking.
  • Eleven screen bindings refreshed every second. Four of them ran a database query on each tick, so every added operator added load.

Tags and alarms

  • 1,340 tags sent their history to a provider that no longer existed, so none of that history was recorded. Most inherited the setting from four UDT types, which makes the fix quick.
  • Two alarm journals wrote to the same table, so every alarm was stored twice, and the shorter retention setting deleted records the other was meant to keep.
  • 58% of alarms were rated High or Critical, so a genuinely urgent alarm arrived on a screen already full of red.
  • 412 of 610 alarms had no display path, so operators saw a bare tag name and had to work out which station it came from.

Recovery and upgrades

  • A restore onto a new server would break 40 screens. They use a third-party chart module, and a gateway backup does not carry modules.
  • Scheduled backups and historian pruning were both switched off. The newest backup was whenever someone last took one by hand, and the history tables grew without limit.
  • An old revision of the SCADA project was still enabled, running its own timers, including one of the three polling copies.

How the report is built

Each finding states what we found, where, what could happen because of it, how severe it is (Critical, High, Medium or Low) and how much effort the fix takes, from a quick fix to a project. A senior engineer reads every report before it is sent, and the report says plainly what the scan cannot see: the PLCs, the database contents and how people use the system.

Read the full sample report (PDF), or send us a backup of your own gateway for a free one.

Let's talk

Want this for your gateway? It’s free.

Call us and we'll connect you with the right engineer. If we're not the right fit for the work, we'll tell you.

Contact us →
(877) 318-0200
Inductive Automation Premier Integrator badge