I appreciate it Mr IT guy, but these changes will occur in a power plant with 150 computers and no domain controller.
Each computer serves a very specific function (e.g. historian, process controller, operator interfaces, etc...).
I mentioned in a previous post that we cannot simply use the computer and see if it works. We have to have a testing plan and implement it.
What I had envisions, which may not be accurate, is a testing procedure (perhaps implemented via a custom designed testing program)that can:
e.g. - for closing/blocking ports
1. monitor traffic coming from and to the active main software or the device as a whole.
2. veryify that it is functioning properly.
e.g. - uninstalling software
1. verify that "this doesn't adversely affect the main functionality of the system".
e.g. - installing firewall
1. verify that no needed ports are blocked.
Again, this is in a power plant. I cannot shut down the plant if I want to keep my job. We can not implement changes nor test changes in a adhoc fassion. Everything must be planned. We cannot simply use the device for a couple of days and say "thats our test"; if the test is a failure in the production environment, chances are high that the plant will be shut down and I will be fired.
So....