Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

storing SSNs, CCNs, password in the DB

from [Francesco] Network Security [Permanent Link]
Subject: storing SSNs, CCNs, password in the DB
Date: Sun, 27 Feb 2005 14:32:12 -0800 
What is the most secure way to store SSNs, CCNs, and passwords in the
DB?

Is this a good general policy?

1. If you need to be able to read the data back, the encrypt/decrypt
with something like TDES, storing the keys in the registry.

2. If you don't need to read the data back and you just need to compare,
then hash/salt with SHA1, storing the hash and salt in the DB.

Francesco
[More with this subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: What is more secure?, blackhat
Next by Date:  Re: Filtering by client IP address for Web App Sessions, Jason Coombs
Previous by Thread:  Re: Solutions, Results, and Comments - Was [ISA Server and SQL Injection], Jeremiah Grossman
Next by Thread:  Re: storing SSNs, CCNs, password in the DB, Adam Shostack
Indexes:  [Date] [Thread] [Top] [All Lists]