Welcome Guest. | Log In | Register | Membership Benefits

Consolidate This

The M&A bug bites proactive security, but convergence will have to wait

Jul 12, 2007 | 03:30 AM | 

By DarkReading

Everyone's talking about consolidation in the security market, and with good reason – lots of M&A activity has occurred. So what’s going on behind the scenes financially, and where will this trend leave us? Will security practitioners be left holding the bag? Most importantly, what impact will consolidation have on the nascent proactive security market?

Convergence versus consolidation
Two distinct threads run through the security market: consolidation and convergence. The first involves the unremitting development of energetic, innovative startups. These little guys are often the targets of consolidation, especially in the form of rollups. One quintessential example of a security rollup is Cybertrust, which bought a number of little companies (and some medium-sized ones like TruSecure) and assembled them into something bigger than the parts alone. In the end, Cybertrust built a company with annual revenues just north of $200 million.

Another rollup-like example is EMC Corp. (NYSE: EMC), with its acquisitions in the data security market, buying up little companies like Authentica and Documentum in order to bolster its data protection capabilities. Of course, EMC has bigger fish to fry, what with its recent $2.1 billion purchase of RSA Security Inc. (Nasdaq: EMC) It seems EMC has become a convergence point.

You see, eventually companies the size of Cybertrust and RSA themselves become targets for mega-corporations. Case in point: Verizon Business ’s $400 million purchase of Cybertrust, which closes this week. (See Verizon Grabs Cybertrust.) Cybertrust was acquired with a multiple on revenue of around 2 – the kind of valuation typical for a services company, even one where the services are heavily commoditized.

The Cybertrust/Verizon deal is more of a convergence than a consolidation. Similarly, the BT Counterpane deal is what I would call a convergence deal. (See BT Buys Counterpane.)

So what exactly is converging in these situations? The convergence involves network security as a commodity service being packaged together with other network-related utilities. If you are a large company, you need certain utilities such as Internet bandwidth and telephone services – and you need security as well. Convergence with the telecom sector makes great sense in the network security market of firewalls, intrusion monitoring, and extrusion detection. Incidentally, that’s why managed security services make a great deal of sense when it comes to network operations and monitoring. These are reactive security solutions.

Probably the two top convergence plays going strong now are IBM Corp. (NYSE: IBM), which bought Internet Security Systems Inc. last August for $1.3 billion, and Symantec Corp. (Nasdaq: SYMC), which bulked up and shifted toward the enterprise with its record-breaking $13.5 billion merger with Veritas. (See IBM Up-Ends Security Services Market.) Convergence is good for the overall security market, because it helps to spread the security “meme” far and wide. If decent network security becomes as ubiquitous as the telephone, that will be a great development for reactive security.

Proactive security is different
The real problem is that the computer security disaster we have created for ourselves looms as large as ever, even as the security market grows to gargantuan proportions and security companies rake in billions of dollars. At the heart of the problem is an emerging conundrum: The kinds of services ripe for convergence are not the kinds of services that can solve the security problem. Reactive network security can only go so far. If we want to get a handle on the unmitigated growth of the computer security problem, we have to build better software.

Software security has certainly come a long way since I wrote Building Secure Software with John Viega way back in 2000. The security market is maturing, demand is very high, and people are beginning to realize how much work remains to be done. A broad realization of the importance of software security is dawning, especially in the financial services market.

The first generation of tools created for the software security market (proactive security) is the Web application security testing tools. I call these tools badness-ometers – affectionately, of course. Black-box testing tools are great because they can help the clueless or the overly optimistic to understand that there is indeed a huge software problem... with their own software! Black-box testing tools are also dangerous, however, because passing all of the tests built into one of these tools does not mean your Web app is secure.

The upshot is that as long as badness-ometers are treated as badness-ometers and not security-meters, we’re OK.

Interestingly, the top two software badness-ometer companies were recently acquired: SPI Dynamics was bought by Hewlett-Packard Co. (NYSE: HPQ) for around $100 million (a multiple on revenue of 5.5), and Watchfire Corp. was bought by IBM for around $85 million (a multiple on revenue of 2.8). (See Want Turns to Need.)

The question is just what impact the consolidation bug will have on the proactive security market. Both HP and IBM are probably counting on Web app security testing tools to be mature enough for use by QA people (that is, non-security people who focus on software testing for a living). If that were true, then every QA department out there would need a few copies. We’ve debated the question of whether these tools are ready to be wielded by QA long and hard at Cigital, and the jury is still out.

There are pros and cons. If QA people could effectively use badness-ometers, awareness of the magnitude of the software security problem would grow, which would be excellent. However, if QA people find themselves over their heads in security nonsense, not much will come of the first wave of consolidation, at least for HP and IBM. What would be really interesting is if the large security services organizations at HP and IBM started applying badness-ometers in all of their projects. Demand for solutions to solve the problems that these tools find would skyrocket.

In the end, it's nice to see software security – the proactive security market – continuing to grow. Expect more consolidation as this trend continues. Convergence will have to wait.

— Gary McGraw is CTO of Cigital Inc. Special to Dark Reading



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












Featured Webcasts
Featured Whitepapers
Featured Reports
Bugs
ENTERPRISE VULNERABILITIES
Vulnerability:ssl-vpn end-point interrogator/installer activex control
Published:2010-11-03
Severity:High
Description:Stack-based buffer overflow in SonicWALL SSL-VPN End-Point Interrogator/Installer ActiveX control (Aventail.EPInstaller) before 10.5.2 and 10.0.5 hotfix 3 allows remote attackers to execute arbitrary code via long (1) CabURL and (2) Location arguments to the Install3rdPartyComponent method.
Vulnerability:gvim
Published:2010-11-03
Severity:High
Description:Untrusted search path vulnerability in VIM Development Group GVim before 7.3.034, and possibly other versions before 7.3.46, allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse User32.dll or other DLL that is located in the same folder as a .TXT file. NOTE: some of these details are obtained from third party information.
Vulnerability:cforms
Published:2010-11-03
Severity:Medium
Description:Multiple cross-site scripting (XSS) vulnerabilities in wp-content/plugins/cforms/lib_ajax.php in cforms WordPress plugin 11.5 allow remote attackers to inject arbitrary web script or HTML via the (1) rs and (2) rsargs[] parameters.
Vulnerability:links, wsn links, wsn links
Published:2010-11-03
Severity:High
Description:Multiple SQL injection vulnerabilities in search.php in WSN Links 5.0.x before 5.0.81, 5.1.x before 5.1.51, and 6.0.x before 6.0.1 allow remote attackers to execute arbitrary SQL commands via the (1) namecondition or (2) namesearch parameter.
Vulnerability:deluxebb
Published:2010-11-03
Severity:Medium
Description:SQL injection vulnerability in misc.php in DeluxeBB 1.3, and possibly earlier, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the xthedateformat parameter in a register action, a different vector than CVE-2005-2989, CVE-2006-2503, and CVE-2009-1033.