Bit9 hack casts spotlight on security industry practices

February 18, 2013

451 Group (a research analyst firm) recently posted a meaningful blog article on this topic – http://idoneous-security.blogspot.com/ . Worth taking a moment to read as it effectively highlights what the security industry faces every day.

By confessing that its mistakes led to security breaches at three customers, Bit9 has sparked debate over whether the industry is ready to block hackers that see vendors as the door to other companies.

Bit9 disclosed last week that cybercriminals stole digital code-signing certificates from its computers and then used them to drop malware in the systems of three unidentified customers. The vendor acknowledged that the theft occurred on computers that it had failed to protect with its own product, which allows only software on a whitelist to run.

The hack is troublesome because cybercriminals are increasingly attacking vendors in order to steal technology that can be used to penetrate their customers’ systems. Vendors whose computers have been breached over the last few years include RSA, Symantec, DigiNotar, Verisign and Comodo.

Bit9 revealed in a blog post on Saturday that the attackers were using the vendor as a way in to its customers. “We can only speculate, but we believe the attack on us was part of a larger campaign against a particular and narrow set of companies,” wrote Harry Sverdlove, chief technology officer for Bit9.

Customers should not expect vendors to be anymore prepared to fend off attackers than most corporations. “Security vendors are no different than their customers and suffer from the same challenges: dealing with the threat landscape, and not having enough time/staffing/resources to accomplish all objectives,” said Rick Holland, an analyst at Forrester Research.

In fact, most security vendors are much smaller than enterprises and often have fewer resources available for security operations, Holland said. “Startups have even more challenges as investments in R&D, marketing and sales trump technology investments.”

Overall, vendors are more focused on implementing best practices in regards to security than their customers, experts say.

“Ultimately vendors of security need to be even more secure than the people that their technologies are protecting,” said Charles Kolodgy, and analyst at IDC. “Most security vendors understand this and I do believe they are better prepared to protect their intellectual property, but mistakes happen so those need to continue to be reduced.”

A certainty is no organization can be 100% protected against a security breach, and everyone is struggling to secure their systems against attackers who are constantly developing new tactics and technology.

“It’s the art of war,” said Gartner analyst Lawrence Pingree.

To better serve customers, vendors need to have procedures in place to handle quickly the consequences of the inevitable hack, Pingree said.

Scott Crawford, analyst for Enterprise Management Associates, said customers need to question their vendors about their security practices. “The focus in the security industry has been pretty similar to the rest of the technology vendor world, which is primarily on getting products out,” Crawford said.

Vendors should be drilled on how well they understand the impact a breach would have on customers, Crawford said. Other discussions should include their secure development practices.

“Do they treat their products the same way that someone designing products for aerospace, defense and the military would?” he said.

Experts agree that the security industry as a whole could benefit from sharing more information about malware and attacks. Currently, there are competing data-sharing frameworks sponsored by government groups, security vendors and the information technology industry, Holland said. Leading groups include OpenIOC, MITRE, and IODEF.

“If I were optimistic in the federal government’s ability to understand the issues as well as execute, I’d welcome legislation in this area,” Holland said.


What exactly is defensible deletion?

October 25, 2012

Philip Favro of Symantec, in an article called Defensible Deletion: The Cornerstone of Intelligent Information Governance on the eDiscovery 2.0 blog, defines defensible deletion as “a comprehensive approach that companies implement to reduce the storage costs and legal risks associated with the retention of electronically stored information (ESI)”.

He goes on to say that organisations which have done this “have been successful in avoiding court sanctions while at the same time eliminating ESI that has little or no business value

That is the point, of course, of the word “defensible” in this context. It matters most in the US, where everyone goes in fear of the sanctions bogeyman, apparently without regard to the terms of Rule 37(e) of the Federal Rules of Civil Procedure which reads as follows:

(e) Failure to Provide Electronically Stored Information. Absent exceptional circumstances, a court may not impose sanctions under these rules on a party for failing to provide electronically stored information lost as a result of the routine, good-faith operation of an electronic information system.

Most other jurisdictions can manage without this “safe harbor” because they do not have the same (alleged) reason to fear sanctions. I say “alleged” because if US companies paid more attention to Rule 37(e), they too could set about the deletion of material which is not presently the subject of a legal hold and which is not required for statutory or business purposes. It would help, too, if they read some of the sanctions Opinions which cause such dread to see how many of them were the consequence of the “routine, good-faith operation of an electronic information system”.

If you are short of ROI information to justify the work involved in a defensible deletion programme, try and calculate how much money was spent last year processing and reprocessing useless data for eDiscovery purposes, rejecting it time after time, at considerable expense. There’s a big chunk of ROI there.

Thanks to http://chrisdale.wordpress.com/


The Difference Between Backup and Replication

March 2, 2012

What’s right for your business – a data backup solution, replication or both? There are advantages and disadvantages to both.  This post will review the considerations that you need to make before reaching a decision on which approach is best for your business.

It’s important to determine your business objectives for choosing a replication or backup strategy and in order to do so, you’ll need a clear understanding around the differences between disaster recovery and business continuity.

Disaster Recovery (DR) is the process by which you resume business after a disruptive event. This could include a natural disaster, such as an earthquake or a hurricane, or could be something less significant, such as malfunctioning software caused by a computer virus.

Business Continuity (BC) describes the processes and procedures an organization puts in place to ensure that essential business functions can continue during and after a disaster. The goal is to prevent interruption of mission-critical services and to re-establish full functioning as swiftly and as smoothly as possible.

If your organization suffers from a failed RAID array or a geographical disaster, for example a hurricane hits one of your regional offices, and you were using a replication strategy with no “point in time” backup, you would be able to restore from replicated storage to get things up and running quickly – translating into seamless business continuance.

It is atypical for something like the above to happen, but it does occur. Let’s look at a few more likely scenarios as it relates to replication. Whenever humans are involved mistakes are bound to happen. If a user accidentally deletes a file from the primary server, the deletion will be replicated across all subsequent secondary and tertiary storage. Another example is that of a corrupted file at the primary site that is replicated – making it impossible to recover.

With more than 90% of restores stemming from user error (accidental deletion) and corruption rather than data loss, replication and snapshots can’t provide the level of protection that is required as part of a comprehensive BC/DR strategy.

Keeping alternative copies of data in multiple locations is a great idea, reducing the risk of data loss and potentially enabling enhanced access, but fails to address recovery point objectives or RPOs that are addressed with data backup—managing multiple historical copies of a data set.

With a proper backup procedure in place you can refer back to a point in time, for example, when the last scheduled backup was run. If  there are multiples sets of backup stored, you can refer back to a version of the file/database, before the corruption/deletion occurred.

Adding basic data protection techniques like snapshots or replication to a storage system doesn’t make it a backup solution. Replication can leverage storage capabilities, but a backup management solution will always be required for complete data protection.

Having both replication and a backup system in place is the ideal scenario – achieving both  high availability for business continuity and the ability to restore for a point in time backup, but it can be expensive.  If the ideal situation is cost prohibitive for your organization, the best solution is to utilize a service based on a backup platform that can create a virtual replica of your environment versus replication.


Follow

Get every new post delivered to your Inbox.

Join 745 other followers