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.

Perimeter

9/10/2012
11:44 AM
Gunnar Peterson
Gunnar Peterson
Commentary
50%
50%

What Identity And Access Management Can Learn From 'Car Talk'

Compliance-driven IAM results in the enterprise staring at a Chinese menu of options, and all they can do is point to one that they partially understand

In the old, pre-Web days, the cool kids who'd later grow up to be computer hackers worked on cars. While listening to the funny and informative radio talk show "Car Talk," I have often thought that hosts Tom and Ray Magliozzi would be computer geeks instead of car guys if born a decade later. Certainly, their rules apply to today.

During one of the last "Car Talk" shows, the hosts were reminiscing about how they used to open up their garages on the weekends and people could come in and use their tools to work on their cars. Tom and Ray started off each session with a series of rules, saying essentially, "You may think you came here to fix stuff. That is actually the third reason you are here. The first thing you are here to do is not hurt yourself. (Lots of ways to do this in a garage full of heavy cars and power tools). The second thing you are here to do is not break anything that's not already broken (curse of the tinkerer). And then the third thing you are here to do is to fix your car."

The distilled wisdom here is instructive to companies embarking on identity and access management (IAM) projects.

Companies typically launch an IAM effort due to:

A) architecture or design initiative for improvement

and/or

B) compliance makes them

The number of products, protocols, and standards in IAM is pretty staggering at first. Large vendors offer dozens of different IAM products. And all of that is before you get to integration. The end result is that enterprises are left staring at a Chinese menu of options, and all they can do is point one that they partially understand.

The enterprise points at something that looks appealing on the Chinese menu of IAM options; in doing so it thinks it is fixing an architecture and/or compliance problem. But now let's go back to the Car Talk guys' rules: Fixing an IAM problem is the third thing they should be doing.

The first thing is do not hurt yourself, specifically your career. Note, I am not advocating that CYA is the right approach -- people should absolutely take a little career risk when the situation calls for it. What I am talking about here is to understand that not all IAM products and projects have the same scope. They can be quite grandiose in scope, and expensive in time, effort, and complexity terms. Your auditor's recommendation likely does not factor this in, and blindly following that checklist -- without considering long run cost and available options -- can result in the career limiting move: championing expensive shelfware.

The second thing is do not break anything that is not already broken. This applies to integration. Your auditor will not be able to address this either; your architects should. Engage them. Make sure that an IAM solution makes sense for what it's trying to solve and that it works with current and future software. This means not only understanding the IAM solution, but further planning for IAM first-mile and last-mile integration.

On the organizational side it means having teams to support the product from architecture, design, development, deployment, and operations. Key to this is realizing that IAM skill sets are not part of most staffing plans, so consulting is guaranteed to play a role (read: cost). Of course, you don't want to rely only on external, so you will need a skills development program so that internal resources can take ownership.

Finally, who is "the owner?" By its nature, IAM impacts apps, data, business processes, security, usability, and compliance. You cannot simply create the right pragmatic approach to those concerns straight from an auditor checklist. Someone must build the IAM vision and plan how to execute it.

And then you can start fixing your IAM problem.

Gunnar Peterson is a Managing Principal at Arctec Group Gunnar Peterson (@oneraindrop) works on AppSec - Cloud, Mobile and Identity. He maintains a blog at http://1raindrop.typepad.com. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/1/2020
9 Tips to Prepare for the Future of Cloud & Network Security
Kelly Sheridan, Staff Editor, Dark Reading,  9/28/2020
Attacker Dwell Time: Ransomware's Most Important Metric
Ricardo Villadiego, Founder and CEO of Lumu,  9/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19393
PUBLISHED: 2020-10-01
The Web application on Rittal CMC PU III 7030.000 V3.00 V3.11.00_2 to V3.15.70_4 devices fails to sanitize user input on the system configurations page. This allows an attacker to backdoor the device with HTML and browser-interpreted content (such as JavaScript or other client-side scripts) as the c...
CVE-2020-16844
PUBLISHED: 2020-10-01
In Istio 1.5.0 though 1.5.8 and Istio 1.6.0 through 1.6.7, when users specify an AuthorizationPolicy resource with DENY actions using wildcard suffixes (e.g. *-some-suffix) for source principals or namespace fields, callers will never be denied access, bypassing the intended policy.
CVE-2020-24620
PUBLISHED: 2020-10-01
Unisys Stealth(core) before 4.0.132 stores Passwords in a Recoverable Format.
CVE-2020-25017
PUBLISHED: 2020-10-01
Envoy through 1.15.0 only considers the first value when multiple header values are present for some HTTP headers. Envoy’s setCopy() header map API does not replace all existing occurences of a non-inline header.
CVE-2020-25018
PUBLISHED: 2020-10-01
Envoy master between 2d69e30 and 3b5acb2 may fail to parse request URL that requires host canonicalization.