Provider inside

 Both infrastructure as a service (IaaS) and platform as a service (PaaS) services are ideal for third party developers to create service offerings or software as a service (SaaS) solutions ready for customers. For instance NetFlix, LinkedIn, and Salesforce are the services powered by PaaS, and IaaS core services but are delivered as a customer ready SaaS service.  As such a Netflix user does not contemplate how Amazon AWS makes their IaaS service work to ensure that they can watch a movie. Bottom line users watch their movies. This model is really the future of cloud services.

However unlike the telecommunications companies that deliver our phone services end to end, cloud solutions like Netflix have a dependency model users should be aware of. Ultimately users should have the right to know who is touching, and managing their data. And providers should be required to expose the information.

Let's consider this.

The videos serviced by Netflix powered by Amazon AWS requires that Amazon hosting, storage, name resolution, and many others be available, and Netflix provisioning, account management, payment, billing, and many more services be online. The connectivity between the front end services and virtual machines in AWS must run flawlessly, and overall provide a seamless service so that customers can sit back and watch a movie, without complaining about the wait time of their log in, or video playback.  The result of an outage in AWS had broad impact on their customers including Netflix ability to provide their services. Clearly both Amazon and Netflix have worked hard to make their solution redundant and failure resistant, but ultimately Amazon faced the wrath of their direct customers (kindle users) as well as corporate customers like Netflix. Try as they might Netflix was ultimately taken offline by an Amazon service failure.  http://techblog.netflix.com/2011/04/lessons-netflix-learned-from-aws-outage.html.

What is fascinating is that at the end of the day, Netflix can blame Amazon and claim that they have done everything they can to ensure quality of service. And Amazon can dance around the fact that they tried everything to prevent their outage. The truth is Netflix is right. Amazon failed. But what's misleading is that Netflix should also be held at fault. For instance why did they not use multiple cloud providers to reduce the chance of failure, and truly claim elastic computing?

And as a user I should have been able to know how and what Amazon was doing to resolve my issue with Netflix, right?


Comments

Post a Comment

Popular posts from this blog

Protecting sensitive data

Image
Last month I wrote an article on key things to consider when protecting high valued assets or sensitive data. The article called Security Tip of the Month: Protecting Highly Sensitive Information addressed some of the key items that organizations should consider when protecting data that has the possible impact on an organization that is irreparable. As my article stated the cost of protecting this data tends to be higher than most data. Fact is that this data is not traditionally just sensitive such as credit card data, or HR data. Key indicators of what is High Value Data can be summed up like this. Assets that are considered to be of high value will frequently have the potential to cause the following conditions if they are lost or divulged: •        Loss of life - such as an informant list •        Regulatory fines - such as financial performance data •        Significant damage to the business - such as code signing and encryption keys (private) or trade secrets
Read more

Secure workstation - Root of trust to manage the cloud

Image
Two months ago I introduced the Azure secure workstation, and I’ve had the privilege to present the ideal to some great audiences. From the discussions, a common question I’ve been asked is a pattern that would provide the Secured PAW model lock down scenario to exclusively manage an Azure Portal (EG how to I assure only secured workstation, and users assigned to the program can manage my cloud services)? In this article I’ll provide the NEXT step to accomplish exactly that outcome. This includes additional configurations that I only lightly covered, or net new technology to apply since the publishing of the doc. Proposed outcome “ How do I” Use a Secured workstation (that I can trust) to manage my Azure cloud. Here’s how I would deploy the solution. First I will start by deploying the Secured Workstation model this using the secured profile. New technology, and capabilities to add: Hardware root of trust – in our solution we post the idea that you can
Read more

Why is privileged access important?

Image
Last year about this time I had published updates to the Azure Secure Workstation that was originally released two years ago. And This month the solution has been considerably rewritten and revised to provide a better more complete management for privileged access!  Collaborating with two great security experts James Noyce, and Mark Simos The content got a massive overhaul, and a broad perspective on what it takes to build and manage a comprehensive privileged access solution, including account management, device management, intermediaries such as VPN's and interfaces such as Web and Cloud services. Additionally, the solution was uniformly designed with three distinct security levels that anyone reading the article can deploy from a more flexible Enterprise security, to a comprehensive isolated PAW or privileged Access Management. Over the past two years I've been working to explain and illustrate how you can use a cloud-based solution to build an effective Zero tr
Read more