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.

Attacks/Breaches

7/20/2007
01:00 AM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Cigna Goes on a Role

Health benefits provider automates upkeep of its role-based user access control

Even the big boys sometimes struggle to get their user access control into compliance. Take Cigna, which is about to automate the management of user-access entitlement for its 27,000 employees and over 1,000 applications.

Cigna started building its role-based access control (RBAC) infrastructure in 2001, which includes IBM's ITIN identity management system and a homegrown tool that handles user requests for application access. Without the tools to automate the upkeep of its RBAC system, most of its access control work was done manually.

Getting all of the roles and access rules set up took the $16.5 billion health benefits provider nearly five years to complete.

"I used to have a lot more hair," says Craig Shumard, chief information security officer at Cigna. "It was a laborious and complex undertaking, and back then, there weren't any tools to assist [you]. Excel spreadsheets were the tool du jour."

But the spreadsheets will soon get tossed: Cigna is now starting to deploy Aveksa 's Linux-based Aveksa 3 appliance to automate the management of its user roles and access to its systems and data. The Apache Web-based tool builds, changes, tests, authorizes, and certifies a particular user's "role," and thus his access to the appropriate Cigna applications for his job. It will help define employees' access needs, and ensure that they receive access only to what they really use, Shumard says.

RBAC is basically a process that groups system resources that users need to do their jobs. The "roles" grant the user access to specific apps when a user is hired or changes jobs.

Shumard says the tool will eliminate spreadsheets as Cigna's sole tracking tool and, ultimately, the company's in-house, mainframe-based System Communication Request (SCR) app, which lets users request access to applications and systems based on their job roles and locations. "They will be able to instead make their requests through the Web-based Aveksa interface," as part of the entire system, he says.

That tool also will immediately revoke any access to users who leave the company -- a high-profile requirement in an audit. The appliance also provides an audit trail of all of the changes and provisioning of user access, Shumard says, and will work hand-in-hand with the ITIN identity management system.

The decision to add the Aveksa tool was both for business and regulatory reasons, Shumard says. "One reason was the fact that it [the RBAC architecture] wasn't sustainable given the volume and activity and number of people in the roles we have now. And two, for folks looking for detailed audit logs and trails for activity in roles, role owners, and access, this provides that information in a timely manner."

"With 27,000 employees, people are moving and changing roles a lot, so it was a significant effort to maintain when you go to the depth we did" with most of our applications, he says. But without a tool to operate the overall RBAC architecture, Cigna was unable to always know for sure who had access to what at any given time, he says. That's where the Aveksa appliance comes in.

"We put a lot of time, money, and resources into [the RBAC]," he says. "This is the next evolution."

Shumard won't say what Cigna has invested in this project. The Aveksa appliance sells for $137,500 for a 1,000-user and 25-application implementation, and comes in volume discounts.

The appliance will also help streamline the auditing process for Cigna, Shumard says. Cigna historically has had to do some hefty manual labor for audits, he notes. "Frankly, we went through a lot of manual effort to ensure we were fully compliant."

Shumard's advice to other organizations building out a role-based access control system: "To effectively maintain an RBAC goes on forever. Plan for the maintenance phase when you start."

— Kelly Jackson Higgins, Senior Editor, Dark Reading

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: George has not accepted that the technology age has come to an end.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23351
PUBLISHED: 2021-03-08
The package github.com/pires/go-proxyproto before 0.5.0 are vulnerable to Denial of Service (DoS) via the parseVersion1() function. The reader in this package is a default bufio.Reader wrapping a net.Conn. It will read from the connection until it finds a newline. Since no limits are implemented in ...
CVE-2009-20001
PUBLISHED: 2021-03-07
An issue was discovered in MantisBT before 2.24.5. It associates a unique cookie string with each user. This string is not reset upon logout (i.e., the user session is still considered valid and active), allowing an attacker who somehow gained access to a user's cookie to login as them.
CVE-2020-28466
PUBLISHED: 2021-03-07
This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers: Running a NATS service which is exposed to untrusted users presents a heightened r...
CVE-2021-27364
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages.
CVE-2021-27365
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. Certain iSCSI data structures do not have appropriate length constraints or checks, and can exceed the PAGE_SIZE value. An unprivileged user can send a Netlink message that is associated with iSCSI, and has a length up to the maximum length...