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-07-29 WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.
Published: 2014-07-29 Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.
Published: 2014-07-29 Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...
Published: 2014-07-29 Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.
Published: 2014-07-29 install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.