Attacks/Breaches
Guest Blog // Selected Security Content Provided By Sophos
What's This?
6/4/2014
04:05 PM
Maxim Weinstein
Maxim Weinstein
Security Insights
Connect Directly
RSS
E-Mail
100%
0%

Back To Basics

By failing to execute on basic security, we're making the attacker's job too easy.

About half of American adults have had data stolen via a breach in the past year, according to a recent study. It would be easy to look at that statistic and the who's who of brands that have been breached -- Target, eBay, Adobe, Nieman Marcus -- and conclude that attackers have gotten so sophisticated that we have no chance to protect our own organizations from a similar fate. The truth, though, is that many of these high-profile attacks have succeeded, not because of their sophistication, but because we continue failing to execute on basic security.

Consider the Adobe breach, which leaked 38 million records and some of the company's source code. It's been alleged, though not officially confirmed, that the point of entry was a public-facing web server that was lacking available patches. The leaked account records were not properly protected with a strong one-way hash algorithm designed for passwords. (Instead, they were encrypted with 3DES, a symmetric encryption algorithm not built for the purpose.) That the attackers could get from a public-facing web server to the company's confidential source code repository implies that the network was not properly segmented, nor access properly controlled and monitored between segments.

Speaking of network segmentation, some of the big retail breaches at Target and elsewhere were aided by point of sale (POS) systems sharing the VLAN with other systems that didn't require the same level of security. If the networks had been segmented, firewall rules could have restricted attempts to exfiltrate stolen data. And, when the average enterprise sees 10,000 security alerts per day, keeping sensitive systems separate make it easier to prioritize alerts like the one Target famously failed to act upon.

Other noteworthy breaches in recent years can be chalked up to dropping the ball on encrypting laptop hard drives or flash drives, restricting and monitoring access to management tools, and protecting encryption keys.

I'm not suggesting that getting security right is easy. I am suggesting that it's time to get back to basics. The latest APT-detecting threat intelligence gizmo with "innovative" technology isn't going to help you if your existing firewall is configured like Swiss cheese and your customer data is being toted around unencrypted on the VP's laptop.

A great place to start is the SANS Critical Security Controls list. The list is prioritized, so you can start at the top and work your way down, making sure you're covering your bases at each step. Call on your vendors to help, as well. They should have best-practices documents available to help you configure their tools for optimum effectiveness. And if you've seen threats slipping by, be sure to report them to the vendors, so they can improve their products and/or guide you in improving your use of the products.

A focus on doing the basics really well doesn't guarantee protection against every threat, but it certainly reduces your exposure to both opportunistic threats and targeted attacks. And if something does slip by, it's a lot easier to explain an attack that took advantage of an obscure vulnerability than one that should have been stopped by standard operating procedures.

Thanks to my colleague Chet Wisnewski, host of the Chet Chat podcast, for the presentation that inspired this post.

Maxim Weinstein, CISSP, is a technologist and educator with a passion for information security. He works in product marketing at Sophos, where he specializes in server protection solutions. He is also a board member and former executive director of StopBadware. Maxim lives ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
chny07
0%
100%
chny07,
User Rank: Apprentice
6/14/2014 | 4:45:59 AM
amazing
Thanks for the great article. i really appreciate it. it will be a great guide for my en ucuz iphone fiyatları thesis
ecowper
100%
0%
ecowper,
User Rank: Apprentice
6/12/2014 | 1:33:55 PM
Basics is the key
The more we analyze the breaches, the more it becomes clear that some really basic things aren't happening well, in general. And I do mean very basic. Network segmentation, user privilege and access management, end point security controls staying set at "factory default", etc. 

Doing security basics better would mitigate much of the impact of the initial entry point into the network. 
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.