Dec
02
Posted (db) in PCI on December-2-2008

I’ve been enjoying LastPass for generating and secure storing and synchronization of passwords between web browsers and my machines. LastPass also has a feature called Automatic Form Filling,  I was a little surprised when I saw a spot to store the following information:

Look at the "Credit Card Number" Section:

12-2-2008 8-28-50 AM

 

Notice the spot for Security Code ?   PCI considers the Security Code (CAV2,CVC2,CVV2,CID) Sensitive Authentication Data, and does not permit the storage of Sensitive Authentication Data, even if it is encrypted.  This is PCI DSS requirement 3.2:  also see this "PCI Data Storage Do’s and Don’ts"

So if a user enters in their Security Code and saves it in their "Form Fill Profile" the encrypted Security Code in stored in encrypted format on your computer (when you log-in to Lastpass.com),  the LastPass.com servers and Amazon S3 (where LastPass stores its backups). [1]  Interesting.

I’ve decided that I can type in my Social Security Number, Credit Card Number, Exp Date and Security on the websites that I frequent :)     (Actually the main card number that I use for e-commerce sites I have memorized anyway.

 

It should also be noted that PCI 3.2 language states "Do not Store sensitive authentication data after authorization (even if encrypted) — With LastPass.com it acts more like a password manager or eWallet, and does not participate in the authorization process – Also the information in the user’s account is solely the cardholder’s. 

 

[1] https://lastpass.com/technology.php


Possibly Related Posts (automatically generated):

  1. Pre-Authorization data for completions and reversals and removal of Track II Data


Comments:
Joe Siegrist on December 2nd, 2008 at 11:22 am #

We at LastPass are quite familiar with the PCI processing regulations coming from the ecommerce space, but as you mentioned LastPass is very different than a company processing credit cards.

The biggest difference might not be obvious though: LastPass _NEVER_ has access to your private data! Your typical ecommerce company has dozens if not hundreds of people that could see your encrypted data — they have a KEY to the data! That’s why it’s so dangerous and why PCI regulations restrict it. LastPass on the other hand is specifically setup so no one at LastPass can see your sensitive data — it’s locally encrypted and we don’t have the key.

Because of this I’d say that LastPass doesn’t violate the “spirit” of this regulation either.

Joe

Andy O on December 4th, 2008 at 5:57 am #

“Do not Store sensitive authentication data after authorization (even if encrypted).”

Brian on January 24th, 2009 at 2:09 pm #

Actually, it doesn’t appear that LastPass is themselves a merchant. If that’s the case, there is no obligation to comply with PCI DSS. PCI DSS is not a law, it’s a burden you accept when you sign a merchant agreement via a contract. No contract, no obligation.

If LastPass wants to collect money via paypal, as I understand it, there’s nothing that Visa or Mastercard can say about storing anything, including the full magnetic strip of a card! What’s prudent is another story, but we’re talking about *required*…

Post a comment
Name: 
Email: 
URL: 
Comments: