Subject: | |
From: | |
Reply To: | |
Date: | Tue, 12 May 2009 18:47:38 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Then what is the point of having NAC in the first place? We limit their access based on antivirus and update status... why not just let anyone on the network in any configuration?
Michael Stanclift
Network Analyst
Rockhurst University
http://help.rockhurst.edu
(816) 501-4231
________________________________________
From: Cisco Clean Access Users and Administrators [[log in to unmask]] On Behalf Of Joe Feise [[log in to unmask]]
Sent: Tuesday, May 12, 2009 4:58 PM
To: [log in to unmask]
Subject: Re: Freedom and the community.
On Tue, May 12, 2009 14:30, Steven Fischer wrote:
>
> By enacting this policy, the school is limiting:
>
> 1. Their legal exposure and liability.
Actually, on the contrary.
By searching non-owned computers for software, it could be argued that the
school then has lost common carrier status and has become liable for all
illegal content on such computers.
That could also mean unlicensed software. Do you know if that copy of MS
Office on the student's computer is licensed???
In other words, you'd open a whole new can of worms, which you could only
prevent by not allowing any non-organization-owned computers on the
network.
If that's your policy, fine. Quite a number of companies indeed do that
(although they may make exceptions for the CEO's personal laptop...)
-Joe
|
|
|