3 ms·
It's a Write-Only Memory. The web server can write the credit card info to the database, but isn't able to read (and decrypt) that same info in case it gets ha
by tbrownaw 14y ago
It's a Write-Only Memory.
The web server can write the credit card info to the database, but isn't able to read (and decrypt) that same info in case it gets hacked.
Presumably there is another machine that only does billing and has a much smaller attack surface, which is the only online place with the key to decrypt the card info.
- sweis 14y agoI've seen web frontends that encrypt submitted credit card info with a public key, then had billing backends that re-encrypted with a symmetric key (usually in a HSM). That was strictly for performance overhead and key rotation flexibility. Perhaps name.com didn't care about that.