The Effect of Snake Oil Security
Trailrunner7 writes "Threatpost has a guest column by Robert Hansen (aka Rsnake) about the long-term effects of snake-oil security products. 'I've talked about this a few times over the years during various presentations but I wanted to document it here as well. It's a concept that I've been wrestling with for 7+ years and I don't think I've made any headway in convincing anyone, beyond a few head nods. Bad security isn't just bad because it allows you to be exploited. It's also a long term cost center. But more interestingly, even the most worthless security tools can be proven to "work" if you look at the numbers.'"
I think it's also a very hard concept that Good security can fail some times as well, so it's hard for some managers and others to understand the difference between good security failing and bad security having really never worked at all...
Good security can fail when new venerabilities are found, when risk assessments are not up dated in a timely manner, to do human / operator errors, etc.
http://www.hawknest.com/
Insightful article. It was worth it just to read the bear in the woods analogy, which will give you a good laugh.
But more interestingly, even the most worthless security tools can be proven to "work" if you look at the numbers.'"
Of course.. look at Mcafee
Statistics can be made to show anything, managerial and C-level executives have to be more responsible and in the end it's cheaper to just let the customers eat the costs of bad security rather than fail trying to do something about it.
The main problem imho is that there are no real punishments when something goes bad. If somebody gets hacked the old adage of "it's happening more often throughout the industry" is used to redirect the blame from the gatekeepers to the attackers. If somebody doesn't get hacked while the competition is, the executives get praised even though they might not have done anything meaningful. Back in the day when castles (security products) were used to protect a lord (the data or the company) and the gatekeeper (managers and sysadmins) didn't do their job, the gatekeeper would get flogged, stripped naked and/or executed. The soldiers didn't blame someone else when somebody invaded their castle and they didn't pat themselves on the back as 'doing a good job' when the neighboring castles were ransacked.
Security procedures have nothing to do with the rest of the industry. Most likely they're unique to your company and structure, and one time, you're going to be up for a targeted attack and you should be ready at all times.
Custom electronics and digital signage for your business: www.evcircuits.com
Meh, everybody knows that a big fence grabs the attention, because you "must" have something to hide.
Anybody can kinda protect a Windows machine by just having spybot, a password and a firewall on his modem/router, for free.
But any big (I mean non free) antivirus will be useless against the stupidity of the end user.
- Do you really want to open pornIMG.exe ?
- YA RLY!
I think we will solve the issues of computer security about the same time we figure out how to deal with conflicts within ourselves and humanity.
Encase your systems in concrete. On the moon. This security will mean you won't have any serious worries about being hacked. Anybody with the spare billions to spend getting access surely has better things to do with their time. It's practically foolproof when you think about it.
Actually using your system? Sorry, that's somebody else, I'm only offering security.
It can also act as a laxative, leading to anal leakage.
http://alternatives.rzero.com/
Stop using MS. The "security" side is like asking if you like your snake-oil with extra cocaine, sugar or alcohol.
Get over the lecture, assistants in the crowd and find a tonic that works. Something based on folk remedies, homespun remedies which-by trial and error have proven to work.
Domestic spying is now "Benign Information Gathering"
Suck it, squirrels! You can not have them!
Snake Oil Security? I use their SSL certificate to lock down all my Apache boxes.
http://httpd.apache.org/docs/2.1/ssl/ssl_howto.html#certauthenticate/
When your webserver dumps its cargo at the first sign of an Imperial Cruiser ...
It isn't just security. I supervise the IT audits in our company, and I can't list anymore how often fake procedures have been tried to pass of as actual processes. Right now, our software development managers try to tell everyone how "agile" they are - but the real work their people do has nothing to do with agile development whatsoever. I've seen so-called "change management" that wasn't worthy of even being in the same room with actual change management, and "access controls" that were essentially bullshit in paper form.
There are usually two causes for this: Malicious people who are greedy for either power and/or money, or incompetent people who don't understand what they're doing (or managing) but are too afraid to ask for help and too stupid to find it on their own. Both kinds of people try to pass off what they're doing as the real thing and will respond to any attempts at questioning or changing it with hostility. In fact, that hostility is a pretty good indicator of both snake oil and incompetence.
Assorted stuff I do sometimes: Lemuria.org
It's also a long term cost center. But more interestingly, even the most worthless security tools can be proven to "work" if you look at the numbers.'"
What would happen if Microsoft did what Apple did in bringing out OS X. What if they put out a new Windows OS built from scratch based on UNIX? What if security is their first focus and everything else branches from that, rather than security being patched in a non-secure environment? Also, what if they made their OS open source and allowed any IT expert to review and make suggestions to their source code? I live in a fantasy world though, none of the above would ever happen :/
The question here is really to coin the phrase "If you always did what you always did, you always get what you always got" So the major problem I see in my consultancy and security engineering is that middle and upper managers do not fully grasp security as a whole. They keep their eyes on a very smaller prize (CYA). If it is PCI, HIPAA or State Legislation the consensus I get is that "WE MUST BE COMPLIANT" the whole time not seeing the actual goal at hand "Protect and secure the data and network!"
What is more funny is the mindset that if the item is out of side it is out of mind because folks cannot grasp the concept of an outsider becoming an insider. "It wont happen to me, or Not on my watch" the whole time not realizing they are actually practicing the whole Security by Obscurity which they profess is the devil.
Next, they often ask in meetings why are we not going to be compliant? Well in short you knew that using application X was a problem 5 years ago, have there been any tests or efforts to either correct the application or migrate to a new platform ?? NO well if you always do what you always did how can you expect any other outcome then what you always get? It is like dropping a cat they always land on their feet if you do not change something in the way you drop the cat it will always land on its feet....Security is the cat!!!!
See: the original blog entry
Security is a process, not a product.
Every time, I mean *every damn time*, someone tells you only to buy this or that product to get more security, he/she is fooling you. Security is a process that needs knowledgeable people with the right tools and the right amount of time available, not just colorful boxes sold by well dressed salesmen. Unfortunately most execs still can't grasp that simple concept.
Ever since we installed the Springfield Bear Protection System, there haven't been any bears in our neighborhood! It works great!
I was just thinking the other day about how antivirus software has been the number one download at Download.com for years. I would think that if the woftware works, the download counts would go down.
Wanna fight ? Bend over, stick your head up your ass, and fight for air.
not like it used to be, which was extremely difficult. which may be why providing 'security' for snake oil may have been challenging back then? people wanted it?
all the snake oil one might be able to consume would not serve as well as a glass of home made Kombucha, a strange brew that really IS good for you. wards off zombies etc....
The Republicans were quite successful with security theatre in 2002 and 2004. It has cost this nation over $1 trillion so far.
The Evil One.
Yours In Moscow,
K. Trout
I whole agree with the article in it's entirety. As a former CSO and retired military, most organizations don't take us seriously until you point out a few social engineering hack attempts. How I implemented security wasn't snake oil, as it was the design of the entire team IT. Our honey-pots were a great tool for finding out what hackers are after, but the 'paid' crackers are we were most scared of - not companies selling us fake products. It's up to IT staff to effectively evaluate any product or service to our organization, not some sleazy sales moron who's selling us fake stuff.
Lets face it - most companies can become complacent quite easily unless something happens to change their perception of IT security. For me, it was a simple and cheap $5000 test and the data I came up with scared the CEO and VP's out of pants. The article author also didn't mention that IT security is something ALL us IT geeks are continually thinking about... Just a thought.
Management is doing things right; leadership is doing the right things. - Peter F. Drucker