Co3 pulls together best practices for data loss reporting, minimizing errors in what's usually a manual process.
A startup that will officially come out of stealth mode on Wednesday has built a software-as-a-service offering for organizations to handle the mostly manual processes involved in responding to a data-loss breach.
Co3 Systems, based in Cambridge, Mass., is headed up by an executive team that hails from key security firms such as Symantec, McAfee, Counterpane, Arbor Networks, Application Security, @stake, and Verdasys. The firm's new SaaS offering encompasses event preparedness, data event analysis, liability assessment, and incident response workflow.
Most of these steps today are handled manually, and mishandling or mistakes can be costly, said Ted Julian, chief marketing officer at Co3 Systems. "[Victim organizations] are doing it themselves, with manual processes and spreadsheets," he said. Or they hire third-party forensics and incident response expert firms such as Mandiant, he said.
"The security industry is focused on pre-incident. There's very little on post-incident," Julian said.
Jon Oltsik, principal analyst with Enterprise Strategy Group, said Co3 has pulled together the tools for best practices for conducting due diligence in the aftermath of a data breach. "A lot of people make the mistake that it's all about incident response," Oltsik said of the post-breach phase. Co3's SaaS is more about the business process involved: how do you work with the legal and PR teams when your firm discovers it was breached, he said, or how do you get in touch with regulators. "All of those things have to be coordinated, and need to be managed," Oltsik said.
The SaaS offering incorporates regulatory reporting requirements, for example, and workflow management for all of the groups within an organization that have some role in the aftermath of a breach, including IT, security, privacy/compliance group, the legal department, and the finance and audit group.
Security professionals often view compliance as a burden, but it doesn't have to be that way. In this report, we show the security team how to partner with the compliance pros. Download the report here. (Free registration required.)
Published: 2014-08-19 The SNMP module in Cisco NX-OS 7.0(3)N1(1) and earlier on Nexus 5000 and 6000 devices provides different error messages for invalid requests depending on whether the VLAN ID exists, which allows remote attackers to enumerate VLANs via a series of requests, aka Bug ID CSCup85616.
Published: 2014-08-19 The EJB invocation handler implementation in Red Hat JBossWS, as used in JBoss Enterprise Application Platform (EAP) 6.2.0 and 6.3.0, does not properly enforce the method level restrictions for outbound messages, which allows remote authenticated users to access otherwise restricted JAX-WS handlers ...
Published: 2014-08-19 The isCallerInRole function in SimpleSecurityManager in JBoss Application Server (AS) 7, as used in Red Hat JBoss Enterprise Application Platform (JBEAP) 6.3.0, does not properly check caller roles, which allows remote authenticated users to bypass access restrictions via unspecified vectors.
Published: 2014-08-19 RESTEasy 2.3.1 before 2.3.8.SP2 and 3.x before 3.0.9, as used in Red Hat JBoss Enterprise Application Platform (EAP) 6.3.0, does not disable external entities when the resteasy.document.expand.entity.references parameter is set to false, which allows remote attackers to read arbitrary files and have...
Published: 2014-08-19 The (1) serf_ssl_cert_issuer, (2) serf_ssl_cert_subject, and (3) serf_ssl_cert_certificate functions in Serf 0.2.0 through 1.3.x before 1.3.7 does not properly handle a NUL byte in a domain name in the subject's Common Name (CN) field of an X.509 certificate, which allows man-in-the-middle attackers...