Commentary

John Foley
Editor, InformationWeek  

Why Cigna Chose Startup For Key Security Function

Getting a foot in the door of big business is the hardest part of being a tech startup. So how did Aveksa, a 3-year-old software company, land a deal with Cigna? It had the right application at the right time to help the health insurer fill a gap in its IT security strategy.

Getting a foot in the door of big business is the hardest part of being a tech startup. So how did Aveksa, a 3-year-old software company, land a deal with Cigna? It had the right application at the right time to help the health insurer fill a gap in its IT security strategy.Aveksa's Enterprise Access Governance Suite helps companies bring discipline to the haphazard process of determining which employees get access to which applications and databases. Aveksa's apps aren't security products, per se. They're business-process tools that work in conjunction with identity management, authentication, and authorization products.

As it happens, that's exactly what Cigna's chief information security officer Craig Shumard needed to put the finishing touches on a role-based access control system that Cigna began developing five years ago. Cigna had the security layer in place, but was lacking a good way to automate and manage "entitlements," or data access privileges based on an employee's position and responsibilities. "There weren't any tools on the market to assist us with that," says Shumard.


More SMB Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Cigna's got 26,000 employees, 22,000 PCs, 9,000 laptops, thousands of applications, and 140 terabytes of data, so tracking who gets access to what was no small problem. Then Aveksa came along. Significantly, Aveksa was no garage shop operation started by two college buddies (though that approach sometimes works, too). Aveksa's founder and CEO, Deepak Taneja, was the former CTO of Netegrity, an ID management software company acquired by CA in 2004. Other members of Aveksa's management team, including VP of engineering Jim Ducharme and VP of sales Patrick Welch, also hailed from Netegrity and CA.

In other words, though Aveksa was a startup, it's top execs had deep expertise in data access management and plenty of experience working with IT departments in midsize and large companies. There were professional connections, too. Cigna's IT security folks had worked with Aveksa people in the past, before Aveksa was ever created. "Relationships count," says Shumard.

Aveksa still had to convince Cigna that its software was up to snuff. Cigna put the startup's technology through extensive testing, while Cigna's sourcing department looked at Aveksa's viability as an early stage company. With $6 million in series A funding from Charles River Ventures and Pequot Ventures, Aveksa got the thumb's up. Aveksa announced the deal with Cigna in June.

Also working in Aveksa's favor was Shumard's willingness to put his trust in a startup, a proposition some IT executives consider too risky. Shumard explains he's merely trying to find the best products to create an air-tight security infrastructure and that sometimes requires working with emerging technologies and companies. "Changes in technology are coming faster than some of the big guys can move," he says.

When the job is to protect data from many and growing threats, security pros aren't inclined to wait for more established software vendors to deliver what they need. "I've got a lot of pressures on me from our business people looking to enable our business securely," Shumard says. Business pressures often translate into technology opportunities. Aveksa seized this one.


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