Welcome Guest. | Log In| Register | Membership Benefits
  • Email this page E-mail this page
  • |  Print Print this page
  • |   Bookmark and Share

StillSecure Bets on Embedded Security

Cobia platform spurs debate over 'open source'

May 23, 2007 | 09:28 AM

By Kelly Jackson Higgins
DarkReading

LAS VEGAS -- Interop -- StillSecure this week took another step in its effort to divorce security software from hardware with new partnership programs for VARs, ISVs, and hardware manufacturers that want to resell, distribute, or port Cobia to hardware. But some experts don't like the security vendor's positioning of the platform as "open source."

Mitchell Ashley, CTO and general manager of StillSecure, says the company is trying to get ahead of the curve in uniting networking and security. "Security is getting embedded in the network -- it will eventually get featured in the network switch and router fabric," Ashley says. "Instead of our playing catch-up," we developed the platform.

StillSecure rolled out the Linux-based Cobia in April for free under a dual-use community and commercial licensed, modular security platform that includes routing, firewall, DNS, IDS/IPS, NAC, spam filtering, WiFi, and VPN. Cobia builds on StillSecure's existing security platform, which also uses Snort and Nessus.

But StillSecure's promoting of Cobia as an "open source" platform has generated some heated controversy. Thomas Ptacek, a researcher with Matasano Security, says Cobia isn't technically "open source" because it doesn't fit the definition of open source.

"It's a proprietary license, plain and simple. You cannot use Cobia's code to build your own products," says Ptacek, who has blogged on this issue before. "It's troubling that they are trying to capitalize on the goodwill that open source justifiably generates, while not providing those same freedoms themselves, and while taking from the open source community by using things like Snort."

Open-source definition debates aside, StillSecure says it envisions its approach as filling a gap, since there are no open standards that address networking and security software. "We are building out a community," Ashley says. And ISVs will add functionality to the Cobia platform: Cymphonix, for instance, is adding content-filtering to it and bandwidth-shaping, he says.

StillSecure also announced it will sell Cobia-based appliances to businesses.

— Kelly Jackson Higgins, Senior Editor, Dark Reading

  • StillSecure
  • Matasano Security LLC


  • Subscribe to RSS










    Bugs
    ENTERPRISE VULNERABILITIES
    Vulnerability:suse linux
    Published:2010-01-22
    Severity:High
    Description:SUSE Linux Enterprise 10 SP3 (SLE10-SP3) configures postfix to listen on all network interfaces, which might allow remote attackers to bypass intended access restrictions.
    Vulnerability:ie
    Published:2010-01-22
    Severity:High
    Description:The URL validation functionality in Microsoft Internet Explorer 7 and 8 does not properly process input parameters, which allows remote attackers to execute arbitrary local programs via a crafted URL, aka "URL Validation Vulnerability."
    Vulnerability:bind
    Published:2010-01-22
    Severity:Medium
    Description:ISC BIND 9.0.x through 9.3.x, 9.4 before 9.4.3-P5, 9.5 before 9.5.2-P2, 9.6 before 9.6.1-P3, and 9.7.0 beta does not properly validate DNSSEC (1) NSEC and (2) NSEC3 records, which allows remote attackers to add the Authenticated Data (AD) flag to a forged NXDOMAIN response for an existing domain.
    Vulnerability:ie
    Published:2010-01-22
    Severity:High
    Description:Microsoft Internet Explorer 6, 6 SP1, 7, and 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to memory corruption, aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2009-2530 and CVE-2009-2531.
    Vulnerability:ie
    Published:2010-01-22
    Severity:High
    Description:Microsoft Internet Explorer 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to memory corruption, aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2009-3671, CVE-2009-3674, and CVE-2010-0246.


    Briefing Centers
    POWERFUL INFORMATION
    AT YOUR FINGERTIPS
    (SPONSORED LINKS)