Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

1/11/2010
11:29 AM
Chris Murphy
Chris Murphy
Commentary
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Global CIO: 5 Points To Make When Your CEO Cries Cloud

The questions inevitably will come: 'Why aren't we doing more of that cloud computing?' Here are your answers.

Whether it's from the board of directors, the CEO, or a business unit leader, CIOs are getting hit with cloud computing questions. What are we doing with cloud computing? Shouldn't we do more? What's our cloud strategy? Here's one attempt at a script for how to reply.

1. Not everyone's in the cloud.

It might feel like the whole world has leapt to cloud computing, and left us behind.

But consider these numbers. Dr. Dobb's and Forrester recently surveyed 1,021 developers and found about 4% currently deploying apps to the cloud. Just 4%. InformationWeek's Outlook 2010 research found 10% of companies doing some kind of cloud computing (meaning online CPU, storage, etc., but not including software as a service), and another 5% absolutely planning to do it. Both those data points to a clear reality: cloud computing--when defined as buying computing power by-the-drink IT from a third party--is in very early adopter stage.

Not to say we should dismiss it. That would be a serious mistake. Interest is soaring not because we CIOs are gullible chumps falling for the hype, but because the capabilities are improving quickly and the potential gains are enticing. A year ago, just 31% of InformationWeek readers expressed a positive view of cloud computing, in the sense of either using it, planning to, or feeling "more likely" to use it given the poor economy. This year, 46% take one of those positive views of the cloud. Fifteen percentage points is a big move in a year. Cloud computing has momentum and mindshare for solid reasons, even if it's more interest than adoption today.

2. We should be learning, not deploying.

Remember when we rushed that critical e-commerce project to an offshore developer in 2002, because the promised cost savings made our mouths water? And how we got back what we asked for, but it didn't remotely do what we needed, because we didn't have the skills to ask for what we really needed? Offshoring came with a steep learning curve on our end--learning how to manage offshore resources, and understand the risks. We're going to go through the same curve with cloud computing.

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our new online community and information resource for CIOs operating in the global economy.

At the InformationWeek 500 conference this year, I heard this comparison: outsourcing your infrastructure is like renting a house; cloud computing is like renting a hotel room. You rent only what you need while co-existing alongside any number of strangers going about their own business. We need to understand the risks and capabilities that come with what's essentially a new flavor of outsourcing.

3. We are learning.

We're not sitting on our hands, waiting for cloud computing to be perfected by everyone else. We have pilot projects in the works, offloading some discrete but computing-intensive jobs to cloud providers, giving our IT teams some experience and hopefully helping our business unit leaders see what's possible as well, so they can bring ideas to us. We're tire-kicking the vendors, including Amazon Web Services and Microsoft's newly launched Azure, to understand their capabilities. We're talking to other companies about the use cases they find for cloud's variable capacity. Eli Lilly, for example, is using Amazon's EC2 for research.

We're also working on applying cloud architecture concepts, in terms of on demand and shared computing resources, to our own data center. That's delivering near-term cost savings, and we hope lays the groundwork for shifting overflow workloads to public clouds like Amazon, in a hybrid cloud model.

 

Recommended Reading:

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15820
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.
CVE-2020-15821
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, a user without permission is able to create an article draft.
CVE-2020-15823
PUBLISHED: 2020-08-08
JetBrains YouTrack before 2020.2.8873 is vulnerable to SSRF in the Workflow component.
CVE-2020-15824
PUBLISHED: 2020-08-08
In JetBrains Kotlin before 1.4.0, there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.
CVE-2020-15825
PUBLISHED: 2020-08-08
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges.