MSU Listserv


MSUNAG Archives

MSUNAG Archives


MSUNAG@LIST.MSU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV at MSU

LISTSERV at MSU

MSUNAG Home

MSUNAG Home

MSUNAG  March 2005

MSUNAG March 2005

Subject:

Re: AUP

From:

"George J. Perkins" <[log in to unmask]>

Reply-To:

George J. Perkins

Date:

Wed, 30 Mar 2005 16:41:26 -0500

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (100 lines)

On Wed, 30 Mar 2005, Bosman, Don wrote:

> After those who have to keep the machines running, citing the AUP as the
> reason of course, refuse to work on those machines they don't have
> permission to look at. Maybe systems people need "HIPPA" forms from every
> patient?

This part is easy: IT personnel shouldn't be looking at systems they "don't
have permission to look at" anyway. It's not their job, regardless of the
SAU.

As for the provision quoted in an earlier message (based on section III.2,
but also with reference to other sections such as IV.4.1) actually makes
having a policy for every system advisable. It just can't be set at the
whim of the IP staff; it has to go through channels and be publicized to
users (a HIPPA-type form would be a good idea in many cases). A local
policy also cannot override the main MSU SAU or negatively affect policies
for other external resources (a prime example would be that one may be
restricted by technical means from reading one's private mail.msu.edu
E-mail from a given PC or workstation during work hours, but nobody can make
one give one's private mail.msu.edu password to someone else so _they_ can
read one's private mail.msu.edu E-mail -- the former would be a stupid-but-
legal policy, the latter would be a stupider-and-grounds-for-University-
action-at-least policy).

> If the AUP were to be interpreted to mean one can't look at system event
> logs then every request for repair or help will have to result in a wipe
> and reload. Just like the standard last result of most manufacturer help
> desks. Common sense has to come in to the picture somewhere.

The usual Acceptable Use guideline for logs is that one should not simply
browse through them for no apparent reason (the usual catch phrase being
"no fishing expeditions). If there is some externally-derived reason to
be suspicious, that triggers one part of the SAU (V.1 et seq.) which would
allow investigation of those logs reasonably expected to have a bearing on
the problem. If a system's owner and users say it's OK (or necessary)
to investigate a problem with the system, that constitutes permission,
which triggers another part of the SAU allowing investigation of the
logs. Most practical instances are covered by one or the other of these
cases, and uninvited snooping for no explicit reason is disallowed, and
overall, that's not a bad thing.

The only grey area instance would be "preventative maintenance" types of log
checks, which are probably best done with some sort of "robotic" assistance
(e.g., a software package which compares log entries and such to known
problem patterns) instead of just reading all entries indiscriminately
anyway. This may or may not be technically against the current SAU,
depending on the details of the package used. The proposed SAU is not
finished, but from current reports to the NCC, it has at least some
provision for making this type of checking legal.

Besides the SAU, there is a set of 'guidelines' in the works clarifying the
conditions under which the Vice Provost's office would grant permission
semi-automatically and therefore would no longer need to be explicitly asked
to do so unless some affected person explicitly objects; the network
component of these guidelines is expected to come out by this summer, and
NCC has asked that a version covering "server-resident" issues which are not
explicitly tied to the network, but are affected by the network SAU, also be
considered. These would list categories of or methodology for system log
checks and similar "preventative maintenance" actions which would be
considered to have minimal impact on user privacy, and thus not violate the
intent of the privacy provisions in the SAU.

>
> Does the AUP committee have any techs, who have to live with the
> restrictions of the AUP, on it?

Since Michael Seadle of the Library is one of the NCC's representatives
on the subcommittee working up recommendations for the new SAU, he might
be someone closer to you whom you could ask for more details, but yes, there
are definitely technical people both from ACNS and from departments and
other administrative units involved (Health Team's Linda Losik, who has been
part of this discussion thread, among them).

>
> Don Bosman
> Information Technologist
> Michigan State University, Libraries
> 100 Library
> East Lansing, MI 48824
> 517-432-6123 ex 233
> [log in to unmask]
> [...]

The idea of having this discussion at a meeting is a good one.

The next MSU NAG meeting is tentatively scheduled for the afternoon of
Friday, April 22nd (start time flexible in the range of 1:15 to 3 pm).
If this is really undoable for some of the people who have been suggested
as speakers/discussion leaders, please contact me (not the whole list) and
perhaps I can find another calendar slot. I'll read through the thread
again in a couple of days and see who's willing, who's not, and who can't,
and then make an announcement.
--
                                George

-------------------------------------------------------------------------
George J Perkins http://www.pa.msu.edu/people/perkins/
1209B BPS Bldg, MSU Phone: 517-355-9200 ext 2567
East Lansing, MI 48824-2320 FAX: 517-353-4500

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
June 2023
May 2022
April 2022
March 2022
February 2022
December 2021
January 2019
August 2018
June 2018
May 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001

ATOM RSS1 RSS2



LIST.MSU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager