IT Decisions Makers and Executives Don't Agree On Cyber Security Responsibility (betanews.com)
Sead Fadilpasic, writing for BetaNews: There's a severe disconnect between IT decision makers and C-suite executives when it comes to handling cyber attacks. Namely, both believe the other one is responsible for keeping a company safe. This is according to a new and extensive research by BAE Systems. A total of 221 C-suite executives and 984 IT decision-makers were polled or the report. According to the research, a third (35 percent) of C-suite executives believe IT teams are responsible for data breaches. On the other hand, 50 percent of IT decision makers would place that responsibility in the hands of their senior management. Cost estimates of a successful breach also differ. IT decision makers think it would set them back $19.2 million, while C-suite thinks of a lesser figure, $11.6m. C-level thinks a tenth (10 percent) of their company's IT budget is spent on cyber security, while IT decision makers think that's 15 percent. Also, 84 percent of C-suite, and 81 percent of IT teams believe they have the right protection set up.
Much like breaking the law and paying a fine has become a cost of doing business, so too has getting hacked and paying a lawsuit settlement become a cost of doing business. No one goes to jail, no one cares. The legal calculus is the same.
If the C-Suite wants to give the responsibility to IT for security decisions, they can start by losing their "I have to have this cool gadget, but there is no business justification" toys.
They can also stop demanding to be exceptions to any security policy that inconveniences them, like full-disk encryption, local administrative rights, multi-factor authentication and complex passwords.
Learning HOW to think is more important than learning WHAT to think.
Managers don't care about security. They give you no time and resources to properly implement it. Then when the breach happens, they suddenly care A LOT about security, and it's all your fault.
There needs to be set security standards for the industry, and managers should have to sign off saying they don't care about these standards when they choose not to allocate the proper time and resources for security.
I know what a C-level exec is. What is an "IT Decision Maker?" The full article is basically the summary plus a bit of fluff with no sources and no additional information.
Is "Decision Maker" ManagerSpeak for "Security Team?" Otherwise, it sounds like the study may just be contrasting the opinions of middle-upper and senior management, which sounds pointless.
The Daddy casts sleep on the Baby. The Baby resists!
When you have a situation where each party is blaming the other, the cause is almost always a lack of effective communication by BOTH sides.
If each thinks that the other is responsible, then neither has successfully articulated their opinions to the other.
As an IT person, I do not mind being given the responsibility for handling cyber attacks, as long as I am also given the express authority that "handling" will require, and the budget to provision security and prevention measures.
Of course, I am not going to get the budget that I ask for, no department head ever does. But then my acceptance of that budget comes with the written caveat that a reduced budget directly impacts my ability to "handle" cyber incidents and will increase the risk of successful attacks or sub-optimal mitigation of attacks.
The IT people are the one who understand the issues and can put things in place.
The C-suites must give the IT people the budget and the power - including telling C-suites that they cannot run their favourite games on corporate equipment.
In the event of a problem the C-suites must be the ones who are blamed, even if the IT people screw up (as they should have checked what they were being told by IT). This is the only way that there is a hope in hell that we might get close to getting this nailed.
This is one thing that Trump appears to be getting right. The latest draft of his Cyber security Executive Order puts the chief exec's butt on the line [ S1 (c) (i) ]. Let us hope that this is what he orders.
Security decisions ultimately come from the board of directors, not the C-Suite or the IT department. The board dictates what direction they way, the C-Suite manages that direction and IT executes the plan.
C-Suite should never be involved with security decisions beyond doing what they are told by the board. History I believe bares this out.
How can the IT department be held responsible if they aren't the ones making the decisions? The 'C-suite execs' have to authorize them first. Amirite?
“He’s not deformed, he’s just drunk!”
*no wrong... unlike we mere mortals who make typos
Don't worry. Perfect spelling is no longer a requirement at the Department of Education.
http://wqad.com/2017/02/12/education-department-misspells-tweet-corrects-error-with-another-typo/
3rd party vendors also have control and can make it hard to lock stuff down.
down time for reboots for updates needs to be ok.
What about old software stuck on 2003 / xp / etc? That the suits don't want to shell out the cost to buy new apps that run on 10 / 2012 / 2016?
In related news, 85% of both groups combined think they are good at their jobs.
Interviewer: You get paid the big bucks. Are you doing it wrong?
Interviewee #1: Well, gosh, I don't know.
Interviewee #2: Every damn time, and twice for breakfast.
Interviewer: Uh, #2, how long have you held your current rank.
Interviewee #2: The previous numbnut is still fumbling for his keys in the parking lot, with all his executive possessions packed in an open box, tucked under his left arm.
Interviewer: How about you, #1?
Interviewee #1: Twenty-two years.
Interviewer: Really? You've been running the IT department for twenty years?
Interviewee #1: Actually, no. I'm the janitor. The chief custodian wears a shirt and tie, so I do, too. Always dress like the boss, you know. Good career advice passed down from my grandfather. You can tell a lot from the texture and density of crumpled, yellow Post-It notes at the bottom of an executive can. I'm not sure about our current IT head. There are days where I think he's in the danger zone.
As this goes, that's probably more useful than the intended interview.
I'd say the only thing one can accurately get out of TFS is the fact that no one involved wants to be the scapegoat when the shit hits the fan.
Gotta love it when fucking finger pointing is the true cause of a vulnerable environment.
Dude, please! Grammar!
Twitter is a proper noun, so capitalize it. And there should be a comma between "Twitter" and "right". There should also be a comma between "petty" and "little", as they both are adjectives describing "bitch". And finally, some punctuation after the second sentence. From your tone I'd suggest an exclamation point, but a period could also be acceptable if you want to imply exasperation instead of passion.
Learning HOW to think is more important than learning WHAT to think.
God forbid anyone make a fucking typo on twitter right?
Spellcheckers exist for a reason. If you're releasing information to the public, it should be error free.
Fuck off you petty little bitch
Ignorance is not a virtue.
Shouldn't the real question be why to we allow vendors to make and sale products with insecure features, and standards, such as Flash, JAVA, VBS, etc..
The real problem comes from the standard that allows remote code execution on the user's machine. If you force people to use crappy tools you get crappy systems.
Crimer is the ahole who would give you heck for mistping a word if you are on the other side of the aisle from him, but if your own team can't find light switches, doesn't read executve orders before they sign them, and makes up msasacres then it was a simple mistake. amiright cremier?
This sentence is almost as annoying as an email from a receptionist who had a plugin for the Eudora email client that displayed each letter in a different color. People who downloaded email in plain text never saw the problem. The rest of us who downloaded in HTML saw the email in its full rainbow glory.
The issue isn't that each thinks the other is responsible, it's that each thinks they, themselves, are not.
IT people have to be the ones to implement. Executives have to pay for it. Proper security cannot be done without both buying in fully.
To frame the issue any other way is to fail.
Well IT is responsible for all the network equipment and infrastructure so if the data breach occurred because something was incorrectly configured then IT is 100% responsible. If the breach occurred on stationary work computers, that were NOT BYOC, IT is responsible. If the data breach occurred because the network was accessed and that access was not correctly configured, IT is responsible. If a computer enters the network that is not pre-authorized and already vetted, and gains unauthorized access IT is responsible. Basically if a computer is at fault, IT is responsible.
Security is the responsibility of the CSO.
Don't have a CSO? Well *there's* your problem. The board and the other Cs should have made sure there was a CSO.
Obviously, if the board and president blow off the CSO's warnings, override his decisions, and don't provide the needed budget, that's on them. It is the responsibility of thr CSO to document those facts.
I wonder many C-level executives can name their IT employees past the CIO/CTO or VP...
They just won't pay someone to develop it right.
No, I don't think that's the case. Any security you pay for is introduced too late. No exceptions. You can't hire security-minded thinking. You need to get everyone to think of security to start with, instead of trying to hire security, and it won't cost nearly as much.
I've worked at companies with 2,000 employees or less that have someone designated as being in charge of security. Many companies don't, that doesn't mean they can't or shouldn't.
> the CFO is often an external accountant and not a real CFO; they're auditing and doing tax work, and providing guidance
A similar model can be used for security. Companies like Alert Logic provide the backing of thousands of security experts in a 24/7 Security Operations Center at a cost starting at dozens of dollars per month. One company (which is a one-person conpany) pays me $100/month, which buys them a couple hours of my time every two or three months when they (he) make changes I should consult on or review. For $100/month he gets a career security professional with 20 years of experience who knows the company's systems inside and out at this point.
There's no excuse to not have anyone designated as being in charge of security.
Upper management just knows never to let profit be wasted on yet more hardware and software?
What about the generation shareholders? Executive bonuses are enjoyed every year. Why is that profit going on security hardware and software?
Are US legal teams haunted by some open court event in the 1980's or 1990's?
Logs finally showed an issue, law enforcement got contacted is all the compliance that needs to be public.
Showing a team understood an issue but could not prevent it or failed to report an issue in time while their security attempted to work the issue?
Incompetence might be legally better and could be cleaned up with good PR. The ability not to have any extra paper work and really not to know anything could be legally useful later? A politician asking questions could be halted with a comment about working with law enforcement rather than producing vast amounts of internal paperwork to show how company failed.
Been a brand in open court or before some gov committee reporting on people, crimes, naming other brands staff, products, services, what was done before law enforcement was contacted in great detail might not be very useful marketing.
Domestic spying is now "Benign Information Gathering"
It's the responsibility of IT decision makers to educate executives the value of cyber security security. Proper education is a risk/benefit/cost analysis rather than just fear mongering.
The goal is to get executive support for both programs and resources (especially $$$) that allow IT decision makers to implement proper security.
If IT decision makers are unable to influence and persuade, pass the management hat and go back to coding.
IT should be responsible if given sufficient resources and latitude to implement security measures. The problem is that that is not always the case. Many times one of those is lacking and that is the responsibility of the executives.
Time makes more converts than reason