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

4/18/2013
09:45 AM
Gunnar Peterson
Gunnar Peterson
Commentary
50%
50%

What IAM Can Learn From Bill Gates

In identity and access management, it pays to be long-term aggressive and short-term conservative

There is a saying that you should never write a project plan that is longer than six months. Why? Because by then there will be a reorg, and you won't finish the project. Unfortunately, this is a truism in many companies, and so it has forced people to think about what they can deliver in the short term. (The Agile people hedged their bets even more -- they use two weeks!)

This kind of short-term thinking has its limitations, especially when it comes to identity and access management (IAM). To paraphrase Bill Gates: Most people overestimate what they can do in the short run and underestimate what they can do in the long run.

IAM is a domain where it's critical to have a top-down strategic view and a bottom-up tactical view. The top-down strategy is important because no one IAM product can do it all. The problem set, brought on by managing a decentralized system, mixtures of technologies, acquisitions, and outsourcing, is too vast. This has led to a sea of IAM products -- SSO, role management, role mining, entitlements, provisioning, federation, strong auth, and on and on. All of these products solve a piece of the overall IAM puzzle; however, trying to execute on too many of them in the short term is a recipe to fail.

Instead, it's better to think top-down and execute bottom-up. Think through a top-down strategic road map for your IAM architecture. Drill down on the scope and priorities for the next three years or so. Any longer is a stretch -- I do not think it's possible to predict too much in this business beyond three years.

Meanwhile, be careful not to overpromise what can be done in the short run. Select projects that help you both evolve your IAM implementation near term and fits into your longer-term road map.

It's OK to be aggressive in planning what can be done in longer-term period. Companies have pulled off some impressive IAM achievements through automation, improving security, and integration. But ensure the tactical iterations to deliver this are based on conservative assumptions.

Generally speaking, companies do the tactical pieces by outsourcing to a consulting shop. This is fine as far as it goes, but it's important to not completely outsource the strategic road map planning. Someone needs to hold the longer term view and see it through across multiple iterations -- that's where the larger scale benefits will be realized. 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
Oldest First  |  Newest First  |  Threaded View
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16772
PUBLISHED: 2019-12-07
The serialize-to-js NPM package before version 3.0.1 is vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.to...
CVE-2019-9464
PUBLISHED: 2019-12-06
In various functions of RecentLocationApps.java, DevicePolicyManagerService.java, and RecognitionService.java, there is an incorrect warning indicating an app accessed the user's location. This could dissolve the trust in the platform's permission system, with no additional execution privileges need...
CVE-2019-2220
PUBLISHED: 2019-12-06
In checkOperation of AppOpsService.java, there is a possible bypass of user interaction requirements due to mishandling application suspend. This could lead to local information disclosure no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVers...
CVE-2019-2221
PUBLISHED: 2019-12-06
In hasActivityInVisibleTask of WindowProcessController.java there?s a possible bypass of user interaction requirements due to incorrect handling of top activities in INITIALIZING state. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction ...
CVE-2019-2222
PUBLISHED: 2019-12-06
n ihevcd_parse_slice_data of ihevcd_parse_slice.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android...