Re: SQL 2005 - Searching Encrypted SSN


"Ron Brent" <RonBrent@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1929F115-F507-4448-9AD7-1F900B9A1F3F@xxxxxxxxxxxxxxxx
Thanks Uri!

It will be helpful once we decide to implement the encryption, but my
question is this -
is it possible to search an encrypted column the way it's described in the
blog and get the results quickly (at the same speed it takes to search on
a
clear text)?

If you want to search using = in the WHERE clause, you can get comparable
speed. Just don't decrypt the SSN's in the column. Theoretically you
should be able to encrypt the SSN you're searching for and compare that to
the already-encrypted columns. Of course this won't work if your column
looks like this:

999-99-9999

And you want to search on last 4 digits or something similar. In that case
you need to decrypt and compare row-by-row (unless you split the SSN up into
separate columns...).


.

Relevant Pages

  • Re: SQL 2005 - Searching Encrypted SSN
    ... Please also note that RC4 use is not recommended. ... purposes, and not for reporting purposes, you could probably hash the SSN ... and forget about encryption altogether. ... for and compare that to the already-encrypted columns. ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 2005 - Searching Encrypted SSN
    ... SQL Server Engine ... specify their own salt/IV values for encryption in the future? ... probably hash the SSN and forget about encryption altogether. ... for and compare that to the already-encrypted columns. ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 2005 - Searching Encrypted SSN
    ... specify their own salt/IV values for encryption in the future? ... probably hash the SSN and forget about encryption altogether. ... "The encryption algortihms in SQL Server 2005 are salted. ... for and compare that to the already-encrypted columns. ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 2005 - Searching Encrypted SSN
    ... don't have SQL 2K5 installed here at work, so I can't test it), you'll ... purposes, and not for reporting purposes, you could probably hash the SSN ... and forget about encryption altogether. ... for and compare that to the already-encrypted columns. ...
    (microsoft.public.sqlserver.security)
  • Re: Bit field vs bit manipulation?
    ... As far as the efficiency of your compression algortihm, ... For example use WinZip on the source file and compare the ... output a garbage (for example zero) byte after each 3 bytes and ... I think encryption and compressing ...
    (microsoft.public.vc.language)