Stay Classy, San Diego!

Stay Classy, San Diego!

Shush it. I know it’s been a little slow around here. There are some major things in the works! I started a new gig, for one, which is consuming the bulk of my time. I’m also working on a 3.1 addendum to our book, which should be out by the summer.

March and April were some busy months for many of us. Three major shows (MAC, ETA, and RSA Conference) all happened in those months. PCI DSS 3.1 was released. You paid your taxes (hopefully).

Here’s what you folks liked the most last month:

  1. The Only Customer Service Script You Will Ever Need. Maybe the economy is heating up? Who knows why this one is still at the top. Regardless, more people inquiring about customer service! Check out this diversion from security that will make you think about how you interact with your customers.
  2. How Starbucks is Revolutionizing Mobile (Micro) Payments. This one was pretty popular last year, and it is still making waves in 2014. You know how you see those crazy fools that pass their phone in front of some magical sensor at Starbucks and never seem to pull out their wallet, yet walk away with coffee? That is really part of a huge master plan to reduce the impact that payments has on the organization. Check out the scenarios discussed!
  3. The Definition of Cardholder Data. Yet another powerhouse that is keeping on top of the links. It’s still on people’s minds, probably because they are looking for ways to drop systems out of scope of PCI DSS, or because they are looking at the new eCommerce guidance from the Council. Hopefully this is a good benchmark for you. UPDATE: This post has new information added for PCI DSS 3.0.
  4. How To Make a Mobile App Comply with PCI DSS. Even though this is an old post, it periodically pops its way back into the top charts. I’m guessing that things are coming back to mobile and PCI DSS. Might be time to revisit/update this post.
  5. Verizon Report Should Be a Wake-up Call for the PCI DSS. I got a little annoyed by some comments the new GM made about the Verizon report. Given the poor state of compliance, shouldn’t the Council be taking a harder look at their role in the ecosystem?

Thanks for stopping by!

This post originally appeared on

Possibly Related Posts: