<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>the corioblog &#187; Security</title>
	<atom:link href="http://www.coriolinus.net/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.coriolinus.net</link>
	<description>read, and be entertained</description>
	<lastBuildDate>Sat, 09 Jul 2011 19:53:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>FW: Wikileaks data on Gov&#8217;t Computers &amp; Personal Owned</title>
		<link>http://www.coriolinus.net/2010/12/09/fw-wikileaks-data-on-govt-computers-personal-owned/</link>
		<comments>http://www.coriolinus.net/2010/12/09/fw-wikileaks-data-on-govt-computers-personal-owned/#comments</comments>
		<pubDate>Thu, 09 Dec 2010 10:09:09 +0000</pubDate>
		<dc:creator>coriolinus</dc:creator>
				<category><![CDATA[army]]></category>
		<category><![CDATA[what i learned at work today]]></category>
		<category><![CDATA[AV]]></category>
		<category><![CDATA[Caching]]></category>
		<category><![CDATA[Classified information]]></category>
		<category><![CDATA[Computer network security]]></category>
		<category><![CDATA[Computer security]]></category>
		<category><![CDATA[Department of Defense]]></category>
		<category><![CDATA[Employee-owned information systems]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Information assurance]]></category>
		<category><![CDATA[Information security]]></category>
		<category><![CDATA[Information sensitivity]]></category>
		<category><![CDATA[National security]]></category>
		<category><![CDATA[officer]]></category>
		<category><![CDATA[Oregon]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[storage media]]></category>
		<category><![CDATA[Technology/Internet]]></category>
		<category><![CDATA[Wikileaks]]></category>

		<guid isPermaLink="false">http://www.coriolinus.net/?p=3148</guid>
		<description><![CDATA[Received the following email regarding the official Army policy on Wikileaks, at least for my unit: From: [redacted] Sent: Wednesday, December 08, 2010 4:03 PM To: 2-2 AVN Staff; 2-2 ASLT COs; 2-2 ASLT 1SGs Subject: FW: Wikileaks data on Gov&#8217;t Computers &#38; Personal Owned Computers (UNCLASSIFIED) Importance: High ALCON, Below is the guidance for [...]]]></description>
			<content:encoded><![CDATA[<p>Received the following email regarding the official Army policy on Wikileaks, at least for my unit:</p>
<blockquote><p>From: [redacted]<br />
Sent: Wednesday, December 08, 2010 4:03 PM<br />
To: 2-2 AVN Staff; 2-2 ASLT COs; 2-2 ASLT 1SGs<br />
Subject: FW: Wikileaks data on Gov&#8217;t Computers &amp; Personal Owned<br />
Computers (UNCLASSIFIED)<br />
Importance: High</p>
<p>ALCON,</p>
<p>Below is the guidance for viewing material on Wikileaks&#8217; website.  To<br />
summarize the below, the Wikileaks website is not to be viewed on a<br />
Government computer, the information is still considered to be<br />
classified and any computer found containing classified information<br />
(i.e. information from Wikileaks) will confiscated and subsequently<br />
wiped.</p>
<p>If there are any questions please contact the S2 office.</p>
<p>v/r</p>
<p>[redacted]<br />
CPT, MI<br />
2-2 AASLT BN S2</p>
<p>&#8212;&#8211;Original Message&#8212;&#8211;<br />
From: [redacted]<br />
Sent: Wednesday, December 08, 2010 11:05 AM<br />
To: [redacted]<br />
Subject: Wikileaks data on Gov&#8217;t Computers &amp; Personal Owned Computers<br />
(UNCLASSIFIED)<br />
Importance: High</p>
<p>BLUF: Do not view released or published classified data found on the<br />
internet (Open Source) on unclassified Government systems OR on personal<br />
owed systems. (See caveats)</p>
<p>Department of the Army policies regarding the issue can be found in AR<br />
380-5 Information Security and AR 25-2 Information Assurance. All of the<br />
information is still considered classified. Although now that it can be<br />
found via open source, DOD still considers it as classified until<br />
further notice and should not be viewed or process on a designated<br />
unclassified government computer. Should a unclassified computer be<br />
found containing classified information, it will need to be isolated and<br />
wiped to remove the information.</p>
<p>As for viewing the information via personal computer, I have not seen<br />
any official message traffic preventing military personnel from viewing<br />
the information; however should a personal laptop be found with<br />
classified information on it, it will be confiscated with the potential<br />
for a 15-6 investigation based on the information on an unapproved<br />
system and improper storage.</p>
<p>AR 380-5, Chapter 10-2 a.</p>
<p>and</p>
<p>AR 25-2</p>
<p>4-31. Employee-owned information systems a. Prohibit the use of<br />
employee-owned information systems (EOISs) for classified or sensitive<br />
information.</p>
<p>AR 25-2 Chapter 3-3</p>
<p>c. General users. Use of Government IS and access to Government networks<br />
is a revocable privilege, not a right.</p>
<p>Users are the foundation of the DiD strategy and their actions affect<br />
the most vulnerable portion of the AEI. Users must have a favorable<br />
background investigation or hold a security clearance and access<br />
approvals commensurate with the level of information processed or<br />
available on the system. Users will-</p>
<p>(1) Comply with the command&#8217;s AUP for Government owned ISs and sign an<br />
AUP prior to or upon account activation.</p>
<p>(2) Complete initial and/or annual IA training as defined in the IA<br />
training BBP (<a href="https://informationassurance.us.army.mil/" target="_blank">https://informationassurance.us.army.mil</a><br />
&lt;<a href="https://informationassurance.us.army.mil/" target="_blank">https://informationassurance.us.army.mil/</a>&gt; ).</p>
<p>(3) Mark and safeguard files, output products, and storage media per the<br />
classification level and disseminate them only to individuals authorized<br />
to receive them with a valid need to know.</p>
<p>(4) Protect ISs and IS peripherals located in their respective areas in<br />
accordance with physical security and data protection requirements.</p>
<p>(5) Practice safe network and Internet operating principles and take no<br />
actions that threaten the integrity of the system or network.</p>
<p>(6) Obtain prior approval for the use of any media (for example, USB,<br />
CD-ROM, floppy disk) from the SA/ IAM.</p>
<p>(7) Scan all files, attachments, and media with an approved and<br />
installed AV product before opening a file or attachment or introducing<br />
media into the IS.</p>
<p>(8) Report all known or suspected spam, chain letters, and violations of<br />
acceptable use to the SA, IAM, or IASO.</p>
<p>(9) Immediately stop using an infected IS; and report suspicious,<br />
erratic, or anomalous IS operations, and missing or added files,<br />
services, or programs to the SA/IASO in accordance with local policy.</p>
<p>(10) Not disclose their individual account password or pass-phrase<br />
authenticators.</p>
<p>(11) Invoke password-protected screen locks on your workstation after<br />
not more than 15 minutes of non-use or inactivity.</p>
<p>(12) Logoff ISs at the end of each workday.</p>
<p>(13) Access only that data, control information, software, hardware, and<br />
firmware for which the user is authorized access.</p>
<p>(14) Access only that data that they are authorized or have a need to<br />
know.</p>
<p>Should someone have additional information regarding this issue please<br />
send to me so I can review and disseminate.</p>
<p>V/r,</p>
<p>CPT [redacted]<br />
BDE S2, 2 CAB, 2 ID</p></blockquote>
<p>I&#8217;ve redacted the names in the emails; what matters is that they came from the BDE and BN S2. For those of you not in the Army, the S2 is the information security office; the bit of each unit in charge of classification, and the officer who signs as S2 is the person in charge of information security for that unit.</p>
<p>The policy they lay out here actually seems pretty sane to me: even though they&#8217;re threatening confiscation and erasure of personal computers discovered to have classified data on them, it&#8217;s not like they&#8217;re proposing to audit everyone&#8217;s individual PC; they&#8217;re just reiterating already extant policy. As it stands, on your own time and internet you&#8217;re perfectly free to look at this; just turn on porn mode and prevent your browser from caching anything!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coriolinus.net/2010/12/09/fw-wikileaks-data-on-govt-computers-personal-owned/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Apache Video</title>
		<link>http://www.coriolinus.net/2010/04/06/the-apache-video/</link>
		<comments>http://www.coriolinus.net/2010/04/06/the-apache-video/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 03:32:58 +0000</pubDate>
		<dc:creator>coriolinus</dc:creator>
				<category><![CDATA[army]]></category>
		<category><![CDATA[opinion]]></category>
		<category><![CDATA[Alaska]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[Apache Corporation]]></category>
		<category><![CDATA[computing]]></category>
		<category><![CDATA[Espionage]]></category>
		<category><![CDATA[Gun camera]]></category>
		<category><![CDATA[Internet censorship]]></category>
		<category><![CDATA[National security]]></category>
		<category><![CDATA[official spokesman]]></category>
		<category><![CDATA[PDF]]></category>
		<category><![CDATA[pentagon]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Thomson Reuters Group Ltd]]></category>
		<category><![CDATA[UH-60]]></category>
		<category><![CDATA[United States Army]]></category>
		<category><![CDATA[War/Conflict]]></category>
		<category><![CDATA[Web 2.0]]></category>
		<category><![CDATA[Whistleblowing]]></category>
		<category><![CDATA[Wikileaks]]></category>
		<category><![CDATA[World Wide Web]]></category>

		<guid isPermaLink="false">http://www.coriolinus.net/?p=3038</guid>
		<description><![CDATA[(Preface: I am neither an official Pentagon source nor an official spokesman for the Army. I am a US Army UH-60 pilot otherwise entirely dissociated from this event; these are my personal opinions.) A video was posted recently by WikiLeaks. It&#8217;s gun camera footage from an Apache engagement on 12 July 2007. The video begins [...]]]></description>
			<content:encoded><![CDATA[<p>(Preface: I am neither an official Pentagon source nor an official spokesman for the Army. I am a US Army UH-60 pilot otherwise entirely dissociated from this event; these are my personal opinions.)</p>
<p>A video was posted recently by WikiLeaks. It&#8217;s gun camera footage from an Apache engagement on 12 July 2007. </p>
<p><object width="640" height="385"><param name="movie" value="http://www.youtube.com/v/is9sxRfU-ik&#038;rel=0&#038;color1=0xb1b1b1&#038;color2=0xcfcfcf&#038;hl=en_GB&#038;feature=player_embedded&#038;fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowScriptAccess" value="always"></param><embed src="http://www.youtube.com/v/is9sxRfU-ik&#038;rel=0&#038;color1=0xb1b1b1&#038;color2=0xcfcfcf&#038;hl=en_GB&#038;feature=player_embedded&#038;fs=1" type="application/x-shockwave-flash" allowfullscreen="true" allowScriptAccess="always" width="640" height="385"></embed></object></p>
<p>The video begins with ground forces requesting support from Crazyhorse, the Apache flight. They mention a group of people, one of whom has a weapon.</p>
<p><a href="http://www.coriolinus.net/wp-content/uploads/2010/04/1-man-with-ak.jpg"><img src="http://www.coriolinus.net/wp-content/uploads/2010/04/1-man-with-ak.jpg" alt="" title="Man with AK" width="640" height="400" class="alignnone size-full wp-image-3039" /></a><br />
<a href="http://www.coriolinus.net/wp-content/uploads/2010/04/2-ak-hilighted.jpg"><img src="http://www.coriolinus.net/wp-content/uploads/2010/04/2-ak-hilighted.jpg" alt="" title="AK hilighted" width="378" height="286" class="alignnone size-full wp-image-3040" /></a></p>
<p>It&#8217;s hard to see, because we&#8217;re looking at a low-resolution version of a low-resolution video looking at a distant target, but the guy does appear to be carrying an AK. It looks like the Apache&#8217;s found the group that the ground forces were talking about.</p>
<p><a href="http://www.coriolinus.net/wp-content/uploads/2010/04/3-hes-got-a-weapon-too.jpg"><img src="http://www.coriolinus.net/wp-content/uploads/2010/04/3-hes-got-a-weapon-too.jpg" alt="" title="He&#039;s got a weapon too" width="640" height="400" class="alignnone size-full wp-image-3042" /></a><br />
<a href="http://www.coriolinus.net/wp-content/uploads/2010/04/4-weapon-hilighted.jpg"><img src="http://www.coriolinus.net/wp-content/uploads/2010/04/4-weapon-hilighted.jpg" alt="" title="Weapon hilighted" width="152" height="288" class="alignnone size-full wp-image-3043" /></a><br />
<a href="http://www.coriolinus.net/wp-content/uploads/2010/04/5-another-man-with-weapon.jpg"><img src="http://www.coriolinus.net/wp-content/uploads/2010/04/5-another-man-with-weapon.jpg" alt="" title="Another man with weapon" width="640" height="400" class="alignnone size-full wp-image-3044" /></a><br />
<a href="http://www.coriolinus.net/wp-content/uploads/2010/04/6-other-weapon-hilighted.jpg"><img src="http://www.coriolinus.net/wp-content/uploads/2010/04/6-other-weapon-hilighted.jpg" alt="" title="Other weapon hilighted" width="245" height="321" class="alignnone size-full wp-image-3045" /></a></p>
<p>After identifying further members of the group, the Apaches requested and received permission to engage. Only after receiving permission did they first fire weapons. Once they had downed all targets, they stopped firing. They did not fire on the wounded. When a van arrived to evacuate the targets, they requested and received permission to engage. Only then did they disable the van. </p>
<p>Wikileaks is consistently referring to these men as &#8216;civilians.&#8217; They may not have been uniformed military personnel, but they were definitely combatants; they may not have been currently actively engaged in a firefight, but there had been small arms fire from that area since before dawn that day. The mission of both the Apache element and the ground forces was to eliminate any insurgents and/or weapons caches from the area. </p>
<p>After the fact, it was discovered that two of the people killed were in fact Reuters employees, and that in the van were two children injured by the attack. Coverage of the video has <a href="http://www.nytimes.com/2010/04/06/world/middleeast/06baghdad.html?hp">focused on this</a>. It&#8217;s tragic, but the newspeople were in the company of armed insurgents and appeared to be part of that group. As for the children, they were simply not detectable from the Apache. </p>
<p>It&#8217;s worth looking at the <a href="http://www2.centcom.mil/sites/foia/rr/CENTCOM Regulation CCR 25210/Death of Reuters Journalists/6--2nd Brigade Combat Team 15-6 Investigation.pdf">official report</a>. (<a href="http://www.coriolinus.net/wp-content/uploads/2010/04/6--2nd%20Brigade%20Combat%20Team%2015-6%20Investigation.pdf">Local Cache</a>) The results findings begin on page 11 of the PDF. The report contains necessary background information, such as the fact that the infantry less than 200 yards away had been receiving small-arms fire all morning. </p>
<p>There are plenty of people out there calling this a <a href="http://andrewsullivan.theatlantic.com/the_daily_dish/2010/04/the-lies-of-the-pentagon.html">war crime</a>, <a href="http://www.collateralmurder.com/">murder</a>, and worse. That is simply not the case. There are people out there who recognize this (<a href="http://www.washingtonpost.com/wp-dyn/content/article/2010/04/06/AR2010040601368_5.html?hpid=topnews&#038;sid=ST2010040601423">1</a>, <a href="http://www.economist.com/blogs/democracyinamerica/2010/04/fog_war">2</a>, <a href="http://gawker.com/5510094/wikileaks-video-demonstrates-conclusively-that-innocent-people-get-killed-in-wars">3</a>), but they are too few. </p>
<p>War is a terrible thing, but this was not a crime. This was professional pilots reacting appropriately to a hostile situation. I feel sympathy for the noncombatants in the group, but they brought it upon themselves. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.coriolinus.net/2010/04/06/the-apache-video/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Secure Flight</title>
		<link>http://www.coriolinus.net/2009/11/13/secure-flight/</link>
		<comments>http://www.coriolinus.net/2009/11/13/secure-flight/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 19:33:18 +0000</pubDate>
		<dc:creator>coriolinus</dc:creator>
				<category><![CDATA[opinion]]></category>
		<category><![CDATA[Air safety]]></category>
		<category><![CDATA[airline]]></category>
		<category><![CDATA[airline ticket purchasing system]]></category>
		<category><![CDATA[airline tickets]]></category>
		<category><![CDATA[Counter-terrorism]]></category>
		<category><![CDATA[Crime prevention]]></category>
		<category><![CDATA[Korea]]></category>
		<category><![CDATA[per-airline basis]]></category>
		<category><![CDATA[Personal identification]]></category>
		<category><![CDATA[Secure Flight]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Transportation Security Administration]]></category>
		<category><![CDATA[United States]]></category>

		<guid isPermaLink="false">http://www.coriolinus.net/?p=2892</guid>
		<description><![CDATA[My first contact with the program triggered all my phishing alerts: an unexpected email purporting to be from a trusted source asked for personal information. I&#8217;d have rejected it out of hand, but I do expect to fly as a passenger on commercial air soon and I&#8217;d rather not be turned back at the gate [...]]]></description>
			<content:encoded><![CDATA[<p>My first contact with the program triggered all my phishing alerts: an unexpected email purporting to be from a trusted source asked for personal information. I&#8217;d have rejected it out of hand, but I do expect to fly as a passenger on commercial air soon and I&#8217;d rather not be turned back at the gate in case it turned out to be real.</p>
<p>It is. Enter Secure Flight, the latest waste of time from the ever-useless TSA. Conceptually, it&#8217;s at least not counterproductive: they want to make the no-fly and extra screening watchlists more selective, by accounting for age and gender as well as name. However, they remain true to form by implementing the idea terribly. </p>
<p>Here&#8217;s the idea: every traveler must submit their full name, their date of birth, and their gender when purchasing a ticket. The airline collates a list of these and submits it to the TSA, where it is compared to the watchlists. </p>
<p>Here are the problems. First, no airline ticket purchasing system is designed to collect all of this information. That could be fixed, but the TSA is rolling out the program slowly on a per-airline basis with no advance notice or public oversight, requiring each of them to send these scammy-looking emails after the fact of purchase to collect this information without which the ticket becomes void. </p>
<p>Second, the filtering is done by computer, so it requires the traveler&#8217;s exact name. The problem here is that few if any people write their name exactly the same way on every document. I buy airline tickets using my first and last name. Some of my identification documents have my full middle name, some include just an initial. Sometimes, as in my upcoming flight, I won&#8217;t have any formal identification documents at all, just military leave paperwork. (Fun fact: I&#8217;ve flown to and from Korea three times so far with nothing more than an 8.5&#215;11&#8243; sheet of paper with a form and some scribbled signatures on it. Mine is authentic. The TSA has never actually verified that it was.) Plenty of people have more than three names. Designing the system such that it can be defeated by leaving out an initial renders it nearly useless.</p>
<p>Finally, if you&#8217;ve got my name, gender, and birth date, you&#8217;re halfway to stealing my identity. I am not comfortable surrendering this information to an organization that has reliably provided security theatre at the expense of actual security. To do much with a stolen identity, you also need at least part of a social security number; I suspect that anyone in a position to misuse the passenger information collected through this program will also have access to resources which can provide that.</p>
<p>Will I submit, and provide the TSA with everything it demands? Yes. Commercial flight is still the only option both fast enough to provide international travel within my leave time and cheap enough to be affordable. However, every time I fly within the US, I am more and more disinclined to ever repeat the experience.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coriolinus.net/2009/11/13/secure-flight/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

