{"id":411,"date":"2013-05-13T00:00:00","date_gmt":"2013-05-13T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2013\/05\/13\/hbgary-announces-next-gen-responder-pro\/"},"modified":"2021-12-30T11:37:15","modified_gmt":"2021-12-30T11:37:15","slug":"hbgary-announces-next-gen-responder-pro","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2013\/05\/13\/hbgary-announces-next-gen-responder-pro\/","title":{"rendered":"HBGary Announces Next-Gen Responder\u2122 Pro"},"content":{"rendered":"<p>In a move to significantly close the gap between discovery and mitigation of targeted attacks, HBGary, a subsidiary of ManTech International Corporation, unveiled the next-generation version of Responder\u2122 Pro, the de facto industry standard in automated Windows\u00ae physical memory analysis. By leveraging Digital DNA\u2122 3.0, HBGary&#8217;s flagship technology, Responder\u2122 Pro 2.1 detects the latest rootkits, trojans, zero-days, and malware variants currently undetected by anti-virus, IOCs (indicators of compromise), and other signature-based solutions.<\/p>\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In a move to significantly close the gap between discovery and mitigation of targeted attacks, HBGary, a subsidiary of ManTech International Corporation, unveiled the next-generation version of Responder\u2122 Pro, the de facto industry standard in automated Windows\u00ae physical memory analysis. By leveraging Digital DNA\u2122 3.0, HBGary&#8217;s flagship technology, Responder\u2122 Pro&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-411","post","type-post","status-publish","format-standard","hentry","category-malware"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/411","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=411"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/411\/revisions"}],"predecessor-version":[{"id":2898,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/411\/revisions\/2898"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=411"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=411"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=411"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}