Q

Is encrypting cookies a PCI DSS requirement?

Security management expert Mike Rothman discusses whether or not storing sensitive information in the form of a cookie is considered a violation of PCI DSS.

This Content Component encountered an error
While scanning my company's Web server log files, I came across a log error that contained data posted during a secure credit card transaction. I mentioned it to our developer and he said that after the customer enters his or her credit card number and before submitting the final order, the credit card number is stored in the user's Web browser as a cookie. Are we responsible for encrypting the cookie on the user's system? Is this a requirement of the PCI DSS standard?
I know enough about Web application development to be dangerous, but I have friends that have been on the cutting edge of Web application security for years. So I figured I would ping my friend Jeremiah Grossman, CTO of White Hat Security and author of a very popular Web application security blog, to see what he had to say about encrypting cookies and PCI DSS. Here's his reply:

"General Web security best practices suggest that sensitive information, such as credit card numbers, must never be stored in cookies (or URLs for that matter). This type of data should be restricted to the POST BODY of the request and nowhere else. A primary reason is -- as the question alludes to -- the storage of the data in an uncontrolled manner on the user's system. As far as cookies are concerned, should any part of the Web site...

not be served up over SSL, then the credit card information would automatically pass over the wire in the clear."

"One possible solution would be to encrypt the data in the cookie, though not the recommended course of action and PCI has explicitly spelled out this nuance. It would be much better to be in line with industry best practices (and also PCI DSS) to simply remove the data from the cookie entirely and instead passing the data over POST. Another option would be to maintain a user session using cookies, and utilize a database for credit card number lookups."

That seems pretty clear; the application needs to be changed to avoid storing the customer's credit card number in the cookie. It may be a little inconvenient and require a bit more work, but that can be weighed against the cost of notifying customers of a data breach or the loss of business because you've violated customers' trust.

For more information:

  • In this expert response, Joel Dubin discusses whether or not tokenization can meet PCI DSS standards for storing credit card data.
  • In this SearchSecuity.com Q&A, discover how other types of sensitive customer data, such as driver's license information, should be handled.
  • This was first published in October 2007

    Dig deeper on PCI Data Security Standard

    Pro+

    Features

    Enjoy the benefits of Pro+ membership, learn more and join.

    Have a question for an expert?

    Please add a title for your question

    Get answers from a TechTarget expert on whatever's puzzling you.

    You will be able to add details on the next page.

    0 comments

    Oldest 

    Forgot Password?

    No problem! Submit your e-mail address below. We'll send you an email containing your password.

    Your password has been sent to:

    -ADS BY GOOGLE

    SearchCloudSecurity

    SearchNetworking

    SearchCIO

    SearchConsumerization

    SearchEnterpriseDesktop

    SearchCloudComputing

    ComputerWeekly

    Close