SaaS is supposed to be ubiquitous, and never go down. But what if the SaaS you are using suddenly goes away, closes up shop, or places the part you are using in an unsupported mode? For some SaaS offerings (such as a game) this may not be a big deal, but for others (such as a CRM) it has huge consequences—ones that can affect your business in subtle and major ways.
Articles Tagged with There and Back Again
Aidan Finn commented recently on a Microsoft infographic about How to Kill Your Business in 5 Simple Steps—and they are very good steps to consider. (Thank you to @gilwood_cs for pointing this out to me.) However, regardless of those issues, there is one, just one, simple way to destroy your business these days. Five is a nice number of items to consider, but one item was missing from the list: one item that has already destroyed one business overnight and put countless others at serious risk. That one item can be addressed with one simple question:
How do you measure your data-protection success? This is a question that has plagued many folks. Data-protection success could be measured by cost savings, peace of mind, recovery success, or the number of support tickets opened to achieve true data protection. Most likely it is a combination of all those items.
Small and medium business and enterprises often make do with what they can do today while dreaming about tomorrow. Most SMBs look to have communication tools in place both for communication with the outside world (email, the Web, Twitter, Facebook, Google+, etc.) and for communication between team members (email, IM, etc.). Most of this can be done online these days by embracing the relevant tools from Google or other sources. Alternatively, SMBs can stand up their own; however, cost is often the bottom line for an SMB.
It was all over the web on June 18: Code Spaces went off the air, as we discussed during the Virtualization Security Podcast on 6/19. The reasons are fairly normal in the world of IT and the cloud. They were hacked. Not by subverting the Amazon cloud, but in ways considered more traditional—even mundane. An account password was discovered, either by hacking using one of the seven SSL attacks that exist today or by guessing with the help of inside knowledge gained through social engineering. However the account was hacked, the damage was total. While we may all ask why Code Spaces was attacked, we may never know the answer. Nevertheless, in general such attacks are all about the Benjamins. What lessons can we learn about this attack? How can we improve our usage of clouds to protect our own data, systems, and more from similar attacks?
Backup, disaster recovery, and business continuity have changed quite a bit over the years, and they will continue to change into the future as more capability, analytics, and functionality are added to the general family of data protection tools. As we launch ourselves into the clouds, we need to perhaps rethink how we do data protection, what tools are available for data protection, and how to use our older tools to accomplish the same goals. We need an integrated data protection plan that not only accounts for cloud or data center failures but also accounts for the need to run within the cloud. There is always the need to get your data there and back again.