Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

8/30/2010
09:56 AM
John H. Sawyer
John H. Sawyer
Commentary
50%
50%

Make Security About Security, Not Compliance

The lack of follow-through and belief in any type of lifecycle for security is one that really bothers me when working with clients who are looking only to meet the minimum compliance requirements.

The lack of follow-through and belief in any type of lifecycle for security is one that really bothers me when working with clients who are looking only to meet the minimum compliance requirements.If you're a security consultant, you've probably experienced at some point, or will in the future, a client that wants you to perform a penetration test or wireless survey in order to check off a box to make the auditors happy. While you'll be happy to do it because you're getting paid, the unfortunate thing you'll come to realize is this is the only time they think about security. After the penetration test is performed, they'll work to correct the issues found and then they're done thinking about security until the following year.

What's wrong with this picture? Heartland Payment Systems comes to mind. They suffered a huge breach in 2008 at a time when they were considered PCI-compliant with the PCI DSS. And I'm guessing they checked off all the little boxes on their PCI compliance checklist saying they met the requirements but never bothered to be sure they were actually secure.

While that's probably the last time Heartland will make this mistake, it's the problem that many security professionals cite with compliance--companies assume being compliant means they are secure--and as we've seen numerous times, that's not the case. Security needs to be baked into IT and business operations from the start, and security needs to be something ongoing and not just a concern when it's time to fill out the auditors' checklists.

So what can be done? Well, obviously, having a penetration test done every month is unreasonable and costly, but what about the other tasks that are only required a few times or less each year? The requirement for quarterly wireless scanning is one example. Instead of performing a wireless survey every few months, the PCI DSS states that a wireless intrusion detection system can be put in place as long as it is properly configured to send alerts to staff.

Often small companies shy away from the wireless IDS option because of the cost, but cost doesn't have to be the limiting factor. For example, low-cost DIY options exist such as the free and open source software Kismet. Combined with consumer-grade hardware, Kismet can be configured as a distributed wireless IDS. The drones can monitor for new wireless networks and wireless attacks, then report the information back to a central Kismet console.

Of course, there are plenty of commercial solutions from companies like AirMagnet, AirTight Networks, and Cisco, but they often come with a hefty price tag that small companies can't afford.

My best advice for companies seeking compliance is to not get stuck thinking inside the box. In other words, think creatively to solve the compliance riddle while making sure that it's bringing you closer to being secure -- and not just closer to the final check box on your checklist.

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Zero Trust doesn't have to break your budget!
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-32243
PUBLISHED: 2021-06-16
FOGProject v1.5.9 is affected by a File Upload RCE (Authenticated).
CVE-2021-32244
PUBLISHED: 2021-06-16
Cross Site Scripting (XSS) in Moodle 3.10.3 allows remote attackers to execute arbitrary web script or HTML via the "Description" field.
CVE-2021-32245
PUBLISHED: 2021-06-16
In PageKit v1.0.18, a user can upload SVG files in the file upload portion of the CMS. These SVG files can contain malicious scripts. This file will be uploaded to the system and it will not be stripped or filtered. The user can create a link on the website pointing to "/storage/exp.svg" t...
CVE-2021-34201
PUBLISHED: 2021-06-16
D-Link DIR-2640-US 1.01B04 is vulnerable to Buffer Overflow. There are multiple out-of-bounds vulnerabilities in some processes of D-Link AC2600(DIR-2640). Local ordinary users can overwrite the global variables in the .bss section, causing the process crashes or changes.
CVE-2021-34203
PUBLISHED: 2021-06-16
D-Link DIR-2640-US 1.01B04 is vulnerable to Incorrect Access Control. Router ac2600 (dir-2640-us), when setting PPPoE, will start quagga process in the way of whole network monitoring, and this function uses the original default password and port. An attacker can easily use telnet to log in, modify ...