<?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: Oops! Unredacted TSA manual released; &#8220;full review&#8221; underway by agency</title>
	<atom:link href="http://www.elliott.org/blog/oops-unredacted-tsa-manual-released-full-review-underway-by-agency/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.elliott.org/blog/oops-unredacted-tsa-manual-released-full-review-underway-by-agency/</link>
	<description>Consumer advocate Christopher Elliott&#039;s site.</description>
	<lastBuildDate>Fri, 10 Feb 2012 05:25:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: TSA, DFW Airport and photography inside the terminal - FlyerTalk Forums</title>
		<link>http://www.elliott.org/blog/oops-unredacted-tsa-manual-released-full-review-underway-by-agency/comment-page-1/#comment-65120</link>
		<dc:creator>TSA, DFW Airport and photography inside the terminal - FlyerTalk Forums</dc:creator>
		<pubDate>Tue, 01 Mar 2011 17:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliott.org/?p=9783#comment-65120</guid>
		<description>[...] this?    You can point to Section 2.7 of the TSA Screening Management SOP that can be opened from here. I have the unredacted version on my computer, but you shouldn&#039;t need that for the purposes of [...]</description>
		<content:encoded><![CDATA[<p>[...] this?    You can point to Section 2.7 of the TSA Screening Management SOP that can be opened from here. I have the unredacted version on my computer, but you shouldn&#039;t need that for the purposes of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A glimpse into the workings of the TSA (not a glimpse they meant for you to have, but very interesting) &#171; Skooba Blog</title>
		<link>http://www.elliott.org/blog/oops-unredacted-tsa-manual-released-full-review-underway-by-agency/comment-page-1/#comment-28402</link>
		<dc:creator>A glimpse into the workings of the TSA (not a glimpse they meant for you to have, but very interesting) &#171; Skooba Blog</dc:creator>
		<pubDate>Tue, 08 Dec 2009 19:24:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliott.org/?p=9783#comment-28402</guid>
		<description>[...] Apparently this particular manual is outdated and has been redone several times since this version, but those who travel frequently may still find some of it interesting and informative. Much of it is boring administrative stuff, but there are a few tidbits in there. For example, apparently it is not against the rules for passengers to take pictures or video in the security area. Yet I have seen many instances where someone was doing just that and was quickly told by a TSA officer to stop. Anyway, I thought the story was interesting&#8230; if you&#8217;re curious, you can read the whole thing here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Apparently this particular manual is outdated and has been redone several times since this version, but those who travel frequently may still find some of it interesting and informative. Much of it is boring administrative stuff, but there are a few tidbits in there. For example, apparently it is not against the rules for passengers to take pictures or video in the security area. Yet I have seen many instances where someone was doing just that and was quickly told by a TSA officer to stop. Anyway, I thought the story was interesting&#8230; if you&#8217;re curious, you can read the whole thing here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LeeAnne</title>
		<link>http://www.elliott.org/blog/oops-unredacted-tsa-manual-released-full-review-underway-by-agency/comment-page-1/#comment-28345</link>
		<dc:creator>LeeAnne</dc:creator>
		<pubDate>Mon, 07 Dec 2009 23:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliott.org/?p=9783#comment-28345</guid>
		<description>As a technical writer, and someone who has developed many cross-functional SOPs, I can confirm both points made by your &quot;person who is familiar with redaction boo-boos.&quot;  Specifically - that Microsoft Word can be a real pain (and if they recently upgraded to Vista, it&#039;s a nightmare - unlearn everything you learned and start over!).  AND, many SOPs are not so much documentation of actual processes or procedures, as they are exercises in getting down on paper the personal agendas and pet issues of competing stakeholders in whatever process is being documented.  I can&#039;t tell you the number of SOPs that I have written that are unfollowable in practice.

This does not necessarily reflect on the ability of the organization to proficiently perform its core function.  All it means is that 1) some technical writer or doc person doesn&#039;t know how to use Word, and 2) TSA is like any other organization in terms of its internal political struggles with process documentation.

I&#039;m NOT suggesting TSA actually does what it&#039;s supposed to do well.  In fact, I personally think they are completely incompetent!  I&#039;m just pointing out that the fact that this *thing* happened with this wrong version of an SOP says nothing whatsoever about their competency at TSA&#039;ing.</description>
		<content:encoded><![CDATA[<p>As a technical writer, and someone who has developed many cross-functional SOPs, I can confirm both points made by your &#8220;person who is familiar with redaction boo-boos.&#8221;  Specifically &#8211; that Microsoft Word can be a real pain (and if they recently upgraded to Vista, it&#8217;s a nightmare &#8211; unlearn everything you learned and start over!).  AND, many SOPs are not so much documentation of actual processes or procedures, as they are exercises in getting down on paper the personal agendas and pet issues of competing stakeholders in whatever process is being documented.  I can&#8217;t tell you the number of SOPs that I have written that are unfollowable in practice.</p>
<p>This does not necessarily reflect on the ability of the organization to proficiently perform its core function.  All it means is that 1) some technical writer or doc person doesn&#8217;t know how to use Word, and 2) TSA is like any other organization in terms of its internal political struggles with process documentation.</p>
<p>I&#8217;m NOT suggesting TSA actually does what it&#8217;s supposed to do well.  In fact, I personally think they are completely incompetent!  I&#8217;m just pointing out that the fact that this *thing* happened with this wrong version of an SOP says nothing whatsoever about their competency at TSA&#8217;ing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wandering Aramean</title>
		<link>http://www.elliott.org/blog/oops-unredacted-tsa-manual-released-full-review-underway-by-agency/comment-page-1/#comment-28344</link>
		<dc:creator>Wandering Aramean</dc:creator>
		<pubDate>Mon, 07 Dec 2009 23:34:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.elliott.org/?p=9783#comment-28344</guid>
		<description>Thanks for the link-back and for reading it after I mentioned it during the WaPo chat this afternoon.

A few interesting things about this.  Yes, it was quite certainly a human error that the redaction didn&#039;t work correctly.  But that&#039;s not an excuse.  Whether juicy or not it is clear that the content &quot;blacked out&quot; was not supposed to be shared with the public.  And now the TSA expects us to trust them in cleaning up the mess.

Second, the version of the TSA response I got was that this version was &quot;outdated&quot; rather than never implemented.  Moreover, even if this explicit version was not implemented it is almost certain that pieces of it were.  Most likely huge chunks of it. 

And then there are the &quot;juicy&quot; bits.  Want to know what the x-ray machines resolution is in terms of noticing wires in a carry-on bag?  That information is in the document.  So are the details on where the folks testing the magnetometers conceal their &quot;gun&quot; as they verify functionality.  Interested in bypassing the selectee screening process?  Probably not so relevant any more, but the information is in the document.  Oh, and the list of twelve countries from which every single citizen is deemed a risk to American air safety is laughable were it not so sad.

Perhaps the greatest irony, however, is just how ridiculous some of the redacted content is.  Why is it important that the public not know that the TSOs are to change their gloves if the ETD machine reports a positive result?  The fact that the TSA continues to hide behind the SSI designation whenever they are pressed for answers by the general public is a farce, especially when taken in the light of just how ridiculous some of the things designated as SSI are.</description>
		<content:encoded><![CDATA[<p>Thanks for the link-back and for reading it after I mentioned it during the WaPo chat this afternoon.</p>
<p>A few interesting things about this.  Yes, it was quite certainly a human error that the redaction didn&#8217;t work correctly.  But that&#8217;s not an excuse.  Whether juicy or not it is clear that the content &#8220;blacked out&#8221; was not supposed to be shared with the public.  And now the TSA expects us to trust them in cleaning up the mess.</p>
<p>Second, the version of the TSA response I got was that this version was &#8220;outdated&#8221; rather than never implemented.  Moreover, even if this explicit version was not implemented it is almost certain that pieces of it were.  Most likely huge chunks of it. </p>
<p>And then there are the &#8220;juicy&#8221; bits.  Want to know what the x-ray machines resolution is in terms of noticing wires in a carry-on bag?  That information is in the document.  So are the details on where the folks testing the magnetometers conceal their &#8220;gun&#8221; as they verify functionality.  Interested in bypassing the selectee screening process?  Probably not so relevant any more, but the information is in the document.  Oh, and the list of twelve countries from which every single citizen is deemed a risk to American air safety is laughable were it not so sad.</p>
<p>Perhaps the greatest irony, however, is just how ridiculous some of the redacted content is.  Why is it important that the public not know that the TSOs are to change their gloves if the ETD machine reports a positive result?  The fact that the TSA continues to hide behind the SSI designation whenever they are pressed for answers by the general public is a farce, especially when taken in the light of just how ridiculous some of the things designated as SSI are.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

