RE: SUS server
From: Brian W. Spolarich (bspolarich@nephrostherapeutics.com)
Date: 04/07/03
- Previous message: Juan José Sánchez Mesa: "Isolating Windows Applications"
- Maybe in reply to: mhunt: "SUS server"
- Next in thread: Bill Mote: "RE: SUS server"
- Reply: Bill Mote: "RE: SUS server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 7 Apr 2003 14:31:25 -0400 From: "Brian W. Spolarich" <bspolarich@nephrostherapeutics.com> To: "Thane Walkup" <twalkup@quorumreview.com>, <focus-ms@securityfocus.com>
Thane Walkup wrote:
> One VERY good reason not to run SP3 is possible HIPAA and 21CFR11
> regulation issues - since the license for SP3 technically gives
> Microsoft unfettered access to your PC, any company under those
> regulations could be in violation of those regulations.
>
> This affects just about any medical facility.
One can configure the SUS client to point at an internal SUS server via Active Directory GPOs. I suspect that if you point it at a non-functional URL the auto-update component will essentially be disabled, and it may be possible to disable it completely via GPO (haven't looked).
-bws
<b>
----------------------------------------------------------------------
Block Spam, Smut & Viruses
SurfControl E-mail Filter for SMTP & Exchange leverages multiple layers of
technology including filtering embedded and attached file content. Rid your
enterprise of unwanted content.
http://www.securityfocus.com/SurfControl-focus-ms2
Download your free fully functional trial, complete with 30-days of free
technical support.
----------------------------------------------------------------------
</b>
- Previous message: Juan José Sánchez Mesa: "Isolating Windows Applications"
- Maybe in reply to: mhunt: "SUS server"
- Next in thread: Bill Mote: "RE: SUS server"
- Reply: Bill Mote: "RE: SUS server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
