{"id":1391,"date":"2005-03-11T00:00:00","date_gmt":"2005-03-11T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/03\/11\/f-secure-takes-on-hidden-malicious-code\/"},"modified":"2021-12-30T11:39:17","modified_gmt":"2021-12-30T11:39:17","slug":"f-secure-takes-on-hidden-malicious-code","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/03\/11\/f-secure-takes-on-hidden-malicious-code\/","title":{"rendered":"F-Secure Takes On Hidden Malicious Code"},"content":{"rendered":"<p>Finnish security firm F-Secure debuted a scanner for &#8220;rootkits,&#8221; software used by some hackers to hide their malicious code, and posted a free beta of the tool to its Web site.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Traditionally, &#8220;rootkit&#8221; referred to software that modified the operating system or environment so that an intruder could gain complete access (root access) to a system or network while remaining undetected.<\/p>\n<p>&#8220;The actual threat is still small compared to the potential,&#8221; admitted F-Secure in an e-mail, but that potential threat is enough, the company believed, to justify releasing F-Secure BlackLight.<\/p>\n<p>The new program scans the computer &#8212; it works on Windows 2000, Windows XP, and Windows Server 2003 &#8212; and reports on objects that are very likely rootkits or files hidden by a rootkit.<\/p>\n<p>http:\/\/www.techweb.com\/wire\/security\/159401468<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1391","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1391","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=1391"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1391\/revisions"}],"predecessor-version":[{"id":3878,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1391\/revisions\/3878"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1391"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1391"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1391"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}