[dba-SQLServer] Security & encryption (cross posted to accessd&dba-sql)

Arthur Fuller artful at rogers.com
Tue May 10 15:41:51 CDT 2005


Your reply reminds me of words of wisdom which were the motto of 
Nantucket (Clipper) 's development team -- "Ask them what they want, 
then deliver what they need." Classic example in this case being the 
addition of the VALID keyword to the xBASE language.... opened a 
thousand new doorways!

dmcafee at pacbell.net wrote:

>Since HR doesn't have access to the development tools, can't they just be
>led to believe that it "is" encrypted for the developer? If the Jedi mind
>trick doesn't work on them, maybe a faux page made up to display "encrypted"
>data could be show to them.
>
>Sometimes, you have to make them think you did what they asked/wanted, even
>though you know better, like when a sales manager wants to tell you how to
>make the table structure.
>
>David
>
>-----Original Message-----
>From: dba-sqlserver-bounces at databaseadvisors.com
>[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of
>Charlotte Foust
>Sent: Tuesday, May 10, 2005 8:14 AM
>To: dba-sqlserver at databaseadvisors.com
>Subject: RE: [dba-SQLServer] Security & encryption (cross posted to
>accessd&dba-sql)
>
>
>It doesn't really make sense to build a database that the dba is locked
>out of.  I've seen discussions of this HR wish before, but I've never
>seen a good answer for it.
>
>Charlotte Foust
>
>
>-----Original Message-----
>From: Roz Clarke [mailto:roz.clarke at donnslaw.co.uk]
>Sent: Tuesday, May 10, 2005 2:05 AM
>To: 'Access Developers discussion and problem solving';
>'dba-sqlserver at databaseadvisors.com'
>Subject: [dba-SQLServer] Security & encryption (cross posted to accessd
>&dba-sql)
>
>
>Hi all
>
>This may or may not be slightly OT... We have been asked by our HR
>department whether it's possible for us to build a storage facility for
>confidential data (such as salary information), that is encrypted and
>that neither we nor the network administrators could get into once it's
>gone live. Ideally it would be integrated with their current application
>which is Access 2002 FE / SQL Server 7.0 BE.
>
>How do I build an encrypted database that I can then lock myself out of
>completely?! Without locking everyone else out too (that I've done
>before).
>
>Management are willing to spend some money if necessary.
>
>TIA
>
>Roz
>_______________________________________________
>dba-SQLServer mailing list
>dba-SQLServer at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
>http://www.databaseadvisors.com
>
>_______________________________________________
>dba-SQLServer mailing list
>dba-SQLServer at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
>http://www.databaseadvisors.com
>
>
>
>  
>


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.11.8 - Release Date: 5/10/2005




More information about the dba-SQLServer mailing list