Slashdot Mirror


The IT Department as Corporate Snoop?

coondoggie writes with a link to a NetworkWorld article about the dangers of IT department snoops. A study released today is likely to exacerbate the trend of failing trust in employees; it shows that one in three IT employees poke through systems and prod at confidential information while on the job. The survey was done by a firm specializing in password security, so some salt might be required for this particular article. "The survey found that more than one-third of IT professionals admit they could still access their company's network once they'd left their current job, with no one to stop them. More than 200 IT professionals participated in the survey with many revealing that although it wasn't corporate policy to allow IT workers to access systems after termination, still almost 25% of respondents knew of another IT staff member who still had access to sensitive networks even though they'd left the company long ago."

116 comments

  1. Only 1/3rd? by Skyshadow · · Score: 3, Funny

    1/3rd of IT professionals poke through other employee's files? What are the other 2/3rds up to all day long?

    Never hire an IT guy who couldn't pass the BOFH test.

    --
    Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
    1. Re:Only 1/3rd? by AaxelB · · Score: 1

      What are the other 2/3rds up to all day long?
      They lie on surveys, of course!

      But I think the more notable lie/damned lie is that 1/3 can still access their previous company's network after termination. It seems like there'd be more important security implications with disgruntled fired IT guys still having unbridled access to the company network.
    2. Re:Only 1/3rd? by tubapro12 · · Score: 1

      Ya isn't it pretty much in the job description that these are the people with the know-how to do this kind of stuff. After terminating the first they need a new one to start snooping for the old admins "easter eggs".

    3. Re:Only 1/3rd? by ajanp · · Score: 2, Funny
      1/3 of them are simply too busy reading /. to trouble themselves with old files.

      The other 1/3... well... when I read their thoughts all that was coming through was "deny, deny, deny."

      --
      File Deletion is Murder.
    4. Re:Only 1/3rd? by grassy_knoll · · Score: 1

      1/3rd of IT professionals poke through other employee's files? What are the other 2/3rds up to all day long?


      Pr0n?

      [badum-ching]
    5. Re:Only 1/3rd? by YrWrstNtmr · · Score: 2, Insightful

      It seems like there'd be more important security implications with disgruntled fired IT guys still having unbridled access to the company network.

      Not all are fired/disgruntled. Some leave on good terms.

    6. Re:Only 1/3rd? by Anonymous Coward · · Score: 0

      1/3rd of IT professionals poke through other employee's files? What are the other 2/3rds up to all day long?

      We're smart enough not to admit it or get caught!

    7. Re:Only 1/3rd? by qzulla · · Score: 1

      I was a kind of disgruntled/gruntled discharged employee once. I just walked away from it. Jail time is not my bag.

      qz

    8. Re:Only 1/3rd? by timmarhy · · Score: 1
      i've never been fired from a single job in my life, and i've always left on good terms. that's how most people i know leave a job, purely because they simply had a better offer.

      i have however had some managers who were pissed off i was leaving purely because i was leaving to make more money then them, and that i wouldn't be there to do their work all the time. that's their problem not mine though.

      --
      If you mod me down, I will become more powerful than you can imagine....
    9. Re:Only 1/3rd? by Anarke_Incarnate · · Score: 1

      I have been fired a couple of times (only once in IT, the rest were in BS jobs in/before college. The IT one was because the company couldn't afford to keep paying me). As for the other part of what you said, one of my bosses was pissed that I was leaving because they just assumed I would be there forever. They felt cheated that they would not have me around 24/7 for when emergencies came up. Now I am contracting with them for when they need me, for training, and on retainer :)

    10. Re:Only 1/3rd? by dodobh · · Score: 1

      1/3rd of IT professionals merely pretend to be real BOFHs. The rest are in your files, compromising your identity.

      --
      I can throw myself at the ground, and miss.
    11. Re:Only 1/3rd? by Anonymous Coward · · Score: 0

      porn behind a firewall? http://sf.net/projects/phproxy

      *jedi hand wave* you didn't hear that from me

    12. Re:Only 1/3rd? by jrockway · · Score: 0

      > The rest AR N YUR FLIES, COMPRMISIN UR ID LOL.

      Fixed that for you.

      Lameness filter encountered. Post aborted!
      Reason: Don't use so many caps. It's like YELLING.

      --
      My other car is first.
    13. Re:Only 1/3rd? by winnabago · · Score: 1

      If someone had asked you a while back if you would ever make a cat macro joke, would you have answered yes? You should feel dirty. I CAN HAS PRVW BTN?

      --
      Dammit Otto, you have lupus.
  2. This wouldn't happen at Slashdot's IT, would it? by buswolley · · Score: 1

    Would it?

    --

    A Good Troll is better than a Bad Human.

  3. me! by Anonymous Coward · · Score: 1, Funny

    I've been hosting http://www.encyclopediadramatica.com/ through my old job. They're going under and the server is falling apart.

    1. Re:me! by Anon-Admin · · Score: 3, Funny

      The company I work for has a firewall is your site is blocked. It tells me "This site belongs to the XXXXXXXXXXXX defined Internet category "Tasteless" which has restrictions."

      I guess Ill have to look at it when I get home. :)

    2. Re:me! by Chabo · · Score: 1

      Eh... looks like a link-farming site right now. Nothing special.

      --
      Convert FLACs to a portable format with FlacSquisher
    3. Re:me! by Anonymous Coward · · Score: 0

      Are you an idiot? It's a parody/social commentary site with a huge quantity of original content. The only external links are in one section at the bottom.

    4. Re:me! by Chabo · · Score: 1

      Umm... hmm... it seems that I thought he was replying to a different comment than he actually was. I thought that the site in question was http://www.martianfrontier.com/, which is the website listed a few comments above under someone's name. I think the comment made by the AC was probably hidden at the time I replied.

      Whoops.

      --
      Convert FLACs to a portable format with FlacSquisher
  4. Hmmm by Anon-Admin · · Score: 2, Interesting

    "The survey found that more than one-third of IT professionals admit they could still access their company's network once they'd left their current job,"

    This is kind of funny, When the layoffs hit back in 2001 I know of lots of instances where this happened. They lay off the IT staff and expect the systems to magically run them selfs, or expect the janitor to be able to run it all.

    But to see that today is a little of a surprise. Maybe they have not hired new IT staff and the equipment is just running on autopilot.

    1. Re:Hmmm by dwarfsoft · · Score: 1

      I had quite a lot of logins for sites that were active up to 4 months after I left my last job. I could basically log into the website and log a job with them, or log on to an affiliates website and order parts :D. I left on good terms so I never abused this power (although I did log into the accounts every month or so just to check if they were still active).

      For all the remote sites that they supported? I have access to their servers still. I haven't logged in to them but I can connect to their session, and there is no way that any of these places would be changing their passwords...

      --
      Cheers, Chris
  5. All the more reason.... by Chabo · · Score: 3, Funny

    All the more reason to put make sure nobody else is snooping on you before you install your backdoor program!

    --
    Convert FLACs to a portable format with FlacSquisher
  6. Re:This wouldn't happen at Slashdot's IT, would it by drinkypoo · · Score: 0

    Well, that could explain what the editors do with their time...

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  7. Seperation of powers by tubapro12 · · Score: 3, Informative

    Like in government (cough cough cough), powers should be divided amongst a number of people i.e. hardware admins, web server admins, database admins, 'maintenance admins', et cetera. But for the majority of places this could easily be too many people. Of course, this is pretty impractical too, and I for one know most admins don't like having obstacles; but after all that's the root of the problem at hand.

    1. Re:Seperation of powers by Anonymous Coward · · Score: 0

      This is also called "divide and conquer" FYI.

  8. default passwords by grassy_knoll · · Score: 4, Funny
    From TFA:

    Eight percent of respondents noted that they still use the manufacturer's default admin password on critical systems.


    Some people are blockheads.
    News at 11.
    1. Re:default passwords by Courageous · · Score: 1

      I really can't count the number of times I've seen oracle:oracle accounts.

      C//

    2. Re:default passwords by grassy_knoll · · Score: 1

      What's really bad about username==password is that some protocols, while being relatively open, will still take steps to obscure the password.

      So, anyone running a sniffer will see the username, but not the password... unless they're the same damn thing, of course.

  9. Why? by Hoi+Polloi · · Score: 3, Funny

    The last thing I want to do after spending 8 hours on my company's network is spend my personal time trying to get back onto my company's network.

    --
    It is by the juice of the coffee bean that thoughts acquire speed, the teeth acquire stains. The stains become a warning
  10. Thinkgeek knows it too by Weaselmancer · · Score: 4, Funny
    --
    Weaselmancer
    rediculous.
  11. Bad security, even without snooping by L.+VeGas · · Score: 4, Interesting

    In the mid 90's, I switched employers. My former employer was a fairly large medical / toxicology (drug testing) laboratory, and the records were fully searchable by name, SS#, and so on. Around this time, I got a new PC, and left the old one pretty much untouched for several years. About five years later, I fired it up out of curiosity. The terminal emulator shortcut was still there, so I plugged in the modem and was on the laboratory's network within minutes. Full access.

    The company has since been bought out and shut down, but that incident has always bugged me.

  12. old work still accessable by timmarhy · · Score: 2, Interesting
    the private files thing is total bullshit - we don't CARE abotu your dirty emails to your wife.

    accessing old work system is true i think... i know i still have access to places i setup 7 years ago, i login once a year to look at the up time on the system. it's nothing more then me checking on how my creation is going, if i saw a problem i'd probably report it to my old boss with a suggested fix.

    by the way, it's linux 2.4... 7 years up time on old salvaged hardware.

    --
    If you mod me down, I will become more powerful than you can imagine....
    1. Re:old work still accessable by Compholio · · Score: 3, Interesting

      it's nothing more then me checking on how my creation is going, if i saw a problem i'd probably report it to my old boss with a suggested fix.
      I would imagine that a lot of employers have actually made the conscious choice to keep people like you online after "termination". After all, who knows when they may need you to fix your creation?
    2. Re:old work still accessable by Anonymous Coward · · Score: 0

      by the way, it's linux 2.4... 7 years up time on old salvaged hardware

      So you've run 7 years without kernel upgrades?

    3. Re:old work still accessable by Anonymous Coward · · Score: 0

      the private files thing is total bullshit - we don't CARE abotu your dirty emails to your wife.

      That depends. Some wives are really hot and send interesting pictures by email!

    4. Re:old work still accessable by Miguelito · · Score: 1

      the private files thing is total bullshit - we don't CARE abotu your dirty emails to your wife. Maybe to you and me, but there are people out there that get off on that kind of thing.

      There were legendary tales of an employee long ago that used to spend a big part of his/her time reading other people's emails. He/She was never reprimanded in any way (that I ever heard of anyway). The fact that his/her family was supposedly a holder of a LOT of stock probably had something to do with that. :-/

      I barely knew said employee, but from the few small interactions I had with him/her.. I believe the stories. Complete slack off, and likely spoiled rotten since birth.
      --
      - My favorite error message: xscreensaver, running on an old Sparc 5 w/ 8bit color: bsod: Couldn't allocate color Blue
    5. Re:old work still accessable by timmarhy · · Score: 1

      er, it was lastest 2.4 version when i left. can't vouch for it right now though

      --
      If you mod me down, I will become more powerful than you can imagine....
    6. Re:old work still accessable by timmarhy · · Score: 1

      your probably right there are wierdo's like that out there, but TFA quotes 1/3 of IT people read private email... it's just crap there's no way it's that high.

      --
      If you mod me down, I will become more powerful than you can imagine....
    7. Re:old work still accessable by akeyes · · Score: 2

      er, it was lastest 2.4 version when i left. can't vouch for it right now though

      I'll tell you what... we will wait while you check. (You did say that you still have access.)

    8. Re:old work still accessable by jimicus · · Score: 2, Insightful

      if i saw a problem i'd probably report it to my old boss with a suggested fix.

      As one IT pro to another... if your former boss doesn't know this, don't do it. There's a strong chance you'll cause far more trouble for yourself than you ever dreamed possible.

  13. Who writes this stuff? by canada_dry · · Score: 1

    "it wasn't corporate policy to allow IT workers to access systems after termination" LOL My organization is implementing RSA two factor authentication http://www.rsa.com/node.aspx?id=1156 to ensure that network admins can't get access once they leave the company. Without controls like this you just need one digruntled admin to cause you some big headaches.

    1. Re:Who writes this stuff? by Anonymous Coward · · Score: 1, Insightful

      The same IT department that doesn't turn off a terminated employee's access would be the same one who doesn't turn off access for the employee's token.

      These tokens don't magically fix broken IT security policies.

    2. Re:Who writes this stuff? by Nonesuch · · Score: 2, Informative
      One nice thing about physical access tokens is you can add them to the security guard's checklist for terminations, just like a laptop, badge/keycard, and company car. You don't turn it in, you don't get your final paycheck.

      The same IT department that doesn't turn off a terminated employee's access would be the same one who doesn't turn off access for the employee's token. These tokens don't magically fix broken IT security policies.
      But these tokens do have a built-in expiration date, the server doesn't fix policies, but it will enforce policies. When the end-of-life arrives, the token becomes a useless fifty buck hunk of plastic. And unlike passwords, lazy admins cannot trivially override the expiration date, like they do for VIPs in the "user must change password every X days" GPO on every Microsoft AD deployment I've ever seen.
    3. Re:Who writes this stuff? by OnlineAlias · · Score: 2, Informative


      Curiously, Microsoft AD has no such ability. Password policies are set domain wide and there are no exceptions for anyone even with a GPO, a well known limitation of AD.

      Let me correct your statement. You have "never seen an AD deployment where a GPO's were making exceptions..."

    4. Re:Who writes this stuff? by jombeewoof · · Score: 2, Interesting

      easy enough to set that token to "lost" with a passcode that doesn't expire.
      If you're an admin you would certainly have access to the RSA ACE server that allows this.

      --
      Linux Zealots: Smarter than Mac Zealots, but still zealots.
    5. Re:Who writes this stuff? by Nonesuch · · Score: 1

      easy enough to set that token to "lost" with a passcode that doesn't expire.
      I believe that the account will still go dead when the original lost token goes to "expired" state. I've seen event messages to this effect in the audit trail. Not sure about the exact behavior in the latest release.

      If you're an admin you would certainly have access to the RSA ACE server that allows this.
      Depends on how the ACE/Server is configured. RSA has done a pretty good job with granular permissions (aka "task lists"), audit trails, and generally making it difficult to intentionally or unintentionally violate security or security policies.

      One drawback is you still need to trust the Linux/Solaris/Windows server where the ACE software is running.

    6. Re:Who writes this stuff? by jaseuk · · Score: 1

      Grandparent is correct Cannot change password, password never expires etc. are user account properties and can be set on a per-user basis.

      Jason.

    7. Re:Who writes this stuff? by Acer500 · · Score: 1

      Seconded. You can also set a second Group Policy that overrides the default Group Policy that overrides the default Group Policy for a child domain or OU (I'm not certain if the password policy in particular can be overriden, which might be what the GP was talking about).

      --
      There are three kinds of lies: lies, damned lies, and statistics.
    8. Re:Who writes this stuff? by toadlife · · Score: 1

      Grandparent is correct Cannot change password, password never expires etc. are user account properties and can be set on a per-user basis. No they can't. Password policies are applied to *machines*, not users, so it's impossible to set them on a per user basis. For domain accounts the relevant password policy is the one applied to the domain controllers.

      What the Grandparent is talking about is lazy IT staff manually setting passwords for VIPs when they expire using their domain admin privileges. This is the only way of "overriding" a password policy. Moving to a hardware token based system only shifts the responsibility of enforcing policies over to a new set of hands; someone with the ability to renew hardware tokens can act just as irresponsibly as the lazy Windows admin, so I fail to see the point of slamming Windows domains in this regard.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    9. Re:Who writes this stuff? by jombeewoof · · Score: 1

      you know what, you're right. I had forgotten that you certain accounts could not be set to lost status. If the token was unavailable you simply could not get in.

      --
      Linux Zealots: Smarter than Mac Zealots, but still zealots.
  14. Shenanigans! by laron · · Score: 3, Insightful

    "The survey found that more than one-third of IT professionals admit..."

    I find that hard to believe.

    --
    "Beware of he who would deny you access to information, for in his heart he dreams himself your master."
  15. Can't be called professional without ethics by erroneus · · Score: 4, Interesting

    It's just my opinion but I'm sure many will agree with me on that. In every case where a person has privileged access to information as part of their job, there is usually some sort of ethical standard of non-disclosure in place. As an IT manager, I thrust my ethics upon people on a regular basis citing that I do not EVER want to know anything I don't need to know. Usually, it's passwords, but wouldn't that just be the start?

    I can't imagine how anyone could consider themselves "professional" without professional standards of behavior to go along with it. Do professionals in all fields get tempted "by the dark side?" Oh yeah... we see it on the news every day.

    But at a rate of 33% of IT professionals breeching company trust? That's pretty frightening... it's probably untrue.

    1. Re:Can't be called professional without ethics by nomadic · · Score: 0, Flamebait

      I can't imagine how anyone could consider themselves "professional" without professional standards of behavior to go along with it.

      Welcome to IT. IT professionals skew younger and more socially maladjusted than other groups I think.

    2. Re:Can't be called professional without ethics by Anonymous Coward · · Score: 0

      Well theres a million ways to breach trust right. Hacking into HR computers so you can masterbate to co-workers pictures is one thing, manipulating accounting data is quite another.

    3. Re:Can't be called professional without ethics by Torvaun · · Score: 1

      It said that 33% accessed confidential information while on the job. In some places, it is part of the Admin's job to snoop. No, I don't care about what you want to do to your wife when you get home, or what you want to do to your secret girlfriend while your wife's out of town. I do care that you're spending up to 20% of your time on various porn sites. First and foremost, that is a leading cause of spyware, and that's cause for distress on my network. Then there's the fact that that's not what you're getting paid to do. That bothers me much less than you trying to damage my network, but it will get reported anyway, as it's supposed to.

      Employee trust can be breached while maintaining company trust.

      --
      I see your informative link, and raise you a pithy comment.
    4. Re:Can't be called professional without ethics by erroneus · · Score: 1

      ...that and the closest thing IT has to a "shingle" to hang are certs. I have NO certs. After seeing the kinds of people who chase after and collect certs, I lost all belief that they represent skill or ability.

      But you know, for a long long time, "doctors" required no credentials and "dentists" were often the same people that cut your hair. Hell, even electricians have varying levels of certifications that are generally agreed upon. So for as long as people have been pushing for reliable IT credentials, maybe one day it will happen.

    5. Re:Can't be called professional without ethics by qzulla · · Score: 1
      It said that 33% accessed confidential information while on the job. In some places, it is part of the Admin's job to snoop.

      Whaoa there, cowboy. It is not our job to snoop. It is managements job to tell us when to snoop. Paper trail in email.

      As an admin I don't snoop. I only do what management wants. I keep my systems running. This is my admin role.

      I keep the servers up. I keep things rolling. I don't care about what it is I keep rolling. I just keep it going.

      If management has issues then I deal with the fallout and my paper trail.

      I just make the roads roll.

      qz

    6. Re:Can't be called professional without ethics by Torvaun · · Score: 1

      ...You haven't actually disagreed with anything I said. If management tells you to snoop, you're still going to snoop, and you're going to fall within that 33%. At some places, the IT department is told to always be snooping, because it's just too difficult to try and catch everyone ahead of time, and they were told that their computer use might be monitored when they signed on to this job. Here, it might be a necessary duty to periodically pull router logs, and see who's going where. At some particularly paranoid shops, you'll end up with all traffic being sniffed, rather than just connections being logged. Now you get to run searches for your lists of suspicious words, and check the context for possible trade secret or confidential information leaking.

      Also, my friend the civil engineer wants me to tell you that you need to know what's going to be rolling on your roads when you design them, because a bridge for cars is not a bridge for trains, and a skyscraper in New York is not a skyscraper in San Francisco.

      --
      I see your informative link, and raise you a pithy comment.
  16. This seems to keep coming up lately... by Yobgod+Ababua · · Score: 3, Insightful

    Your company should have a published policy regarding user privacy and IT, and all members of IT should abide by that policy at all times. (In our case, for files or email, we require the approval of the user themselves or of a department manager and human resources before we go off reading your stuff. We do reserve the right to monitor network traffic at any time, for any reason, but we also make sure your email access runs encrypted over the network...)

    In any case, please encourage your local IT Professionals to behave like Professionals. How should they behave, you ask?

    Like THIS.

    Anyone who doesn't lock the accounts of ex-root-access employees and change the shared passwords that they had access to is lazy and negligent, bordering on criminally negligent. That's just inexcuseable...

    1. Re:This seems to keep coming up lately... by sys_mast · · Score: 1

      You bring up a good point. Should Email be considered different than say files on a hard drive? Considering that Email could easily and commonly contain personal information, medical or other stuff not work related but private. Or Email could even contain sensitive communications with HR, which would be work related but could easily be personal/sensitive stuff.

      Just my $0.02

      --
      Those who can, do.
  17. True enough by grasshoppa · · Score: 2, Insightful

    From my perspective, this is true enough. There are places that I still have access to that, by all rights, I shouldn't. I log in about once a year to see if I still have access, and if I do, I email the owner/manager of the place to that effect. Last thing I want is for something to go legal and me have a finger in the pie.

    Of course, for a few places around here, me still having access is a good thing. Seeing how they call me about once a week because they couldn't follow well laid out documentation on managing the system...but I digress.

    --
    Mod me down with all of your hatred and your journey towards the dark side will be complete!
    1. Re:True enough by qzulla · · Score: 1

      This is not wise. Go legal? Heh. Once the first thing goes wrong who will be holding the bag?

      On every job I have left that is it. I have never tried to log on.

      Case closed. Move on.

      Emailing the owner/manager of a flaw in the system? Not wise.

      It is best to cut the cord and go away.

      So you emailed the owner/manager you still had access?

      Good luck in court.

      qz

    2. Re:True enough by grasshoppa · · Score: 1


      So you emailed the owner/manager you still had access?


      Any decent forensic work will turn up that I still have access; From there it's a short hop into believing that I logged in and covered my tracks ( assuming for a moment that I didn't log in at all ). While I agree not logging in is a good idea, they're lack of diligence puts me at risk. Therefore, I chose the course that will provide me with the greatest level of information and legal protection.

      It isn't perfect, but it serves.

      --
      Mod me down with all of your hatred and your journey towards the dark side will be complete!
    3. Re:True enough by TeraCo · · Score: 1

      One of the last things I do when I leave a job is send a mail to my manager listing all of my administrative access and advising that as per security best practices these accounts should be immediately revoked.

      A bit of CYA goes a long way.

      --
      Not Meta-modding due to apathy.
  18. Wot no exit procedures? by Colin+Smith · · Score: 2, Interesting

    It's almost impossible not to occasionally catch sight of something sensitive when you work in IT; Employee databases, email folders/logs, web browser histories, chat logs etc etc.

    More than any other reason, this is why your IT team should be well paid and why duties should be segregated.

    Course there should be documented exit procedures for HR and IT when people leave.

    --
    Deleted
    1. Re:Wot no exit procedures? by nine-times · · Score: 5, Informative

      More than any other reason, this is why your IT team should be well paid and why duties should be segregated.

      And also "trustworthiness" really has to be high on your priority list of job-qualifications for IT people. I always tell people, if you can't trust your IT people, you're in trouble.

      You might ask why. "Why can't you put security in place that prevents your IT people from accessing the information you don't want them to see?" Well, I'll answer that with another question: who will put that security in place? Inevitably, there will have to be people who put security in place, and whoever that is could leave back-doors for themselves. There will be people who maintain the systems and security, people with powerful logins and passwords, and those people can override your security.

      And ultimately, there are accidents. At one company, we can a common spam database for the whole company (years ago). Every piece of spam went into the same place. While looking for false positives in order to see whether the filter needed adjusting, you'd see every e-mail that had a swear word in it. If someone wrote about "f*%king", it was in the spam filter. Every mention of "penis" went in the spam filter. A lot of it was spam, but there was plenty of employee e-mail going around, talking about things they probably didn't want anyone to see.

      Also, there were plenty of times where someone invited me to look at their desktop or e-mail in order to help them with something. Like, "hey, can you help me find this e-mail I'm looking for?" I say "yeah," and the e-mail up on the screen is an e-mail about having an affair and an Excel file containing everyone's salaries. It happens!

      My point is, even if your IT personnel are honest, they'll probably see sensitive information somehow, even if by accident. Trustworthiness is an important trait. My advice: If you're hiring IT people, it might be good to hire the person you'd feel most comfortable telling all your dirty secrets. If you're just another employee, keep any information on your work computer or pass information through your work systems unless you'd be comfortable with your IT people seeing it. If you must send information from work that you don't want your IT people to see, use a Gmail account, and don't leave your browser open while you're away from your computer.

    2. Re:Wot no exit procedures? by DragonWriter · · Score: 1

      Course there should be documented exit procedures for HR and IT when people leave.


      And, a critical step that many places I've seen with "documented procedures" for all kinds of important thing seem to miss: those procedures need to be (1) communicated to those responsible for implementing them, and (2) actually followed consistently.

    3. Re:Wot no exit procedures? by turbidostato · · Score: 2, Funny

      "who will put that security in place?"

      Why, indian engineers we get on green cards, of course. After the job is done, we bury them alive within the datacenter.

      We already used that trick on our pyramids.

    4. Re:Wot no exit procedures? by Phantom+Gremlin · · Score: 1

      And also "trustworthiness" really has to be high on your priority list of job-qualifications for IT people. I always tell people, if you can't trust your IT people, you're in trouble.

      I know it's late to comment on this discussion, but anyway ...

      Just how do you measure trustworthiness?

      I can discuss things like real vs effective UIDs with people. I can ask them the derivative of x^2. I can even ask them to estimate how many gas stations are in the state of Texas.

      But are there reliable ways of measuring how trustworthy someone is?

    5. Re:Wot no exit procedures? by nine-times · · Score: 1

      Well i guess that's why you have an interview rather than a standardized test. A good manager or HR person should be able to get some kind of a read on people, even if it's not always 100% correct. You know, you see their response to different sorts of questions, check whether they know as much as they claim, and check to see if their resume/cover letter is accurate. You talk to them and hopefully you'll have some sense.

      However, I'm not really talking about how you tell people are trustworthy. That's more of a philosophic, sociological, or psychological sort of question. I'm just advising that, however you get a sense of trustworthiness, you set that as a priority when hiring.

      So lets say you have two potential hires come into your office. One of them appears to be competent, but perhaps merely 'competent'; he seems like a decent person that you could trust. The other seems a little smarter, has more certificates, more experience, and even impresses you a little, but whom you have a gut feeling is probably a little dishonest and not-so-much a "good person".

      Now, some people would say you should go with the more qualified person without much consideration for whether he's a "decent person". After all, he's going to be your employee, and not necessarily your friend. On the other hand, I would claim that trustworthiness should be a huge factor in your hiring process because IT people often (necessarily) have access to private, sensitive, and confidential information. Of course, you don't want to hire an incompetent moron just because he seems honest-- it shouldn't be the ONLY factor, but it is an important factor.

  19. IT people could go to jail by Anonymous Coward · · Score: 2, Interesting

    The Air Canada vs. Westjet case involved computer espionage and a former employee who kept access to Air Canada's computer system. The result cost Westjet millions. The settlement left no doubt that what Westjet and its employees did was illegal. Illegal, as in someone could end up in jail, that kind of illegal. http://www.lockergnome.com/nexus/news/2006/05/29/w estjet-accepts-blame-settles-with-air-canada-in-es pionage-case/

    1. Re:IT people could go to jail by Anonymous Coward · · Score: 1, Interesting

      The Air Canada vs. Westjet case involved computer espionage and a former employee who kept access to Air Canada's computer system.

      Not quite. The former employee was an executive at Air Canada and one of his perks (despite the fact he was leaving Air Canada - quite a golden parachute) was a very large number of free flights on Air Canada for a very long time.

      To book his free flights, he was authorized and given access to an internal booking system at Air Canada.

      To book his free flights, obviously the system would have to show which flights had seats available.

      However, knowing which Air Canada flights had seats available was very useful information to Westjet.

      The result cost Westjet millions. The settlement left no doubt that what Westjet and its employees did was illegal. Illegal, as in someone could end up in jail, that kind of illegal.

      I think that is a bad decision. Air Canada deliberately gave access to the former employee, knowing that he was a former employee, and knowing that he was working at a competing airline. This wasn't a break-in, this wasn't a hack, this wasn't a case of forgetting to terminate access. HE WAS AN AUTHORIZED USER!

      Further, knowing which Air Canada flights had seats available isn't even that private or secret. Thousands of travel agents have access to that information, as do many travel booking websites.

    2. Re:IT people could go to jail by Anonymous Coward · · Score: 0

      one of his perks (despite the fact he was leaving Air Canada - quite a golden parachute) was a very large number of free flights on Air Canada for a very long time.


      Actually, it was only two free tickets per year until 2005. Not exactly a very large number, or for a very long time.

  20. My solution... by __aaclcg7560 · · Score: 1

    I had a supervisor at one company pop up in my cube saying that I was wasting company time by looking at Amazon (which was up on my web browser) and threaten to write me up. With breakfast burrito in hand, I told him I was on my break and to bugger off as I was within policy. After that, I browsed the Internet on my PDA by going through the open wireless access point for the company next door. The virtual keyboard was a pain in the butt for Slashdot posts. :P

    1. Re:My solution... by Anonymous Coward · · Score: 0

      Our IT Manager doesn't care. In fact, I see him browsing cars.com, playing sol.exe and working on online crossword puzzles all of the time and he doesn't hide it. If he knows there is work to be done, he knows we will be doing it. If I'm playing around or watching a clip of something, he trusts that I am using my time wisely. Until proven otherwise, he upholds that unwritten rule. He has fired people in the past, it was not for browsing the internet, it was for not doing a good job. There is a difference.
      Oddly enough, our previous manager was demoted and she was a complete tyrant and walked around with a magnifying glass. When a lot of people leave in a short period of time and the exit interviews point to a specific person as the cause, HR and the senior managers will eventually do something about it.

  21. Poor Statistics by Toonol · · Score: 1

    almost 25% of respondents knew of another IT staff member who still had access to sensitive networks even though they'd left the company long ago.

    That's absolutely meaningless, and including that as a 'result' means that the pollsters are either ignorant or deceptive.

    I bet 95% of slashdot readers know a homosexual. What does that say about the frequency of homosexuality? Pretty much nothing. There's overlap (two responders thinking of the same person) and selection bias (25% know of one case of a terminated employee with access... that might be out of a hundred terminations where rights were appropriately revoked).

  22. Beyond the files by Average · · Score: 1

    I always found that sysadmins (myself included) tend to acquire keys whenever possible. I don't care if it's just a broom closet, I want to know what's in there. There's a mix of paranoia, extreme curiosity, and helpfulness that come with the profile.

    1. Re:Beyond the files by swb · · Score: 1

      My technique for getting keys was to come up with a legitimate need to get into a space and then bug whoever had keys continuously to open the door until they got around to getting me my own set.

      For those doors where no key would ever be issued (electrical vaults, restricted building spaces) we would occasionally put a thin metal sheet over the part of the doorjam where the lock went in. Door looked locked from the outside, but actually wasn't. It usually kept the doors available for a while.

      The ONE door I could never reliably get access into was the return air shaft off the data center. Freaky room, it went up 20+ floors to the main ventilation room.

  23. Having access after you leave by nurb432 · · Score: 0, Redundant

    And doing someting bad with it are 2 different things.

    --
    ---- Booth was a patriot ----
  24. Passwords by Otter · · Score: 2, Interesting
    The study also showed that over 50% of workers still keep their passwords on a Post-It note, in spite of all the education the IT security industry to do it differently. And in the don't do-as-I do-dept., more than 50% of respondents admitted to using Post-It notes to store passwords to administrator accounts. One-fifth of all organizations admitted that they rarely changed their administrative passwords with seven percent saying they never change administrative passwords.

    I'm skeptical about the snooping (much as I bitch about admins, they're actually remarkably ethical about privacy given the access they have, IME) but that password thing sounds dead on. Whenever they give us the lecture about how keeping track of the login/password combos for 25 different accounts, each rotated every 60-90 days, with mandatory mixed case, numbers and punctuation is easy -- why all you do is make up a little story -- "Mary went to the store to buy milk" becomes h7^Y8U0bs# -- I always ask them for the story to their previous password to the office furniture request page. They splutter about how no, that's a security risk to part with one of their expired stories but I can see the Post-It with the root password in their minds, like I'm Professor Snape.

    1. Re:Passwords by drinkypoo · · Score: 2, Interesting

      They splutter about how no, that's a security risk to part with one of their expired stories but I can see the Post-It with the root password in their minds, like I'm Professor Snape.

      I've always written down my new passwords until I memorize them. Then I burn the paper.

      If you lose it while you're still memorizing it, you change it quickly :)

      But you don't write down what it's for, either...

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Passwords by Torvaun · · Score: 1

      I have every password needed on the system written down. That piece of paper is in a fireproof safe accessible by me and the head honcho. Now, if I should get hit by a bus while crossing the street, the company is not utterly screwed. I also choose strong passwords, 'e=2.71828', 'answer:42' and other things that are easy to remember, but hard to brute-force. Biggest issue for me is remembering what password goes to which log-in, but that's on the paper if they need it.

      --
      I see your informative link, and raise you a pithy comment.
    3. Re:Passwords by Acer500 · · Score: 1

      I have every password needed on the system written down. That piece of paper is in a fireproof safe accessible by me and the head honcho. Ditto. That's company policy where I work for, we have to change the critical passwords every 6 months - and that's quite lenient, but reasonable considering it's a day of work just changing every badly programmed system that has sensitive passwords hardcoded, and that's AFTER we documented where they have to be changed.
      --
      There are three kinds of lies: lies, damned lies, and statistics.
    4. Re:Passwords by mojine · · Score: 1

      Good music ...

      --
      "It's not how many people I've killed - it's how I get along with the ones that are still alive."
  25. Telegraph Operators by Frogbert · · Score: 4, Insightful

    I like to think of myself as a Telegraph Operator. Sure I know peoples secrets, but it would be unprofessional for me to tell them to anyone.

  26. ethics and sociopathy by obtuse · · Score: 1

    Two separate problems here.
    Some people are just scum. There are too many of these people in any group.
    Some people need rudimentary ethics education. These are the interesting ones.

    It's hard to imagine that people just don't think about ethics, but from what I've seen, much of the problem is exactly that. I've seen people who act badly but later with a little education, they actually work hard to behave well. Working with High School students and junior IT staff I found them ethically naive (to be generous) but remarkably amenable to argument and explanation on the ethical problems we face.

    I really don't think much of human nature so I'm not surprised much by simple dishonesty, but working with a few of these kids, I was surprised at how well they learned to behave. Of course, some folks just acted badly anyway. Some people are just born sh*ts.

    While I believe the quoted (>1/3) figure, I also think that with just a little effort, those of us who are professionals can improve it substantially. Listen to your cow-orkers. Their stories will probably illuminate their attitude.

    The other thing that I find interesting is that it is easier to identify the ethically naive than the fundamentally dishonest. That's why those personal stories are so telling.

    --
    Assembly is the reverse of disassembly.
  27. Maybe this explains Ameritrade spamming by Jon+Abbott · · Score: 1

    Maybe this explains how so many Ameritrade customers are getting spammed with pump-and-dump stock spams... An ex-employee (or hell, even a current employee) could be pocketing quite a bit by selling off their email addresses. This is assuming, of course, that the company isn't doing this itself.

  28. It's called exploration. by Anonymous Coward · · Score: 1, Insightful

    Which means 2/3rds of IT professionals don't familiarize themselves with the systems they're running.

    If you're in IT, and you're an administrator, the company must be able to trust you with ALL DATA! That means ALL FUCKING DATA, not what the top people just think you should or shouldn't be familiar with. If your company is shit and fucks people over daily, IT will know, and IT Will find another job and leave you with some shitty guy who can't even turn a machine on doing your work. Then you get targeted, taken down, and goodbye and good riddance company.

    The only alarming thing is that the asshats at the top who give life to the term "shit flows down hill" think "oh shit, my pants are down, my hand is in the cookie jar and I'm going to get caught".

  29. It's a problem by Phil+Wherry · · Score: 4, Interesting

    In the security business, a lot of the danger from IT employees comes from a class of attack known as "abuse of authority." It's near-impossible to prevent through technical measures, since the people in question need the elevated privileges in order to do their jobs. A careful program of auditing can often detect these abuses after they've occurred, however.

    I had a situation occur a few years ago in which I had to fire a trusted and valuable staff member for snooping through a senior manager's email. Another staff member actually detected this when he printed a copy of the email, and it came out of the printer in his home office even though he was on travel. This came to my attention very quickly, and we reviewed audit logs that we'd put in place earlier and found plenty of evidence of his snooping. It pained me to fire the guy--he was smart, ambitious, and held up really well under pressure. But in the end, I concluded that a slap on the wrist would just send the message to other team members that it was OK to cheat until caught for the first time. I suspect that it was the right move for him, too; our sudden, decisive response to his lapse in judgment doubtless made an impression.

    So, some advice to IT managers: ensure that there's an audit trail for all privileged activity. You'll detect and stop abuse if it's going in, and will deter staffers from being tempted to misuse their rights.

    Phil

  30. Once upon a time by bl8n8r · · Score: 1

    There was something called integrity. I don't think there is as much of a focus on it anymore as there should be. The focus has shifted into mostly monetary interest; on both the part of the employee and the employer.

    --
    boycott slashdot February 10th - 17th check out: altSlashdot.org
  31. Salt for passwords too by omnirealm · · Score: 2, Funny

    Not only should the article written by the firm specializing in password security be taken with some salt, but it is also a good idea to add salt to passwords.

    Okay, that was a stretch.

    --
    An unjust law is no law at all. - St. Augustine
  32. Exit Procedures? by weeble1 · · Score: 1

    Isn't the Late Friday Afternoon Stealth S***can Ambush Maneuver(tm) still the standard in IT to prevent this kind of thing? You know, where you log off and head out towards the car after a hard week at work when the boss grabs you and takes you into the Tiny Conference Room of Doom(tm), makes you wait ten minutes while he goes and kills your accounts, and THEN comes back in with the empty Office Depot copier paper box? Because that's been SOP at every IT department I've ever worked for. If the exit boots aren't run by paranoid IT people who know the dangers, they ARE run by paranoid HR types who don't trust anyone (that's why they are in HR). Seems a load of crap to me.

    1. Re:Exit Procedures? by Anonymous Coward · · Score: 0

      "makes you wait ten minutes while he goes and kills your accounts"

      If an HR guy can go and kill my accounts in ten minutes, that certainly means I deserve to be fired. That's why I'm the BOFH and him a PHHR luser.

    2. Re:Exit Procedures? by Anonymous Coward · · Score: 0

      Give me a break. Paranoid HR types? Most HR types are lucky if they can figure out how to flush a toilet, nevermind figuring out how to out process someone. In most of the companies I've worked for, IT was the department that was always bitching about HR never being able to figure out how to do things like this correctly. Though it's most likely a problem for them as they spend so much time brown nosing senior management that the stupidity rubs off.

  33. Curiousity herded the cat by Nonesuch · · Score: 2, Insightful
    I've found as I've gotten older and now have more to lose, I go out of my way to not acquire keys, to not know users passwords, to not have accounts on systems where I don't need them -- I'm just as curious, yet more risk-adverse.

    Average wrote: I always found that sysadmins (myself included) tend to acquire keys whenever possible. I don't care if it's just a broom closet, I want to know what's in there. There's a mix of paranoia, extreme curiosity, and helpfulness that come with the profile.
    When I want to see what's in a broom closet, I have security send up a guard with a key and have him open the door and show me around. My curiousity is satisified, and no worries about being liable if later a broom turns up missing :)
  34. Document Requests by bill_mcgonigle · · Score: 1

    It's almost impossible not to occasionally catch sight of something sensitive when you work in IT; Employee databases, email folders/logs, web browser histories, chat logs etc etc.

    This one is thorny. I actually had a former boss accuse me of snooping through his e-mail after he asked me to look at his e-mail to figure out why he was getting so many spam messages (SpamAssassin was just out at the time and I was writing custom procmail rules for him).

    Of course, this was before he turned into a complete ass, was 'over beers', and he subsequently denied it (of course he thanked me for the reduced spam at the time).

    Moral of the story - if you deal with confidential information, make up a form and have it signed off each time you have a request to work on said information. It's the assholes who create the bureaucracy, ain't it?

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  35. Its all fair by Anonymous Coward · · Score: 1, Insightful

    If your company is like the ones I've worked for (in the UK btw), then you are underpaid, undervalued and mistreated. The whole system stinks and you get paid far less than people who've a tenth of your brains. So you try to reclaim a little power over the bastards. You take their passwords and read their email and then use the information against this. You've the right to do this because you can do this. They themselves have adhered to this law by treating you like crap in the first place. What goes around...

    1. Re:Its all fair by Prog_Burner · · Score: 1

      Maybe if you're willing to do that, then you are getting the fair treatment from your company? If you want to be respected and treated as a professonial, act like one. It does go around, good as well as bad.

  36. Integrity is gone by Anonymous Coward · · Score: 0

    There is no such thing any more.
    Employees are liability for companies, not assets, but thing that damages bottom line.
    If there is no trust between employees and employers there is no integrity.
    Anyway, corporations are not human beings just organizations to make money

  37. Why...? by Telephone+Sanitizer · · Score: 3, Insightful

    > The survey found that more than one-third of IT professionals
    > admit they could still access their company's network once
    > they'd left their current job, with no one to stop them.

    Does it seem that people are villainizing the IT guys that left?

    Shouldn't the criticism be levied upon the IT guys who REMAIN?

    And as for snooping, it's not the snooping that bugs me, but the disclosures that sometimes follow. I was really pissed off when my boss started publicly ripping on me for the quality of some code scraps he found in my documents folder.

    I didn't mind that he looked -- I don't expect privacy on a corporate computer. But he used what he found in an attempt to humiliate me (which failed since the rest of the department knew that the code was something that I was reviewing from a new intern).

  38. Oblig. Thompson hack by Organic+User · · Score: 1

    I am sure Ken Thompson still has access to Bell Labs' information.

    I guess a few of us may be a bit young to remember this one.

  39. The settlement stipulated that it was illegal by Anonymous Coward · · Score: 0

    The guy was not authorized for the use he made of his login rights. THE USE WAS NOT AUTHORIZED. In the settlement, Westjet agreed that what they, and their employee, did was illegal. The question here is what anyone has the right to do.

  40. This has happened too many times... by SirKron · · Score: 2

    I agree with many of the people before me. I do not accept keys to client locations unless I am onsite more than a month. I do not accept domain administrator passwords, I ask for a unique admin account with delegated rights. And I do not snoop into files.

    Just recently I went to my boss and told him that our ex-HR person's home directory was wide open. I pointed out to him his hire letter and more from my other collegues. I almost did not approach him about it for fear of repricussions. However, I did not have any more than domain user rights and found it using Vista's new desktop search.

  41. See it all the time by phorm · · Score: 1

    As the IT guy, I am constantly exposed to data that, personally, I'd rather not see.

    A big one is emails. Got an administrative staff member moving to a new computer, one of the things that I have to do is move all his/her email settings to the new machine, and ensure that her mailbox (if it's POP3) and address book make it over. Even if it's something like an IMAP account, I still need to test that the username/password and settings are correct.

    Generally in most cases I just catch a glimpse of the mail headers, etc, but you never know what you could have access to when copying a user's confidential files. In cases where I've had to do data recovery it gets even harder to avoid poking around, as one has to at least partially verify that files are being restored intact, etc.

    The IT department has access to a lot of things, and frankly a rogue IT Dept member could very easily read/filter his boss's email, documents, and pretty much anything else. The best policy for data security is to hire people you can *trust* with your data, and to treat them well (I'm sure we've all heard heard stories of what disgruntled IT dept employees have pilled off).

  42. Well that makes me Occupationally Inferior by trippeh · · Score: 1

    Cool!

    I wash dishes for a living.

    - - - - - {sotto voce} - - - - -
    It's okay, I'm still in tertiary education. Plenty of time for a long-term career in data-entry.

    --
    THUD~*
  43. Yes, but why? by jonadab · · Score: 1

    > The survey found that more than one-third of IT professionals admit they could still access their
    > company's network once they'd left their current job

    Did they say why, or was it a yes-or-no question?

    If it were a yes-or-no question, stated along the lines of "If you left your job, would you subsequently still have the ability to access your employer's network?", then I would have to answer "yes", but this has nothing to do with my being a snoop and everything to do with my employer not having anyone else on staff who understands security AT ALL.

    As an IT guy (_the_ IT guy, actually -- we're small), I understand the value of passwords, but my coworkers view them as an impediment to convenience (which, granted, they are) and little more (which is a mistake). If I quit, there is absolutely ZERO possibility they would change the passwords. Two or three years ago there was a certain password that we knew for certain had been compromised and was being actively abused, and it took me upwards of six months to finally get permission to change it -- and when I did... well, you have never heard such whining as then ensued.

    There's also the small matter of password quality. If it weren't for me, most of the passwords would be short dictionary words strongly related to the nature of the organization.

    In my experience, the IT department is the only portion of the organization that knows or cares ANYTHING about security. This has nothing to do with the IT department being snoops and everything to do with the perspective of everyone else in the organization.

    And it's absolutely not just because non-IT people don't understand computers. Computer-systems security is not the only kind of security they don't understand. Think in terms of locking the money in a safe every night and then keeping the safe key in a desk drawer ten feet away and NEVER EVER changing where it is kept, not in the entire time I have worked there. They did finally start locking the office door most nights (but NOT every night, because certain mornings there's nobody there with a key, and they HAVE to be able to get in there) after there were two unexplained thefts, which might or might not have been inside jobs, it was never determined. (I suspect they were probably NOT inside jobs, because it's been months now and no repeats. A thief usually can't stop stealing, so that probably means it's someone from outside the organization and they've moved on to steal elsewhere. But that's a guess.) And the staff were never careful about letting the general public see where the money was put at night when they were getting ready to close up. (Put the money away AFTER closing? Heck, no, that would mean the employees would have to stay in the building after closing for an extra thirty seconds.)

    I don't expect non-IT people to understand about arcane technical details, like what a firewall does or how a worm differs from a virus. That's why you HAVE an IT department. But a total lack of interest in anything vaguely related to any kind of security as another matter entirely. If that's the environment, then of COURSE the IT people are going to be able to get in (to the computers, to the building, to the money, to whatever) after leaving, not because the IT people are snoops, but because no precautions are taken against it.

    And I said I would still be *able*, if I leave (or am fired), to get into the network. I didn't say I'd DO it. You have to watch out for that sort of thing in the wording of questions too, because IT people take things fairly literally. How you ask the question actually matters.

    --
    Cut that out, or I will ship you to Norilsk in a box.
  44. Corporate Snoop? Wearing a tie with cornrows? by jsolan · · Score: 2, Funny

    fo shizzle

  45. Ethics anyone? by Anonymous Coward · · Score: 0

    Maybe it is just me but I've always considered it unethical to even attempt to log in to a previous employer's system. After all, I did a job, they paid me, and now our relationship is over. It annoys me when people brag, "yeah, I can still get into my old accounts." Like that is some impressive feat of engineering.

    People need to grow up and gain some ethics. After all, do you go back to an old apartment with a spare set of keys "just to see" if you can unlock the front door?

  46. User sheep by techpawn · · Score: 1

    As a DBA part of what I do is actively monitor outside query executions to relation to server performance. Really wicked looking monitors display this information constantly of the external system, internal users come by asking if I'm able to see what they're doing and I give them the honest answer of "Yes... But you guys aren't that interesting." They automatically assume that because I can be big brother that I AM big brother.
    I only monitor specific user activity if they complain of performance problems. But, the monitor for external user activity is always up so they think I'm always watching them. It's all about perception.

    --
    Ask not what you can do for your country. Ask what your country did to you
  47. oh duh by WeeBit · · Score: 1

    Cyber-Ark Software, a company that, naturally specializes in password protection.

    Maybe they proved their point about access to the departments data. But they didn't prove to me that they accessed the data in order to commit harm to the business. There is maybe a slight number of ex employees that still have access that you probably need to worry about more. Those will be the ones, that would never admit to being able to access the data.

    Cyber-Ark Software has a lot to gain by inflating the risk.

  48. too common even in bigger companies by Anonymous Coward · · Score: 0

    These things are all too common. I used to work for a rather large ISP doing simple "level 1" technical support. I worked there about two and a half years before the place was bought out and the office moved about 45 miles away and I decided not to continue working there since I didn't want to move or drive that far. FOUR YEARS later i STILL have an ftp account on their server, webspace and last I checked....a dialup account. Since there was also an issue during the "move" there are several people who now have free dialup accounts, email & webspace and have never been billed for it to this day. But as far as snooping goes, I am guilty as charged for poking around all too much. Infact one time a buddy and I modified a few programs and were able to get everyones email password, see what they were doing, modify traffic and so on. Actually if we had any hostility in mind we could of shut 90% of the place down on demand without anyone being able to tell how it happened or who even did it. Of all the things that we ever found wrong with anything there almost none of it was ever fixed and that is still the way everything there operates to this day even though they handle 100,000+ customers

  49. Unpatched holes by billcopc · · Score: 1

    It would be interesting to see just how many security holes go unpatched because the new IT guy takes an interest in the vulnerability. For example, let's pretend I'm the big cheese admin leaving the company, and I have a nice little backdoor that I leave open for my own dirty uses. My replacement finds my backdoor, and is faced with a few options:

    1. Close the vulnerability and stool me
    2. Close the vulnerability and keep quiet (to keep management from panicking)
    3. Leave it open and ignore it (unlikely)
    4. Leave it open and exploit it

    And if the new guy is really young, there's always:

    5. Leave it open and tell all his friends about it, get busted and spend the rest of his life doing crap jobs because he now has an ugly criminal record

    But seriously, I'd be willing to bet a good portion of the new guys, maybe 25% or so, would simply take advantage of the vulnerability for their own voyeuristic tendencies. I dunno, maybe I've worked with too many skeevy techies, my perception could very well be skewed.

    --
    -Billco, Fnarg.com
  50. For a fast climb up the IT corporate ladder.... by bodland · · Score: 1

    Be the security Nazi...watch how fast you get promoted and lavished with praise and money. Here is a template.
    In still fear by over promoting the risk.
    Hire a aduiting firm to tell you what to do.
    Install keyloggers on each workstation and create the corporation's largest database. Then implement a sexy program to find "bad thoughts"
    Fire a few people and put the fear in your employees.

    Who cares if it has nothing to do with the business...we at war.