Slashdot Mirror


Should Colleges Monitor Students' PCs?

dancedance asks: "I am a CS student at a small Liberal Arts college. Like most academic institutions, we have to deal with worm-infested computers being brought into the network from the outside. In the past the school's response has been to require all windows computers to install the virus software provided by the school. Although this helped protect the network, it was certainly not a complete solution, especially at the beginning of the school year. This year computing services is taking a more proactive approach to network security: it is requiring all Windows-based computers to install software which will allow the school to automatically update virus software, apply windows patches, install software 'deemed necessary' for network security, and 'report on the status of your computer'. This seems like a 'one step foreword, two steps backward,' approach to network safety as I fear that, under this system, a malicious user would only have to break into one central system to wreak havoc on the entire network. Are my concerns about this system well founded, or is this less of a problem than I make it out to be? Are similar policies getting implemented at other academic institutions?"

35 of 554 comments (clear)

  1. Education by agent+dero · · Score: 5, Interesting

    Colleges are for education, for those students who most likely won't know already about protecting their computers, make them take a class on how to do it. And if their computers turn out to be infected afterwards, ban their MAC from the network until they prove otherwise.

    Students are at college to learn. Educate them :)

    --
    Error 407 - No creative sig found
    1. Re:Education by LostCluster · · Score: 5, Insightful

      MAC banning is ineffective since nearly every card these days can have it's MAC address reprogramed. Real solutions are tied to the student's university login account which is associated with their other student records.

    2. Re:Education by EvanED · · Score: 5, Interesting

      You don't want to disable this though, so they can still use lab computers.

      Here at PSU you must register your computer's MAC address and your dorm room and the port you plug your computer in within your room. If you change your MAC address from what's on file, you can't connect. If you plug into another port, you can't connect.

    3. Re:Education by BillyBlaze · · Score: 5, Insightful

      If you know how to reprogram your MAC address, you probably also know how to keep your computer virus-free, so banning by MAC address is a perfectly good reactive solution to viruses until they start randomly changing MAC addresses. And then you could ban unregistered MAC addresses, which is fine until viruses sniff and copy other MAC addresses, which isn't always possible.

    4. Re:Education by BobPaul · · Score: 5, Informative

      This is exactly what our school does. When you first go on the network you're given a 10. ip address. Any DNS calls resolve to an oncompus webserver that allows you to register your computer (ie, if you load your home page, the school computer responds instead). When you register, you enter your username and password (or create one) and your computer is scanned for known security vulnerabilities (are you vuln to Blaster, etc) and any broadcasting virii. If you are, you are not even given a 10. address lease until you install patches (free CDs available from ITS or Dorm staff.) Once you've installed, you have to call ITS and ask to be unbanned.

      You don't have to use the schools antivirus, but if you get a virus that broadcasts you are DHCP banned. Just like before, you have to ask to be unbanned and you must re-do the registration process from before (since your mac was removed from the "good" list).

      While the computer is scanned, we are not required to install spyware. I think our policy is a good trade off, campus required spyware is too much. I'd move off campus or hurry up and switch to Linux.

    5. Re:Education by DrEldarion · · Score: 5, Insightful

      Generally, though, the set of people who know how to change their MAC address and the set of people who keep their computer virus/worm-free intersect pretty well.

    6. Re:Education by binarybum · · Score: 5, Interesting

      I like this restricted subnet leper colony idea. A healthy network is one that runs well independently of how crapped out end nodes are. I think in this day, it is best to develop networks that assume that every node is a virus-ridden maggot that could potentially be a threat. Networks that rely on users keeping their systems tidy will not scale well and will invetibaly become weaker by not having to deal with minor day to day issues due to an intially placid user base.
      By moving "leper" systems into a restricted subnet until they prove themselves cured, you minimize the risk to your infrastructure without completely terminating access. Additionally, people that let their systems become infested usually will not be power users and may not even notice/mind the restricted access state.

      --
      ôó
    7. Re:Education by Anonymous Coward · · Score: 4, Interesting

      As a network admin (Network Nazi, thank you very much) I know the effects of having just one compromised pc on the network. With all the viruses out there that spoof email addresses, I know instantly when an infected pc comes online (I get an email from every server that gets attacked by a virues...)

      On one hand, I commend the university staff for trying to keep everyone safe. Nothing worse than one infected pc spreading through the windows "security flaw" flavor of the week and dragging everything down.

      On the other hand, they are taking on a huge responsibility to keep the students pc's running. Case and point - we demand that everyone on our network runs McAfee and is kept up to date with patches. One lady in admin installs McAfee so that she can use her home pc to connect (via Cisco VPN,) and the whole pc stops blows up. I ended up spending 10 hours (6 hours trying to fix what went wrong, the other 4 giving up and reloading the damn thing.) Add to that getting grief the whole time because "This wouldn't have happened if I didn't install that.." Nevermind the spyware that was already installed.

      Moral of my rant? Don't do this kind of thing unless you have a mass of cheap labor (college kids who are on work/study,) and are allowed to fix what went wrong when it most likely will.

  2. It may not be all it's cracked up to be... by jgrider · · Score: 5, Insightful

    Perhaps you might want to (anonymously) remind them that by assuming management of individuals computers (not uni. owned) like that, they are also assuming some liability. Who gets sued, if they miss a virus or something, and it eats your term paper... theoretically you could sue them... I bet they haven't thought of that.

    1. Re:It may not be all it's cracked up to be... by fitten · · Score: 5, Insightful

      The network is owned by the school. If you don't agree to the terms, with a waiver of liability, you don't use the network. Simple enough. If you don't agree with it, move off campus and get your own ISP and network. If you can't afford to live off campus, either do without a computer because you don't agree with the terms, or agree to the terms and use their network. Simple. There is nothing complicated here.

  3. Not unreasonable by Rhesus+Piece · · Score: 5, Informative

    My campus will disconnect any computer it finds vulnerable. I suppose this could be considered the next step in that direction, but this time students have a way to be sure that they don't end up disconnected at an inconvenient time.

    If this were my school, however, I think I'd find it easier to make my computer not look like a windows machine to the network, then deal with stuff on my own instead of trusting their software.

    1. Re:Not unreasonable by ScrewMaster · · Score: 5, Insightful

      If it were my school, I think I'd find it easier to make my computer not be a Windows machine. Which begs the question: how is this outfit going to handle non-Windows systems? Are they going to force a similar level of compliance on Mac or Linux users? Personally I wouldn't want to have my machine subject to such regulations: I don't know as I would trust an IT department to ... well, let's just say I don't know as I would trust an IT department. I particularly wouldn't trust them with unfettered remote access to my personal property. I would also want to know what criteria were used in the selection of the software suite to be installed: if it's just because they got a good deal from Symantec I would have a problem with that too.

      --
      The higher the technology, the sharper that two-edged sword.
  4. alternate invasive uses by Shmoe · · Score: 5, Insightful

    next step:

    request a hard drive scan for copyright owner's works.

    I'm not sure where the happy medium is between total computer intrusion and none at all. It's hard to trust anyone else messing around with my computer with software i MUST install.

  5. Just cut them off by Spetiam · · Score: 5, Informative

    Personally, I'd much rather just get cut off and be notified why. I don't like the idea of giving over control of my computer like that.

  6. It's a good thing and a bad thing by Coldeagle · · Score: 4, Interesting

    I believe that as long as it's network security things, it's a good thing; however I would investigate any software they want to install on my system before I say yes or no. My work has a similar policy and I don't really have a problem with it on my laptop, because I did some checking and they can't do anything but patch security holes, and it lakes anything that infringes on privacy (such as reporting what websites are being hit, password loggers, etc), so if the software it self doesn't infringe on privacy, I think it's a good thing, well with Window$ machines at least :P

  7. Use a carrot, not a stick by Aneurysm9 · · Score: 4, Interesting

    My school has taken a similar route, however, we're not pushing patches onto end users, but requiring that they authenticate and verifying that they're up to date before letting them out into the wild. If they fail the verification they're provided resources to update their computer, but we don't push the patches without their consent.

    --
    There was Cowboy Neal at the wheel of a bus to never-ever land.
    1. Re:Use a carrot, not a stick by Frater+219 · · Score: 5, Insightful
      Some steps I think might be useful:
      • Be honest and up-front with security advice. You know that Windows is a massive security risk. You know that Linux, BSD, and Mac OS X systems aren't virus-proof, but that they have on average a lot fewer problems. You know that a Windows system can be operated reasonably securely only if it's protected with up-to-date anti-virus software, zero-day Windows Update, and careful choices of third-party software. Communicate these facts.
      • Let students make choices freely, but offer them the tools you think are worth using. Don't require them to install particular software -- especially not something they will find untrustworthy, like monitoring software. Instead, make tools easily available which you have found to be valuable. That may mean a site license for your favorite anti-virus software. It may mean handing out Knoppix CDs. Or it may mean selling inexpensive NAT "firewalls" in the campus store, and giving the Help Desk the setup instructions.
      • Support smart choices, not just popular ones. Sure, most of your students use Windows. Some don't. Of the Windows users, most use Internet Explorer. Some don't. Make sure the ones who don't are welcome. The campus Web site needs to work in Safari, Konqueror, Galeon, and Firefox. The wireless network can't rely on a Cisco client program that only works properly on Windows. The help desk needs to be able to answer Mac OS X questions and some basic Linux desktop questions -- or, if not, refer them to someone who can, like the campus LUG.
      • Monitor for problems that harm others -- don't snoop. Ideally, every border on your campus network should have enough IDS to detect portscans. If not, no big deal -- monitor what you can. You're looking for signs of viruses, break-ins, bots, backdoors. You aren't looking for porn, MP3s, or passwords. You do not have the right to access students' files on their own computers; those are their property. (Don't claim to have that right in your AUP. You still don't have it.)
      • Cut off compromised systems. When you find a compromised system, cut it off the network first, then contact the owner. Use MAC-based blocking -- automatic, if at all possible. If your network registration system (you do have one, right?) associates the wired and wireless interfaces of a given computer, make sure to block both, since XP will wake up wireless if the wired cuts out. (Really, this is not all that much Perl!)
      • Don't punish accidents, but don't shield students from their choices' consequences. If a student's computer is infected with a virus and cut off, that's a bummer for the student. But it's probably in part the consequence of that student's choices. (After all, the Mac user next door didn't get the virus, and neither did the XP user who installed this week's patch the day it came out.) Your IT staff are not obligated to provide free disinfection services or OS reinstalls, and you are entitled to bill for clean-up, just as the residential life office would if someone trashed their room. The purpose here isn't punishment; it's simply to place the costs on the persons whose choices incurred those costs.
      • Some troublemaker freshmen will be your student computing assistants next year. Not all of them will. But you will hear about students who are doing "bad things" on the network. (You will hear -- you probably don't have to scan for them.) Students who act up, portscan their dorm, index the SMB shares of all the lusers who didn't realize they were exporting all their porn, piss off the systems staff, and make crazy demands are probably not sociopathic techno-crooks. They will get over it. Call them in and make friends with them. Some will start being useful to others. Hire them. Others will be nasty and malicious. Get them expelled.
      • Maintain
  8. Same experience by AgentOJ · · Score: 5, Interesting

    I'm in the same boat as you. I work for computer services at my college, and we went through the exact routine you did. Originally we were using Novell (ugh) to push the antivirus updates, but we're moving away from Novell next year. I'm still not sure exactly what we're going to be doing as far as mandatory updates go, but something needs to be done. Our firewall is fine for blocking worms coming from the outside, but the minute a student opens the wrong kind of attachment, all hell breaks loose on the internal network.

    I've brought up this issue with my superiors, but they have always told me that any intra-network segregation would be too costly for our meager budget to handle. Though draconian, it has gotten to the point where I almost feel that we should turn off most outbound connections at the switch level between dorms...that way the problem is confined to a single dorm. If a user could give good reason why they needed ports opened, we could grant them that.

    Nothing, however, will stop users from opening attachments. We've tried user education, and it just doesn't seem to work. Aside from banning outlook (our biggest problem is with mass-mailing viruses) on campus, does anyone have a cost effective solution that a small private college can implement?

  9. Um, shhhh! by acidrain · · Score: 4, Funny

    Think man! Stop drawing attention to it, and start trying to hack it. Don't be a fool!

    --
    -- http://thegirlorthecar.com funny dating game for guys
    1. Re:Um, shhhh! by Quasar1999 · · Score: 4, Funny

      You're one smart cookie... but unfortunetly we're looking for a cracker...

      Bada Boom!

      Thanks folks, I'm here all week!

      --

      ---
      Programming is like sex... Make one mistake and support it the rest of your life.
  10. Balancing out the evils by h2oliu · · Score: 5, Insightful

    Having gone to a liberal (in all senses of the word) arts college, and now being an IT manager responsible for a few hundred machines I can understand both sides.

    Yes. There is a more central location for someone to attack. However, the average user doesn't take care of their system. In this case, you have to defend a single, actively malicious individual targetting your environment, rather than having to deal with the after effects of the bzillions of non-targetted attacks.

    Unfortunately, as usually happens in situations like this, it is the conscientious user that has their system's security lowered. While, on average, the general security of the population is improved.

    In my new position I can completely understand it.

    When I was in college, I would have despised the very concept.

    Overall, I think that this is probably better for the system. But I can sure understand why the "good" ones would feel like they are being punished for someone elses actions.

    Side note: The people who are truly technical will probably be running some flavor of Linux/Unix so they won't be affected by this.

    --
    Ok, I give up, why you?
  11. Don't do this by EvanED · · Score: 5, Interesting

    I would forgo high speed internet access and dial up, then use lab computers for fast internet access before I would submit to this.

    Simply cut off any computer that is sending packets trying to exploit a hole, like Blaster or whatever. Hell, commercial ISPs don't even do this unless it's really really bad, let alone require such software to be installed.

    I would have no problem with requiring users to install the latest security patches or virus software and keep definitions up to date, but no campus network service is gonna be installing stuff on my computer.

  12. Re:apples? by kfg · · Score: 4, Funny

    I didn't hear apples mentioned?

    We polish 'em up and give 'em to teacher.

    KFG

  13. University ResNet Responsibilties by KidGlory · · Score: 5, Informative

    I just attended ResNet 2004 which is a conference devoted to the Information Technology departments of all Colleges and Universities across the globe. There are usually around 300 participants and many other who do not make the guest list. I think the biggest conversation among those at the conference was how where is the line between appropriate and not appropriate actions to help keep the networks clean as well as the students computers. You can check out http://www.resnetsymposium.com for the website or http://web.princeton.edu/sites/resnet/ for a list of those who attended. There is also a listserv for @ http://listserv.nd.edu/archives/resnet-l.html. All of these sites will give you contacts for people who have answers to your questions. A trend for schools is purchasing solutions such as Perfigo www.perfigo.com or Bsi's campus manager http://www.bradford-sw.com to help them do their dirty work.

  14. Re:apples? by AgentOJ · · Score: 5, Informative

    I work for computer services at my college, and we have a number of Mac labs. We have absolutely no problem with these whatsoever. However, it's impossible in a college setting to have a completely homogeneous selection of platforms. We need our PCs for everything from our accounting courses (some specialized software) to our comp sci courses (Yeah, they force us to use Visual C++, switching to .NET next year).

    In all honesty, at a small college like the one I attend, there's a good reason to go with PCs from a financial standpoint: Despite educational discounts, Macs still cost more than PCs. That's a simple fact. Secondly, Microsoft gives AMAZING educational discounts for their software. I'm not talking about the "Educational" licenses for students, but rather we get X amount of free software per year, which is really a boon for our computer services department. We recently got our budget cut in half (management isn't comprised of the brightest of individuals), so the financial aspect is really appealing.

    If we had the option to run all Macs, I'd swing for it in a minute, as far as my duties for computer services are concerned. It would make my job a helluva lot easier. However, we don't have that option, and I think you'll find that the same is true for most small colleges.

  15. The college is question is Wheaton. by Vellmont · · Score: 4, Interesting

    A little investigation reveals Mr Sanford (dancedance) goes to Wheaton College in IL. Why are you so vague about which college is doing this Mr Sanford?

    --
    AccountKiller
  16. Campuses, workplaces and ISPs by Brandybuck · · Score: 5, Insightful

    Why must a college campus be treated any differently from other organizations? If you're an employee, grad student, or are otherwise obligated to connect to their network, then they should supply you with the computer, just like an employer. My employer does NOT come to my home and tell me what software must be on my personally owned computer. They have the right to prevent me from accessing their network from home, but no further.

    If campuses are providing internet access as a benefit to students, then they're acting like ISPs. If a small mom-n-pop ISP can handle issues like this, then so can a college or university.

    Most campuses seem to be a combination of both. They have their local network(s) with gateways to the internet. So they have to act like both businesses and ISPs. Both the campus AND the students need to realize this.

    --
    Don't blame me, I didn't vote for either of them!
  17. Reading too much Penthouse... by hoggoth · · Score: 4, Funny

    > I am a CS student at a small Liberal Arts college

    When I read this my mind immediately expected it to be followed by something like:

    "I am a CS student at a small Liberal Arts college. I've never been lucky with girls and nothing like this has ever happened to me before. One night I was up late in the laundry room and this beautiful girl walked in..."

    --
    - For the complete works of Shakespeare: cat /dev/random (may take some time)
  18. This is true by captainmoo · · Score: 5, Informative

    Any time an institution requires software to be installed at all, it's a red flag that says that institution is doing something else wrong. While it's a good idea for students to keep their computers up to date with virus scanners and security patches and the like, it's not a good idea for the institution to take that responsibility away from the students themselves.

    I worked in the NOC here at the University of Washington, and the policy was to kill ethernet ports of infected computers. It was determined whether the computer was infected by analyzing traffic flow to/from the computers and picking out patterns characteristic of common worms and viruses. This not only helped alleviate the problem by preventing the viruses from propagating, but forcing the user to take action to get the wallport reactivated increased awareness.

    The UW also makes CDs with the latest virus software and patches available for free from the bookstore and various other places on campus. This way users don't have to connect to the internet to clean and patch their systems, and it makes the job easy through automated software. This kit doesn't, however, let the institution perform updates automatically or install arbitrary software. The university also maintains a repository on the LAN containing virus definition files, and the virus scanner on the CD is set up to download these automatically.

    So aside from the security implications the poster mentions, there are privacy issues with allowing the institution to install arbitrary software. By forcing the user to take action in order to use the resources provided, it eliminates the privacy concerns, and raises awareness of the greater issue.

  19. There will be no request, it will just happen. by twitter · · Score: 5, Insightful
    From the link above:

    As part of Microsoft's Strategic Technology Protection Program, and in response to direct customer need for a streamlined method of identifying common security misconfigurations, Microsoft has developed the Microsoft Baseline Security Analyzer (MBSA). MBSA Version 1.2 includes a graphical and command line interface that can perform local or remote scans of Windows systems.

    It's a backdoor, they can do anything they want to your system. It can scan, read and write files. It's like giving them root, so they own your computer.

    With abilities like that, do you think they will bother to ask you when it comes time to satisfy some big power? RIAA requests to eliminate your music collection will be honored. CIA/FBI requests to search and monitor suspicious characters will be carried out. Anyone who would require such powers will abuse them.

    It's as unAmerican as all hell. Such scans would obviously violate your fourth amendment right to be secure in your personal papers. At State schools, the network is public and at many it has been paid for by special student fees, so this is an abuse of a public network, comparable to wholesale wiretaping, post violation and even bugging, if your computer has a microphone they can turn on. At private schools, ownership of the network depends on the amount of public money paid to build it and is encumbered by the fact that they will want to connect it to other public networks. That desire to connect to public networks should be used to enforce the kind decent behavior.

    All of the other services mentioned can and should be required of Windows machines but Winblows itself should be optional. Up to date virus definitions are helpful but generally too difficult for the end user to keep up with. All the services besides system monitoring are helpful to the user and the school. If the user chooses to be rooted as a condition of running Winblows, that's their choice.

    Operating systems that don't have problems should be encouraged by the University. Not being rooted can be one more reason to run Linux, Mac and other OS. Traffic should still be monitored. If my computer starts belching spam, I'd be happy if my ISP sent me a message and chopped the line. There's a big difference between that and requiring read write to my computer.

    --

    Friends don't help friends install M$ junk.

  20. Then it is simple: by Avihson · · Score: 5, Interesting

    You do not connect!

    If you want to use the facilities, you follow the rules. The only vote you get is with your feet. Their house - their rules.

    If I didn't trust the IT department, I would never hook up anything that I personally value to their infrastructure. I would (ab)use their equipment, and save my data on a thumb drive.

    I've been that route: last semester, I was a part-time instructor at the local CC and knew that the IT Dept was full of mediocre windows power users - not even an MCSE in the bunch.
    I was hired to teach a Linux course, and was not permitted to connect those "insecure" machines to the LAN! Before every lab session, we had to disconnect the lab switch from the network, so there was no possibility of "hacking" into the school's network. I wasted about 15 minutes trying to educate the IT manager, before I figured it was better to let him stew in ignorance, since they were not paying me to educate him.

    Never argue with an idiot, they drag you down to their level and beat you with experience.

  21. Re:apples? by AgentOJ · · Score: 4, Informative

    Before the rash of viruses over the past two years, I would have said that the software costs outweighed the downtime and maintenance costs. I would say that now, no, they don't outweigh the costs, but when they are paying us students (who do 99% of the cleanup when a virus hits) close to minimum wage, it probably is still cheaper for them to take the free flawed software. And yeah, I know the job has a crappy pay rate, but you can't beat how flexible they are around exams, homework, etc.

    The 'free' software is generally used, as most of it is comp sci department stuff (VC++, .NET, etc), or some web design stuff, or Word, etc. So yeah, overall it is used for the most part.

    I can't think of the name of the software package off the top of my head, but I remember there was some large-scale app that went to waste, and the copies are still sitting in a box in storage from two semesters ago. And due to the licensing agreements, we can't sell or give it away, so it kinda sucks.

  22. Liberal Arts colleges and OS choice by wing03 · · Score: 4, Interesting

    A few factors to consider here

    1. Liberal arts college
    2. Artsy fartsies
    3. Starving students or parents who are budget conscious.

    I went to a liberal arts college too, and as a graduate looking back on that experience, I have one observation.

    As much as we liked to think we are expanding our minds, thinking outside of the box and bucking trends, the majority of us still went for the path of least resistance and followed the herd because it was so difficult to be the iconoclast and march to the beat of a different drum.

    What that means is that the vast majority of computers will be M$ based. A few windbags will talk about Linux vs the evil corporate M$ (not having any idea what BSD, BeOS or any other marginal open source OS is). They will either try to install the OS or get a friend to do so.

    Over time, they'll not have a clue about what's going on, go back to Windows, graduate and become a sales and marketing jockey for one of those companies they crapped all over during their idealistic days in university.

    But hey, what do I know? I'm just another jaded IT worker who happens to have a liberal arts education....

  23. Management by aynrandfan · · Score: 5, Funny
    management isn't comprised of the brightest of individuals

    People in management can get very bright; you just need to burn them at a higher temperature until they glow a nice, pretty blue.

    :)

    --

    ----

    "Ours was a free culture. It is becoming much less so."-Lawrence Lessig

  24. A good thing your experience is far from universal by orthancstone · · Score: 4, Informative

    You sound like you went to school where the department was run by crappy CS profs. I got my undergraduate degree at a liberal arts college and 99% of my Computer Science experience there was gained while using Linux (and even a bit of Solaris my first year) systems. We all knew BSDs, open source alternative software, and more. Many of us used it daily; some developed and tested for the open source community. Windows was pretty much shunned by all but one prof. Even the necessary evil of connecting to the IT Windows systems was considered highly undesireable.

    In reference to the topic at hand, I have to say this University is taking the wrong course of action. My school took the "lock the port" approach. Quite simply, if they could tell your computer was infected and you weren't doing jack to fix it, you lost your internet. Didn't like it? Well fix it. Otherwise you're gonna be going to another dorm room to try to hook up (and remember, your roommate isn't gonna like you either, cause you cost both of you an internet connection).

    PS to grandparent of this message - The author states he/she is a CS student; the author never states the CS department is the head of this action (I'm strongly willing to believe it is not).