Re: Monitor Services on Windows machines

• Previous message: Levinson, Karl: "RE: [despammed] Utility to determine who deteled files"
• Maybe in reply to: MOHESOWA BYAS: "Monitor Services on Windows machines"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: Thu, 27 Feb 2003 08:10:19 +0100
From: "Robert Formanek" <robert.formanek@wipo.int>
To: <work@silverwraith.com>

Avleen:

Please keep in mind that the original aim was to monitor that users do not shutdown or start services that they are not supposed to. This can and should be covered using a simple "if you do that I will do that" rule.

> Ok, I accept that there are some situation where an automatic restart
> may be an option. I still feel it's a bad idea. I mean, isn't it better
> to find out *why* a produciton system just went offline, before blindly
> bringing it back?
> This partly assumes you have some form of redundancy.

Of course, you want to find out what has happened on a server before you do anything, but troubleshooting for the sake of troubleshooting won't be accepted in most business I know, not even the non-for-profits. Business has to continue, if you want to troubleshoot - do it after-hours. Don't get me wrong, I am not opposed to your idea, but the balance between 'security' and 'business' has to be kept.

>>> The security implications are horrible! :-)
>> That may depend on the Security officer ;-)

> Absolutely not!

Yes, I know. Everyone in every company is responsible, naturally. But, I know at least 1.000.000 Examples where employees don't feel the same... But, this will lead into a different discussion.

Regards,
Robert

• Next message: Avleen Vig: "Re: How do you patch yours? (was: Monitor Services on Windows machines)"
• Previous message: Levinson, Karl: "RE: [despammed] Utility to determine who deteled files"
• Maybe in reply to: MOHESOWA BYAS: "Monitor Services on Windows machines"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]