Re: Encrypting Data in SQL 2000
- From: "Arnie Rowland" <arnie@xxxxxxxx>
- Date: Thu, 13 Jul 2006 16:18:37 -0700
Thanks Laurentin, for the clarification about CRYPTOAPI library.
--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"Laurentiu Cristofor [MSFT]" <laur@xxxxxxxxxx> wrote in message
news:elpC%23vspGHA.4188@xxxxxxxxxxxxxxxxxxxxxxx
Just to clarify: CryptoAPI is a set of encryption functions available in
Windows that expose standard cryptographic algorithms. .Net encryption
routines offer a higher level interface to CryptoAPI. The encryption in
SQL Server 2005 is also based on CryptoAPI. Any Windows application can
use these routines. For a list of the algorithms available through
CryptoAPI, you can take a look at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/alg_id.asp.
Thanks
--
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Arnie Rowland" <arnie@xxxxxxxx> wrote in message
news:O2IubprpGHA.4268@xxxxxxxxxxxxxxxxxxxxxxx
Yes, that could be used. (I'm not sure if it's status is still considered
secure...)
You may wish to check the resourses at:
http://www.sqlsecurity.com/FAQs/SQLServerFAQ/tabid/55/Default.aspx
--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"Steven" <Lazans@xxxxxxxxx> wrote in message
news:ucwNjZrpGHA.3324@xxxxxxxxxxxxxxxxxxxxxxx
What about Microsoft's Crypto API?
Steve
"Arnie Rowland" <arnie@xxxxxxxx> wrote in message
news:e8qenSrpGHA.3324@xxxxxxxxxxxxxxxxxxxxxxx
Very limited.
If using a .NET applicaiton, there is a rich encryption library that
could be used at the application level to encrypt data before it is
stored in the server, and decrypt it after if is retreived.
And there are several third party 'Add-ins' to allow encryption via
extended procedures.
A very crude 'hiding (and generally ineffective) scheme would be to use
one of the checksum() functions and do a one-way process. You couldn't
'decrypt' it but you could use a comparison to verify if an input value
matches.
As far as I know, the application level method is the only way to keep
a determined DBA (or Admin) from being able to access the encrypted
data AND the means to decrypt it. (But then, the question is "Is that a
wise decision?, Are you feeling lucky? Go ahead, make my ..."
--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"Steven" <Lazans@xxxxxxxxx> wrote in message
news:eDdtTMrpGHA.4812@xxxxxxxxxxxxxxxxxxxxxxx
What is the recommended way to store data in SQL Server 2000 encrypted
so not even DBA can see the values? I know SQL 2005 has encryption at
the row level, but what are my options in SQL 2000?
Thank you,
Steve
.
- References:
- Encrypting Data in SQL 2000
- From: Steven
- Re: Encrypting Data in SQL 2000
- From: Arnie Rowland
- Re: Encrypting Data in SQL 2000
- From: Steven
- Re: Encrypting Data in SQL 2000
- From: Arnie Rowland
- Re: Encrypting Data in SQL 2000
- From: Laurentiu Cristofor [MSFT]
- Encrypting Data in SQL 2000
- Prev by Date: Re: SQL Profiler 2005 - IP Address?
- Next by Date: Re: Application sending email
- Previous by thread: Re: Encrypting Data in SQL 2000
- Next by thread: Re: Encrypting Data in SQL 2000
- Index(es):
Relevant Pages
|
|