<?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: Controlled Unclassified Information</title>
	<atom:link href="http://www.outsidethebeltway.com/archives/controlled_unclassified_information/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.outsidethebeltway.com/archives/controlled_unclassified_information/</link>
	<description>Online Journal of Politics and Foreign Affairs</description>
	<lastBuildDate>Wed, 25 Nov 2009 18:04:01 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael</title>
		<link>http://www.outsidethebeltway.com/archives/controlled_unclassified_information/comment-page-1/#comment-405408</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 10 Jun 2008 12:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.outsidethebeltway.com/archives/2008/06/controlled_unclassified_information/#comment-405408</guid>
		<description>&lt;blockquote&gt;My suspicion, unfortunately, is that the bill which actually emerges — at least after the bean counters lard it with “clarifying” regulation — will further the tendency to treat routine operating information as sensitive and thus not sharable with the public because those who would do us harm could cobble together something damaging from bits and pieces of information that, in isolation, are innocuous.&lt;/blockquote&gt;Security through obscurity is not actual security.

&lt;blockquote&gt;An example is a detailed map (GPS exact) of all the natural gas pipelines and pumping stations in an area. Just marking it proprietary information isn&#039;t adequate, as that is mostly used in the financial end of things. Should such information be available to anyone that submits a FOIA or Sunshine Act request?&lt;/blockquote&gt;The problem is that the locations of these things are not secrets.  All you&#039;re doing by not making the maps available is requiring someone to go look for themselves, you&#039;re not preventing them from finding it out.  

It&#039;s like preventing someone without a security badge from using the elevator, but keeping the stairs freely accessible.  The top floors are no more secure in that situation than if you just let everyone use the elevator.</description>
		<content:encoded><![CDATA[<blockquote><p>My suspicion, unfortunately, is that the bill which actually emerges — at least after the bean counters lard it with “clarifying” regulation — will further the tendency to treat routine operating information as sensitive and thus not sharable with the public because those who would do us harm could cobble together something damaging from bits and pieces of information that, in isolation, are innocuous.</p></blockquote>
<p>Security through obscurity is not actual security.</p>
<blockquote><p>An example is a detailed map (GPS exact) of all the natural gas pipelines and pumping stations in an area. Just marking it proprietary information isn't adequate, as that is mostly used in the financial end of things. Should such information be available to anyone that submits a FOIA or Sunshine Act request?</p></blockquote>
<p>The problem is that the locations of these things are not secrets.  All you're doing by not making the maps available is requiring someone to go look for themselves, you're not preventing them from finding it out.  </p>
<p>It's like preventing someone without a security badge from using the elevator, but keeping the stairs freely accessible.  The top floors are no more secure in that situation than if you just let everyone use the elevator.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Gardner</title>
		<link>http://www.outsidethebeltway.com/archives/controlled_unclassified_information/comment-page-1/#comment-404450</link>
		<dc:creator>Richard Gardner</dc:creator>
		<pubDate>Mon, 09 Jun 2008 22:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.outsidethebeltway.com/archives/2008/06/controlled_unclassified_information/#comment-404450</guid>
		<description>&lt;blockquote&gt;Ending the practice of stamping that sort of material — including huge documents with only a sentence of such material — “classified” could be a boon.&lt;/blockquote&gt;

On the other hand, sometimes you have a piece of paper whose individual items are all unclassified but when combined make it a sensitive document, particularly in homeland security. An example is a detailed map (GPS exact) of all the natural gas pipelines and pumping stations in an area. Just marking it proprietary information isn&#039;t adequate, as that is mostly used in the financial end of things. Should such information be available to anyone that submits a FOIA or Sunshine Act request?

The above natural gas pipeline example actually occurred in WA State a year or so ago (State Emergency Department or equivalent (in this case the WA Utilities and Transportation Commission)) required the companies to provide the info), but the same could apply to FEMA/DHS/&lt;a href=&quot;https://www.npms.phmsa.dot.gov/&quot; rel=&quot;nofollow&quot;&gt;DOT&lt;/a&gt;.  

The problem with classifying this info in the conventional Confidential/Secret/Top Secret methodology is that it just doesn&#039;t fit into the (outdated in my mind) &quot;National Security Information&quot; framework. It should be need-to-know, but there is no need to massively increase the number of folks with security clearances (even Confidential).</description>
		<content:encoded><![CDATA[<blockquote><p>Ending the practice of stamping that sort of material — including huge documents with only a sentence of such material — “classified” could be a boon.</p></blockquote>
<p>On the other hand, sometimes you have a piece of paper whose individual items are all unclassified but when combined make it a sensitive document, particularly in homeland security. An example is a detailed map (GPS exact) of all the natural gas pipelines and pumping stations in an area. Just marking it proprietary information isn't adequate, as that is mostly used in the financial end of things. Should such information be available to anyone that submits a FOIA or Sunshine Act request?</p>
<p>The above natural gas pipeline example actually occurred in WA State a year or so ago (State Emergency Department or equivalent (in this case the WA Utilities and Transportation Commission)) required the companies to provide the info), but the same could apply to FEMA/DHS/<a href="https://www.npms.phmsa.dot.gov/" rel="nofollow">DOT</a>.  </p>
<p>The problem with classifying this info in the conventional Confidential/Secret/Top Secret methodology is that it just doesn't fit into the (outdated in my mind) "National Security Information" framework. It should be need-to-know, but there is no need to massively increase the number of folks with security clearances (even Confidential).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
