<?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: Why Information Security Professionals Should Learn Texas Hold &#8216;em Poker</title>
	<atom:link href="http://www.bloginfosec.com/2008/06/11/why-information-security-professionals-should-learn-texas-hold-em-poker/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloginfosec.com/2008/06/11/why-information-security-professionals-should-learn-texas-hold-em-poker/</link>
	<description>An Information Security Magazine in a Blog Format</description>
	<lastBuildDate>Mon, 30 Jan 2012 11:01:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Navin</title>
		<link>http://www.bloginfosec.com/2008/06/11/why-information-security-professionals-should-learn-texas-hold-em-poker/comment-page-1/#comment-10576</link>
		<dc:creator>Navin</dc:creator>
		<pubDate>Fri, 18 Jul 2008 06:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloginfosec.com/?p=448#comment-10576</guid>
		<description>Agree with you Gary.  I think that the business would actually like us to be calculated risk takers.  Business leaders are all about taking calculated risks so that they can effectively execute on business strategy.  Since we are best placed to make decisions regarding acceptable risk relating to information security, if our risk appetite is significantly different to that of the business, then we will either pull them back or pitch them forward.  We&#039;ve got to calibrate infosec risk against business operational risk, financial risk, etc. and make decisions regarding information security in the same vein.</description>
		<content:encoded><![CDATA[<p>Agree with you Gary.  I think that the business would actually like us to be calculated risk takers.  Business leaders are all about taking calculated risks so that they can effectively execute on business strategy.  Since we are best placed to make decisions regarding acceptable risk relating to information security, if our risk appetite is significantly different to that of the business, then we will either pull them back or pitch them forward.  We&#8217;ve got to calibrate infosec risk against business operational risk, financial risk, etc. and make decisions regarding information security in the same vein.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary</title>
		<link>http://www.bloginfosec.com/2008/06/11/why-information-security-professionals-should-learn-texas-hold-em-poker/comment-page-1/#comment-7860</link>
		<dc:creator>Gary</dc:creator>
		<pubDate>Tue, 17 Jun 2008 08:42:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloginfosec.com/?p=448#comment-7860</guid>
		<description>Speak for yourself, Kenneth.  Not all infosec pros are &quot;risk adverse&quot; as you say (I believe you mean &#039;risk averse&#039;, by the way).  Risk aware, maybe, cautious by nature but not risk averse.  To get things done in The Real World, most of us realized early in our careers that outright principled risk aversion sets us against the rest f the organization.  It&#039;s the root cause of naive ISM functions commonly being known as The No Department.  

I&#039;m not saying we should be The Yes Department either.  Mostly I&#039;d settle for a &quot;Yes If ...&quot; or &quot;No Unless ...&quot;, so long as it leads to incremental improvement and a greater level of knowledge, understanding and most of all accountability for our business management colleagues who are paid to make the difficult decisions.  And there ARE situations in which it is totally appropriate to say No!  NO!  NO NO NO!  The trick is to pick your battles, and beware the scars.

G.</description>
		<content:encoded><![CDATA[<p>Speak for yourself, Kenneth.  Not all infosec pros are &#8220;risk adverse&#8221; as you say (I believe you mean &#8216;risk averse&#8217;, by the way).  Risk aware, maybe, cautious by nature but not risk averse.  To get things done in The Real World, most of us realized early in our careers that outright principled risk aversion sets us against the rest f the organization.  It&#8217;s the root cause of naive ISM functions commonly being known as The No Department.  </p>
<p>I&#8217;m not saying we should be The Yes Department either.  Mostly I&#8217;d settle for a &#8220;Yes If &#8230;&#8221; or &#8220;No Unless &#8230;&#8221;, so long as it leads to incremental improvement and a greater level of knowledge, understanding and most of all accountability for our business management colleagues who are paid to make the difficult decisions.  And there ARE situations in which it is totally appropriate to say No!  NO!  NO NO NO!  The trick is to pick your battles, and beware the scars.</p>
<p>G.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

