Educause Security Discussion mailing list archives

Re: Screensaver Timeouts


From: "Penn, Blake" <pennb () UWW EDU>
Date: Tue, 13 Sep 2005 15:01:15 -0500

Forgot to mention ... another potential solution for those of you concerned
about HIPAA to consider is one of the several prox card authentication
solutions (XyLoc from Ensure Technologies comes to mind, although there are
others).  These solutions may be expensive if you have lots of personal
workstations, but can make sense if you share workstations a lot or have a
large number of kiosks in your environment.  They simply eliminate the need
for a true user "log in" entirely, and the related hassles as well.

__________________________________
Blake Penn, CISSP
Information Security Officer
University of Wisconsin-Whitewater
(p) 262-472-5513 (f) 262-472-1285
e-mail: pennb () uww edu


-----Original Message-----
From: Sherry Callahan [mailto:scallahan () KUMC EDU]
Sent: Tuesday, September 13, 2005 2:14 PM
To: SECURITY () LISTSERV EDUCAUSE EDU
Subject: Re: [SECURITY] Screensaver Timeouts

Our organization also has implemented a 15-minute timeout for screensavers,
based on NIST recommendations.  Good luck with implementing this as a new
policy, as this is one of those settings that usually causes very loud
screams from the user community.


Sherry Callahan
Director, Information Security
University of Kansas Medical Center
3901 Rainbow Blvd, MS 3024
Kansas City,  Kansas 66160
913-588-0966

Neal-Clonts () OUHSC EDU 9/13/2005 1:01 PM >>>
Fellow Security Professionals,

Our campus is looking at implementing a policy for screensaver timeouts and
we are wondering if anyone else currently has this type of policy in place.
If you do have a policy on screensaver timeouts, how many minutes do you
require before the screensaver is activated?

Neal Clonts, CISSP, CISA, MCP
Information Security Services
University of Oklahoma Health Sciences Center Office Phone: 405-271-2476,
Option 2 Cell Phone: 405-255-2999
Website: http://security.ouhsc.edu <http://security.ouhsc.edu/>


Attachment: smime.p7s
Description:


Current thread: