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-04-24 Cisco IOS before 15.3(2)S allows remote attackers to bypass interface ACL restrictions in opportunistic circumstances by sending IPv6 packets in an unspecified scenario in which expected packet drops do not occur for "a small percentage" of the packets, aka Bug ID CSCty73682.
Published: 2014-04-24 Cisco ASR 1000 devices with software before 3.8S, when BDI routing is enabled, allow remote attackers to cause a denial of service (device reload) via crafted (1) broadcast or (2) multicast ICMP packets with fragmentation, aka Bug ID CSCub55948.
Published: 2014-04-24 Cross-site scripting (XSS) vulnerability in IBM SmartCloud Analytics Log Analysis 1.1 and 1.2 before 22.214.171.124-CSI-SCALA-IF0003 allows remote attackers to inject arbitrary web script or HTML via an invalid query parameter in a response from an OAuth authorization endpoint.
Published: 2014-04-24 The openshift-origin-broker in Red Hat OpenShift Enterprise 2.0.5, 1.2.7, and earlier does not properly handle authentication requests from the remote-user auth plugin, which allows remote attackers to bypass authentication and impersonate arbitrary users via the X-Remote-User header in a request to...
Published: 2014-04-24 The password recovery service in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 makes an improper decision about the sensitivity of a string representing a previously used but currently invalid password, which allows remote attackers to obtain potent...