<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: My Certifications, My Choice!</title>
	<atom:link href="http://www.andrewhay.ca/archives/82/feed" rel="self" type="application/rss+xml" />
	<link>http://www.andrewhay.ca/archives/82</link>
	<description>the website of a devastatingly handsome author, sporadic blogger, bbq junkie, and security strong man</description>
	<lastBuildDate>Mon, 09 Aug 2010 03:23:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Scott Wright</title>
		<link>http://www.andrewhay.ca/archives/82/comment-page-1#comment-1455</link>
		<dc:creator>Scott Wright</dc:creator>
		<pubDate>Tue, 13 Mar 2007 14:40:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrewhay.ca/archives/82#comment-1455</guid>
		<description>To CISSP or not to CISSP? I believe that if the designation is valued by your client, and will allow you to get more consulting engagements it is worth getting.  If you are full-time employed and are looking to build your skillset across all security domains, it is worth getting.

However, I don’t believe that getting and maintaining a CISSP is necessarily going to keep you “up to date” on the state of the industry.  I believe subscribing to blogs, listening to podcasts, writing your own articles and engaging in debates on forums like the Security Catalyst will do a better job of keeping you current, and making your skills visible.

Several years ago I wanted to move into IT Security consulting from Product Management at Entrust.  When I met with some of the heads of local consulting companies, they said it would be a good idea for me to write the CISSP, if only to demonstrate that my work experience had given me the relevant knowledge.  They recognized that it didn&#039;t give a guaranteed skillset, just an indicator.

I did get my CISSP and it worked; and within a year I was working as an independent consultant.  However, after 3 years I found that my job experience covered enough of the industry, and I was keeping up to date.  So, I let my CISSP certification lapse.  None of my clients to date has questioned the currency of my skills, and I may have missed 5 points out of 100 on a compliance matrix for a government standing offer by not having it.  I dont feel I need to use it as an indicator of my knowledge any more.

I don’t bad-mouth the certification.  It is a pretty tough mental exercise to prepare for and write.  But once you have the experience and inherent credibility from your work, you may not need it. But people who wield their CISSP initials like a sword get the brunt of the scorn from others; mostly because it has become a bit of a stereotype in the industry.  It is certainly an achievement, but when people see it in an email signature block there is a thought that flashes through their mind, “How much real experience does this person have, if they have to display their badge in every email?&quot;

I think its important to take some pride in accomplishments, but more important to keep them in the right context.</description>
		<content:encoded><![CDATA[<p>To CISSP or not to CISSP? I believe that if the designation is valued by your client, and will allow you to get more consulting engagements it is worth getting.  If you are full-time employed and are looking to build your skillset across all security domains, it is worth getting.</p>
<p>However, I don’t believe that getting and maintaining a CISSP is necessarily going to keep you “up to date” on the state of the industry.  I believe subscribing to blogs, listening to podcasts, writing your own articles and engaging in debates on forums like the Security Catalyst will do a better job of keeping you current, and making your skills visible.</p>
<p>Several years ago I wanted to move into IT Security consulting from Product Management at Entrust.  When I met with some of the heads of local consulting companies, they said it would be a good idea for me to write the CISSP, if only to demonstrate that my work experience had given me the relevant knowledge.  They recognized that it didn&#8217;t give a guaranteed skillset, just an indicator.</p>
<p>I did get my CISSP and it worked; and within a year I was working as an independent consultant.  However, after 3 years I found that my job experience covered enough of the industry, and I was keeping up to date.  So, I let my CISSP certification lapse.  None of my clients to date has questioned the currency of my skills, and I may have missed 5 points out of 100 on a compliance matrix for a government standing offer by not having it.  I dont feel I need to use it as an indicator of my knowledge any more.</p>
<p>I don’t bad-mouth the certification.  It is a pretty tough mental exercise to prepare for and write.  But once you have the experience and inherent credibility from your work, you may not need it. But people who wield their CISSP initials like a sword get the brunt of the scorn from others; mostly because it has become a bit of a stereotype in the industry.  It is certainly an achievement, but when people see it in an email signature block there is a thought that flashes through their mind, “How much real experience does this person have, if they have to display their badge in every email?&#8221;</p>
<p>I think its important to take some pride in accomplishments, but more important to keep them in the right context.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
