Stories
Slash Boxes
Comments
typodupeerror delete not in

Comments: 147 + -   Pennsylvania CISO Fired Over Talk At RSA Conference on Thursday March 11, @05:07PM

Posted by timothy on Thursday March 11, @05:07PM
from the perfecting-the-art-of-the-ham-fist dept.
censorship
government
An anonymous reader writes "Pennsylvania's chief information security officer Robert Maley has been fired for publicly talking about a security incident involving the Commonwealth's online driving exam scheduling system. He apparently did not get the required approval for talking about the incident from appropriate authorities."
story

Related Stories

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Must have not got the memo..
  • by AliasMarlowe (1042386) on Thursday March 11, @05:11PM (#31444352) Journal
    What's the story here? He blabbed on a security issue without approval, and got his ass roasted.
    • by DoofusOfDeath (636671) on Thursday March 11, @05:15PM (#31444416)

      What's the story here? He blabbed on a security issue without approval, and got his ass roasted.

      The same reason I don't want nuclear regulators getting fired for admitting when there was a heavy water leak into an aquifer.

      • by HungryHobo (1314109) on Thursday March 11, @05:18PM (#31444486)

        If this were a private company I'd be of the opinion that their internal security is their concern but this is a government office and the people who pay the bills have a right to know what's going on.

        • by Mathinker (909784) on Thursday March 11, @05:54PM (#31445078) Journal

          If this were a private company I'd be of the opinion that their internal security is their concern but this is a government office and the people who pay the bills have a right to know what's going on.

          If the internal security failure lead to your private information being leaked and the possibility of financial loss to you, I think that you might be of the opinion that there should be legislation which deals with disclosure. Actually, there is such legislation in many jurisdictions. And you also have Sarbanes–Oxley stuff which is supposed to encourage whistleblowing.

          Some "internal" things are more internal than others....

      • The same reason I don't want nuclear regulators getting fired for admitting when there was a heavy water leak into an aquifer.

        Apples and oranges, one is a health risk, one isn't.

        • Re: (Score:3, Insightful)

          by crymeph0 (682581)

          ...He just yapped without checking.

          Which is just sloppy corporate citizenry.

          Except his employer isn't "corporate", they're a U.S. state, funded by taxpayers. As a taxpayer, I demand to know if there are security (or "configuration") holes that have been actively exploited at the institutions my taxes fund, unless the dissemination of such knowledge would hurt an ongoing police investigation. There is no mention in the story of such a request from the police, just a general indication that the police are investigating.

    • by firewrought (36952) on Thursday March 11, @05:38PM (#31444844)

      What's the story here? He blabbed on a security issue without approval...

      The firing seems heavy-handed. Don't you want your Chief Information Security Officer participating in industry security conferences, selectively sharing the experiences of your organization with security professionals so as to help find long term solutions? Who knows... maybe he shared some sort of special classified/secret/private data that he really ought not to have, but it sounds like good old bureaucracy + control freaks at the top who think it's all about militaristic need-to-know.

      • Re: (Score:3, Interesting)

        by OzPeter (195038)

        What's the story here? He blabbed on a security issue without approval...

        The firing seems heavy-handed. Don't you want your Chief Information Security Officer participating in industry security conferences, selectively sharing the experiences of your organization with security professionals so as to help find long term solutions?

        Do you want this happening while there is apparently an on going investigation? There are reasons why there are approval rules and they aren't about old bureaucracy and control freaks

      • Re: (Score:3, Informative)

        by ircmaxell (1117387)
        You do realize that he didn't work for a company, don't you? He worked for the state government...
      • Re: (Score:3, Funny)

        by Locke2005 (849178)
        "You want the truth? You can't handle the truth!"
      • You really don't see the story? This is a security breach involving a public computer system THERE SHOULD BE NO SECRETS WHEN TAXPAYERS' MONEY IS INVOLVED.

        Do you really want the taxpayers having the root password?

        • by plover (150551) * on Thursday March 11, @06:21PM (#31445468) Homepage Journal

          Do you really want the taxpayers having the root password?

          I'll give them to you. There are actually two root passwords to the Constitution: "terrorism" and "child pornography". By using either password, you can bypass any of the security protections or protocols built into the document, and you can invalidate its signatures.

          • Re: (Score:3, Funny)

            by Chris Burke (6130)

            Just a practical note from personal experience. Screaming "child pornography" at the top of my lungs did not let me undo the Constitutionally granted power of the Executive Branch to create law enforcement agencies to enforce federal laws while agents of said agencies were hauling me away. Quite the opposite in fact.

      • by Fjandr (66656) on Thursday March 11, @05:55PM (#31445094) Homepage Journal

        If the CISO treats one rule casually, what is the dolt liable to ignore next?

        This is probably one of the most specious arguments anyone ever trots out about someone breaking (or overlooking) a rule, especially in organizations known for coming up with rules for every single thought or action one engages in (e.g. a bureaucracy). Unless the incident was actually ongoing, or had the potential to risk the security or integrity of the systems it was his job to oversee, talking about a past incident germane to the topic of the conference is what people do at conferences. That's the entire point. Yes, he violated a minor rule. "Oh lordy lordy, who will he kill next?" is not really the best response to the situation.

          • Re: (Score:3, Interesting)

            by Fjandr (66656)

            Every time the media has reported on something I knew about personally, I was always shocked at the number and magnitude of factual errors they made, the twisting of focus away from the main issue.

            I agree 110%. The stories I've seen broadcast about events I had personal knowledge of made it so I trust the media story about as much as I'd trust a junkie with the safekeeping of a kilo of heroin.

            I was mostly responding to the theory that if someone screws up once in a (seemingly) minor way they are untrustwort

      • Re: (Score:3, Insightful)

        If the CISO treats one rule casually, what is the dolt liable to ignore next?

        Not every slope is a slippery one.

  • Good job... (Score:5, Insightful)

    by kurokame (1764228) on Thursday March 11, @05:13PM (#31444388)
    Firing the guy will absolutely convince the public that you've fixed your security problems.
  • by Anonymous Coward on Thursday March 11, @05:14PM (#31444412)

    (had to make sure I hit the "Post Anonymously" button...)
    I'm one of many server administrators for LUTX, the (US) Federal Government IT "swat team" that was put in place during the Clinton Administration. One day I was working on a code-blue 456 system using the X-K-Red-27 technique and suddenly a bunch of drunken Canadian's broke in and try to SSH the HTTPS server. Well, as you can imagine, all hell broke loose and we had to double-slot the uranium deuteride fast on the flip-flop before the Russkies could notice.
    I hope I don't get fired for sharing this amazing story with Slashdot

    • by OzPeter (195038) on Thursday March 11, @05:35PM (#31444772)

      (had to make sure I hit the "Post Anonymously" button...) I'm one of many server administrators for LUTX, the (US) Federal Government IT "swat team" that was put in place during the Clinton Administration. One day I was working on a code-blue 456 system using the X-K-Red-27 technique and suddenly a bunch of drunken Canadian's broke in and try to SSH the HTTPS server. Well, as you can imagine, all hell broke loose and we had to double-slot the uranium deuteride fast on the flip-flop before the Russkies could notice. I hope I don't get fired for sharing this amazing story with Slashdot

      Its times like this that I really want to apply a Post Humously moderation

    • Re: (Score:3, Funny)

      by kybred (795293)

      a bunch of drunken Canadian's

      -1: redundant

  • reasonable? (Score:5, Insightful)

    by DaveGod (703167) on Thursday March 11, @05:16PM (#31444438)

    Seeing as careless talk can lead to image problems and/or lawsuits (or harming your case if prosecuting them). If you're in a senior position and you talk publicly in a work-related context, you talk on behalf of the organisation whether you intend to or not. OTOH if you are "blowing the whistle" on wrongdoing, there is a specific procedure for that which offers protection.

        • Re: (Score:3, Insightful)

          "You don't get given authority to say what you please, you get given authority to apply policy."

          Point being he was the CISO. He is the very one not to apply but to *create* the policy in regards to IT security incidents.

          If you don't want somebody to have such power you don't get to create the role.

  • by introspekt.i (1233118) on Thursday March 11, @05:25PM (#31444610)
    Who fired him? Sounds like he made the wrong people look bad. Rules are rules, I suppose, but if the problem has been fixed, isn't talking about security and attack vectors generally a good thing?
    • Obviously, his manager doesn't read /.

    • by tlambert (566799) on Thursday March 11, @06:07PM (#31445254)

      Who fired him?

      According to public records having to do with reporting structure, he would have been fired by Brenda Orth, CIO (Chief Information Officer) in the OA (Office of Administration, Commonwealth of Pennsylvania). The reporting chain is easily verifiable using either the Google cached copy of their page, or the Internet Way Back Machine.

      She basically reports to the state Governors staff, so there's no telling how far up hill you'd have to go to find the source of the firing, but as his immediate supervisor, whe would have been the one to pull the trigger.

      -- Terry

  • by haruchai (17472) on Thursday March 11, @05:26PM (#31444616)

    Now all your remaining security issues will fix themselves. But, don't worry, I'm sure Robert Maley will be happy to help you out - at 5 times what you were paying him.

  • The key paragraph (Score:5, Informative)

    by Wintermute__ (22920) on Thursday March 11, @05:32PM (#31444716)

    The important paragraph in TFA:

    "Maley's dismissal comes amid ongoing budget and staff cuts at Pennsylvania's IT security organization, the source said. Over the past 18 months to two years, the administration has cut information security budgets by close to 38%, and staff by 40%. They also put a "lockdown" on talking about cybersecurity, the source claimed."

    Now there's a good plan: If you don't talk about it, no one will know you have a problem, and you can save all that money you were spending on those annoying security types.

    • by timothy (36799) * Works for Slashdot on Thursday March 11, @07:09PM (#31446198) Homepage Journal

      Howard County, Maryland (back when I was living there -- might be many other places like this, too) decided to make the local parks "trash free." By removing the trash cans. I leave the results as an exercise for the reader ;)

      timothy

  • Easy fix? (Score:4, Insightful)

    by Shadyman (939863) on Thursday March 11, @05:32PM (#31444720) Homepage
    From TFA: Over the past 18 months to two years, the administration has cut information security budgets by close to 38%, and staff by 40%. They also put a "lockdown" on talking about cybersecurity, the source claimed.

    So instead of paying people to fix our security holes, we're just not allowed to talk about them?
    • by plover (150551) *

      So instead of paying people to fix our security holes, we're just not allowed to talk about them?

      It's a hell of a lot cheaper that way. (Except for the parts where the bad guys break-in and steal your stuff; yeah, those are kind of expensive, but fixing them doesn't come out of the CIO's paycheck.)

      Therefore this is all your fault for complaining about your taxes. You said to your lawmakers "we want less state services and lower quality workers" and there you go! You got exactly what you voted for.

  • by Archangel Michael (180766) on Thursday March 11, @05:33PM (#31444738) Journal

    If I were him, I'd start spilling all the info I ever had on security for the state. No amount of money or threats would stop me.

    I mean any and every item. I'd expose every stupid supervisory move that compromised security and my ability to protect the network. EVERYTHING would be exposed.

    Nothing worse than people getting their panties all in a wad over a "talk" about a well publicized incident, of which all the bad guys already knew about.

    There is only one thing these people understand, and that is how to look good. Ruin it for them.

    • by plover (150551) * on Thursday March 11, @06:35PM (#31445660) Homepage Journal

      Compromising your own ethics for revenge is a net loss. A vengeful, spiteful CISO would have about 0.00% chance of a new job that paid anything above "volunteer" wages.

      Remember, CIO already jokingly stands for "Career Is Over." I don't think he needs to pile on "Career Is So Over" limiting moves by acting like a 13-year-old dumped by his first girlfriend.

        • by plover (150551) * on Thursday March 11, @08:38PM (#31447162) Homepage Journal

          A whistleblower reveals secret information to right a wrong. Perhaps there's a safety issue that is going uncorrected, or an unfair pay gap, or workplace racism, or where the bodies are buried. Those are kept secret to keep costs down at the expense of human health, or to protect the criminally negligent or guilty.

          The GP said:

          If I were him, I'd start spilling all the info I ever had on security for the state. No amount of money or threats would stop me. I mean any and every item.

          There are plenty of legitimate secrets a CISO is expected to keep. Plans for upgrades that reveal current deficiencies but can't be implemented yet due to budget constraints. Ongoing operational security tasks. Or command and control structures: a list of the three key people without whom an emergency response would fail would provide a juicy target list for a serious attack. The identities of sting or honeypot operations. Those are all perfectly legitimate security items that should be kept secret.

          A whistleblower is trying to correct an inequity. A traitor provides secret information only to damage an organization. See the difference?

  • Another telling fact from the article is that the security staff and budget have both been cut by upwards of 40%...no wonder they don't want anybody talking...
  • Cluetrain... (Score:3, Insightful)

    by jacks0n (112153) on Thursday March 11, @05:41PM (#31444896) Homepage

    Cluetrain Manifesto.... Dead. Slashdot Confirms.

    I'm personally not interested in what comes out of any organization's public orifice because it always looks and smells like BS.

    When they shut down their non-public orifices they become more and more useless. They lose value. real, actual dollars value.

    In a way I'm more worried about this from a public organization because they have a monopoly on governance

    and when they're doing it wrong they can keep doing it wrong a lot longer than a private company.

  • by Anonymous Coward on Thursday March 11, @05:44PM (#31444926)

    I'm simply rehashing the same thing I wrote over at SC Magazine's site:

    We do not know all the facts behind the termination, but if was based primarly on his RSA appearance, that's a shame. There are so many variants of qualitative and quantitative risk assessment, that regular meetings with your peers seems to be just as critical with regards to understanding the important controls which need to be put in place. The days of leading with FUD appears to be in our rear view mirror, and building up a positive outlook in security by learning from the past and attempting to stay ahead of the curve is imperative to our support of the business or the public entity. What was the common theme with all the CISO's at RSA? Information sharing is critical and we're way behind. We don't share information, we put ourselves on "lockdown" and don't get invited to the table anymore as security professionals. We're seen as roadblocks, as negative drags on the bottom line. Something has to change or else we're going to lose ground as a country. In fact we already have.

    Sharing information with other professionals is now critical to any InfoSec career. We do need to account for privacy, so a balance must be achived. Maley may have violated a confidentiality component of his employment, but that doesn't make the spirit of what he did wrong in any way. If anything, some clear guidance on what types of information is shared behind closed doors at peer review and group meetings at RSA should be discussed. You can't vette everyone who attends the meetings, but openness is a good thing, not a bad thing. More transparency is needed across the public and private sectors. More openness is needed among security professionals. The state of PA has it wrong. Lockdown is not a way to progress forward out of this losing battle with regards to properly securing the infrastructure while allowing the inevitable growth of technology and information.

  • lucky not to be in jail as other who have came out with info on security incidentes / holes have been locked up.

  • by BlueBoxSW.com (745855) on Thursday March 11, @06:20PM (#31445444) Homepage

    Didn't he know that you're only supposed to talk at conferences when A) you have something to sell, or B) you're being paid in a round-about way to promote a product while appearing to have no conflicting interest?

    No one does a post-mortem of ACTUAL issues that matter to ACTUAL people, anymore.

  • First rule (Score:5, Funny)

    by 93 Escort Wagon (326346) on Thursday March 11, @07:01PM (#31446058)

    The first rule of Commonwealth's online driving exam scheduling system is: You don't talk about Commonwealth's online driving exam scheduling system.

"Why are we importing all these highbrow plays like `Amadeus'? I could have told you Mozart was a jerk for nothing." -- Ian Shoales