﻿<?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: The Presidential Transition and Secrecy</title>
	<atom:link href="http://www.fas.org/blog/secrecy/2008/11/transition_and_secrecy.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.fas.org/blog/secrecy/2008/11/transition_and_secrecy.html</link>
	<description>Secrecy News from the FAS Project on Government Secrecy</description>
	<lastBuildDate>Mon, 13 Feb 2012 21:51:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Java Click</title>
		<link>http://www.fas.org/blog/secrecy/2008/11/transition_and_secrecy.html/comment-page-1#comment-2219</link>
		<dc:creator>Java Click</dc:creator>
		<pubDate>Sun, 09 Nov 2008 20:36:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.fas.org/blog/secrecy/?p=2074#comment-2219</guid>
		<description>Governmental organizational policies are almost always going to evolve into  incomprehensible and illogical quagmires. 

Those struggling for solutions often find themselves victim to another human failing; fixating on foreground details, mistaking immediacy for importance. Inevitably this leads to bandaging the problem, and patting oneself on the back for creating such an effective &quot;solution&quot;, when in fact only the symptom has been addressed.  The actual problem requires emotional divestment and enlarged perspective.  

In this particular case, the problem is not the byzantine system that has been implemented, but rather that the system is specified by personnel who have no business specifying these systems in the first place.  

Instead of microanalyses of individual procedures, a better approach would be a reworking of the expectations of and requirements for the policy making individual, with a heavy emphasis on real-world experience, with a track record of proven results, and not someone who has developed their philosophy from inside the governmental structure.  

This is the origin of the current system and it relies on political alliance and legal-writing skills, with a focus on self-advancement more than technical understanding and experience.

Once again, the politically adept emerge victorious over the socially-impaired genius. Lets stop rewarding idiocy and emotionalism and start giving the public a more positive view of intellectualism. I will talk about that dynamic in a later blog post. For now, I suggest a reread of Dale Carnegie&#039;s book, a lot of patience, and herbal tea.</description>
		<content:encoded><![CDATA[<p>Governmental organizational policies are almost always going to evolve into  incomprehensible and illogical quagmires. </p>
<p>Those struggling for solutions often find themselves victim to another human failing; fixating on foreground details, mistaking immediacy for importance. Inevitably this leads to bandaging the problem, and patting oneself on the back for creating such an effective &#8220;solution&#8221;, when in fact only the symptom has been addressed.  The actual problem requires emotional divestment and enlarged perspective.  </p>
<p>In this particular case, the problem is not the byzantine system that has been implemented, but rather that the system is specified by personnel who have no business specifying these systems in the first place.  </p>
<p>Instead of microanalyses of individual procedures, a better approach would be a reworking of the expectations of and requirements for the policy making individual, with a heavy emphasis on real-world experience, with a track record of proven results, and not someone who has developed their philosophy from inside the governmental structure.  </p>
<p>This is the origin of the current system and it relies on political alliance and legal-writing skills, with a focus on self-advancement more than technical understanding and experience.</p>
<p>Once again, the politically adept emerge victorious over the socially-impaired genius. Lets stop rewarding idiocy and emotionalism and start giving the public a more positive view of intellectualism. I will talk about that dynamic in a later blog post. For now, I suggest a reread of Dale Carnegie&#8217;s book, a lot of patience, and herbal tea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://www.fas.org/blog/secrecy/2008/11/transition_and_secrecy.html/comment-page-1#comment-2193</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Thu, 06 Nov 2008 20:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.fas.org/blog/secrecy/?p=2074#comment-2193</guid>
		<description>Those of us worker bees in the Executive Branch have been required to take training about &quot;Sensitive But Unclassified&quot; information, including rules about labeling such information and who is allowed to remove such a label. Swept up in this catch-all net were everything from vendor proprietary information and data protected by the Privacy Act, to technical data that&#039;s export restricted. The result is an unworkable hodge-podge that has been impossible to implement well in non-defense agencies. (So how much of my hard drive do I have to encrypt? Do I edit my electronic copy of an informational vendor presentation to add &#039;SBU&#039; on every page? Do I then have to notify my supervisor when I delete the file? What do I do now that implementing Microsoft&#039;s Active Directory has broken the fingerprint reader on my laptop?) 

A silly example: It was recently decided that SSL and protections used by commercial web sites weren&#039;t good enough for teleworkers filling out our time sheets. That&#039;s because the employee time-keeping system has personally identifiable information in it. Duh. Now we have to apply for electronic VPN tokens to access an on-site machine to use a commercial web-based time-keeping application. Of course I&#039;m in favor of securing personal data against identity thieves, but this policy change seems to have been implemented without much thought to the side-effects (e.g., more DC traffic and/or more tax money for hundreds of thousands of electronic gizzmo&#039;s we have to carry on our persons). 

The new administration needs to get rid of this pseudo-category of restricted information ASAP and return to a presumption of openness--as well as ensure that the specific types of legally valid restrictions on information sharing are enforced. Privacy Act restrictions are not at all like export restrictions and neither is like embargoes on prepublication scientific data. Lumping them together just confuses things and reinforces a general presumption of government secrecy.</description>
		<content:encoded><![CDATA[<p>Those of us worker bees in the Executive Branch have been required to take training about &#8220;Sensitive But Unclassified&#8221; information, including rules about labeling such information and who is allowed to remove such a label. Swept up in this catch-all net were everything from vendor proprietary information and data protected by the Privacy Act, to technical data that&#8217;s export restricted. The result is an unworkable hodge-podge that has been impossible to implement well in non-defense agencies. (So how much of my hard drive do I have to encrypt? Do I edit my electronic copy of an informational vendor presentation to add &#8216;SBU&#8217; on every page? Do I then have to notify my supervisor when I delete the file? What do I do now that implementing Microsoft&#8217;s Active Directory has broken the fingerprint reader on my laptop?) </p>
<p>A silly example: It was recently decided that SSL and protections used by commercial web sites weren&#8217;t good enough for teleworkers filling out our time sheets. That&#8217;s because the employee time-keeping system has personally identifiable information in it. Duh. Now we have to apply for electronic VPN tokens to access an on-site machine to use a commercial web-based time-keeping application. Of course I&#8217;m in favor of securing personal data against identity thieves, but this policy change seems to have been implemented without much thought to the side-effects (e.g., more DC traffic and/or more tax money for hundreds of thousands of electronic gizzmo&#8217;s we have to carry on our persons). </p>
<p>The new administration needs to get rid of this pseudo-category of restricted information ASAP and return to a presumption of openness&#8211;as well as ensure that the specific types of legally valid restrictions on information sharing are enforced. Privacy Act restrictions are not at all like export restrictions and neither is like embargoes on prepublication scientific data. Lumping them together just confuses things and reinforces a general presumption of government secrecy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Hansen</title>
		<link>http://www.fas.org/blog/secrecy/2008/11/transition_and_secrecy.html/comment-page-1#comment-2192</link>
		<dc:creator>Nick Hansen</dc:creator>
		<pubDate>Thu, 06 Nov 2008 19:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.fas.org/blog/secrecy/?p=2074#comment-2192</guid>
		<description>Steven, 

Keep fighting your good fight! Now is the time to push this change and Secrecy News should lead the way. Your knowledge and passion on Openness is remarkable and I hope you find very willing ears to bend in the new Administration.

Thanks for all you do!!!</description>
		<content:encoded><![CDATA[<p>Steven, </p>
<p>Keep fighting your good fight! Now is the time to push this change and Secrecy News should lead the way. Your knowledge and passion on Openness is remarkable and I hope you find very willing ears to bend in the new Administration.</p>
<p>Thanks for all you do!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

