Privacy: The Cloud Model’s Waterloo?

Part 2 – How Privacy Could Cripple the Cloud

Security and privacy are often mentioned together. This is natural, because they are related, yet distinct topics.  Security is a technical concept concerned with the controlled access, protection, integrity, and availability of data and computer system functions.  Privacy is a common policy objective that can be achieved in part by applying security principles and technical solutions.  In previous posts, I’ve discussed how cloud security is not really a problem, any more so than it is in IT in general, when it is approached properly in the cloud environment.  Privacy, as discussed in Part 1 of this series, is unfortunately not so “simple.”

I’ve already made the case that some commonly held beliefs about what is inherently secure or insecure are based on control of the physical infrastructure and ownership of the premises where the infrastructure is located.  I’ve further posited that these ideas are outdated, and at the very least insufficient to insure secure cloud systems (as well as traditional data centers, for that matter).

In the discussion of privacy, we’ve seen governments urged to action by their citizenry to combat the erosion of individual control of personal information.  Unfortunately, lawmakers have approached such legislation from the outmoded perspective of physical security.  Privacy laws are rife with injunctions that PII must only be stored or transmitted under circumstances that derive from a physical location.  The European Union, for example, forbids the PII of any EU citizen from being stored or transmitted outside of the EU. Although treaties such as the EU-US Safe Harbor Framework, established in 2000, facilitates some degree of data sharing across the EU-US boundary, it is showing signs of failure when applied to cloud-based application scenarios. Although laudable in their intent, privacy laws that dependent upon containing data within a particular jurisdiction can prove to have more negative effects on both privacy outcomes and achieving the full benefit of cloud-based global services to the individual being “protected.”

First, given the highly-publicized data breaches of large corporations and government entities, it is obvious that data behind a brick wall is still quite vulnerable.  Laws that mandate limits on where data can be stored may convey a false sense of security to those who think that meeting the law’s requirements results in sufficient protection.  Socially engineered attacks can penetrate all but the most highly guarded installations, and once the data has been extracted, it is impossible to “undisclose” it. Again, it is the perimeter-based model that is not up to the task of protecting data in a hyper-connected world. Second, limitations on how data can be shared and transmitted can negatively impact the owner of PII when they cannot be serviced by cloud vendors outside of their jurisdiction.  Frameworks such as Safe Harbor are band-aids, not solutions.

One solution is to endow sensitive data with innate protection, such that wherever the data goes, its protection must also go. A container model for self-protecting data allows for the owner to specify his or her intentions regarding the data’s distribution and use, regardless of its location, and is the zero trust model for data.  Rather than depend on a perimeter and control of physical infrastructure to insure privacy objectives are met, the policy is built into the data container, and only when the policy is followed will the data be made available.

Of course, such a solution is easier described in a paragraph than implemented, although many valiant efforts have been attempted to varying degrees of success.  Still, a viable implementation – one that is scalable, robust, and easily made ubiquitous – has yet to be created.  Unfortunately, the wheels of governments and legal systems will not be inclined to wait for it.  Without educating policy makers to better understand the real threats to privacy rather than the perceived ones, we invite a continued spate of ill-conceived requirements that could make the problem worse while ironically robbing “protected” citizens of the full value of cloud technology.


Posted in Cloud Computing Technology Insights | Comments Off

Privacy: The Cloud Model’s Waterloo?

Part 1 – Privacy Ain’t the Same As Security

Most people consider the word privacy solely in the context of cloud deployment models, where a private cloud is one reserved strictly for the use of a specific group of people that have a common affiliation, such as being employed by the same company. But it is becoming quickly evident that the more broad context of global legal systems and basic human rights are where cloud computing may meet its privacy Waterloo.

The concept of personal privacy is present in all cultures to varying degrees.  Western cultures have developed the expectation of universal individual privacy as a right.  As such, privacy is a legal construct, not a technical one.  It is founded upon the idea that information not publicly observable about a person belongs to that person, and is subject to their will regarding disclosure and subsequent use.

By default, most legal systems require the individual to opt out of their rights to privacy, rather than opt in.  This means that, unless there is specific permission from the owner of the data to allow its use in specific ways, the use is unlawful and a violation of that person’s privacy rights. Examples include the United States healthcare privacy laws, and the European Union’s privacy directive.

There are instances to the contrary, where opt-in is the default.  One is the privacy-related right to not be approached without consent.  An example is the US Federal Trade Commission’s National Do Not Call Registry, which one must actively join in order to supposedly avoid unwanted marketing telephone calls. This solution also demonstrates the difficulty in balancing privacy of the individual with the free-speech rights of others.

The details of privacy law vary across jurisdictions, and historically have been somewhat anemic.  Before the printed word, propagation of personal information could only occur by word-of-mouth, which was highly suspect as mere gossip.  The printed word resulted in more accurate and authoritative data communication, but the cost rarely allowed for transmitting personal details outside the realm of celebrity (in which case it was considered part and parcel of one’s celebrated position). These limitations rarely tested the laws, and when they did, it was infrequently enough to manage on a case-by-case basis. But, as with so many other legal constructs, computer systems and networking have strained the law to breaking points.

The modern, democratized Internet has enabled the near instantaneous propagation of data at little expense, by almost anyone, to broad audiences.  In supposed acts of public service, “whistle blowers” purposefully disclose private information to call attention to illicit activities or behaviors of the data owners: Whether their ends justify their means is hotly debated, though it is a clear violation of privacy. Vast databases of personal information collected by governments and corporations are at much greater risk to be copied by unauthorized agents, which most people agree is data theft.  In these cases, it is fairly easy to spot the transgressor and the violation.

But the free flow of information in the cloud computing era brings ambiguity to what once seemed straightforward.  Individuals who volunteer personal information often do not realize just how far their voluntary disclosure may propagate, or how it might be used, especially when combined with other information gleaned from other sources.  The hyper-connected Internet allows data from multiple sources to be correlated, creating a more complete picture of an individual than he or she may know, or would otherwise condone.  The data may come from a seemingly innocuous disclosure such as a marketing questionnaire, or from public records which, until today, were simply too difficult to find, much less match up with other personally identifiable information (PII).  Attempts to ensure data anonymity by “scrubbing” it for obvious PII such as name, address, phone number, and so on, is increasingly ineffective as something as simple as a time stamp can tie two datum together and lead to an eventual PII link in other data sets.

This particular problem is one of the negative aspects of big data analytics, by which vast sources of data, both structured like database tables and unstructured like tweets or blog posts, can be pulled together to find deeper meaning through inferential analysis.  Certainly, big data analytics can discover important trends and help identify solutions to problems by giving us insight in a way we could never have achieved before. The scope, diversity, size, and access of data combined with cheap, distributed, open source software has brought this capability to the masses.  The fact that we can also infer personal information that the owner believes to be private, and has not given us consent to use, must also be dealt with.

As cloud computing continues on the ascendant, and high-profile data breaches fill the news headlines, governments have been forced to revisit their privacy laws and increase protection, specifically for individuals.  In jurisdictions such as the United States, privacy rules are legislated and enforced by sector.  For example, the Health Insurance Portability and Accountability Act (HIPPA) established strict privacy rules for the healthcare sector, building upon previous acts such as the Privacy Act of 1974.  Although the Payment Card Industry (PCI) standard is not a law, it is motivated by laws in many states designed to protect financial privacy and guard against fraud. In the European Union, the Data Protection Directive of 1995 created strict protections of personal data processing, storage and transmission that applies in all cases.  This directive is expected to be superseded by a much stronger law in coming years.

In an environment where there are legal sanctions and remedies for those who have suffered violations of their privacy, one is wise to exercise caution in collecting, handling, storing, and using PII, regardless of the source.  Cloud technologies make it all too easy to unintentionally break privacy laws, and ignorance is not an acceptable plea in the emerging legal environment.  Clearly, for cloud to be successful, and for us to be successful in applying it to our business problems, we need systematic controls to prevent such abuses.

But is a failure to guarantee privacy in the cloud enough to kill the cloud model, or hobble it to insignificance?  More on this line of thinking in Part 2.

Posted in Cloud Computing Technology Insights | Comments Off

Becoming an IoT Automation Geek

I’ve long wanted more automation and remote control over my house, but until recently such wasn’t possible without a lot of special project boards, wiring,  gaps in functionality and – most importantly – time. Now, with the Internet of Things (latest buzzword for automating and monitoring using Internet technologies for transport) this is becoming so much easier, and something for which I can make time.  Also, it is somewhat synergistic with my cloud architecture role at Dell: Although IoT is assigned to others and not to me, it still warrants some first-hand experience to be a fully competent chief cloud architect.  (At least, that’s my rationale!)

Two weeks ago, the two thermostats in our house were replaced with Honeywell WiFi models. It makes it SO easy to program a schedule when you can do it in a web interface! We never have to touch the controls now – they change for different times of the day automatically, and we can control them from our phones remotely if necessary.

I’ve just completed upgrading the pool control system to include WiFi connectivity and Internet remote monitoring and management. I upgraded the pool control to a Jandy AquaLink RS Dual Equipment model, so that now pool, spa, spa heater, spa lights, blower, and pool solar heater are all unified into a single controller, controllable via the network.

Now, the only missing item is the pool light, which is wired through a toggle switch on the other side of the house, near the master bedroom. Rather than run a wire from the controller to that switch, I’ve decided to branch out further into home automation with a SmartThings hub. I’ll replace the pool light with a smart toggle switch, and I’ll put a relay sensor in the Jandy controller so that when we “turn on” the pool light via the pool remotes (phones, etc.) it will close the relay, send an event to the SmartThings hub, and it will then turn on the actual switch.

Since I’m putting in the SmartThings hub, I can now add more Z-Wave IoT devices to the house and solve some other quirky problems, like turning the porch lights on and off at dusk/dawn and power cycling my server or desktop if necessary when traveling. I’m sure I’ll think of others. With SmartThings, you program your own apps and device drivers in Groovy, so I can make it do just about anything I want.  Well, at least that’s the theory.  I’m supposed to receive the hub and devices tomorrow, so it shall be tested shortly.


Posted in Cloud Computing Technology Insights | Comments Off

The Myth of Cloud Insecurity (cont.)

Part 3 – Leaping the Chasm

In my previous posts (Part 1, Part 2) in this series, we established the theory that the human species has come to rely on physical ownership and control of something as necessary and sometimes even sufficient to securing that thing.  This theory doesn’t hold in the cloud-era IT world where virtual objects such as applications and data, backed by physical machines, are more vulnerable in that virtual world than they are in the physical one in which they are rooted.  This line of reasoning is challenging for those who insist that “private” clouds will always trump public cloud services when it comes to providing the ultimate security.

The key to security in the cloud is to make the application responsible for its security, not the supporting infrastructure.  This implies that not all applications as they may currently exist in a private data center are suitable for “true” cloud deployment.  In fact, it is likely that very few are ready to make the jump into the cloud, because there is a gap in application fitness that must first be addressed.  Perhaps the staunch supporters of private cloud as the bastion of security take their positions not understanding or simply being dismissive of the fact that application transformation is a requirement to achieving the most secure public cloud deployments.

When the distributed perimeter pattern is followed by cloud application developers, the CSP is left to focus on creating the most secure service possible, meaning that it is generically configurable for each application, and that those configurations are difficult if not impossible for interlopers to modify to their own advantage.  Because CSPs operate on such large scale, they are arguably more likely to do a better job of securing these basic services than all but a handful of enterprise data centers could.  Of course, this model can only succeed when the application properly configures and uses the service.  To do otherwise could invite a security breach.

But even in the case where an individual cloud application is misconfigured and vulnerable, it is important to note that the cloud service itself and other applications are not likely affected by the vulnerability.  If a poorly designed app is compromised, the attacker can only gain control over what that app controls.  Even if the app has “superuser” privileges for the tenant (a very bad thing to do!), it cannot impact other tenants except possibly by side effect, such as launching a denial-of-service attack by saturating the network or CPU.  Even then, good CSPs will enforce limits that prevent the DoS attack from having significant negative impacts on other tenants. In effect, the CSP approaches each tenant as a potential security risk that could behave poorly, even if not officially “compromised.”

This is not to say that private cloud has no place in cloud-era IT. In the security context alone, there are many applications that will never be refactored for cloud, and for good reasons. It’s expensive to refactor.  The application may not have a very long lifespan, anyway.  It may be that the nature of the application is such that a full public-cloud makeover won’t add much value to it where users or the organization are concerned.  In these cases, it is best to either leave the application as is, or recast it partially to a cloud model to take advantage of efficiencies in the private cloud, while still depending on the existing security controls.

For new application development, however, there should be no question of adopting the full-on cloud model because it maximizes deployment flexibility.  Even if you don’t think you’ll ever deploy the app to public cloud, write it as if you will!   When we design and write applications to take responsibility for their own security, we are subscribing to the zero trust security principle at a fine level of granularity (the application, or its container).   By not trusting anything beyond the boundaries of the application’s container, and designing the application accordingly, we endow it with the strongest possible security profile, and thus the potential for greater mobility between cloud service providers and locations, regardless of deployment model.

Posted in Cloud Computing Technology Insights | Comments Off

The Myth of Cloud Insecurity (cont.)

Part 2 – Distributing the Security Perimeter

In part 1 of this series,  we examined the fallacy that physical ownership and control of hardware, combined with multi-layered perimeter defense strategies, leads to the most secure IT deployments.  In the hyper-connected cloud era, this concept doesn’t hold. In private data centers that rely on this model (see figure A below), a breach in one co-resident system typically exposes others to attack. Indeed, some of the most successful viral and worm attacks follow the model of gaining entry first, then using information gleaned from the most vulnerable systems to break into others in the same data center without having to navigate the “strong” outer perimeter again.  One analysis of this type of leap-frog attack leads us to the conclusion that it is actually not a good example of defense-in-depth. Defense in depth would dictate that, having gained new information from attacking one system, the attacker has at least as difficult of a time using the new-found knowledge to get to its next victim as it did this one.

Applications that are written to run “in the cloud” make very few assumptions about the security of the cloud service as a whole.  Concepts such as a firewall move from the data center’s network boundary to the application’s network boundary, where rules can be configured to suit exactly the requirements of the application, rather than the aggregate requirements of all apps within the data center.  This distributed custom-perimeter model is shown in figure B, below.  By forcing applications to take on more responsibility for their own security, we make them more portable.  They can run in a private cloud, public cloud, on or off premises.  The degree to which ownership and proximity of the service affect the security of the application is much smaller when the application is designed with this self-enforced security model in mind.


Although applications should not rely on data center security for their own specific needs, security at the data center level is still critical to overall success of the cloud model.  Since the application relies heavily on the network connection to implement persistence and access, the application developer/operator has the responsibility of configuring the cloud services for that application to achieve those specific goals. The cloud service provider (CSP) is responsible to deliver a reliable, secure infrastructure service that, once configured for the application, maintains that configuration in a secure and available fashion, as shown in the figure below. Each tenant’s apartment is constructed by the CSP in accordance with the tenant’s requirements, such as size and ingress/egress protections. The CSP further guarantees the isolation of the tenants as part of its security obligations.


As an example, let us return to our firewall scenario, but with a bit more detail.  Suppose an application requires only connections for HTTP and HTTPS for all communication and persistence operations.  Upon deployment, the cloud service is configured to assign an Internet Protocol address and associated Domain Name System name to the application, and to implement rules to admit only HTTP and HTTPS traffic from specific sources to the application’s container.  Subsequent to deployment, the cloud service must insure that the IP address and DNS names are not changed, that the firewall rules are not altered, that the rules are enforced, and that isolation of the application from other applications in other tenancies is strictly enforced.  In this way, the cloud service provider’s role is cleanly separated from that of the application developer/operator because the CSP does not know or care what the firewall rules are. It only knows that it must enforce the ones configured.  This is in stark contrast to traditional data centers where firewall rules are a merge, often with conflicts, of the various rules each application and subsystem behind the firewall might require.

In my third and final post in this series, I’ll further expound the virtues and caveats of this model and how, when properly implemented, it solves the security problem for applications in the most general case: public cloud.

Posted in Cloud Computing Technology Insights | Comments Off

The Myth of Cloud Insecurity

Part 1 – The False Sense of Physical Security

As is often the case when new paradigms are advanced, cloud computing as a viable method for sourcing information technology resources has met with many criticisms, ranging from doubts about the basic suitability for enterprise applications, to warnings that “pay-as-you-go” models harbor unacceptable hidden costs when used at scale.  But perhaps the most widespread and difficult to repudiate is the notion that the cloud model is inherently less secure than traditional data center models.

It is easy to understand why some take the position that cloud is unsuitable, or at the least very difficult to harness for conducting secure business operations.  Traditional security depends heavily on the fortress concept, one that is ingrained in us as a species: We have a long history of securing physical spaces with brick walls, barbed wire fences, moats, and castles.  Security practice has long advocated placing IT resources inside highly controlled spaces, with perimeter defenses as the first and sometimes only obstacle to would-be attacks.  Best practice teaches the “onion model,” a direct application of the defense in depth concept, where there are castles within brick walls within barbed-wire fences, creating multiple layers of protection for the crown jewels at the center, as shown in Figure A below.  This model is appealing because it is natural to assume that if we place our servers and disk drives inside a fenced-in facility on gated property with access controlled doors and locked equipment racks (i.e., a modern data center), then they are most secure.  The fact that we have physical control over the infrastructures translates automatically to a sense that the applications and data that they contain are protected.  Similarly, when those same applications and data are placed on infrastructure we can’t see, touch, or control at the lowest level, we question just how secure they really can be. This requires more faith in the cloud service provider than most are able to muster.



But the advent of the commercial Internet resulted in exponential growth of the adoption of networking services, and, today, Internet connectivity is an absolute “must have” for nearly all computing applications, not the novelty it was 20 years ago.  The degree of required connectivity is such that most organizations can no longer keep up with requested changes in firewalls and access policies. The result is a less agile, less competitive business encumbered by unwieldy nested perimeter-based security systems, as shown in Figure A above. Even when implemented correctly, those traditional security measures often fail because the perimeter defenses cannot possibly anticipate all the ways that applications on either side of the Internet demarcation may interact.

The implication is that applications must now be written without assumptions about or dependencies upon the security profile of a broader execution environment.  One can’t simply assume the hosting environment is secure, although that is still quite important, but for different reasons.  More on this line of thinking, and the explanation of Figure B and why it is more desirable in the cloud era, in my next post.




Posted in Cloud Computing Technology Insights | Comments Off

The Private Cloud Pendulum

We once had a unified vision of how cloud would be adopted by the average enterprise.   With all the uncertainty around security, cost and performance of public cloud, they would naturally transform their private data centers into private clouds. Once successful in that incremental transition, they would be more comfortable with extending to the public cloud, resulting in the Holy Grail – a hybrid deployment.

We were only half right.

As events have unfolded, we see that hybrid clouds are indeed the desired outcome. However, the way-points on that journey are, for a number of cloud adoption profiles, reversed from what we had predicted. Instead of first stopping at private cloud, many skipped it entirely and went to using public cloud in spite of their own previously voiced objections. Why?

For all but the larger enterprises and the very capable mid-market IT organizations, a private cloud has often been too difficult to build and maintain. The technology existed, but it was far from turnkey. In the face of the challenging business and operational transformations that cloud demands, this was too distracting and unnecessary: public cloud was sitting there, gleamingly simple and ready-to-use without the burdens of operational hassles.

So, for these “I need it to be as easy as possible” cloud adopters, the pendulum largely bypassed private and swung to public. But will it stay there?

The costs of public cloud are tricky to pin down and manage. You are paying a premium for someone else to handle the headaches. For many projects this makes sense. For long-running activities that don’t take advantage of public cloud’s scale and global reach, you will likely pay more than is necessary.

The chickens, as they say, will come home to roost. The true cost of public cloud will become apparent, and the advantages of private cloud more compelling for the mid-market. The pendulum will return, and when it does, we’ll have evolved private cloud technologies to make them suitable for organizations looking for an appliance-like experience instead of building an IT practice around them.

But what if we’re wrong again? Regardless of how that pendulum swings, having choices and management capabilities that span multiple clouds (public, private, whatever) ensures you’ll be able to keep cost and utility in balance. The trick is to invest in tools and technologies that enable that choice;  buy and design software that is infrastructure-agnostic, dependent only upon abstracted network services of which analogs are available from many providers. That way, whether it’s now or in the future, when you’re ready for private cloud (or it is ready for you), you’ll be in a position to further expand your selection of cloud targets by adding your own.

Posted in Cloud Computing Technology Insights | Comments Off

The Elusive Butterfly of Policy

I love it when visionaries bridge the gaps in their utopian depictions of The Future of IT with hand-waving explanations.  As a supposed said visionary, I plead guilty.  My most recent transgression: presenting the concept of “policy” in the context of data centers, workloads, etc., as if it were well understood and its supporting technologies mature enough for market adoption.

In spinning our tales of how great life will be when we finally complete this transformation rather appropriately (due to the ambiguities involved) labeled “cloud,” we realize we can’t tell a convincing story without the Policy character.  He’s like the Sherriff in the Wild West – without him enforcing The Law, it’s just too dangerous a place for normal, everyday people.

Why do I believe policy is a gating factor for accelerating cloud adoption?

Although it is the favorite analogy of cloud evangelists, electric service is not the same as compute-as-a-service.  Unlike the power company, which sends indistinguishable electrons into your home or business and eventually into the ground, cloud computing services require that data and intents to act upon it move across that boundary.  And data is quite distinguishable, valuable, even dangerous in the wrong hands.

And that’s why policy is not simply “important” – it is essential to the success of cloud computing. Data and data access must be managed in a controlled manner, and cloud consumers will need guarantees to that effect.  Policy is the mechanism by which the degree and type of control is specified.  Policy enforcement ensures those controls are observed.

Easy. (Did you feel the rush of air on your cheek?)  Seriously, although much progress has been made to begin to express and implement policies in IT systems, it is a largely manual error-prone process.  Still, some technologies are beginning to emerge that give us a bit of hope we can really solve the problem.

But that’s only the first chapter of a longer story in which the right kinds of policies must be crafted in order to meet the intended objectives.  That’s the poster child use case for policy – compliance.  In future posts I’ll discuss how policy and automation are mutually dependent, and how together they will help us achieve policy enforcement and compliance objectives in tomorrow’s virtual data centers.

Posted in Cloud Computing Technology Insights | 2 Comments

The Rebirth of Automation

I suppose by now it is fait accompli that cloud computing is going to revolutionize the information technology industry.  It certainly seems on track to do so.  One of the main reasons for its success is the highly dynamic and virtualized environments that most cloud platforms provide.  In these modern “data centers” every resource – from virtualized processors and storage to network configuration – can be defined, deployed, configured, managed and maintained through software interaction alone.  No more cables to plug and unplug. No more racks to re-wire just because a server is being re-purposed. RAM can be added to an under-provisioned system in seconds, and never a chassis opened. And the list goes on…

It is in this only recently realized totally virtual data center that one of IT’s oldest workhorses may finally see its full potential realized: automation. It’s the key to achieving maximum efficiency because it provides the following benefits:

  • Task Compression – This time-honored method of increasing efficiency through abstraction is at the heart of automation’s promise. Processes which would normally require many manual steps are reduced to a single invocation.
  • Speed – Not only are machines good at repeating long lists of steps, they can do it quickly! Automated processes can be made to execute as fast as possible, with no unnecessary delays between steps.
  • Repeatable Successful Outcomes – Even with the best documentation, manual execution is prone to human error, such as missing, misreading, or misinterpreting a step. Automation helps to ensure that the same set of steps is always followed, in the same order, with the same results, every time an operation is performed.

So, if automation is so great, why is it only now getting broad traction?

“Run Book Automation” (RBA) has been around for decades, but has never been an easy-to-use or widely accessible technology.  Sure, it’s been possible to fully (well, nearly fully) automate many of the most mundane, frequently used, or most error-prone manual processes through brute force of a million different API’s and a few special-purpose proxies and operating system agents.  But those implementations – with many moving parts under the control of as many different companies that have little incentive to ensure their pieces work “better together” – have proved extremely brittle.  The expense of the software and human resources to design, construct and maintain such systems has only made them useful to the largest of organizations.

A modern incarnation of RBA – “Orchestration” – is well positioned to take full advantage of the new totally virtualized cloud platforms, with visual tools that make the creation and maintenance of automated processes more intuitive, and translation of those high-level intentions to various APIs and endpoints effortless.  Not only that: Codified processes, or “orchestrations,” can be packaged up and shared in community, or sold as products themselves.  Thus, modern orchestration solutions unleash automation from the shackles of traditional RBA and make it available to the masses.  Since cloud computing is in effect “enterprise-grade data centers for the masses,” it is no surprise that orchestration will find its way in to that very same market alongside it.

Although orchestration is finally hitting its stride, uncontrolled automation is a recipe for disaster.  That’s where “policy” comes in….a topic for another day…

Posted in Cloud Computing Technology Insights | Tagged , | 2 Comments

Are End Users Too Stupid To Self-Serve Workloads?

In one of my former lives I founded a tech support team on a college campus.  Staffed with computer science students, the team was responsible for rolling out and supporting Internet and desktop computing technologies across a population of several thousand people.  As CS students, I suppose they were a bit of an elitist group.  They invariably faced users who were largely unfamiliar with these new tools, and were simply ignorant of how they worked, which generated support tickets.  When this happened, the team used a special support code to tag the incident:

Code PEBKAC = “Problem Exists Between Keyboard and Chair”

Not as often used, was:

Code ID-10-T = “Idiot”

Of course, over time they learned the technology and these smug little codes fell into disuse.

Today, I’m seeing a similar attitude with some of the IT support cultures in companies that are considering rolling out cloud technologies in their organizations. Specifically, the concept of self-service is drawing a considerable amount of snickering and eye-rolling from many an IT professional.  The idea that we would actually give a USER the ability to requisition SERVERS through a portal is laughable, and is immediately dismissed.  Why?

The reason invariably given: Users are too stupid to know when they need a server, and why, and they’d just end up creating a big mess that IT would have to clean up later.

But how much of that attitude is grounded in reality, and how much is based in the elitism which many IT organizations see being eroded by the user emancipation cloud and attending concepts like self-service bring?  I suspect the latter to be the case.

Keep in mind that “end user” is a broad term.  It could be the marketing professional needing a web site for a promotion, or a software dev who would normally have to wait months for a work order to complete before an environment is available to work in.  The point is: they are customers of the IT organization.

It can’t be denied that IT’s role in deploying workloads for the business is diminishing  Most users view the IT organization as a barrier to getting work done, not a helper.  When it can be sidestepped, it will be. Unlike those users many years ago who had never accessed the Internet before, and had never had a desktop PC all to themselves, today’s end users are computer-savvy, and self-service is something they understand from many contexts in their experience, from online shopping to subscribing to Internet services like Skype.  Doing it for workloads they need to achieve their business objectives is natural and inevitable.

So if you find yourself scoffing at the very idea that an end user should be allowed to (gasp!) self-serve and deploy their own web servers, etc., as needed, take a moment to search your soul: Is it because you REALLY don’t think they’re capable of making a good decision, or because you’re afraid they just won’t need you anymore?


Posted in Cloud Computing Technology Insights | Tagged , | 1 Comment