<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Securing Your Infrastructure : Security virus imaging build workstation</title><link>http://blogs.technet.com/infrastructure_security/archive/tags/Security+virus+imaging+build+workstation/default.aspx</link><description>Tags: Security virus imaging build workstation</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Researchers Raise Alarm Over New Iteration of Coreflood Botnet - Desktop Security News Analysis - Dark Reading</title><link>http://blogs.technet.com/infrastructure_security/archive/2008/08/14/researchers-raise-alarm-over-new-iteration-of-coreflood-botnet-desktop-security-news-analysis-dark-reading.aspx</link><pubDate>Thu, 14 Aug 2008 19:24:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3105867</guid><dc:creator>chrisr</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/infrastructure_security/comments/3105867.aspx</comments><wfw:commentRss>http://blogs.technet.com/infrastructure_security/commentrss.aspx?PostID=3105867</wfw:commentRss><description>&lt;BLOCKQUOTE cite=http://www.darkreading.com/document.asp?doc_id=159874&amp;amp;WT.svl=news1_4&gt;&lt;/BLOCKQUOTE&gt;
&lt;P class=citation&gt;&lt;CITE cite=http://www.darkreading.com/document.asp?doc_id=159874&amp;amp;WT.svl=news1_4&gt;&lt;A href="http://www.darkreading.com/document.asp?doc_id=159874&amp;amp;WT.svl=news1_4" mce_href="http://www.darkreading.com/document.asp?doc_id=159874&amp;amp;WT.svl=news1_4"&gt;Researchers Raise Alarm Over New Iteration of Coreflood Botnet - Desktop Security News Analysis - Dark Reading&lt;/A&gt;&lt;/CITE&gt;.&lt;/P&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This recent article from the Dark Reading web site talks about the Coreflood Trojan horse virus which steals passwords.&amp;nbsp; The major concern of this virus is the ability of this virus to steal accounts and passwords from the infected machine and transfer those accounts to the hackers.&amp;nbsp; While signature based virus detection programs can detect and remove the virus, it is too late since the program has done its damage.&amp;nbsp; The prediction is that this botnet will become a favorite among hackers to steal passwords and then use those passwords to carry out attacks on enterprises. The problem in mind is how to protect against such an attack.&amp;nbsp; The first is pretty much common since which is to always have AV protection and the latest signature file.&amp;nbsp; We will not&amp;nbsp;go into this area since this pretty much common practice.&amp;nbsp; The second area and perhaps more difficult to address is to have a process of bringing new systems into the environment.&lt;/P&gt;
&lt;P&gt;So here is the problem.&amp;nbsp; You image a new system with an image that was create a couple of months ago.&amp;nbsp;&amp;nbsp;The image has A/V protection but the signature file is a couple of months old.&amp;nbsp; The system imaging goes fine but shortly after initial boot to the network, the system gets attacked by a virus.&amp;nbsp; The problem here is that the system does not have&amp;nbsp;a current signature file and the virus was not captured by the heuristics technology built into most A/V products.&amp;nbsp; Now you are stuck with how to clean the system.&amp;nbsp; So how do you avoid this type of problem in the first place.&amp;nbsp; I have defined three ways to avoid this potential problem.&amp;nbsp; These are in the imaging process, using a safe network and Network Access Protection (NAP).&lt;/P&gt;
&lt;P&gt;First lets start off with a solution that could be implemented pretty easy today and does help reduce the exposure time.&amp;nbsp; As part of the imaging process add a step in the process that downloads the latest signature file from a known location.&amp;nbsp; One way to implement this is simply to have a script that kicks off the signature update process with the A/V client.&amp;nbsp; To do this the client will need access to the network which still leaves it open to attacks.&amp;nbsp; Another way to implement this process is to store the latest signature file on a USB device so the signature can be updated before the client attaches to the network.&amp;nbsp; By using either of these two methods, you will either reduce or eliminate the exposure time on the network&lt;/P&gt;
&lt;P&gt;Another way to attack this problem is to build a safe network.&amp;nbsp; As safe network is a network that had a limited number of clients with no Internet or corpnet connectivity.&amp;nbsp; The client is built on this safe network and the signature file is updated before the client is allowed to connect to the corpnet.&amp;nbsp; This may require a change in your build process especially if a re-imaging process is part of the part of the problem resolution process.&amp;nbsp; In this case, the end user may have to bring his system to a help desk location with a safe network connection.&lt;/P&gt;
&lt;P&gt;The third way to address this problem is to leverage NAP and quarantine the client to a restricted network until the signature file is updated.&amp;nbsp; You will need to use a NAP implementation that uses the network devices and not a simple DHCP solution.&amp;nbsp; You will want a separate network to protect the client.&amp;nbsp; In the quarantine environment, you provide all the necessary systems to build a system and update the system with the latest signature files and security updates.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;Using one of these three ways (and there are probably others) you can start with a clean protected system and reduce the number of infections due to unprotected systems.&amp;nbsp; Carefully look at your a build process and identify ways of reduce the exposure time to attacks.&lt;/P&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3105867" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/infrastructure_security/archive/tags/Security+virus+imaging+build+workstation/default.aspx">Security virus imaging build workstation</category></item></channel></rss>