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

3/31/2010
03:32 PM
John H. Sawyer
John H. Sawyer
Commentary
50%
50%

When To Choose: Preventive VS Reactive Security

Information security is an area of IT that can have an extremely varied budget based on the parent organizations' belief of whether or not they'll be hacked. It's a mentality that seems silly if you've been in the infosec biz for a while because you most likely have realized by now that everyone gets hacked or has a data breach at some point.

Information security is an area of IT that can have an extremely varied budget based on the parent organizations' belief of whether or not they'll be hacked. It's a mentality that seems silly if you've been in the infosec biz for a while because you most likely have realized by now that everyone gets hacked or has a data breach at some point.We're faced with a tough question. How do we get management to buy into that mentality? Better yet, do we want them to? It's not easy telling your boss that a data breach is inevitable. That's not what bosses like to hear, but either way, someone is going to lose a cell phone or USB flash drive, have a laptop stolen, or an attacker is going to break in through a SQL injection vulnerability in your Web app or via information socially engineered over the phone.

You know what your boss is going to say next…"We need to prevent those things!" And, that's where we stuck with trying to prevent every possible breach scenario that we can think of, even those we can't think of via methods that haven't been discovered. One of the things you have to decide is how to balance preventive security with that of reactive security. In other words, do you spend money on laptop encryption and patch management or intrusion detection and centralized log monitoring?

I keep thinking back to Dave Shackleford's blog entry, "5 Reasons Your Security Program is a Failure." There are several great points there, but the one that I keep thinking about is #2, Lack of monitoring capabilities. Where does monitoring fall in terms of preventive and reactive security?

In the incident response process, monitoring fits nicely in the identification stage. Alerts coming from an intrusion detection system can identify a compromised host because an attack was seen followed by a command shell.

But, can't monitoring be preventive, also? For example, monitoring changes on workstations could turn up an employee plugging in an external USB drive and trying to access documents that he or she isn't authorized to access. Security could respond immediately and prevent a potential data breach before the employee has a chance to copy files and leave. Hmm…doesn't that still seem a little reactive?

So, where does monitoring fit? We all know we need to have log analysis and intrusion detection systems in place, but where do we draw the line? Should we ever place the need to have monitoring technologies over patch management and application whitelisting that could prevent infections and compromises that we'd be using the monitoring systems to detect?

My choice would be the preventive technologies first, then the monitoring because I know I can implement cheap, open source monitoring tools in the interim while waiting for additional budget for more costly, enterprise monitoring solutions. The problem is when you don't have the budget for both. What then? I'd love to get some feedback from those of you facing shrinking budgets and what choices and sacrifices you've had to make. Send me an e-mail or leave a comment below.

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.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15820
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.
CVE-2020-15821
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, a user without permission is able to create an article draft.
CVE-2020-15823
PUBLISHED: 2020-08-08
JetBrains YouTrack before 2020.2.8873 is vulnerable to SSRF in the Workflow component.
CVE-2020-15824
PUBLISHED: 2020-08-08
In JetBrains Kotlin before 1.4.0, there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.
CVE-2020-15825
PUBLISHED: 2020-08-08
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges.