CONSIDERING CLOUD SECURITY
There is a great deal of discussion and focus on the security and trust of the environments of cloud providers. This area of interest basically compares the cloud provider environment with the security capabilities of an on-premises solution. It should not be merely a comparison of capabilities as they exist today, but a discussion of future state should be included. The unfortunate reality in computing security is that there are a growing number of threats and threat types and an ever increasing ease with which a bad actor can launch any kind of attack they can figure out or purchase through a growing number of means. So, building on that grim reality, the truth is CIO’s that control the budgets of on-premises solutions will be forced to spend an ever increasing share of their budget for security-related products and services. Even after the increased spend, they may not have a computing environment that is as efficient with dealing with the myriad threats as the cloud providers. The major cloud providers have teams of people and the latest technology to deal with various threat types already in place and they are constantly adding new attack mitigation technologies. For the CIO of a medium to large organization with a limited and/or shrinking IT budget, mitigating attacks in the future will be a monstrous challenge. From this perspective, every organization needs to assess how their current and future security spend stacks up with the security environments of the major cloud providers.
USING CLOUD IAAS PROVISIONING TIME AS AN INDICATOR OF FUTURE PERFORMANCE
As someone who has tested and used multiple public cloud providers and local virtualization platforms, I can unequivocally say that the amount of time it takes to provision a server through the providers UI or scripting environment is a good indicator of the overall performance of that cloud providers infrastructure. Further, that performance level with have a direct financial impact on every role that uses that cloud service from development, infrastructure maintainers, and end users. There are many, many criteria that can affect the purchase and use of a public cloud provider, but the first thing testers must do is compare how long it takes to provision servers in a public cloud candidate. That comparison alone will be very telling and can eliminate the poor performing clouds from consideration. Poor performance is a cost pit that should be, and easily can be, avoided with some very simple and inexpensive testing.
CLOUD PERFORMANCE IS A CRITICAL ASPECT FOR CHOOSING A PUBLIC CLOUD PROVIDER
The internal performance of a public cloud provider has significant ramifications for a variety of aspects of a public cloud solution. One major consequence is the overall cost of a solution that is based on pure usage could end up being significantly higher for a poor performing cloud provider. One company that provides some pretty solid evidence around Public Cloud Provider Performance is Cloud Spectator. There main focus is IaaS, but the results are relevant to others aspects as well. For example, if a vendor builds a SaaS solution on a poorly performant public cloud, they would be paying more for each client than a highly performant cloud that has the same cost and billing structure.
Check em out – http://www.cloudspectator.com/