ADSM-L

Re: tape encryption and TSM

2006-01-13 11:04:02
Subject: Re: tape encryption and TSM
From: Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 13 Jan 2006 11:03:17 -0500
The current issue of STORAGE magazine (January 2006) has a large article
about encryption appliances.

http://storagemagazine.techtarget.com/

Rick




             Richard Sims
             <rbs AT BU DOT EDU>
             Sent by: "ADSM:                                            To
             Dist Stor                 ADSM-L AT VM.MARIST DOT EDU
             Manager"                                                   cc
             <[email protected]
             .EDU>                                                 Subject
                                       Re: tape encryption and TSM

             01/13/2006 08:39
             AM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






On Jan 13, 2006, at 8:30 AM, Murray, Jim wrote:

> I would be more interested in the answer not so much as recovery of
> data
> but in securing data.  Being a financial institution we have
> regulatory
> requirements for data protection, new State laws say I must encrypt
> all
> data on tape that is moved off site.

Jim - As Geoff alluded, the List has reviewed solutions in the past...

If data cannot be sent encrypted from the client, then another
solution is to insert an appliance in the tape write path, such as
CryptoStor Tape, from http://www.neoscale.com/.

   Richard Sims



-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If the
reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are hereby
notified that you have received this document in error and that any
review, dissemination, distribution, or copying of this message is
strictly prohibited. If you have received this communication in error,
please notify us immediately, and delete the original message.

<Prev in Thread] Current Thread [Next in Thread>