<?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>Lithik Systems &#187; autoplay</title>
	<atom:link href="http://www.lithik.com/tag/autoplay/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lithik.com</link>
	<description>Transforming businesses by bending technology to the will of our clients</description>
	<lastBuildDate>Thu, 26 Jan 2012 15:28:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Disabling the Windows AutoRun Feature</title>
		<link>http://www.lithik.com/2009/10/22/disabling-the-windows-autorun-feature/</link>
		<comments>http://www.lithik.com/2009/10/22/disabling-the-windows-autorun-feature/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 20:46:51 +0000</pubDate>
		<dc:creator>Karl Fox</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[auto-play]]></category>
		<category><![CDATA[auto-run]]></category>
		<category><![CDATA[autoplay]]></category>
		<category><![CDATA[autorun]]></category>
		<category><![CDATA[cd-rom]]></category>
		<category><![CDATA[cdrom]]></category>
		<category><![CDATA[disable]]></category>
		<category><![CDATA[disabling]]></category>
		<category><![CDATA[group policy]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[usb]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://www.lithik.com/?p=339</guid>
		<description><![CDATA[We often help organizations test how well their staff knows their security policy by performing social engineering tests.  In one, we drop hacked USB drives around the premises that notify our home server when inserted into a Windows computer.  Such tests are a lot of fun when they&#8217;re just tests, but when a real hacker [...]]]></description>
			<content:encoded><![CDATA[<p>We often help organizations test how well their staff knows their security policy by performing social engineering tests.  In one, we drop hacked USB drives around the premises that notify our home server when inserted into a Windows computer.  Such tests are a lot of fun when they&#8217;re just tests, but when a real hacker leaves such a tasty tidbit in your parking lot, you can bet it&#8217;s going to do a lot more mischief than phone home when an employee plugs it into one of your computers.</p>
<p>AutoRun and the companion feature AutoPlay are components of the Microsoft Windows operating system that dictate what actions the system takes when a drive is mounted.  The main purpose of AutoRun is to provide helpful actions and capabilities when removable media or network shares are mounted.  When such a device is mounted, the <code>autorun.inf</code> file from the media is parsed. This file specifies which commands the system should run. Many companies use this functionality to automatically start up their installers when a CD-ROM is inserted, but attackers can also use it to run data extraction sessions or automatic installations of malware.<br />
<span id="more-339"></span><br />
AutoRun and AutoPlay can be friendly features, but they are almost never necessary in an enterprise environment.  The security risk typically far outweighs any benefit.</p>
<p>All AutoRun/AutoPlay features are controlled by values stored in the Windows registry.  There are a number of ways to set these values, including</p>
<ul>
<li>Group Policy</li>
<li>Double-clicking a <code>.REG</code> file containing registry settings</li>
</ul>
<h2>Disabling AutoRun Using Group Policy</h2>
<p>If you think that Windows Group Policy would be the most convenient and thorough way to distribute such a policy, you&#8217;d be partly right.  The only gotcha is that a number of people report that it doesn&#8217;t always get every machine.  I&#8217;d recommend both belt and suspenders—use a GPO to catch future machines, but set each existing machine by hand to make sure none fall through the cracks today.</p>
<p>Before configuring Group Policy, you must ensure that one of the following updates has been applied to each of the machines you intend to configure.  Note that only one update applies to each machine.</p>
<ul>
<li>Update for Windows Server 2003 for Itanium-based Systems (KB967715)</li>
<li>Update for Windows Server 2003 x64 Edition (KB967715)</li>
<li>Update for Windows Server 2003 (KB967715)</li>
<li>Update for Windows XP x64 Edition (KB967715)</li>
<li>Update for Windows 2000 (KB967715)</li>
<li>Windows Vista-based and Windows Server 2008-based systems must have update 950582 (Security bulletin MS08-038) installed to take advantage of the registry key settings that disable AutoRun.</li>
</ul>
<p>This update will create a new registry entry, <code>HonorAutorunSetting</code>.  Without the update, <code>autorun.inf</code> gets read even with AutoRun disabled, but simply does not execute any AutoPlay commands inside.  This still allows attacks to be made using <code>autorun.inf</code>, and <code>HonorAutorunSetting</code> should be set to <code>1</code> to disable this. The default is <code>1</code> after the patch is applied.</p>
<p>To disable all AutoRun features in Windows Server 2003, Windows XP Professional and Windows 2000,</p>
<ul>
<li>Click <strong>Start</strong>, click <strong>Run</strong>, type <code>gpmc.msc</code> in the <strong>Open</strong> box, and then click <strong>OK</strong>.  If you don&#8217;t yet have <a href="http://www.microsoft.com/DownLoads/details.aspx?FamilyID=0a6d4c24-8cbd-4b35-9272-dd3cbfc81887&amp;displaylang=en">GPMC</a> installed, do so first.</li>
<li>Choose an appropriate Group Policy Object in the left pane (or create a new one and attach it in the appropriate place), right-click it, and select <strong>Edit</strong>.</li>
<li>Under <strong>Computer Configuration</strong>, expand <strong>Administrative Templates</strong>, and then click <strong>System</strong>.</li>
<li>In the <strong>Settings</strong> pane, right-click <strong>Turn off Autoplay</strong>, and then click <strong>Properties</strong>. Note: In Windows 2000, the policy setting is named <strong>Disable Autoplay</strong>.</li>
<li>Click <strong>Enabled</strong>, and then select <strong>All drives</strong> in the <strong>Turn off Autoplay</strong> box to disable Autorun on all drives.</li>
<li>Click <strong>OK</strong> to close the <strong>Turn off Autoplay Properties</strong> dialog box.</li>
</ul>
<p>Windows will propagate the group policy settings to all machines controlled by the edited Group Policy Object.  Once the settings have been applied to a computer, it must be rebooted before the changes take effect.</p>
<h2>Disabling AutoRun Using a Registry File</h2>
<p>Create a file called <code>autorun.reg</code> containing the following lines.  Some of the lines here are long; make sure you don&#8217;t break them in the middle somewhere when you cut and paste the text below.</p>
<blockquote><p><code>Windows Registry Editor Version 5.00</code></p>
<p><code>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\Autorun.inf]<br />
@="@SYS:DoesNotExist"</code></p>
<p><code>[-HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2]</code></p>
<p><code>[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]<br />
"HonorAutorunSetting"=dword:00000001<br />
"NoDriveAutoRun"=dword:03ffffff<br />
"NoDriveTypeAutoRun"=dword:000000ff</code>
</p></blockquote>
<p>On each computer to be updated, browse to this file and double-click it.  The computer must be rebooted for the changes to take effect.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.lithik.com/2009/10/22/disabling-the-windows-autorun-feature/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

