OS, Embedded Controllers, Viruses

[Randy Given]

We have three AtlasPC embedded controllers here, all which operate on the Windows NT operating system. We are in the process of ordering a new VxWorks one and probably upgrading the others to VxWorks. In the meantime, we have all three on our in-house network.

We are moving the controllers from one location to another. However, the IT department is having problems in that since the controllers have an "operating system" (NT), they want some assurances that it will not be spreading viruses.

Despite them having been on the network for several years and despite trying to explain how the controllers are "different" from the typical computer, we are at an impasse.

Do you have any feedback and/or literature that will ease their minds?

Thanks!

[The Gorn]

A while back I was collecting white papers on internet security issues for a client project.

The main thing I got out of it was that active network services running under Windows (actually, any OS) are what get people into trouble. In other words, if you have FTP, telnet, RPC, SMB (windows shares), and/or HTTPservers active on a given OS without any hardening provisions and/or while not changing default logins, then you are inviting hackers.

This implies in the reverse sense that if a given box or processor has no history of serving network connections, then chances are that it's pristine (regardless of any code YOU put on it, Randy. )

So, that's a place to start. Make a case that these units have never had the opportunity to be misused, internet services wise.