{"id":1535,"date":"2007-05-12T00:00:00","date_gmt":"2007-05-12T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/05\/12\/rsa-envision-boasts-ha-features-and-integration-with-emc-storage\/"},"modified":"2021-12-30T11:39:33","modified_gmt":"2021-12-30T11:39:33","slug":"rsa-envision-boasts-ha-features-and-integration-with-emc-storage","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2007\/05\/12\/rsa-envision-boasts-ha-features-and-integration-with-emc-storage\/","title":{"rendered":"RSA enVision boasts HA features and integration with EMC storage."},"content":{"rendered":"<p>Formerly from Network Intelligence (acquired by RSA parent company EMC in September of 2006), RSA enVision is a centralized, appliance-based offering that facilitates both the collection\/storage, and analysis of event data from disparate security and network devices.  Based on a locked-down Windows OS, the enVision appliance is managed remotely (one or many appliance can be so managed) with scalability listed from 500 to 3,000,000 EPS and from 320 GB to 3 TB per appliance.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Key features listed for the IPDB include a write-optimized architecture that stores the collected event and log data in its raw form&#8211;no pre-processing required (but with compression and encryption); WORM support for the protection of stored data; and direct support for the storage of Internet Protocol information (IP address, MAC address, hostname, etc.).<\/p>\n<p>In addition to this, the appliance offers &#8220;Universal Device Support&#8221;&#8211;including a user interface for the definition of new messages, their payload data, and their classifications&#8211;allowing the integration of custom event sources.<\/p>\n<p>http:\/\/www.products.datamation.com\/security\/security\/1178815743.html<\/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-1535","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\/1535","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=1535"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1535\/revisions"}],"predecessor-version":[{"id":4022,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1535\/revisions\/4022"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1535"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1535"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1535"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}