raymor |
03-12-2012 10:05 AM |
Quote:
Originally Posted by jigg
(Post 18817879)
"The Consortium claims some of the credit card data was stored in plain text form"
really? in 2012?
Idiots
|
A free tip for them and anyone with a similar system where the web server needs access to the same database that holds billing information:
Use federated tables. Tables with sensitive data like card numbers are on an intranet machine, behind the firewall. Card numbers etc. can be encrypted with Twofish or AES. That intranet server then federates the user table from the web server, so the public web server only has access to the data it needs.
Which tables go on the protected intranet machine and which on the public web server? The web server should hold only the tables it needs to do it's job. Any data that doesn't HAVE to be on the web server isn't placed there.
Similarly for internal email - run your internal IMAP from the intranet, preferably with each essential service on a VM which has one way access control so it can make only outgoing connections if at all possible, and only to those internet servers it needs to access.
The theme here is clear separation between public data (web pages) and secured data. The same concept makes transparent tours less secure, despite their convenience.
|