Timeline for Storing sensitive info in DB with Public/Private Asymmetric keys
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 13, 2016 at 17:37 | comment | added | Andrew Alaniz | Are you certain you actually need to collect this information? I would avoid collecting information like this at all costs. Can it be replaced with a a pseudo random identifier? Last 4 of social? | |
| Dec 13, 2016 at 6:39 | comment | added | Alex Urcioli | Yes, as long as the SSN is transmitted over HTTPS than you are doing your due diligence in terms of transport security. (Obviously making sure you have a valid certificate signed by a trusted CA). In terms of storing the data, you need to make sure you are encrypting it and compartmentalizing it properly. That is the difficult part. | |
| Dec 13, 2016 at 0:25 | comment | added | wlingke | so you are saying that there's no need for some sort of public key encryption since HTTPS is already handling this? So it would be okay to send the SSN over https directly to my server? | |
| Dec 12, 2016 at 21:43 | history | answered | Alex Urcioli | CC BY-SA 3.0 |