Welcome Guest. | Log In | Register | Membership Benefits

Most IT Security Pros Disabling Security Functions In Favor Of Network Speed

New survey shows dilemma faced by organizations over performance trade-offs with network security products

Jul 21, 2011 | 10:03 AM | 

By Kelly Jackson Higgins
Dark Reading
More than 80 percent of organizations disable functions in their network security products because they slow the network, according to a newly released survey.

Crossbeam Systems surveyed 500 network security, IT, and C-level executives at companies worldwide and found that 90 percent say there's a trade-off between security and throughput. Around 67 percent say security is a higher priority than throughput performance when evaluating a security product.

It's the age-old problem of balancing security and productivity. "We found in the survey that they are having to make significant trade-offs between security and performance ... They are having to switch off functionality they paid for to meet their performance goals," says Peter Doggart, director of product marketing at Crossbeam.

Organizations are keeping their firewall, IDS, network access control, and IPSec functions turned on, but they are shutting off application control, user identification control, and some anti-malware features. In next-generation firewall products, for instance, 91 percent are using stateful firewall features; 73 percent, NAT; 71 percent, IPsec; and 65 percent, IDS/IPS.

Only 29 percent had deployed the anti-malware functions in these next-generation firewalls; 29 percent, user ID control; 33 percent, application control; 34 percent, antivirus; and 45 percent, Web filtering.

"Every platform has this problem. You turn on more security processing and performance goes down," Doggart says. "We need to makes sure customers are turning on this functionality to protect themselves."

But the reality of their service-level agreement requirements and misleading performance claims by network security vendors is making this impossible, according to Doggart.

More than 93 percent of the survey respondents don't trust the performance metrics that security hardware vendors provide on their data sheets, and 58 percent say they don't trust the performance metrics themselves. More than 60 percent say they had to purchase additional hardware to make up for unmet claims by security hardware vendors.

But it's not just the security vendors: The customers have to better vet the tools, according to the study. Almost half of those surveyed did not conduct any "real-world testing" of the products before rolling them out. "I think you're asking for trouble if you're not doing that. And [in the survey], of those that did do real-world testing, half never turned on IPS," Doggart notes. "Both sides are culpable."

A copy of the survey report is available for download here.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Vulnerability Management Reports

report Choosing the Right Vulnerability Scanner for Your Organization
Vulnerability scanners can be used to help detect and fix systemic problems in an organization's security program and monitor the effectiveness of security controls. However, a vulnerability scanner can improve the organization?s security posture only when it is used as part of a vulnerability management program, in which products, processes and people are working together to find, identify, prioritize and mitigate threats. Here are some tips on choosing and implementing vulnerability scanners in your enterprise.

report Using Google to Find Vulnerabilities In Your IT Environment
Attackers are increasingly using a simple method for finding flaws in websites and applications: they Google them. Using Google code search, hackers can identify crucial vulnerabilities in application code strings, providing the entry point they need to break through application security. Sound scary? It is, but there is good news: You can use these same methods to find flaws before the bad guys do. In this special report, we outline methods for using search engines such as Google and Bing to identify vulnerabilities in your applications, systems and services--and to fix them before they can be exploited.

report Security Pro's Guide to Patch Management
It's no longer sufficient to patch just Windows, Office and IE. With the massive array of applications now residing on enterprise PCs, and the proliferation of mobile and cloud-based applications, your business is far too vulnerable to exploitation unless you have a solid strategy for patch prioritization, deployment and quality assurance. Follow these steps to put your plan in place.

Other reports from the Vulnerability Management Tech Center:




Featured Webcasts
Featured Whitepapers
Featured Reports