<?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"
	>

<channel>
	<title>UW Computer Security Research and Course Blog</title>
	<atom:link href="http://cubist.cs.washington.edu/Security/feed/" rel="self" type="application/rss+xml" />
	<link>http://cubist.cs.washington.edu/Security</link>
	<description></description>
	<pubDate>Mon, 26 May 2008 15:06:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<item>
		<title>Pacemaker and Implantable Defibrillator Security Paper at Oakland</title>
		<link>http://cubist.cs.washington.edu/Security/2008/05/26/pacemaker-and-implantable-defibrillator-paper-at-oakland/</link>
		<comments>http://cubist.cs.washington.edu/Security/2008/05/26/pacemaker-and-implantable-defibrillator-paper-at-oakland/#comments</comments>
		<pubDate>Mon, 26 May 2008 14:54:55 +0000</pubDate>
		<dc:creator>Tadayoshi Kohno</dc:creator>
		
		<category><![CDATA[Announcements]]></category>

		<category><![CDATA[Current Events]]></category>

		<category><![CDATA[Research]]></category>

		<category><![CDATA[Security Reviews]]></category>

		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/?p=232</guid>
		<description><![CDATA[University of Washington CSE PhD student Dan Halperin et al.&#8217;s paper on the security and privacy for pacemakers and implantable defibrillators just received the Best Paper Award at the annual IEEE Symposium on Security and Privacy (a.k.a. the &#8220;Oakland&#8221; conference).
Dan and the rest of the team from UW, UMass Amherst, and Harvard Medical School found that an [...]]]></description>
			<content:encoded><![CDATA[<p>University of Washington CSE PhD student <a href="http://www.cs.washington.edu/homes/dhalperi/">Dan Halperin</a> <em>et al.</em>&#8217;s paper on the security and privacy for pacemakers and implantable defibrillators just received the Best Paper Award at the annual <a href="http://www.ieee-security.org/TC/SP2008/oakland08.html">IEEE Symposium on Security and Privacy</a> (a.k.a. the &#8220;Oakland&#8221; conference).</p>
<p>Dan and the rest of the team from UW, UMass Amherst, and Harvard Medical School found that an implantable cardioverter defibrillator can leak private information and can allow unauthorized parties to modify settings that control, among other things, shock therapies.  </p>
<p>You can read Dan&#8217;s <a href="http://www.secure-medicine.org/icd-study/icd-study.pdf">full paper</a> and the <a href="http://www.secure-medicine.org/icd-study/icd-faq.html">FAQ</a>, as well as his <a href="http://www.secure-medicine.org/PervasiveIMDSecurity.pdf">earlier work</a> on the topic of medical device security.  You can also read summaries of Dan&#8217;s work in <a href="http://www.nytimes.com/2008/03/12/business/12heart-web.html?_r=1&amp;oref=slogin">The New York Times</a>, the <a href="http://online.wsj.com/article/SB120528705417629357.html">Wall Street Journal</a>, <a href="http://www.reuters.com/article/rbssHealthcareNews/idUSN1163065520080312">Reuters</a>, and the <a href="http://www.usatoday.com/tech/news/computersecurity/hacking/2008-03-12-defribrillator-hack_N.htm">Associated Press</a>.  Bruce Schneier also provides excellent <a href="http://www.schneier.com/blog/archives/2008/03/hacking_medical_1.html">commentary</a>.</p>
<p>Congratulations Dan!</p>
]]></content:encoded>
			<wfw:commentRss>http://cubist.cs.washington.edu/Security/2008/05/26/pacemaker-and-implantable-defibrillator-paper-at-oakland/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Phalanx attains Slashdot fame!</title>
		<link>http://cubist.cs.washington.edu/Security/2008/04/22/phalanx-attains-slashdot-fame/</link>
		<comments>http://cubist.cs.washington.edu/Security/2008/04/22/phalanx-attains-slashdot-fame/#comments</comments>
		<pubDate>Tue, 22 Apr 2008 21:40:05 +0000</pubDate>
		<dc:creator>alpers</dc:creator>
		
		<category><![CDATA[Current Events]]></category>

		<category><![CDATA[Integrity]]></category>

		<category><![CDATA[botnet]]></category>

		<category><![CDATA[Phalanx]]></category>

		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/04/22/phalanx-attains-slashdot-fame/</guid>
		<description><![CDATA[I&#8217;m not sure if many people read this blog, but I recently noticed that the UW project Phalanx (slides, paper, and poster available from Colin Dixon&#8217;s site, recently featured on Slashdot) brought up the idea of countering botnets by setting up neutral (&#8217;white-hat&#8217; was tossed around in the /. comments) botnets to negate the adverse [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m not sure if many people read this blog, but I recently noticed that the UW project <em>Phalanx</em> (slides, paper, and poster available from <a href="http://www.cs.washington.edu/homes/ckd/" title="Colin Dixon">Colin Dixon&#8217;s site</a>, <a href="http://it.slashdot.org/it/08/04/22/1830205.shtml" title=" Recruiting Friendly Botnets To Counter Bad Botnets">recently featured on Slashdot</a>) brought up the idea of countering botnets by setting up neutral (&#8217;white-hat&#8217; was tossed around in the /. comments) botnets to negate the adverse effects.</p>
<p>Any thoughts on this?  It&#8217;s a curiously fun conceptualization, but could this potentially be just digging a bigger grave for the internet?</p>
]]></content:encoded>
			<wfw:commentRss>http://cubist.cs.washington.edu/Security/2008/04/22/phalanx-attains-slashdot-fame/feed/</wfw:commentRss>
		</item>
		<item>
		<title>In-Flight Web Page Modifications</title>
		<link>http://cubist.cs.washington.edu/Security/2008/04/20/in-flight-web-page-modifications/</link>
		<comments>http://cubist.cs.washington.edu/Security/2008/04/20/in-flight-web-page-modifications/#comments</comments>
		<pubDate>Mon, 21 Apr 2008 01:29:32 +0000</pubDate>
		<dc:creator>creis</dc:creator>
		
		<category><![CDATA[Current Events]]></category>

		<category><![CDATA[Integrity]]></category>

		<category><![CDATA[Research]]></category>

		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/04/20/in-flight-web-page-modifications/</guid>
		<description><![CDATA[Our research group (Charlie Reis, Yoshi Kohno, and Steve Gribble from UW CSE, and Nick Weaver from ICSI) has just presented a measurement study showing that many users are receiving web pages that have been modified in-flight.  The pages are changed between the web server and the user&#8217;s browser, either by ISPs injecting advertisements, enterprise [...]]]></description>
			<content:encoded><![CDATA[<p>Our research group (Charlie Reis, Yoshi Kohno, and Steve Gribble from UW CSE, and Nick Weaver from ICSI) has just presented a measurement study showing that many users are receiving web pages that have been modified in-flight.  The pages are changed between the web server and the user&#8217;s browser, either by ISPs injecting advertisements, enterprise firewalls injecting script code, or client-side proxies that block popups and ads.  These changes are often unwanted by either publishers or users, and they can also be dangerous: we found that several types of changes introduced bugs and security vulnerabilities into otherwise safe and functional pages.</p>
<p>To study this, we measured how often our own web page, <a href="http://vancouver.cs.washington.edu">http://vancouver.cs.washington.edu</a>, was modified when users visited it.  A piece of JavaScript code that we call a &#8220;web tripwire&#8221; detected such modifications, allowing us to record the change and notify the user.  Our study found that about 1% of the 50,000 visitors to our page received a modified version.  While 70% of these changes were caused by client-side proxies, we did see many changes caused by ISPs and firewalls as well.</p>
<p>For more information on our study and our results, you can read our analysis at <a href="http://www.cs.washington.edu/research/security/web-tripwire.html">Detecting In-Flight Page Changes with Web Tripwires</a>, as well as our recent <a href="http://www.cs.washington.edu/research/security/web-tripwire/nsdi-2008.pdf">NSDI 2008 paper</a> (PDF).  Our results have also been covered recently in the news media <a href="http://www.networkworld.com/news/2008/041608-isps-meddled-with-their-customers.html">here</a>, <a href="http://arstechnica.com/news.ars/post/20080416-research-1-3-percent-of-web-pages-altered-in-transit.html">here</a>, and <a href="http://yro.slashdot.org/article.pl?sid=08/04/18/0118256">here</a>.</p>
<p>If you would like to add a web tripwire to your own page, we have an <a href="http://www.cs.washington.edu/research/security/web-tripwire.html#toolkit">open source toolkit</a> that you can download and host on your web server.  We also have a <a href="http://www.cs.washington.edu/research/security/web-tripwire.html#service">web tripwire service</a> that is hosted by our server, which you can add to your page with a single line of JavaScript code.</p>
]]></content:encoded>
			<wfw:commentRss>http://cubist.cs.washington.edu/Security/2008/04/20/in-flight-web-page-modifications/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Happy Spring Break!</title>
		<link>http://cubist.cs.washington.edu/Security/2008/03/25/happy-spring-break/</link>
		<comments>http://cubist.cs.washington.edu/Security/2008/03/25/happy-spring-break/#comments</comments>
		<pubDate>Tue, 25 Mar 2008 17:58:14 +0000</pubDate>
		<dc:creator>Tadayoshi Kohno</dc:creator>
		
		<category><![CDATA[Announcements]]></category>

		<category><![CDATA[Security Reviews]]></category>

		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/03/25/happy-spring-break/</guid>
		<description><![CDATA[Have a great spring break everyone!
To readers of this blog:  Please expect low activity for a while. The University of Washington is on the quarter system, and our quarter just ended.  Everyone in the class is, of course, encouraged to still contribute articles to this blog.  And we&#8217;ll continue using this blog [...]]]></description>
			<content:encoded><![CDATA[<p>Have a great spring break everyone!</p>
<p>To readers of this blog:  Please expect low activity for a while. The University of Washington is on the quarter system, and our quarter just ended.  Everyone in the class is, of course, encouraged to still contribute articles to this blog.  And we&#8217;ll continue using this blog (or more sophisticated forum environments) in future courses.  Stay tuned for more information <img src='http://cubist.cs.washington.edu/Security/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> .</p>
]]></content:encoded>
			<wfw:commentRss>http://cubist.cs.washington.edu/Security/2008/03/25/happy-spring-break/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Security Review: IMA</title>
		<link>http://cubist.cs.washington.edu/Security/2008/03/20/the-husky-union-building-is-the-center-of-life-on-campus-it-is-home-to-the-associated-students-of-the-university-of-washington-hundreds-of-student-clubs-and-organizations-the-university-bookstore/</link>
		<comments>http://cubist.cs.washington.edu/Security/2008/03/20/the-husky-union-building-is-the-center-of-life-on-campus-it-is-home-to-the-associated-students-of-the-university-of-washington-hundreds-of-student-clubs-and-organizations-the-university-bookstore/#comments</comments>
		<pubDate>Thu, 20 Mar 2008 20:09:08 +0000</pubDate>
		<dc:creator>patriw</dc:creator>
		
		<category><![CDATA[Miscellaneous]]></category>

		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/03/20/the-husky-union-building-is-the-center-of-life-on-campus-it-is-home-to-the-associated-students-of-the-university-of-washington-hundreds-of-student-clubs-and-organizations-the-university-bookstore/</guid>
		<description><![CDATA[The IMA is a rather public place where students, faculty, and spouses can take fitness classes, lift weights, or use an expansive cardio room.
The assests include fitness machines, sports equipement, and simply the space, which when occupied by a unwelcome visitor, makes it unusable to a valid ima-goer. In addition, there is wifi access, as [...]]]></description>
			<content:encoded><![CDATA[<p>The IMA is a rather public place where students, faculty, and spouses can take fitness classes, lift weights, or use an expansive cardio room.</p>
<p>The assests include fitness machines, sports equipement, and simply the space, which when occupied by a unwelcome visitor, makes it unusable to a valid ima-goer. In addition, there is wifi access, as well as internet ready terminals.<span id="more-228"></span>Adversaries might include, anyone who wants to take the equipement. Rival school members who want to somehow hinder our sports teams preperations, or even your average joe who wants to work out. We must not let random people get healthy! In addition, the IMA is one of very few places in seattle where regular pick up games of basketball can be found, and we must ensure that the general public doesn&#8217;t overwhelm the 10 courts that are provided. Luckly, the security has been sufficient to ensure that only 2 of these courts are ever in use at any given time.</p>
<p>The security that is currently in place includes students who guard a gated entrance. They swipe your card, which says whether your card was issued to someone who should have access to the ima, then the student may or may not due some visual authentication, comparing your face to the face on the card. However, as the gates are waist high, it probably wouldn&#8217;t be that hard to simply jump it. However, there are easier ways in. One must only know a valid name-student number combo to receive a one time pass into the IMA. While the form asks for more information, these are all that are ever required. In addition, at the same desk that handles the one time forms, one can also sign a guest in for a one time pass for seven dollars. Steep yes, but if you are looking to untracably enter the premise, asking a random person entering the building to let you be their guest isn&#8217;t a bad way to go. Then comes the best way in&#8230;locker room pins. One must only have a baby pin with a piece of paper taped on with a locker number to be instantly granted access, no questions asked. These are impossible to authenticate (or at least prohibitively difficult), and can be easily created without leaving your home for supplies. Bingo!</p>
<p>In conclusion, the IMA is wide open for access to anyone who really wants it. However, given that it is run by students who are almost always studying while working, it seems like the state has spoken about its commitment to IMA security. Access points such as the locker room pins exist because they are a convenience to the users, and very little harm can come from having unauthorized persons in the building. There is security on the premise that could respond, should someone try to run away with a collection of weights.  Which raises the question, given that it is a state run facility, and it already charges for parking, a virtual must for people not conveniently coming from the UW, why charge at all? The general public could certainly use an additional fitness center&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://cubist.cs.washington.edu/Security/2008/03/20/the-husky-union-building-is-the-center-of-life-on-campus-it-is-home-to-the-associated-students-of-the-university-of-washington-hundreds-of-student-clubs-and-organizations-the-university-bookstore/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Security Review:  Husky Union Building</title>
		<link>http://cubist.cs.washington.edu/Security/2008/03/18/security-review-husky-union-building/</link>
		<comments>http://cubist.cs.washington.edu/Security/2008/03/18/security-review-husky-union-building/#comments</comments>
		<pubDate>Tue, 18 Mar 2008 23:36:09 +0000</pubDate>
		<dc:creator>esoteric</dc:creator>
		
		<category><![CDATA[Miscellaneous]]></category>

		<category><![CDATA[Physical Security]]></category>

		<category><![CDATA[Security Reviews]]></category>

		<category><![CDATA[HUB]]></category>

		<category><![CDATA[Husky Union Building]]></category>

		<category><![CDATA[physical security]]></category>

		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/03/18/security-review-husky-union-building/</guid>
		<description><![CDATA[The Husky Union Building is the center of life on campus.  It is home to the Associated Students of the University of Washington, hundreds of student clubs and organizations, the university bookstore, food vendors, university employee payroll and accounting, information services, games area, campus-wide lost &#38; found, US Bank, bike shop, hair salon, newsstand, [...]]]></description>
			<content:encoded><![CDATA[<p>The Husky Union Building is the center of life on campus.  It is home to the Associated Students of the University of Washington, hundreds of student clubs and organizations, the university bookstore, food vendors, university employee payroll and accounting, information services, games area, campus-wide lost &amp; found, US Bank, bike shop, hair salon, newsstand, event services, and many more departments.</p>
<p><span id="more-227"></span></p>
<p>Needless to say, there are many assets to protect in such a large, public space.  Some of the more notable ones include the fully operational branch of US Bank, which resides on the ground floor.  Clearly there is a lot of money as well as private records stored in the bank that must be protected.  In addition, there is an accounting office on the third floor of the building that maintains records containing personal information about university employees and their jobs.  These records must be protected in order to prevent crimes such as identity theft or tampering with payroll documents.</p>
<p>There are many adversaries who might want to break into the HUB.  These include bank robbers looking to steal cash from the bank branch or from the multitude of ATMs in the building, identity thieves looking to steal private employee information, malicious employees looking to alter work records for profit, homeless people seeking a warm place to sleep, people attempting to steal items from the lost &amp; found, vandals, etc.</p>
<p>The Husky Union Building has many weaknesses.  First, it has many entrances and exits that must be monitored.  There are countless doors that must be manually locked and unlocked at the proper times, and if just one of them is overlooked, an adversary can gain access to most of the building.  This is analogous to having a lot of unfiltered ports open on a computer; the more potential entry points there are, the greater the risk.  In addition, there are many windows on the ground floor that are accessible from the outside.  This can be especially problematic during the summer, when people open their windows and sometimes forget to lock them when they leave.  Another weakness the building has is that it is a very public place where lots of people work, so it can be hard to identify someone who shouldn&#8217;t be there, even after hours.  The HUB doesn&#8217;t have a building-wide security system, and many staffmembers have keys to the building, so it&#8217;s not uncommon to see someone walking around inside, even late at night.</p>
<p>The HUB does have some defenses against adversaries.  Every night, there is a trusted student employee, called a Student Building Manager (SBM), who walks around and makes sure everything is in order.  The SBM is in the building as late as 12:30am on some nights, and has keys to every room in the building so he/she can check up on things.  The SBM has a radio, and can call the nearby UW Police at the first sign of trouble.  In addition, there are safes at various locations in the building that are used to store valuables, such as money and records.  These safes, which are already in locked rooms, are an example of a defense-in-depth approach that was chosen by the building administration.</p>
<p>Despite these defenses, the HUB is definitely still at risk.  The Student Building Managers, for example, keep their building keys on their personal key chains so that they can get in and out of the building after hours when they need to.  It would be trivial for an adversary to steal one of these keys from a student and use it to gain entry.  In addition, the system relies on trusting the SBMs, and although they are experienced staff who have shown responsibility and have perfect track records, they are still susceptible to malice and could do a lot of intentional harm.  In addition, one of these students could forget to lock a door properly and unintentionally allow someone to gain access.</p>
<p>In conclusion, the HUB is a large entity that cannot easily be protected.  There are rudimentary security measures in place to deter casual adversaries, but in truth it wouldn&#8217;t be too hard for an outsider to gain access.  The university should consider installing a more robust security system in the building, or at least set up some kind of surveillance.  It also wouldn&#8217;t hurt to have a security officer walking around on each floor, rather than one student employee who leaves at midnight.</p>
]]></content:encoded>
			<wfw:commentRss>http://cubist.cs.washington.edu/Security/2008/03/18/security-review-husky-union-building/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Security Review: Wireless Home Automation Systems</title>
		<link>http://cubist.cs.washington.edu/Security/2008/03/17/226/</link>
		<comments>http://cubist.cs.washington.edu/Security/2008/03/17/226/#comments</comments>
		<pubDate>Tue, 18 Mar 2008 06:57:31 +0000</pubDate>
		<dc:creator>chernyak</dc:creator>
		
		<category><![CDATA[Physical Security]]></category>

		<category><![CDATA[Privacy]]></category>

		<category><![CDATA[Security Reviews]]></category>

		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/03/17/226/</guid>
		<description><![CDATA[Summary:Home automation systems in general attempt to enable home owners to have a &#8220;smart&#8221; house. Instead of light switches you have integrated panels that control everything from your lights, to your shades, to your entertainment system, climate control, alarm system, motorized locks, etc. Some specific examples of such systems like those offered by Control4 use [...]]]></description>
			<content:encoded><![CDATA[<p>Summary:Home automation systems in general attempt to enable home owners to have a &#8220;smart&#8221; house. Instead of light switches you have integrated panels that control everything from your lights, to your shades, to your entertainment system, climate control, alarm system, motorized locks, etc. Some specific examples of such systems like those offered by Control4 use wireless communications between the panels and devices they control. Some also have integration with cell phone applications. One of the selling points for these systems is that they improve security.</p>
<p><span id="more-226"></span></p>
<p>Assets</p>
<p>- The security of your home.</p>
<p>- The proper and desired functionality of your home automation</p>
<p>Adversaries</p>
<p>- Any malicious individuals wanting to gain access to your home by exploiting home automation.</p>
<p>- Vandals or pranksters who wish to disrupt the functioning of your home automation system</p>
<p>Weaknesses:</p>
<p>- Information is communicated wirelessly from control panels in your home to the devices they control. These can be security cameras, motorized locks, an alarm system, or even something benign like climate control. As far as information is available, the communication is done over z-wave which is a publicly described protocol for appliance networking. This means that the devices in the home will be susceptible to outside interference and signals. (Z-wave uses something called &#8216;home codes&#8217; which is a 32 bit sig that all the devices are marked with to make sure they only communicate with devices with the same &#8216;home code.&#8217; However it is noted in the specification that an attacker could easily forge the home code and join the network of z-wave devices). Even if some sort of crypto is used on top, if it is not done properly it will be susceptible to replay, man in the middle, and all the other classic forms of attack.</p>
<p>- Furthermore, the cell phone application can take one of two forms. It is either a web application that a user with a data-enabled mobile device can use (and thus has to be considered for security as any web app would - except in this case alarm systems and security camera feeds are involved), or it is an application somehow attempting to authenticate via the use of cell phone. In the latter case, the only identifying information conceivable is that stored on the SIM card - but as we have already seen, we can clone these!</p>
<p>Defenses:</p>
<p>- Real security with good crypto MUST be used for appliance networks. Luckily this problem has been long solved in computer networks <img src='http://cubist.cs.washington.edu/Security/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>- I question the validity of making resources as sensitive as security camera feeds available via web applications that are visible on the internet - chances are there is a security flaw somewhere and an attacker can see in your house.</p>
<p>Risk Analysis:</p>
<p>I think the risks here are quite real. Individuals with such expensive integrated home automation systems probably have very nice houses, and these systems can in fact give potential adversaries more avenues for attack.</p>
<p>Conclusion:</p>
<p>I am not trying to say these systems are &#8220;bad.&#8221; I think the idea is extremely cool, but to boast about how they improve security seems strange when they have potentially only weakened it.</p>
]]></content:encoded>
			<wfw:commentRss>http://cubist.cs.washington.edu/Security/2008/03/17/226/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Ethics&#8230;?</title>
		<link>http://cubist.cs.washington.edu/Security/2008/03/17/ethics/</link>
		<comments>http://cubist.cs.washington.edu/Security/2008/03/17/ethics/#comments</comments>
		<pubDate>Tue, 18 Mar 2008 01:52:33 +0000</pubDate>
		<dc:creator>robert</dc:creator>
		
		<category><![CDATA[Ethics]]></category>

		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/03/17/ethics/</guid>
		<description><![CDATA[This blog post on freedom-to-tinker came up in my feed reader today: http://www.freedom-to-tinker.com/?p=1265
The post is an e-mail from a company that makes e-voting machines that is threatening legal action if their voting machine is analyzed and the results published.
What does everyone think of this?
]]></description>
			<content:encoded><![CDATA[<p>This blog post on freedom-to-tinker came up in my feed reader today: <a href="http://www.freedom-to-tinker.com/?p=1265">http://www.freedom-to-tinker.com/?p=1265</a></p>
<p>The post is an e-mail from a company that makes e-voting machines that is threatening legal action if their voting machine is analyzed and the results published.</p>
<p>What does everyone think of this?</p>
]]></content:encoded>
			<wfw:commentRss>http://cubist.cs.washington.edu/Security/2008/03/17/ethics/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Security Review: &#8220;Smart Guns&#8221;</title>
		<link>http://cubist.cs.washington.edu/Security/2008/03/16/security-review-smart-guns/</link>
		<comments>http://cubist.cs.washington.edu/Security/2008/03/16/security-review-smart-guns/#comments</comments>
		<pubDate>Mon, 17 Mar 2008 07:59:11 +0000</pubDate>
		<dc:creator>Trip Volpe</dc:creator>
		
		<category><![CDATA[Availability]]></category>

		<category><![CDATA[Physical Security]]></category>

		<category><![CDATA[Policy]]></category>

		<category><![CDATA[Security Reviews]]></category>

		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/03/16/security-review-smart-guns/</guid>
		<description><![CDATA[Overview
This is a security review of &#8220;Smart Guns,&#8221; a general class of locking/use prevention mechanisms for firearms that rely on biometrics or other authentication indicators (such as &#8220;smart&#8221; chips embedded in the gun and in rings or other tokens worn by the intended user) to identify a person who is authorized to use the firearm, [...]]]></description>
			<content:encoded><![CDATA[<h2>Overview</h2>
<p>This is a security review of &#8220;Smart Guns,&#8221; a general class of locking/use prevention mechanisms for firearms that rely on biometrics or other authentication indicators (such as &#8220;smart&#8221; chips embedded in the gun and in rings or other tokens worn by the intended user) to identify a person who is authorized to use the firearm, while preventing unauthorized persons from discharging the weapon. The Wikipedia <a href="http://en.wikipedia.org/wiki/Smart_Gun">article</a> has some further broad overview information regarding the subject.</p>
<h2><span id="more-223"></span>Assets</h2>
<ul>
<li>Accessibility. Ideally, one security goal is for the firearm to be capable of being used in short order by the authorized user.</li>
<li>Personal safety. The other security goal is that an unauthorized individual should not be able to use the gun to injure or kill the owner or any other person.</li>
</ul>
<h2>Adversaries</h2>
<ul>
<li>The most obvious potential adversary is a criminal intent on using someone else&#8217;s gun to do harm; e.g., a criminal struggling with a police officer or a burglar breaking into someone&#8217;s house.</li>
<li>Another &#8220;adversary&#8221; could be the small children of the owner of such a firearm; if a child somehow gains access to the firearm, the locking mechanism should be capable of preventing them from discharging the weapon and possibly killing or injuring themselves or others.</li>
</ul>
<h2>Possible Weaknesses</h2>
<ul>
<li>If the locking system requires a battery to operate, one major problem that could compromise one of the security assets is a dead battery. If the battery is dead and the gun cannot be unlocked, it is useless to its owner, whether that be a police officer in the line of duty, or a civilian trying to defend himself from an attacker.</li>
<li>If the system relies on biometrics to identify the owner (such as grip style, pulse, or other such indicators), a stressful situation (such as a shootout) might substantially change those indicators in the user, resulting in the owner being unable to use the firearm.</li>
<li>Further, if the owner of a firearm is killed or injured in a gunfight, a partner, family member, or other ally will be unable to use their weapon against the attackers.</li>
</ul>
<h2>Possible Defenses</h2>
<ul>
<li>To guard against the &#8220;dead battery&#8221; problem, one option is to design the lock so that the default (unpowered)  state is unlocked. This prevents the accessibility of the firearm from being compromised, but it also poses a major problem itself: when the battery dies, it is no longer protected against unauthorized use, and it might be possible for an adversary to damage or disable the battery, thus unlocking the firearm. A better solution might be to devise a system that does not require internal power, although this poses a significant technological challenge.</li>
<li>Situations where an ally might need to use another&#8217;s gun to continue a fight arise more often in law enforcement; agencies might be able to employ a system where all officers could be issued tokens (e.g., rings) that would grant access to use all of the department&#8217;s issued firearms.</li>
</ul>
<h2>Risks</h2>
<p>As with anything involving firearms, the risks are quite substantial:</p>
<ul>
<li>If the battery dies or another circumstance renders the gun unusable, the consequences could be quite dire, depending on the situation: if the user is practicing at the range, the result would be an annoying delay while the battery was replaced; if, on the other hand, the user is attempting to defend his or her life against an attacker, the result could easily be serious injury or death.</li>
<li>On the other side of the issue, if an unauthorized user gains access to a firearm that is not protected (e.g., the firearm was unprotected, or the battery has died and the mechanism defaults to unlocked), they could use it to kill or seriously injure the intended user or others, or in the case of a small child, themselves.</li>
</ul>
<h2>Conclusions</h2>
<p>While &#8220;Smart Gun&#8221; technology proposes to address a good security goal (namely, preventing a bad guy from turning someone&#8217;s gun against them), reliability is a major issue. In most of the eventualities when such a locking system becomes important, absolute reliability and speed of access are also critically important for the user. For this reason, many people do not consider the technology to be worthwhile at the present time. Ultimately, a better solution for most people is to employ other methods of keeping the firearm out of undesirable hands in the first place, rather than trying to defend against an adversary who already has physical access.</p>
]]></content:encoded>
			<wfw:commentRss>http://cubist.cs.washington.edu/Security/2008/03/16/security-review-smart-guns/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Microsoft, Yahoo, and Internet Breakage</title>
		<link>http://cubist.cs.washington.edu/Security/2008/03/16/microsoft-yahoo-and-internet-breakage/</link>
		<comments>http://cubist.cs.washington.edu/Security/2008/03/16/microsoft-yahoo-and-internet-breakage/#comments</comments>
		<pubDate>Mon, 17 Mar 2008 07:58:43 +0000</pubDate>
		<dc:creator>Justin McOmie</dc:creator>
		
		<category><![CDATA[Current Events]]></category>

		<category><![CDATA[Miscellaneous]]></category>

		<category><![CDATA[Satire]]></category>

		<category><![CDATA[untruthiness]]></category>

		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/03/16/microsoft-yahoo-and-internet-breakage/</guid>
		<description><![CDATA[In a recent interview with “Condé Nast Portfolio”, Google CEO Eric Schmidt warns us all that a Microsoft-Yahoo merger might “break the internet” due to the consolidation of web-mail, instant messaging, and other services that would follow as a result.  This relates to a still on the table 40+ billion dollar offer that Microsoft [...]]]></description>
			<content:encoded><![CDATA[<p>In a recent interview with “Condé Nast Portfolio”, Google CEO Eric Schmidt warns us all that a Microsoft-Yahoo merger might “break the internet” due to the consolidation of web-mail, instant messaging, and other services that would follow as a result.  This relates to a still on the table 40+ billion dollar offer that Microsoft has proposed to Yahoo.  While the deal is not cemented yet, representatives for the respective companies have reportedly had frequent rendezvous at Mayflower conference rooms to “feel things out” before big money exchanges hands.</p>
<p>The big issue at hand is the oncoming breaking of the Internet, which clearly has broad reaching implications, particularly for Google.  The search giant has bet its entire business model on the premise that the Internet be categorically unbroken, at least most of the time, and has a vested interest in ensuring the continued heartbeat of the web.  This is in contrast with Microsoft, which could deal with an Internet breakage without all that much worry for its bottom line.  This fact should alarm anyone with perceptive eyes; perhaps “breaking the Internet” is the first gunshot in a drawn out war of attrition Microsoft has planned.</p>
<p>According to Schmidt, Microsoft’s previous antitrust trial was about breaking interoperable open systems.  Thus, we should all be wondering what level of nefariousness currently runs through Microsoft’s veins that it would embark on a conquest to contort the consolidation of Yahoo’s web offerings in someway as to weaponize open systems into a torrent of Internet pain and disruptiveness.  One can only grimace at the proverbial ring of power Microsoft will be able to wield when it is able commit such acts as merging its MSN messenger userbase with that of the wildly popular Yahoo Messenger.</p>
<p>The Internet using public should assess the risk for Internet breakage and policy makers should react accordingly.   But we should also keep in mind that if a Microsoft Yahoo merger could break the Internet, smaller deals might lead to some sort of fractures or cracks in the Internet.  For example, Microsoft recently invested several hundred million dollars into Facebook, which caused observable tremors in the Internet’s various tubes.  Caveat emptor.</p>
<p>Source:  http://www.portfolio.com/executives/features/2008/03/14/Google-CEO-Eric-Schmidt-Interview</p>
]]></content:encoded>
			<wfw:commentRss>http://cubist.cs.washington.edu/Security/2008/03/16/microsoft-yahoo-and-internet-breakage/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
