News for hackers. Stuff that matters.
Re:MoviePass database exposes 161M records by symlinkk on Thursday August 22, 2019 @05:16PM (#20772429)
Just use a password manager so you can have a different password for each site. It's not that hard.
Re:MoviePass database exposes 161M records by jvagner on Thursday August 22, 2019 @05:18PM (#20772439)
The article points out that MoviePass had user and credit card data in plain text. A password manager wouldn't have helped with that.
Re:MoviePass database exposes 161M records by checker on Thursday August 22, 2019 @06:35PM (#20773000)
The credit agencies are supposed to protect cardholders via PCI DSS audits (see https://www.pcisecuritystandards.org/pdfs/pci_fs_data_storag...). This is definitely non-compliant. Obviously this system is broken.

Additionally, I don't understand why companies continue to roll their own payment processing rather than paying a service that knows how to do it. I guess it seems easy...

Re:MoviePass database exposes 161M records by nineears on Thursday August 22, 2019 @07:59PM (#20773496)
PCI DSS is a program of the card associations to protect the issuing banks from fraud losses. Merchants have difficulty complying so it ends up as a balancing act between keeping the wheels of commerce moving and preventing fraud.

Fully outsourced payment solutions are a good fit for some business models but not for others.

Re:MoviePass database exposes 161M records by AdieuToLogic on Thursday August 22, 2019 @08:27PM (#20773644)
Great post.

One thing I would add is that PCI DSS is also applicable for ISO's as well VAR's which operate payment processing gateways.

Re:MoviePass database exposes 161M records by tsukurimashou on Thursday August 22, 2019 @07:42PM (#20773402)
Well if you can make more profit, have all the advantages without being PCI DSS compliant. Why would you not roll your own payment processing? Since nothing happens apparently when the data of your customers get "breached"
Re:MoviePass database exposes 161M records by AdieuToLogic on Thursday August 22, 2019 @08:10PM (#20773555)
> Why would you not roll your own payment processing?

There are various "financial hammers" these types of breaches will induce, depending on the network (Visa, MasterCard, etc.). Plus, processors (the banks) will put the liability onto Merchants which are shown to have violated thier ToS. Storing PAN's in clear text (or at all in some cases) is certain to trigger one or both of these ramifications.

Re:MoviePass database exposes 161M records by heavenlyblue on Friday August 23, 2019 @10:22AM (#20777914)
What about being “big enough that they will discount all of these ramifications”?
Re:MoviePass database exposes 161M records by soulofmischief on Thursday August 22, 2019 @05:31PM (#20772576)
I do use a password manager. Offline, in a separate VM. No amount of password security is going to protect my credit card information, address, phone number, shopping data, and other PI from being leaked by incompetent companies.
Re:MoviePass database exposes 161M records by realshowbiz on Thursday August 22, 2019 @05:20PM (#20772457)
It is a hard-ish habit to start, and fully migrate into. But easy to maintain
Re:MoviePass database exposes 161M records by aloknnikhil on Thursday August 22, 2019 @05:49PM (#20772706)
That and 2FA. If a service fucks even 2FA up, then I don't know.