Social Security Fields - encrypting

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an access 2003 application that links to SQL Server 2000. One of the
fields is the Social Security field. What do most people do to secure
certain fields? Can you encrypt the field in SQL Server and then unencrypt
the field in Access for the user to see?

Thanks
 
Generally, you never want to store sensitive personal data that isn't a
business requirement. Unless it's a payroll application, a SSN isn't really
necessary and you should avoid storing them at all. Even the the best
security won't keep determined thieves out.

That said, all you can do is secure the database. I would use a SQL-Server
back-end because it is more secure than Jet.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Concatenate Text field and date field 4
How to display last for digits of SSN? 4
Dashes in Social Security Number 4
News Encrypted SSDs are not as secure as we thought 3
how can I change a field to have dashes, (ie social security no.) 3
Query in which I am trying to match records from one table toanother, based on Two Fields 2
hiding part of a social security number on a field 2
Limit places in a number field 3

Back
Top