Layer 8

Security is fundamentally about people, and everything we know about people is relevant to security. -- B. Schneier

Let go, let Cloud.

Pretty soon the New School Guys are going to say everything I wanted to say, only better, and I can hang up my cleats and get out of the game.

Alex Hutton, who appears to be catching up to David Mortman in the number of blogs he appears on, had this post over at the Verizon blog on clouds and the evolving role of the CISO.  The magic phrase is this:

[T]he Cloud transition is about how to gracefully lose control over computing assets.



Ten years ago, IT outsourcing meant that you hired the bodies from somebody else, but they still did what you wanted them to do.  Someone else paid them and managed their benefits, and if they had a management structure, it was embedded within yours.  That didn’t achieve economies of scale as much as everyone hoped, so these days, instead of buying (or renting) the bodies, you’re buying the service—which means they get to do it THEIR way, presumably to save money.  Hence, the hounds^H^H^H^H^H^HCloud.

It should be intuitively obvious, but everyone keeps hitting their faces against the same lamppost over and over again:  “economies of scale” means “cookie-cutter.”  It means one size fits all, and you’re stuck with the resultant blisters or chopped-off toes to make your organization fit within the shoe.  In theory, everyone is in favor of standards, but there are an incredible number of different ways even to implement the same standard, much less choose among several standards to implement.  IT is not “cookie-cutter” by any stretch of the imagination, even at the lower ISO layers.

So with the “cloud,” you’re expected to buy someone else’s implementation of infrastructure/platform/software/whatever, and you’re not SUPPOSED to change it.  If you’re not supposed to change it, why would you need to know exactly how it’s being done?  This is the conundrum for today’s CISO.

As Alex says, you start giving up visibility, which means you need to trust that cloud provider.  Not only do we lose the important data necessary to form risk decisions, but we also lose the ability to implement and respond to risk.  Take a very small example:  say that you have an uptime SLA with your provider that says that if something is down, they have to have it back up and running within four hours.  Sounds good in the contract, but in the actual execution, this means that if your server is shooting out warning errors, you would probably start making plans to replace the failing hardware (or whatever it is) proactively.  Economy-of-scale providers don’t do proactive; it’s not economical.  So THEIR operational rule will be, “We’ll replace it when it fails, and not before.”  And you will spend a lot of time watching tickets go by that state as the resolution, “We rebooted it and the errors went away.”  A slowdown in performance is not the same as an outright failure, so you will have no recourse but to sit and watch your business limp along.  (I’m actually surprised that we don’t see more arson in hosted data centers, where someone in desperation sets fire to a server to get it to FAIL ALREADY.)

So there are two main areas of expanded risk that need to be calculated:  our knowledge into the state of the system, and our ability to control the controls.  I’m only a FAIR padawan, so I haven’t been inducted into the mysteries of calculating this far down, but I’ll bet someone around here can shed light on it.

As we get dragged kicking and screaming by our business areas into the Cloud, it will be very interesting to see whether the CISO’s accountability is correspondingly reduced, and whether more real liability is transferred to the cloud provider.  I’m not talking performance penalties here;  I’m talking REAL liability, in which the provider shoulders the total loss incurred by an incident on their watch.  When are we going to start seeing cloud providers sued by their customers?

I’m getting the popcorn and the lawn chair ready.

 

 

 

Posted by shrdlu on Thursday, May 07, 2009
(5) CommentsPermalink blogmarks Favicon del.icio.us Favicon Digg Favicon Fark Favicon Furl Favicon Google Bookmarks Favicon StumbleUpon Favicon Technorati Favicon TailRank Favicon

Comments

dunsany United States on 05/07  at  12:56 PM:

Like I was tweeting before, I recently engaged in discussions with a cloud vendor.  We chose very carefully since we have strict security requirements - our bread and butter is financial PII.  That immediately narrowed down the list of which cloud we could talk to.  All of them tossed up their fancy certifications - SAS-70, PCI, ISO, Webtrust, even a few certs I’d never even heard of. Comments like “We’re secure and we can prove it.” Lots of interaction with their tech team who talked a real good game about all the cool things they do.  Even I was impressed and felt some warm fuzzies of assurance.

Then ever so nicely, we asked how much liability they’d assume if their actions caused a breach of our data.  Basically we know we’d get our pants sued off by our Very Large Banking Customers, so we needed to put some skin in the game for the cloud vendor.  Should be a no-brainer if half those security certs mean anything.

At that point they shut up and ran away.

LonerVamp United States on 05/07  at  09:22 PM:

I agree with a road you sort of headed down. I don’t like all this marketing crap about the magical cloud (my phone provider is in the cloud because I beam my cell signals to OUTER SPACE!), but I do agree that it will take hold over time. If nothing else, I think we’ll see IT get really sick and overburdened with the cost of all the damn homegrown apps we all have churning away and keeping the business kicking and getting older and not maintained. It will actually make sense to use cookie-cutter tools as businesses realize they’re just not adding the IT piece to their competitive advantage list any faster than anyone else in their market.

Of course, not only does this mean IT needs to let go, but business as a whole needs to let go as their power to customize stuff dramatically drops.

It’s a silly dance between what business thinks it needs and what IT can deliver efficiently. It works great when a product plugs into a need! It’s just fast food mediocre if it’s not adding anything new or the business has to adjust to use it properly.

Certainly, over time we’ll go to the cloud, get our cookie-cutter apps for about 5-10 years, then start getting fancy ideas that we can pull some of this back in-house again and customize it how it will really maximize our business, and enter the centralized/decentralized cycle all over again…


Side note: Business in general sucks ass with security. I don’t care what audits say, I think extremely few businesses are honestly doing things well (and being honest about it!). Cloud providers are still businesses. I’ll say again, business in general sucks ass with security. Hopefully at least cloud providers have less on their plates such that they can devote proper resources to it.

Etherealmind Great Britain (UK) on 05/08  at  04:46 AM:

You sound like such an optimist in this post.

Liability, as if any computer company has ever heard of that.

LonerVamp United States on 05/08  at  10:37 AM:

Oh, and I will add that I expect “cloud providers” themselves to make this market ugly, like a choppy storm rolling in with 30 boats still trying to fish.

Some will die, others will move to something else, others will be bought and consolidated. And where will that leave those people depending on the solutions and APIs? Screwed.

At best, I think we will see a couple niche providers but otherwise 2-3 dominant fish, kinda like Microsoft, Apple, *nix, in computers. The world can’t otherwise handle tons of cloud providers. (Depending on your definition of cloud).

.(JavaScript must be enabled to view this email address) Sweden on 05/08  at  02:28 PM:

What I believe has been missing in our industry (okay, one of the many things) is an effective way of measuring an organization’s ABILITY TO MANAGE RISK.  Like so much of how we’ve approached our problems, to-date we simply break out a checklist (pick your standard) and start evaluating whether the subject org has certain policies defined and communicated, whether they’re security org is engaged in the technology lifecycle process, whether and how often they test/review their security practices, etc., and whether they’ve undergone someone else’s similar checklist approach to looking at the same stuff.  But that’s like picking a doctor by looking to see if they finished medical school (and asking for evidence that other people also have looked at their diploma.  Unfortunately, a diploma (or security certification) doesn’t tell us a thing about their judgment and their actual effectiveness over time. 

Yes, it’s reasonable to assume that an organization that has “adopted” an ISO (or other relatively well-considered) standard is somewhat less likely to make as many mistakes as those that haven’t, but if I’m to entrust someone else with stuff that ultimately I’m still responsible for, I want to be able to measure their risk management capability in a meaningful way.  In fact, I’m perhaps more interested in understanding their risk management capability than their current risk, because risk management is a leading indicator of what their future risk exposure (and mine if I engage them) is likely to be. 

So, how do you measure an organization’s risk management capability?  Well, I’m not going to open the kimono all the way, but a great place to start is by measuring their current risk.  Huh?  Yeah, I know, I said above that I was more interested in understanding what their risk management capability is than their current risk, but if you think about it, their current risk is a lagging indicator of their previous ability to manage risk.  In other words, the decisions they made in the past, and their ability to execute against those decisions led them to where they are today from a risk perspective. 

So, bottom line—when I’m in the position of having to trust another organization with my valuables, I’m going to be looking hard at risk information.  More importantly, I’m going to be interpreting it through the lens of how it portrays their ability to manage risk.

Cheers,
Jack

Page 1 of 1 pages

Add a comment

Name:

Email:

Location:

URL:

Smileys

Remember my personal information

Notify me of follow-up comments?

Submit the word you see below: