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
Threaded  |  Newest First  |  Oldest First
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...
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
How to Think Like a Hacker
Dr. Giovanni Vigna, Chief Technology Officer at Lastline,  10/10/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-4031
PUBLISHED: 2019-10-16
IBM Workload Scheduler Distributed 9.2, 9.3, 9.4, and 9.5 contains a vulnerability that could allow a local user to write files as root in the file system, which could allow the attacker to gain root privileges. IBM X-Force ID: 155997.
CVE-2019-17626
PUBLISHED: 2019-10-16
ReportLab through 3.5.26 allows remote code execution because of toColor(eval(arg)) in colors.py, as demonstrated by a crafted XML document with '<span color="' followed by arbitrary Python code.
CVE-2019-17627
PUBLISHED: 2019-10-16
The Yale Bluetooth Key application for mobile devices allows unauthorized unlock actions by sniffing Bluetooth Low Energy (BLE) traffic during one authorized unlock action, and then calculating the authentication key via simple computations on the hex digits of a valid authentication request. This a...
CVE-2019-17625
PUBLISHED: 2019-10-16
There is a stored XSS in Rambox 0.6.9 that can lead to code execution. The XSS is in the name field while adding/editing a service. The problem occurs due to incorrect sanitization of the name field when being processed and stored. This allows a user to craft a payload for Node.js and Electron, such...
CVE-2019-17624
PUBLISHED: 2019-10-16
In X.Org X Server 1.20.4, there is a stack-based buffer overflow in the function XQueryKeymap. For example, by sending ct.c_char 1000 times, an attacker can cause a denial of service (application crash) or possibly have unspecified other impact.