{"id":2362,"date":"2005-02-17T00:00:00","date_gmt":"2005-02-17T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/02\/17\/rsa-microsoft-on-rootkits-be-afraid-be-very-afraid\/"},"modified":"2021-12-30T11:41:09","modified_gmt":"2021-12-30T11:41:09","slug":"rsa-microsoft-on-rootkits-be-afraid-be-very-afraid","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/02\/17\/rsa-microsoft-on-rootkits-be-afraid-be-very-afraid\/","title":{"rendered":"RSA: Microsoft on &#8216;rootkits&#8217;: Be afraid. Be very afraid."},"content":{"rendered":"<p>Microsoft security researchers are warning about a new generation of powerful system monitoring programs, or &#8220;rootkits,&#8221; that are almost impossible to detect using current security products and that could pose a serious risk to corporations and individuals.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The researchers Tuesday discussed the growing threat posed by kernel rootkits at a session at the RSA Security Conference in San Francisco.<\/p>\n<p>The malicious snooping programs are becoming more common and could soon be used to create a new generation of mass-distributed spyware and worms.<\/p>\n<p>With names like &#8220;Hacker Defender,&#8221; &#8220;FU&#8221; and &#8220;Vanquish,&#8221; the programs are the latest generation of remote system monitoring software that has been around for years, according to Mike Danseglio and Kurt Dillard, both of Microsoft&#8217;s Security Solutions Group.<\/p>\n<p>The programs are used by malicious hackers to control, attack or ferret information from systems on which the software has been installed and are typically installed on a machine without the owner&#8217;s knowledge, either by a virus or following a successful hack of the computer&#8217;s defenses, they said.<\/p>\n<p>Once installed, many rootkits simply run quietly in the background but can easily be spotted by looking for memory processes that are running on the infected system, monitoring outbound communications from the machine, or checking for newly installed programs.<\/p>\n<p>Rootkit authors are also making huge strides in their ability to hide their creations, said Danseglio.  The result is that typical signs that a program is running, such as an executable file name, a named process that uses some of the computer&#8217;s memory, or configuration settings in the operating system&#8217;s registry, are invisible to administrators and to detection tools, said Danseglio.<\/p>\n<p>One rootkit, called Hacker Defender, which was released about one year ago, even uses encryption to protect outbound communications and can piggyback on commonly used ports such as Transmission Control Protocol (TCP) port 135 to communicate with the outside world without interrupting other applications that communicate on that port, he said.<\/p>\n<p>The kernel rootkits are invisible to many detection tools, including anti-virus, host and network intrusion detection sensors (IDS) and anti-spyware products, the researchers said.<\/p>\n<p>One strategy to spot kernel rootkits is to use Windows PE, a stripped-down version of the Windows XP operating system that can be run from a CD-ROM, to boot a computer, then comparing the profile of the clean operating system to the infected system, according to Dillard and Danseglio.<\/p>\n<p>http:\/\/www.nwfusion.com\/news\/2005\/0217rsa-mic.html<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-2362","post","type-post","status-publish","format-standard","hentry","category-warnings"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2362","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=2362"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2362\/revisions"}],"predecessor-version":[{"id":4849,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2362\/revisions\/4849"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2362"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2362"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2362"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}