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/21/2012
11:57 AM
Gunnar Peterson
Gunnar Peterson
Commentary
50%
50%

Launching An IAM Project: Where To Start

How to think architecture-centric, not audit-centric, in identity and access

In my last blog post, we looked at some of the hazards in identity and access management (IAM) projects. Specifically, most IAM project initiatives are created from a very dangerous place -- the auditor's spreadsheet.

Audit plays an important role, but blindly following an audit report into large-scale IAM "suite" (in name only) deployment, can result in seven-figure disappointment and hinder career upside.

IAM efforts should be architecture-centric, not audit-centric. Audit is an input to architecture, but IAM architecture focuses on assets, risk, standards, and integration -- how to deliver on the requirements in a real-world system, not simply completing the audit Checkbox Olympics.

The value of an architecture-centric approach to IAM is clear, but the next question becomes: What processes can be used to get there? Outside of specialty consulting groups, there are limited options for industry-standard IAM design, development, and deployment processes.

As IAM matures, this will likely change much the same way secure coding has been progressively baked into the Software Development Lifecycle. Enterprises now have a number of choices, such as BSIMM and Microsoft's SDL, that offer concrete ideas, guidance, and sequencing on improving security in code.

IAM faces similar challenges to those who drove the movement to BSIMM and SDL, but the IAM space lacks a "you go in A, you come out Z" cohesive approach to delivering IAM in real-world systems.

So while there is not a fully baked IAM process out and available, there are some starting points to consider. Taking an architecture-centric approach to IAM means starting with, wait for it, architecture. There are several sources to consider, including The Open Group Enterprise Security Architecture, which covers much of the core territory for IAM architects to design and plan for.

Delivering on architecture is the next pressing challenge, and here the work from BSIMM on software security is instructive. BSIMM's framework has four main categories: Governance, Intelligence, SSDL Touchpoints, and Deployment. Each of these has a direct implications for the IAM project life cycle:

  • Governance: As previously discussed, compliance is one of the main drivers of IAM efforts, but an architecture cannot live by compliance alone. Strategy is required to make sure the IAM efforts align with enterprise goals and priorities, and that long-term impacts of new teams for IAM design and ops are factored in.

  • Intelligence: In BSIMM terms, IAM is a "security feature," but the standards and security behind these features require very careful design and testing. Mistakes made here cascade across the system.

  • SSDL: This part covers architecture analysis, code review, and testing. Most IAM efforts are a mix of buy and build, but this step should not be skipped. It's the key to achieving integration

  • Deployment: Penetration testing, vulnerability management, and related deployment concerns are likewise of paramount importance for IAM efforts. IAM vendors' PowerPoint does not crash, but their implementations do. This process step closes the loop from concept to reality.

In conclusion, BSIMM's focus on software security is not a one-for-one for IAM's top concerns; it's missing some areas, such as operations that are important for IAM efforts. BSIMM requires some adaptation to be useful in IAM, but most of the core bits required to get a successful IAM project up and running are present in BSIMM. Hybrids are the strongest plants in nature. If you're starting an IAM project now and need a framework to adapt for IAM, I would recommend starting with BSIMM.

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
Jay O'Donnell
50%
50%
Jay O'Donnell,
User Rank: Apprentice
11/9/2012 | 8:06:05 PM
re: Launching An IAM Project: Where To Start


Thanks
Gunnar for the great read - It is true that compliance plays a leading role in
IAM efforts. IAM has evolved from an IT mandate to an enterprise imperative. N8
Identity's Employee Lifecycle Manager-(ELMG) ensures compliance by tracking employees
from their first day to their last day, including any changes in responsibility
that happen in between. The compliance module of ELM makes compliance reporting
simple and straightforward. Learn more here: http://n8id.com/our-offering/e...
More SolarWinds Attack Details Emerge
Kelly Jackson Higgins, Executive Editor at Dark Reading,  1/12/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-36192
PUBLISHED: 2021-01-18
An issue was discovered in the Source Integration plugin before 2.4.1 for MantisBT. An attacker can gain access to the Summary field of private Issues (either marked as Private, or part of a private Project), if they are attached to an existing Changeset. The information is visible on the view.php p...
CVE-2020-36193
PUBLISHED: 2021-01-18
Tar.php in Archive_Tar through 1.4.11 allows write operations with Directory Traversal due to inadequate checking of symbolic links, a related issue to CVE-2020-28948.
CVE-2020-7343
PUBLISHED: 2021-01-18
Missing Authorization vulnerability in McAfee Agent (MA) for Windows prior to 5.7.1 allows local users to block McAfee product updates by manipulating a directory used by MA for temporary files. The product would continue to function with out-of-date detection files.
CVE-2020-28476
PUBLISHED: 2021-01-18
All versions of package tornado are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configura...
CVE-2020-28473
PUBLISHED: 2021-01-18
The package bottle from 0 and before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with defa...