Educause Security Discussion mailing list archives
Re: Securing common access computers
From: Terence Ma <Terence.Ma () TUN TOURO EDU>
Date: Wed, 24 Mar 2010 14:44:06 -0700
We use Deep Freeze also. We used/tested Clean Slate for about a year. In our environment, it did not meet our needs as well as Deep Freeze. Our staff really likes Deep Freeze. Best, Terence P. Ma, PhD Chief Information Officer Touro University Nevada 874 American Pacific Drive Henderson, NV 89014, USA P: 702-777-1805 M: 702-469-1770 F: 702-777-1736 E: terence.ma () tun touro edu From: The EDUCAUSE Security Constituent Group Listserv [mailto:SECURITY () LISTSERV EDUCAUSE EDU] On Behalf Of Witmer, Robert Sent: Wednesday, March 24, 2010 9:09 AM To: SECURITY () LISTSERV EDUCAUSE EDU Subject: [SECURITY] Securing common access computers Even though we require every student to have a laptop computer, historically our organization has provided personal computers in common areas around main campus/remote campuses for students to access specialized software, print papers, access email or their student accounts, etc. I'm wondering how other organizations are securing their common access computers located in pc labs, library, etc. Specifically, from a hardware point of view, does someone inventory every device for hardware key loggers/recording devices? Do you require users to log into the machine for accountability? Do you restrict users from executing programs other than those you've loaded on the pc? Thanks, Bob Please consider the environment before printing this e-mail.
Current thread:
- Securing common access computers Witmer, Robert (Mar 24)
- <Possible follow-ups>
- Re: Securing common access computers Patrick Goggins (Mar 24)
- Re: Securing common access computers Zach Jansen (Mar 24)
- Re: Securing common access computers Cal Frye (Mar 24)
- Re: Securing common access computers SCHALIP, MICHAEL (Mar 24)
- Re: Securing common access computers Amber Weishaar (Mar 24)
- Re: Securing common access computers Patrick Goggins (Mar 24)
- Re: Securing common access computers Todd Britton (Mar 24)
- Re: Securing common access computers David Gillett (Mar 24)
- Re: Securing common access computers Terence Ma (Mar 24)
- Re: Securing common access computers Michael Sana (Mar 24)
- Re: Securing common access computers SCHALIP, MICHAEL (Mar 24)
- Re: Securing common access computers Michael Sana (Mar 24)
- Re: Securing common access computers Brewer, Alex D (Mar 25)
- Re: Securing common access computers Witmer, Robert (Mar 25)
- Re: Securing common access computers James R. Pardonek (Mar 25)
- Re: Securing common access computers Zach Jansen (Mar 25)