|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 3:26 PM
Points: 31,425,
Visits: 13,738
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, December 13, 2002 12:00 AM
Points: 3,
Visits: 1
|
|
At my last place of employment we were an 'Oracle house' - and simply used the built-in oracle Function TRANSLATE to store passwords. This wasn't for any real encryption reasons but more so people could not look at a DBA's or developer's screen and see a password (or list of passwords).
Translate is used with a character string which simply replaces a character with another such as[SELECT user_id ... FROM table a WHERE a.user_id = @userID AND a.password = Translate(@password,'pONmlkjihgfeDCBA','abcdefghijklmnop')]
Translate can, of course, must used in reverse order to store the password. Storing the password retrieval and update sql in stored procedures kept the integrity current.
Finally.. my question... Are there any such built-in functions for SQL Server 2000? Or, could a user-defined function be built into SQL server itself - or perhaps in a stored procedure? What is your suggestion?
Thanks
Shaun
|
|
|
|
|
SSCertifiable
       
Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462,
Visits: 1,384
|
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 3:26 PM
Points: 31,425,
Visits: 13,738
|
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Tuesday, July 31, 2007 8:20 AM
Points: 885,
Visits: 1
|
|
In oracle there are built in obfuscation routines so no need to code your own :)
Anyhow, I agree that encrypting data in the DB is not the best practice in the world. More time should be spend on
a) underlying roles and access to the DB b) DB and backup file encryption c) securing the server and associated sql*server service users d) encrypting t-sql code e) auditing
the trick is always credit-card id's etc. you need to carefully analyse your routines that check and report on such data. Perhaps consider views with instead of triggers etc..
The cost of writing encryption logic into a app to crypt data that can be cracked with simple routines is tough to justify.
Chris Kempster www.chriskempster.com Author of "SQL Server Backup, Recovery & Troubleshooting" Author of "SQL Server 2k for the Oracle DBA"
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 3:26 PM
Points: 31,425,
Visits: 13,738
|
|
Does Oracle have encryption/ decryption routines? How does it manage keys? I think the db is a good place for encrypted data, but it is extremely difficult to manage. Plus, to be secure , it has to be encrypted when it crosses the wire.
I just with there was a way to lock out sa's. there are places where this is a good idea.
Steve Jones steve@dkranch.net
Follow me on Twitter: @way0utwest
 Forum Etiquette: How to post data/code on a forum to get the best help
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Tuesday, July 31, 2007 8:20 AM
Points: 885,
Visits: 1
|
|
Steve
http://download-west.oracle.com/otndoc/oracle9i/901_doc/appdev.901/a88876/adgsec04.htm
basically pl-sql stored procedure routines, ie:
dbms_obfuscation_toolkit.DESDecrypt(input_string => encrypted_string, key => raw_key, decrypted_string => decrypted_string);
for example.
Includes:
a) Data Encryption Standard (DES) algorithm b) encrypt and decrypt using 2-key and 3-key DES c) require keylengths of 128 and 192 bits, respectively d) DES algorithm itself has an effective key length of 56-bits
Chris Kempster www.chriskempster.com Author of "SQL Server Backup, Recovery & Troubleshooting" Author of "SQL Server 2k for the Oracle DBA"
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 3:26 PM
Points: 31,425,
Visits: 13,738
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, September 05, 2003 12:00 AM
Points: 2,
Visits: 1
|
|
These are valid points. Enhanced security will always have a price, and in the Database world, that equals response time. If security is that important to your organization then I would approach it like most other problems, do everything you can to tighten up the code then make up for the rest by scaling up. In this case since Disk IO is the potential bottleneck, I would consider implementing a Solid State SAN. There is no seek time to speak of and the randow reads are the same as sequential reads. As far as transmitting the data, SSL on ASP pages does pretty well, again performance is just a matter of how much you want to spend.
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 3:26 PM
Points: 31,425,
Visits: 13,738
|
|
|
|
|