Commentary

Andrew Conry Murray
 

Cisco Tiptoes Into The Cloud

New hosted e-mail security offerings underscore the struggle of hardware vendors to stay relevant in the age of cloud services.

New hosted e-mail security offerings underscore the struggle of hardware vendors to stay relevant in the age of cloud services.Today Cisco announced a trio of e-mail security services based on the company's IronPort anti-spam and AV appliances.

First is a managed on-premises offering, in which Cisco remotely monitors and manages IronPort appliances that reside on the customer premises. This service is available today.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Second is fully hosted mail security, in which Cisco hosts and operates the appliances on behalf of the customer in one of Cisco's data centers. Unlike other cloud-based offerings built on a multitenant architecture, each customer gets dedicated hardware. This service will be available in April.

Third is a hybrid premises/hosted offering, in which Cisco filters in-bound mail, and customers maintain IronPort devices on their own networks for outbound messages. In this hybrid approach, customers don't have to plug in more appliances to handle the processing load as spam volumes increase.

Meanwhile, customers still have the premises appliance with which to apply outbound controls, such as DLP and encryption. These services could be handled just as securely by a provider, but the premises device acts like a security blanket for customers who aren't ready to let go entirely of mail management.

Proofpoint announced a similar hybrid e-mail security service last month.

Hidden beneath the PR fanfare around this announcement is that Cisco suffers from a real dilemma. How can a hardware vendor capitalize on the cloud without killing its own business?

The e-mail security appliance market is robust enough that Cisco won't cannibalize it with a pure-play cloud offering. But the growth momentum is tipping toward the cloud and SaaS. So Cisco is trying to split the difference with something that looks like a cloud offering, but isn't built like one. And in the end, it probably won't be as profitable as one.

Cisco uses "cloud" and "SaaS" to describe these offerings, but that's not accurate. They are more like an application service provider (ASP) model, which is a problem for Cisco.

Cloud/SaaS offerings tend to be built on a multitenant architecture, in which customers share infrastructure resources. In theory, a multitenant architecture is more efficient and scalable than an ASP because providers can spin up new customers without having to add new capacity to the system.

By contrast, Cisco will dedicate IronPort appliances to each customer. Where a cloud provider would run three customers on one box, Cisco has to deploy three boxes for three customers -- even if those boxes are only 30% utilized. That's wasteful and inefficient on many fronts, including capacity, power and cooling, and management.

This model leaves Cisco with two options: eat the cost of that inefficiency, or pass it along to customers.

I suspect that for now, Cisco plans to eat it. I asked the company if it thinks it can affordably run an operation built on dedicated hardware. It assured me it has plenty of margin in the business to scale up.

Luckily for Cisco, many companies aren't ready to leave the ground for a full cloud security deployment. The company can probably bank on this reluctance for a few more years while it searches for a more sustainable solution.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links