Solutions / Mining, Energy & Industrial
The plant doesn't stop for a patch window.
Every security recommendation you've been given assumes you can reboot something. You can't. Production runs, the PLC is fifteen years old, the vendor needs remote access, and the site is on a satellite link. We test inside those constraints instead of pretending they aren't there.
- CCCS approved
- National Defence endorsed
- Canadian owned
Sound familiar
Downtime is the only number that matters.
- Corporate IT and site OT were separated once, and nobody's checked since.
- Six vendors have remote access to control systems and no one owns the list.
- Half the equipment can't be patched and the other half can't be taken offline.
- Remote sites run on satellite or LTE, with a contractor laptop as the weak point.
- A peer in your sector lost a week of production and the board noticed.
- Your last assessor wanted to run an active scan against a live PLC.
How it works
Passive first. Always.
-
01
Listen before touching anything
We start passive — traffic capture, asset discovery from what the network already says about itself. Nothing gets probed until we know what it is and what it controls.
-
02
Map where IT meets OT
Historians, jump hosts, engineering workstations, vendor tunnels and the remote-site links. The crossing points are where incidents actually start — not the PLC itself.
-
03
Test up to the line we agree on
Full-depth testing on the corporate and convergence layers, and safe methodology on the control layer, with the boundary written down and signed before we start.
-
04
Watch the crossing points
Monitoring focused on the paths that lead to production, plus an incident playbook written for a site that can't simply be unplugged.
What you get
Findings priced in hours of production.
-
Convergence map
Every real path from an internet-facing asset to something that moves ore or power.
-
Vendor access inventory
Who can reach your control systems, through what, and which ones should be revoked today.
-
Risk in operational terms
Ranked by hours of downtime and cost, not by CVSS. That's the language your exec team funds.
-
An IR playbook for a live site
What to isolate, in what order, when isolation itself can halt production.
Why us
Availability is part of our scope, not your risk.
Our methodology treats the control layer as read-only until there's a written agreement saying otherwise, and our operators start from a simple position: an availability incident caused by the security test is still an availability incident, and it's ours.
Remote and northern sites are normal work for us, not an exception with a travel surcharge attached. We scope around satellite latency, rotating crews and the fact that nobody is driving four hours to reboot an appliance.
Start with one site.
Pick the site that worries you most. We'll assess it end to end, show you the path from the internet to the process floor, and you decide whether the rest is worth doing.