{"id":4229,"date":"2015-06-12T15:42:23","date_gmt":"2015-06-12T21:42:23","guid":{"rendered":"http:\/\/allidm.com\/blog\/?p=4229"},"modified":"2015-06-12T15:42:23","modified_gmt":"2015-06-12T21:42:23","slug":"privileged-accounts-the-new-espionage-asset","status":"publish","type":"post","link":"https:\/\/allidm.com\/blog\/privileged-accounts-the-new-espionage-asset\/","title":{"rendered":"Privileged Accounts \u2013 the New Espionage \u2018Asset&#8217;"},"content":{"rendered":"<h2>Privileged Accounts \u2013 the New Espionage \u2018Asset&#8217;<\/h2>\n<p>Discussions about the breach and infiltration of Kaspersky\u2019s network continue to reinforce the emergence of dangerous attack patterns that are leaving no one out of attackers\u2019 sights \u2013 not even a security company.<\/p>\n<p>As we know, attribution of an attack is a difficult part of deconstructing a breach \u2013 we can see the signatures in malware, see what networks the attackers used to support the attack, but ultimately, we\u2019re almost never 100 percent sure of attribution.<\/p>\n<p>Ultimately, the question of \u201cwho\u201d is less important than the \u201chow.\u201d<\/p>\n<p>The motivation for the attack on Kaspersky appears to be pure espionage activity. According to sources, the malware used to execute the attack was an updated version of Duqu, which features code directly derived from Stuxnet, and was allegedly used to spy on Iran\u2019s trade relationships and efforts to develop nuclear material.<\/p>\n<p>Read more at &#8211; <a href=\"http:\/\/www.cyberark.com\/blog\/privileged-accounts-the-new-espionage-asset\/\" target=\"_blank\">Privileged Accounts \u2013 the New Espionage \u2018Asset&#8217;<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Privileged Accounts \u2013 the New Espionage \u2018Asset&#8217; Discussions about the breach and infiltration of Kaspersky\u2019s network continue to reinforce the emergence of dangerous attack patterns that are leaving no one out of attackers\u2019 sights \u2013 not even a security company. As we know, attribution of an attack is a difficult part of deconstructing a breach [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[88],"tags":[1273,750,1345],"class_list":["post-4229","post","type-post","status-publish","format-standard","hentry","category-identity-space","tag-iam-cyberark","tag-iam-privileged","tag-iam-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p25vfy-16d","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/allidm.com\/blog\/wp-json\/wp\/v2\/posts\/4229","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/allidm.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/allidm.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/allidm.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/allidm.com\/blog\/wp-json\/wp\/v2\/comments?post=4229"}],"version-history":[{"count":1,"href":"https:\/\/allidm.com\/blog\/wp-json\/wp\/v2\/posts\/4229\/revisions"}],"predecessor-version":[{"id":4230,"href":"https:\/\/allidm.com\/blog\/wp-json\/wp\/v2\/posts\/4229\/revisions\/4230"}],"wp:attachment":[{"href":"https:\/\/allidm.com\/blog\/wp-json\/wp\/v2\/media?parent=4229"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/allidm.com\/blog\/wp-json\/wp\/v2\/categories?post=4229"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/allidm.com\/blog\/wp-json\/wp\/v2\/tags?post=4229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}