<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Alwyn Van Niekerk &#187; Uncategorized</title>
	<atom:link href="http://www.alwynvanniekerk.com/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.alwynvanniekerk.com</link>
	<description></description>
	<lastBuildDate>Tue, 26 Jan 2010 19:44:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Identity Management Pitfalls</title>
		<link>http://www.alwynvanniekerk.com/2008/identity-management-pitfalls/</link>
		<comments>http://www.alwynvanniekerk.com/2008/identity-management-pitfalls/#comments</comments>
		<pubDate>Wed, 21 May 2008 08:00:02 +0000</pubDate>
		<dc:creator>Alwyn</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.alwynvanniekerk.com/?p=42</guid>
		<description><![CDATA[In article one and two I made the case for Identity management (IdM) and how an IdM solution can address the every day problems experienced in organizations. In this article I&#8217;m bringing things back to reality and I&#8217;ll be highlighting the aspects that could cause your IdM project to overrun and under-deliver.
Firstly, technology is only [...]]]></description>
			<content:encoded><![CDATA[<p>In article <a href="http://www.alwynvanniekerk.com/p=38">one</a> and <a href="http://www.alwynvanniekerk.com/p=40">two</a> I made the case for Identity management (IdM) and how an IdM solution can address the every day problems experienced in organizations. In this article I&#8217;m bringing things back to reality and I&#8217;ll be highlighting the aspects that could cause your IdM project to overrun and under-deliver.</p>
<p>Firstly, technology is only 20% of the solution. IdM is an extremely process driven solution and as with any new system where you automate manual processes you have to realize that those processes will change and that they have to be redefined with all the parties involved. Depending on the maturity of your business processes this can be a lengthy part of the overall project.</p>
<p>Be aware of your internal skill set when attempting an IdM project. IdM is still the new technology on the block, and although there&#8217;s nothing resembling rocket science about it, you still need to understand the concepts of implementing an IdM solution and learn the technology you will choose to do so. Consider using external consultants who specialize in IdM with a proven track record to speed things up to realizing your ROI in a shorter time period.</p>
<p>Your chosen IdM solution might also force you to run specific software and hardware infrastructure in which you have no experience or available skills. This will obviously put extra strain on existing resources or you&#8217;ll have to appoint new staff to deal with it.</p>
<p>Be frugal when establishing your identity attributes. Don&#8217;t manage attributes that you might need one day, or because it&#8217;s easy for the IdM solution to do so. Depending on the maturity of your application architecture you should try and avoid managing business attributes (account balances, policy status) in your solution, unless it has a direct impact on the security aspect of the identity. There are exceptions of course.</p>
<p>If you have a successful IdM implementation the chances are extremely good that you will make certain people and positions redundant, as these positions were created to deal with the lack of a proper IdM solution. Identify these people and positions early in the project and provide them with the opportunity to improve their skills and either make them a part of the IdM project, or migrate them to another area of the organization. </p>
<p>IdM projects take time. 2 – 3 year implementations are not unheard of and the key to a successful implementation is proper planning. External consultants with experience can help to speed things and up mitigate many of the risks you will encounter sooner or later.</p>
<p>Identify the low hanging fruit. IdM solutions tend to be costly and lengthy because of sheer scale and legacy complications, but by delivering quick and continuous returns to prove it as an asset will ensure that your project will survive the budget-axe wielded on all financial black hole projects.</p>
<p>I hope these 3 articles have provided some insight into what IdM is, what it can do for you, and which things you need to keep an eye out for. Implementing an IdM project is extremely rewarding, but can become very sticky as well, so don&#8217;t go into it with your eyes closed.</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.alwynvanniekerk.com/2008/identity-management-pitfalls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
