Data loss through defunct payment gateway
Recently, a de-functional payment gateway exposed as many as 19,000 credit card numbers. Details could be found here. The exposed data was cached by google and includes 22,000 credit card numbers, including CVVs, expiry dates, names and addresses.
If your organization deals with online credit processing through your own payment gateway, make sure that you don’t fall prey to misconfigured on insecure gateway, which could lead to not only the possibility of hacking and data tempering but also a much bigger risk of your data being crawled and cached by search engine biggies like google.
This makes the situation even more serious because search engine starts making everyone aware about this mess by start processing the data it found on your gateway, starts indexing it, putting its data mining algorithms to connect your information to billions of other pages and keywords.
data loss
[...] Payment Gateway details available to the public would suggest that you remove the zip files. …Data loss through defunct payment gateway Recently, a de-functional payment gateway exposed as many as 19,000 credit card numbers. Details [...]
well, there could be lot of other reasons besides zip files, db dumps etc on the payment gateways. It is essential that you secure your payment gateways by maintaining properly hardened systems, regularly monitoring the traffic and log files and conducting regular network security exercises such as vulnerability assessment and penetration testing.