[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Full-Disclosure] Re: Microsoft Security, baby steps ?[Scanned] [Scanned] [Scanned]
- To: full-disclosure@xxxxxxxxxxxxxxxx
- Subject: RE: [Full-Disclosure] Re: Microsoft Security, baby steps ?[Scanned] [Scanned] [Scanned]
- From: Luke Scharf <lscharf@xxxxxxxxxx>
- Date: Fri, 19 Mar 2004 09:22:59 -0500
On Thu, 2004-03-18 at 14:40, James P. Saveker wrote:
> That's the *real* challenge of trying to secure a network - the vast gap
> between what could be done given the proper mandate and financing, and what
> you can usually actually deploy with the mandate and financing you actually
> got. :)
Plus, in the case of VT, many of the machines on campus are owned, for
instance, by the students who use them. It's a little harder to impose
something like a domain and SUS on them -- when it's their own machine.
The current policy, AFAIK, is "if your machine does something bad, we'll
turn off the network port and sort it out later."
-Luke
--
Luke Scharf, Systems Administrator
Virginia Tech Aerospace and Ocean Engineering
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html