News for hackers. Stuff that matters.

altron

Thank you for your advice. Luckily, I was never logged into their systems; simply remote viewing via screen share with an authorized user.
I hadn't thought of that. Very interesting insight. Thanks!
That's my biggest issue. The people who end up seeing the CC numbers are minimum wage receptionists.

I have a customer who told me that her manager's boyfriend was writing down customer's addresses to go rob them. The nature of the business indicates that the customer is not at their home for extended periods of time. We ended up building in user permissions to see name, address and phone number.

Thank you for your support.

Edit:: I have not made up my mind yet. Admittedly, at the time of posting I was leaning more toward that side.

After reading everyone's advice, I'm leaning more toward a multi-tiered approach as @jacquesm suggested. It seems to avoid bad karma and burning bridges. Also, it seems as though the PCI Industry rarely acts on reports. So, working with the competitor to fix their issues could be the best thing down the road. It's a very small industry, and the possibility of a buy-out could exist in a few years.

Ask HN: Should I report my main competitor for PCI Violations?

It has recently come to my attention that my largest competitor (B2B SaaS in a niche market) has blatantly disregarded all PCI regulations for close to a decade.He uses a multi-tenant database, stores CC numbers in plain-text (full 16 digits, CVV and Expiration Date), and shows that data to the user, in plain-text, at the time of payment.I discovered this in the process of helping a new...

( Read More... | 126 comments | 118 points | on HN )