<?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: Cyber-Security Discussion at the Fedscoop Conference</title>
	<atom:link href="http://www.ourownlittlecorner.com/2009/10/15/cyber-security-discussion-at-the-fedscoop-conference/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ourownlittlecorner.com/2009/10/15/cyber-security-discussion-at-the-fedscoop-conference/</link>
	<description>Commentary on social networking, technology, movies, society, and random musings</description>
	<lastBuildDate>Wed, 26 Oct 2011 20:53:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Daniel</title>
		<link>http://www.ourownlittlecorner.com/2009/10/15/cyber-security-discussion-at-the-fedscoop-conference/comment-page-1/#comment-10</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sat, 17 Oct 2009 11:09:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.ourownlittlecorner.com/?p=91#comment-10</guid>
		<description>The C&amp;A issue, to me, is part of a different, broader issue.

Whenever Federal Government IT initiatives are put in place which require actions by the CIO&#039;s, whatever they do will be reviewed and in a public fashion evaluated on by a series of oversight organizations; these include the Inspectors General and GAO with guidance provided by NIST and in some cases using a framework contained in legislation.

Thus, regardless of the quality and usefulness of the initiative, the actual implementation is shaped by the interaction of the level of political/organization strength (and nerve) of the CIO and the perceived nature of the oversight evaluation. 

The result can be different than the intent.

The point of all this is that when OMB or other senior management in an administration think through what they want to accomplish, it would be valuable to also think about how the oversight requirements will impact on those goals.</description>
		<content:encoded><![CDATA[<p>The C&amp;A issue, to me, is part of a different, broader issue.</p>
<p>Whenever Federal Government IT initiatives are put in place which require actions by the CIO&#8217;s, whatever they do will be reviewed and in a public fashion evaluated on by a series of oversight organizations; these include the Inspectors General and GAO with guidance provided by NIST and in some cases using a framework contained in legislation.</p>
<p>Thus, regardless of the quality and usefulness of the initiative, the actual implementation is shaped by the interaction of the level of political/organization strength (and nerve) of the CIO and the perceived nature of the oversight evaluation. </p>
<p>The result can be different than the intent.</p>
<p>The point of all this is that when OMB or other senior management in an administration think through what they want to accomplish, it would be valuable to also think about how the oversight requirements will impact on those goals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Filler</title>
		<link>http://www.ourownlittlecorner.com/2009/10/15/cyber-security-discussion-at-the-fedscoop-conference/comment-page-1/#comment-9</link>
		<dc:creator>Dennis Filler</dc:creator>
		<pubDate>Fri, 16 Oct 2009 14:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.ourownlittlecorner.com/?p=91#comment-9</guid>
		<description>You&#039;ve captured the essence of the problem.  I describe it as a water drop.  It is a a system in tension. A balance of security and access dependent upon the surface that the water drop is on. If it gets out of balance, the drop ceases to exist until a new equilibrium is established. 

As far as metrics, no one cares about the millions of intrusion attempts that one prohibits.  I routinely had to address the failed login (access) attempts that some of the security personnel wanted us to address.  I routinely dismissed them as  security successes and didn&#039;t apply any resources to following up on these types of events.   The only events that folks really get concerned about are the successful intrusions.  The measures that you can  (try to) use are the speed of detection (only available through post analysis),  the quality  (accuracy) of data that your security folks pass to operations for event resolution,  the speed of event containment and services restoration and scope (relative size/ containment) of the security breach.   All security folks will probably agree that it is only a question of when you&#039;ll be breached.  What makes a difference is what you do operationally to manage the breach and work through the event.</description>
		<content:encoded><![CDATA[<p>You&#8217;ve captured the essence of the problem.  I describe it as a water drop.  It is a a system in tension. A balance of security and access dependent upon the surface that the water drop is on. If it gets out of balance, the drop ceases to exist until a new equilibrium is established. </p>
<p>As far as metrics, no one cares about the millions of intrusion attempts that one prohibits.  I routinely had to address the failed login (access) attempts that some of the security personnel wanted us to address.  I routinely dismissed them as  security successes and didn&#8217;t apply any resources to following up on these types of events.   The only events that folks really get concerned about are the successful intrusions.  The measures that you can  (try to) use are the speed of detection (only available through post analysis),  the quality  (accuracy) of data that your security folks pass to operations for event resolution,  the speed of event containment and services restoration and scope (relative size/ containment) of the security breach.   All security folks will probably agree that it is only a question of when you&#8217;ll be breached.  What makes a difference is what you do operationally to manage the breach and work through the event.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Dowell</title>
		<link>http://www.ourownlittlecorner.com/2009/10/15/cyber-security-discussion-at-the-fedscoop-conference/comment-page-1/#comment-8</link>
		<dc:creator>Scott Dowell</dc:creator>
		<pubDate>Thu, 15 Oct 2009 23:13:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.ourownlittlecorner.com/?p=91#comment-8</guid>
		<description>Dan,
Your comments are right on.  The key is to define a good balance of security, risk, and cost models.

As I read your post, I was struck by a similar, if smaller scale argument posed a recent panel discussing cloud at a very tactical level.  As you know, within the Navy context the C&amp;A function can be a challenge - and - with Cloud there appears to be significant confusion as to the appropriate accreditation &amp; certification process. 

Do you believe that your remarks regarding standardization and rational decision making extend to the C&amp;A level as well?

Great post
-Scott</description>
		<content:encoded><![CDATA[<p>Dan,<br />
Your comments are right on.  The key is to define a good balance of security, risk, and cost models.</p>
<p>As I read your post, I was struck by a similar, if smaller scale argument posed a recent panel discussing cloud at a very tactical level.  As you know, within the Navy context the C&amp;A function can be a challenge &#8211; and &#8211; with Cloud there appears to be significant confusion as to the appropriate accreditation &amp; certification process. </p>
<p>Do you believe that your remarks regarding standardization and rational decision making extend to the C&amp;A level as well?</p>
<p>Great post<br />
-Scott</p>
]]></content:encoded>
	</item>
</channel>
</rss>

