I am making a module for job applications, in it is, as you might imagine, some highly private data like ssn's. I am trying to see what steps I need to take to make sure that security is bullet proof around this data, there by insuring my continued employment :)  This is what I have so far, please tell me if I am missing something that would close any loop holes:

• Limit the Number of hosts and admins and train on the importance of securing their workstations when not at them.
• Set page and module level access to a security group (likely a limited number of HR employees with the same security training)
• Turn on CAPTCHA
• Check "encrypt url" (this is a feature of the product used to make the form/ module - xmod)
• Purchase SSL certificate from Verisign or other, load to the site and checked "active" on the sensitive pages

I feel a little hazy on the actual server security needed. We have the web server on one machine, the sql db on another, both have security but I'm wondering what specifically is needed and if that will allow other db's to function normally?

Any input would be most educational. Thanks! Mike

Ok, and after doing all those items above plus encrypting the db tables with sensitive info, is there anything further that is done by companies that is not covered here? I guess what I'm wondering is if we hired a 3rd party to handle sensitive data through a separate web app, would they be offering anything more secure than what the above steps would provide? Thereby wasting our money on something I could just do myself? Or are you really paying for someone else to take the blame if info does get out?
Thanks
Mike

HR would have to get SSN - not from applicants, but as part of post-hire data collection. Gotta have their SSN in order to pay them.

Is your company hosting the web and database servers, or hiring it out? If hosting self, inside two firewalls with a DMZ? Who can get at the servers, via network, applications or on foot?

If you pay another company to host - are you familiar with their level of secure practices and have they signed confidentiality agreements concerning your data? Are they known for and capable of this level of secure service?

From a tech perspective, I think you are covering yourself ok. Hashing the SSN may be a good idea, or it may be overkill if it is going to be used a lot in-house; more important there is limiting who has access to the data and normal strong technical security.