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:

Proportional Font

LISTSERV at MSU

LISTSERV at MSU

MSUNAG Home

MSUNAG Home

MSUNAG  October 2001

MSUNAG October 2001

Subject:

Re: NAG discussion of A/V for Pilot

From:

Doug Nelson <[log in to unmask]>

Reply-To:

MSU Network Administrators Group <[log in to unmask]>

Date:

Mon, 22 Oct 2001 14:38:27 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (115 lines)

> Number two, I would like to drop my own two cents in on this.
> Realistically, I have no idea why this isn't being done to start with. I
> find it tantamount to lunacy that we feel that we "cannot" or are
> "not allowed" to protect our systems from viruses. I'm pretty sure
> that we all have some kind of anti-virus system already up and
> running on whatever email package we are using internally (we run
> NAV on our Pegasus email). I'm not really sure who owns Pilot, but
> I am sure that each of our groups have users who use it on a
> regular basis. To put it bluntly, it is a whole in the security shema
> we have all attempted to setup. From what I am hearing the issue
> seems to be whether or not we would be in violation of AUP by
> doing so?? If this is the case, on what grounds does MSU uphold
> these policies. Are they saying that by scanning the emails for
> viruses that we as system admin's would be reading the emails?
> Are they aware that when any programs scans for a virus, that we
> do not see any of it happening, and even if we wish to monitor it
> scanning we STILL would not see the email. Are they concerned
> that we will write a program that will run in conjunction with the
> virus scanner, or in place of the virus scanner that will allow us to
> read the email. If that is what they believe or fear, I find that very
> offensive. I, for one, do not like being accused low moral values by
> folks whom I have never met, nor have they met me. Hey, if the
> post office trusts the folks that they hire off the street to sort my
> mail not to read it, you would think that MSU could trust us
> proffesionally.

It's not that anyone's accusing you or other system administrators of low
moral values, but that we're all required to take the high road in this
respect.  Perhaps some of us think that line may be drawn a bit too high,
but it's the one we're expected to live with, and it does provide a level
of consistency from location to location around campus.

As for where and how to do virus protection, we still need to do
some work in that regard.  In general, though, users should run virus
protection on their own workstations, and system administrators should
do virus protection on shared (non-personal) data.  That should adequately
protect systems from the viruses and worms themselves.  That may not
protect fully against side effects such as filled disks or poor system
performance from traffic overload, but there are other ways to deal with
those problems.

> Ok, hard as that is to put aside, let me wonder this. Is MSU
> worried that by doing any of the above we would be violating the
> users 4th ammendment rights? Let me clarify something here;
>
> [portions of ECPA and comments omitted]

It's a bit simpler than that, although this may have been part of the
thinking in creating the AUP.  It's clear that the AUP is more restrictive
than the ECPA requires, and is certainly different from the standard
corporation business model.  One of the most notable differences is
that personal e-mail is permitted, particularly under a user's Pilot
e-mail account, but in many cases this would also extend to a user's
departmental e-mail box, assuming it is under the user's name.

The MSU AUP creates an expectation of privacy for personal communications
and data storage for all members of the MSU community.  The Network
Communications Committee (NCC) is working on developing the interpretations
of the MSU AUP, but the gist of it with respect to communications and data
storage is that data is presumed to be personal when associated in any way
with an individual, unless it is stored in a location explicitly declared
to be for non-personal (e.g. business or research) data.  Such a declaration
needs to be made known to the individual in advance, preferably by the use
of a system-specific AUP.

Any data that is deemed to be personal data is not to be accessed, scanned,
etc., without the express permission of the user, the Vice Provost's
office, or other legal means.  In general, if the user gives permission for
a specific activity, then, and only then, can the system owner or manager
perform that activity.  I think the NCC will have to give some thought to
whether a "shrink-wrap" policy notification and/or consent (e.g. a login
banner) is satisfactory, or whether an explicit signoff is required.

> If employers are exempted under this provision, then presumably
> they may monitor electronic communications in order to promote
> quality control, prevent loss of trade secrets, investigate employees
> suspected of wrongdoing, deter personal use of company property, etc.

At MSU, the authority under this exemption has been given to the Vice
Provost's office, barring a specific system AUP to the contrary.  And
further discussion may be necessary as to how far a system AUP can go
in this respect.

> Under the consent exception, an employer may intercept electronic
> communications if the prior consent of one of the parties to the
> communication has been obtained. (18 U.S.C. § 2511(2)(d) (1994)).
> To come within this exception, an employer need only acquire the
> implied or express consent of one employee in an employee-
> customer or employee-employee communication. It is important to
> remember that the ECPA does not preempt stricter statutes in
> states, such as Maryland, which require the consent of all parties.
>
> An employee will likely be deemed to have given consent if, having
> knowledge of the employer’s policy, he or she continues to use the
> e-mail system. To this end, a written policy is preferred because all
> parties will have expressly consented to its terms. Even when the
> policy is written, the employer would be ill-advised to monitor e-
> mails to a degree that exceeds the scope of the policy. For
> example, in the context of telephone calls, the courts agree that an
> employer is not privileged to continue listening to conversations of
> a purely personal nature. Further, a policy that merely suggests
> that monitoring may be done may not be sufficient to create
> implied consent.
>
> Now I know that we have a acceptable use policy in place at MSU,
> and I also know that at least for our division in order to log onto our
> network you must click OK  that you have read and understand the
> policy. Seems pretty clear cut to me..

See above.  An individual at MSU can acknowledge understanding and
abiding by the MSU AUP, without providing any reason for MSU (as
employer, or otherwise) to assume that there is any consent for
monitoring e-mail or other communications.

Doug

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