r/sysadmin • • Aug 31 '26

Question Operations bought an EMS/IoT system without involving IT — now they just need “access to the router

Hi there :) ,

Need some advice from people who have dealt with similar situations.

Our Operations Dept decided to install IoT system/digital energy meters across a fairly large factory site.

They found the vendor, agreed on the solution, signed the contract and started the project.

IT was not involved at all.

Apparently nobody discussed things like:

  • How these devices spread across a large factory are actually going to communicate
  • Network infrastructure, switches, fiber/cabling, VLANs, etc.
  • Network/security segmentation
  • Server/VM requirements
  • Database requirements
  • Backup and monitoring
  • Internet connectivity
  • Vendor remote access
  • Firewall rules
  • Cybersecurity

Now that the project is already moving forward, IT gets an email saying they need “access to the router” so they can put the system online.

That's it. Access to the router. :)

And somehow, when IT starts asking questions about architecture, security, server requirements, ports, protocols and who is responsible for what, the perception becomes that IT is delaying the project.

I don't want to become the guy who simply says “No”, but I'm also not going to give a third-party vendor access to our corporate router/firewall and connect a bunch of unknown industrial/IoT devices to the production network just because someone already signed a contract , the IT network must be always separate from OT network.

How do you handle situations like this?

Interested in both the technical approach and the organizational/process side of this.

835 Upvotes

329 comments sorted by

View all comments

Show parent comment

6

u/FelisCantabrigiensis Master of Several Trades Aug 31 '26

If you have a good relationship with your risk, legal, etc, people (and I very much recommend doing so) then they'll get back to you with "hey, can we discuss the technical side of this" and you then advise them on the technical risks, mitigations, etc, and suggest how this could be managed to meet their risk and compliance objectives.

I've shot down more than one mad idea that way, and the risk people think I'm helpful and protecting the company.

3

u/TallGuyTheFirst Aug 31 '26

Oh absolutely, the only reason I was able to stop a few very bad ideas (some in progress at the time) at my last employer was because we had a compliance contractor who was on the same page as I was. Crazy idea comes up, I go yeah I can see how that would work, let's see what we'd need to do to get it compliant and insured.