United States: PCI SSC Releases Version 3.1 Of Data Security Standard

On April 15, 2015, the Payment Card Industry Security Standards Council (the "PCI SSC" or "Council") released a new version of its Data Security Standard ("PCI DSS"), version 3.1, which contains numerous updates including, most significantly, a shift away from the use of the Secure Sockets Layer ("SSL") and early Transport Layer Security ("TLS") encryption protocols. Coming only three and a half months after most provisions of PCI DSS version 3.0 became mandatory, this newest version is an unusually quick follow-up for the Council. The release will require organizations to respond quickly to meet compliance requirements and avoid potential fines and other liabilities. Version 3.1 is available on the PCI SSC website here

The PCI DSS is prepared by the PCI SSC, an organization originally formed by the major card brands, and, according to the brands, is intended to provide technical and operational requirements for all entities that store, process or transmit cardholder data. Many merchants and other entities subject to the PCI DSS have a contractual obligation to annually demonstrate compliance with the Standard's numerous requirements. Non-compliance with such requirements could result in potential liability, including the assertion of claims by the payment card brands for fines and assessments. 

Under PCI DSS 3.1, SSL and early versions of TLS are no longer considered "strong cryptography." The change is described as being made in response to recent concerns that SSL and early TLS contain vulnerabilities, including what is referred to as the Padding Oracle On Downgraded Legacy Encryption ("POODLE") vulnerability. The National Institute of Standards and Technology ("NIST") similarly does not approve SSL for use in the protection of federal information due to concerns that there are weaknesses in the protocol.

As set out in revised Requirements 2.2.3, 2.3, and 4.1, "new implementations" may not use SSL or early TLS to satisfy PCI DSS requirements. In addition to the issuance of PCI DSS version 3.1, the Council has also published an Information Supplement titled "Migrating from SSL and Early TLS" that describes "new implementations" as those that "have no existing dependency on the use of the vulnerable protocols." The Information Supplement is available here. Examples of new implementations include: (1) installing a system into an environment that currently uses only protocols the Council considers secure; (2) installing an application onto a system that currently uses only protocols the Council considers secure; and (3) building a new system or network to communicate with other systems/networks that support protocols the Council considers secure. The Council recommends phasing out existing implementations of SSL and early TLS immediately. Under PCI DSS 3.1, such protocols cannot be used as a security control to satisfy PCI DSS requirements even for existing implementations after June 30, 2016. Point of Sale ("POS") Point of Interaction ("POI") terminals and termination points connected to them may continue using SSL and early TLS after June 30, 2016 if it can be verified that they are not susceptible to any known exploits for SSL and early TLS. 

Under PCI DSS 3.1, protocols that are still considered "strong cryptography" include IPSEC, SSH, and some versions of TLS. In the Information Supplement, the Council states that entities using TLS must use TLS version 1.1 at a minimum, although version 1.2 is strongly encouraged. Additionally, not all implementations of TLS version 1.1 are considered secure by the Council. The Council refers to NIST SP 800-52 rev 1 for further guidance on secure TLS configurations. 

Prior to June 30, 2016, if a company continues to use SSL or early TLS on existing implementations, the revised requirements provide that the company must put in place a risk mitigation and migration plan, which will require substantial organizational efforts. According to the Information Supplement, such plans should identify, among other things, the type of environment where the protocols are used, including the type of payment channel and functions for which the protocols are used, the number and type of systems using or supporting the protocols, risks to the organization's information security environment due to the use of SSL or early TLS as well as controls that will address such risks, and the process in place to monitor for new vulnerabilities associated with the protocols. The plans must require full migration to updated encryption protocols by June 30, 2016.

In addition to the changes made regarding SSL and early TLS, PCI DSS 3.1 contains several changes that the Council characterizes as "clarifications" or "additional guidance" that could potentially impact your organization. Some involve new testing procedures, while others modify the requirements themselves. Some notable changes include:

  • In Requirement 3.4, which relates to rendering PAN unreadable where stored, a testing procedure is added that addresses whether hashed and truncated versions of the same payment account number ("PAN"), if both are present in the environment, can be correlated to reconstruct the original PAN;
  • In Requirement 6.6, which relates to public facing web applications, the testing procedure previously providing that the assessor should verify that certain automated technical solutions are configured "to either block web-based attacks, or generate an alert" has been revised to read "to either block web-based attacks or generate an alert that is immediately investigated" (emphasis added); 
  • In Requirement 10.6.1, which relates to daily log review, the phrase "or that could impact the security of CHD and/or SAD" is removed from the description of system component logs covered by the requirement; and
  • In Requirement 11.5, which relates to the deployment of change detection mechanisms to alert personnel to unauthorized modification of certain files, the word "modification" is now followed by the parenthetical "(including changes, additions and deletions)".

The Council has released a high level summary of the changes from version 3.0 to version 3.1 here. However, the language changes in version 3.1 itself should be carefully reviewed to determine the potential impact on your organization.

Because PCI DSS 3.1 purports to be effective immediately (although PCI DSS version 3.0 will not be retired until June 30, 2015), it is important that your organization move quickly to evaluate its potential impact. As discussed, credit card brands may try to assert claims for fines and other assessments in the event of a failure to comply with applicable PCI DSS requirements. 

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

*** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.