{"id":1418,"date":"2005-05-09T00:00:00","date_gmt":"2005-05-09T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/05\/09\/rsa-rolls-out-compliance-management-application\/"},"modified":"2021-12-30T11:39:20","modified_gmt":"2021-12-30T11:39:20","slug":"rsa-rolls-out-compliance-management-application","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/05\/09\/rsa-rolls-out-compliance-management-application\/","title":{"rendered":"RSA Rolls Out Compliance-Management Application"},"content":{"rendered":"<p>The software helps companies monitor, manage, and report on their compliance efforts.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Businesses are looking for security products that do more than just put out fires on the network.  They want technology that helps to protect the bottom line, especially when it comes to complying with the growing number of government regulations such as Sarbanes-Oxley and HIPAA.  Failing to comply with those regulations, or not being able to prove that you&#8217;re complying, can damage a company&#8217;s revenue and reputation, and could even result in criminal charges.<\/p>\n<p>RSA Security Inc. will introduce software to help companies monitor and report on their compliance efforts.  <\/p>\n<p>The RSA Reporting &#038; Compliance Manager is designed to provide better logging and reporting capabilities for both IT administrators and auditors.  The software provides views into user access rights and the activities of employees, partners, and customers working on networks protected by RSA security products.  It can produce reports to show who has access to what data and who actually looked at what information, what changes have been made to access policies and who made them, and the number and types of unsuccessful unauthorized attempts at access.<\/p>\n<p>http:\/\/www.informationweek.com\/showArticle.jhtml;jsessionid=GZBQXMEDOA2N0QSNDBNCKH0CJUMEKJVN?articleID=162800084<\/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-1418","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\/1418","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=1418"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1418\/revisions"}],"predecessor-version":[{"id":3905,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1418\/revisions\/3905"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1418"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1418"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1418"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}