{"id":1475,"date":"2006-05-04T00:00:00","date_gmt":"2006-05-04T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/05\/04\/ca-introduces-tape-encryption-management-product\/"},"modified":"2021-12-30T11:39:27","modified_gmt":"2021-12-30T11:39:27","slug":"ca-introduces-tape-encryption-management-product","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/05\/04\/ca-introduces-tape-encryption-management-product\/","title":{"rendered":"CA introduces tape encryption management product"},"content":{"rendered":"<p>CA has just announced the general availability of its BrightStor Tape Encryption product, which encrypts data as it is being written to standard label z\/OS tapes.  It has been estimated that it costs $140 per person to disclose the loss of data, and as many of these cases have involved the details of thousands of people, the cost of the loss of unencrypted back-up tapes is generally extremely high.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>An application program interface (API) is provided to enable third-parties to integrate the solution with their tape management systems.  This enables organizations to select the level of encryption that is appropriate for each data set, with the option of not encrypting some data at all.  In symmetric cryptography the same key is used to encrypt and decrypt the data, while in asymmetric cryptography a public and private key are used.<\/p>\n<p>http:\/\/www.cbronline.com\/article_feature.asp?guid=99560C5B-5D86-4768-951A-B296C240152D<\/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-1475","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\/1475","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=1475"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1475\/revisions"}],"predecessor-version":[{"id":3962,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1475\/revisions\/3962"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1475"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1475"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1475"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}