Slashdot Mirror


Security's Shaky State

Ant writes "According to InformationWeek, Information Technology (I.T.) security professionals say when it comes to security, most I.T. departments are underfunded, understaffed, and underrepresented. Resourceful I.T. security professionals are getting the job done, but their efforts have been hampered by undersized staffs and underfunded budgets that limit choices ranging from what products they buy to the vendors they work with."

14 of 184 comments (clear)

  1. No one notices a well done security job... by jmp_nyc · · Score: 4, Insightful

    A major part of the problem is that CFO types don't like spending money on things they don't see a need for. By the time they see a need for security, it's past the point at which throwing money at the problem will fix things.

    Likewise, the security side of an I.T. department is the sort of job that is hard to justify to people who assume that if they don't notice results, the job isn't really doing much.

    Ah the glory of an invisible job.
    -JMP

    1. Re:No one notices a well done security job... by Velox_SwiftFox · · Score: 4, Insightful

      Sigh. I've learned "I don't understand why we need X" is all too often a warning from a superior that continuing to push for X (including by providing the supposedly requested info) may be a career-limiting move. OTOH, if X turns out to have been needed after all, not having gotten it is hard to explain to that same superior.

    2. Re:No one notices a well done security job... by jmp_nyc · · Score: 4, Interesting

      Sigh. I've learned "I don't understand why we need X" is all too often a warning from a superior that continuing to push for X (including by providing the supposedly requested info) may be a career-limiting move. OTOH, if X turns out to have been needed after all, not having gotten it is hard to explain to that same superior.

      I've experienced worse. At one company I worked at, I warned of the pitfalls of a particular implementation my boss had been sold on. I was ignored. When the problems I predicted showed up, I was then blamed for creating them.

      I quit that job as soon as a chance to move to a reasonably solid company came along...
      -JMP

    3. Re:No one notices a well done security job... by CrazyClimber · · Score: 5, Funny

      I was going to moderate this thread until I saw your post. There's no option for "needs hug" and you sure deserve it.

    4. Re:No one notices a well done security job... by jmp_nyc · · Score: 4, Insightful

      I was going to moderate this thread until I saw your post. There's no option for "needs hug" and you sure deserve it.

      Thanks, but I did gain an important bit of wisdom working there. The company brought in a supposedly hot shit developer to build systems. In departmental meetings where we went over our current projects, he was never interested in hearing about anyone else's project, but more importantly he got defensive when asked questions about how he dealt with various potential pitfalls. It turned out that he usually simply didn't deal with the pitfalls.

      It's no wonder that the project managers dreaded having their projects assigned to him, as they would not only take longer to get to launch, but he would rush things past testing because he presumed himself to be infallible. His projects therefore always launched with bugs. (We're talking basic things here, like web apps for thousands of concurrent users that couldn't handle concurrent requests.)

      Not only did I come away understanding the importance of bouncing ideas off others, but ever since that experience, I'm overly self-conscious about making sure to listen carefully to questions asked by people who aren't immersed in my projects. I find that those questions can often save me great deals of aggrivation later in the dev process. I don't want to be a master-of-the-universe hot shit developer. I want to build things that work.
      -JMP

    5. Re:No one notices a well done security job... by Frater+219 · · Score: 4, Insightful
      Likewise, the security side of an I.T. department is the sort of job that is hard to justify to people who assume that if they don't notice results, the job isn't really doing much.

      Here's a possible fix for that situation: Document and present to your bosses the nature of what you are preventing.

      Gather information about sites that are less fortunate or less competent than your own. Make sure that your boss knows when your competitor's Web site gets vandalized, or when some well-known business starts spewing out virus spam. Provide information about the specific techniques that you used which kept that from happening to your site.

      "In May of 20x6, businesses and home users across the Internet were hit by the Quigmorf worm, which was reported on the front page of the New York Times as causing $25 billion in damage. Our mail server anti-virus filtering rejected an average of 16 copies of this worm per second over the worst day of the outbreak."

      Disseminate periodic alerts about viruses that have stricken other sites, but which your own defenses are ably filtering out. Couch these in the language of protecting your users from threats they may face on other (and hence lesser) networks.

      "This Monday, Snarkashvili Anti-Virus discovered a new virus known as 'Quigmorf'. This virus infects Windows systems by sending email messages with a subject line of 'I love Quigmorf, click here to see why!' Infected systems become very slow and send out thousands of viruses to other email users. While our mail server anti-virus program is blocking Quigmorf, your home ISP may not be. Be sure to delete any messages with this subject line without opening them."

      Instrument your systems. Gather logs and present them in understandable form. Bosses know what a quarterly report is, and they can understand claims such as:

      "In 4Q05, our mail server blocked an average of 100 spam and 50 viruses every minute. This is a 25% increase over last quarter, and a 50% increase over last year. Spam complaints to spam@oursite.net are down by 65% over last year on a total email volume of 30% more messages. We attribute the improvement to the free open-source anti-spam and anti-virus programs that we installed last quarter."

      If worse comes to worst, you could always try talking time and money:

      "Our mail server blocks 100 spam every minute -- all day, every day; during working hours and after hours. It takes approximately 3 seconds for an employee to look at a message, recognize it as spam, and press the Delete key. This means our mail server does the work of more than twenty full-time employees dedicated to doing nothing but deleting spam."

      It's true! (100 spam / minute) * (1 minute / 60 sec) * (3 person*sec / spam) = 5 person, but a person only works less than 1/4 of the time (8 out of 24 hours, 5 out of 7 days) whereas a mail server works 24/7.

  2. Simple Reason by matr0x_x · · Score: 4, Insightful

    The IT Security department does more preventative solutions then anything else... so basically, if you don't hear booh about them, it's a good thing. Essentially, the better the job they do, the less the management of a company realizes they are important. "Oh, well we haven't gotten hacked in 3 years... we can afford to cut our security department budget this quarter".

    --
    LINUX ONLINE POKER: Linux Poker
    1. Re:Simple Reason by aussie_a · · Score: 4, Insightful

      Which is crazy. You don't hear people say "oh you know. I haven't been broken into in the past 3 years. I think I can replace my deadbolt with a padlock I brought from K-mart." Why companies continue to short-change their data security (in what many people claim is the Information Age) while beefing up their physical security. And whilever they continue to do this, we'll continue to hear of times when credit cards are stolen. Oh, I just realised why they don't care about information being stolen. Because it's only customer information. And it's not being stolen like physical objects, it's being duplicated.

      Until these companies are forced to care about their customer's data (and customers aint doing shit about it at the moment), they won't.

    2. Re:Simple Reason by plover · · Score: 4, Insightful
      The actual PCI requirements are for your company to establish standards and then document following them. But the details aren't completely spelled out by the PCI. Visa CISP did add certain restrictions, such as "you must never write certain Visa card data (Discretionary data, CVV2) to a storage device," and "if you keep the account number and the related guest data together, you must encrypt it."

      But they certainly made no such foolish rule as "YOU MUST STORE the data AND encrypt it." If anything, that was a misread at your company of "IFF you must store the data THEN you must encrypt it." Their guidelines are sound. The Visa cryptographers I've met with have been really sharp, and wouldn't allow a chump mistake like that to creep in.

      --
      John
  3. SOX by Bonker · · Score: 5, Insightful

    Sarbanes-Oxley act is the new security-minded sysadmin's best friend.

    Managers and Execs start taking IT security a hell of a lot more seriously when they realize they can go to jail if they're implicated in fraud.

    To comply with SOX, you have to document all your procedures, all your data flow, and make it available to gov't regulators. You also have to document what holes you're aware of in your systems and how you plug them.

    Whistleblowing is quick, easy, anonymous, and DEVESTATING.

    SOX ROX.

    --
    The next Slashdot story will be ready soon, but subscribers can beat the rush and slashdot the links early!
  4. Unions are a good idea by ReformedExCon · · Score: 5, Insightful

    It's unfortunate that unions have gotten such a bad rap, especially among engineers in the computer-related fields. For all the Randian talk of rugged individualism, most people really are just sycophants and sheep. That's not bashing, it's just the way it is. For every engineer demanding better pay and working conditions, there are one thousand who are just happy to collect a paycheck every two weeks. If the industry was made up of solely the former type of engineer, there really wouldn't be any need for unions, each person acting in his own self-interest would be a union unto himself.

    However, when you look around and see people working 40+ hours a week, working on the weekends, working through the night, showering at work because they don't have time to go home, and being pushed through project cycles that are causing undo stress, something is wrong. The balance of power is not maintained and the employers are exploiting the engineers. That "great" paycheck you're raking in every two weeks suddenly comes out to barely double minimum wage when you break it down hourly. The cost to your family is also incredibly high as they don't have you around. It's a terrible situation.

    So what's the solution? Well, the favored solution among the computer cognoscenti is to "go find yourself a new line of work". Why should someone who is good at their job be forced to take a different job just because the industry is unwilling to offer a fair wage as well as reasonable working conditions? It should not be a requirement that anyone who wants to work in the computer industry should also be forced to give up their personal lives. Unionizing is one very good way of forcing employers to bend to the needs of the employed.

    It's unfortunate that so many people are against the idea. We ought to be working to live, not living to work.

    --
    Jesus saved me from my past. He can save you as well.
  5. Overprivileged workers by phorm · · Score: 4, Insightful

    My biggest beef is not the lack of staff or budget but the lack of discipline. Nowadays it seems that everyone *needs* a computer at their desk, and they seem to have no problem misusing company resources. I don't mean things like checking email while on the clock, but rather installing their favorite IM program, or perhaps a fancy calendar doodad or toolbar (laced with an unhealthy dose of spyware, of course). Let us not forget those "important people" higher up the chain that would have your hide if you even mentioned that perhaps they shouldn't be using Kazaa on a company machine or opening every email attachment under the sun.

    There was a day where staff were wary of computers, and treated them with respect. Those days have long past... all they're wary of is that weird IT guy who tries to tell them what to do with their machine.

  6. And maybe that isnt a bad thing by 3ryon · · Score: 4, Insightful

    First of all, I agree that security is a typically under-appreciated job. However, I've also seen what happens with security has the power to implement whatever tools/measures they want. That situation is probably worse than the lack of security at most places...not only can your security team get in the way of the business with insane risk avoidance policies (making the business less efficient), but it can be directly expensive in the price of staff and tools.

    Security people need to understand that not every risk has to be avoided. Many risks are an acceptable trade off to allow the business to be efficient. Honestly, I want my security team to be a little paranoid...but I want their manager to have a good understanding of the impact security policies can have on the people who do the things that bring money into the company.

  7. Re:The value of the IT department by lanced · · Score: 4, Insightful

    Wow! Where do I begin to comment on that? Your first assertion, that companies will calculate the cost of failure versus the cost of prevention, is completely true; that is why and how insurance works. Alternatively, that is why punitive damages tend to be so high in the most egregious court cases; the court is trying to tilt the equation in favor of humanity -- hot cups of coffee not withstanding.

    That being said, the value of data has increased exponentially in the past 5 to 10 years and companies have not fully accounted for that rapid shift. I saw a study a few years ago that said at least half (but I seem to recall that it was more like 90%) of all business will go out-of-business within 1 year of a major data loss. That was before the .com boom. That figure has probably only gotten worse. Keep in mind, only than 15 years ago, 'the web' didn't exist. Now, my office virtually halts when e-mail stops or a fileserver crashes. Imagine your day if suddenly all of the computers became unusable. How does your office fair?

    As for IT techs being underpaid, that has very little to do with the value of the work you are doing. It has much more to do with the number of you that are doing the work. It is a classic economic supply and demand problem: an abundance of paper technicians (MCSE, A+, etc), 18-year-old 'ub3r g33ks' and other money-driven late-comers to the .com boom has allowed companies to turn system administration and helpdesk support into commodity jobs and consequently also low-skill jobs. Unfortunately, these types often have never been taught proper security practices. This class of worker learns only from experience. It's like expecting the construction workers to calculate the structural soundness of a skyscraper.

    But what scares me more than a lack of real investment in security within the private sector, is the lack of investment in security by the public sector. I used to work in 'cyber security' for a major governmental research organization. The department has quite a reputation for the quality of its security infrastructure research, but the department is still only 10 regular employees and about 30 summer interns. And the department's budget was provided by and was a significant portion of the cyber security expenditures for a few of the major US departments. A major cyber security gaff at a blue chip would strain the US economy, but a major cyber security attack on public utilities could cripple North America (Canada, I'm looking in your direction too...).

    I'm off my soap box now. Thank you for your attention. You may now resume your hacking activities.