{"id":1613,"date":"2013-02-25T00:00:00","date_gmt":"2013-02-25T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2013\/02\/25\/next-generation-threat-protection-from-fireeye\/"},"modified":"2021-12-30T11:39:42","modified_gmt":"2021-12-30T11:39:42","slug":"next-generation-threat-protection-from-fireeye","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2013\/02\/25\/next-generation-threat-protection-from-fireeye\/","title":{"rendered":"Next-Generation Threat Protection From FireEye"},"content":{"rendered":"<p>FireEye\u00ae, Inc., the leader in stopping today\u2019s new breed of cyber attacks, today announced its threat protection platform designed to help enterprises deploy new security models to counter modern cyber attacks.The FireEye platform creates a cross-enterprise threat protection fabric using a next-generation threat detection engine, dynamic threat intelligence, and interoperability with a broad ecosystem of more than two dozen technology alliance partners to secure all major threat vectors and enable rapid detection, validation, and response to cyber attacks.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Multi-Vector Virtual Execution\u2122 (MVX) Engine \u2013 The MVX engine is designed to capture and confirm today\u2019s cyber attacks by detonating Web objects, files, suspicious attachments, and mobile applications within instrumented virtual environments.   It is the leading signature-less technology that can be used across threat vectors to automate the discovery and forensic analysis of malicious code resulting in multi-vector dynamic threat intelligence on attacks specific to an organization. <\/p>\n<p>By exchanging anonymized threat intelligence through the DTI cloud, participants gain contextual visibility of global attacks and can strengthen their collective security with the latest protections and neutralize attacks before they cause catastrophic damage.<\/p>\n<p>Partner Interoperability via APIs and Standards-based Threat Intelligence Metadata \u2013 Partner integrations utilize the FireEye APIs to address the network visibility, endpoint validation, and enforcement options needed by today\u2019s organizations.   In addition, FireEye will be publishing a standards-based threat intelligence metadata exchange format that enables FireEye and third-party security solutions to interoperate and automate key cyber security workflows. <\/p>\n<p>\u201cDynamic threat intelligence is critical to combating advanced threats from adversaries that may already be inside your network,\u201d said Mark Seward, senior director of security and compliance at Splunk Inc. <\/p>\n<p>\u201cFireEye is the security platform organizations can rely upon for protection against today\u2019s new breed of cyber attacks,\u201d said David DeWalt, FireEye chairman and CEO.   \u201cWe have enabled flexible options so customers can integrate our dynamic threat intelligence into their existing security infrastructure to automate the threat response and rapidly neutralize today\u2019s cyber attacks.\u201d<\/p>\n<p>Link: http:\/\/www.webhostmagazine.com\/2013\/02\/next-generation-threat-protection-from-fireeye\/<\/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-1613","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\/1613","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=1613"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1613\/revisions"}],"predecessor-version":[{"id":4100,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1613\/revisions\/4100"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1613"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1613"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1613"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}