Canada: New Cardholder Security Guidance Issued For Third-Party Service Providers

On August 7, 2014, the PCI Security Standards Council (PCI SSC) published an information supplement entitled Third-Party Security Assurance (the Guidance), which provides guidance to organizations in relation to their engagement of third-party service providers (TPSPs) with whom cardholder data is shared or that could impact the security of cardholder data. The Guidance assists organizations and TPSPs in understanding how to meet new requirements for managing service providers in version 3.0 of the Payment Card Industry Data Security Standard (PCI DSS).

As we reported in our December 2013 Blakes Bulletin: New Standard Provides Guidance on Cardholder Data Security, PCI DSS version 3.0 became effective on January 1, 2014 (with the exception of certain requirements that are not effective until July 1, 2015). PCI DSS was developed to enhance cardholder data security and facilitate the broad adoption of consistent data security measures globally. PCI DSS applies to all entities involved in payment card processing, including merchants, processors, financial institutions, and service providers, as well as all other entities that store, process, or transmit cardholder data and/or sensitive authentication data.

The Guidance is intended as supplemental and does not supersede, replace or extend PCI DSS requirements.


The Guidance will benefit all organizations – including issuers, merchants, acquirers and service providers – that engage TPSPs for the storage, transmission, or processing of cardholder data, or for services that control or impact the security of cardholder data. Further, the Guidance is intended to assist TPSPs in understanding their responsibilities to the organizations that have engaged them, as well as how best to engage with downstream service providers engaged by the TPSPs themselves. 


The Guidance provides a number of examples of the different types of TPSPs an organization may engage. Four categories of TPSPs are identified:

  • Organizations involved in the storage, processing and/or transmission of cardholder data, such as call centres, e-commerce payment providers, gateway processors and credit reporting service providers
  • Organizations involved in securing cardholder data, such as secure storage facility providers and companies that tokenize or encrypt cardholder data
  • Organizations involved in the protection of the cardholder data environment, such as infrastructure service providers and data centre hosting providers
  • Organizations that may have incidental access to cardholder data or cardholder data environments, such as software developers and application maintenance providers

The four categories underscore how broad an organization's spectrum of TPSPs may be.


The Guidance urges organizations to develop an appropriate due diligence program for TPSPs that it is seeking to engage to understand the overall risk assumed by the organization.

Scope of Services

The Guidance emphasizes the importance of determining the scope of the services to be provided by the TPSP with regard to storing, processing or transmitting cardholder data and the effect on the security of the cardholder data environment.

Due Diligence Research

Once the scope of services to be provided by the TPSP has been determined, an organization is to undertake due diligence research to determine the impact the TPSP will have on the organization's PCI DSS compliance.

Acquirer/Payment Card Brands

An organization is encouraged to inquire with its acquirer or payment card brand to ensure that the services to be provided by the TPSP have been approved for use and that no restrictions have been imposed by the acquirer or payment card brand with respect to the engagement of the TPSP.

Validation Documentation

The Guidance proposes that an organization consider requesting documentation from the TPSP that demonstrates the TPSP has achieved PCI DSS compliance. The payment card brands define how and whether a TPSP must validate PCI DSS compliance; hence the required validation documentation may vary. The documentation should confirm that the services to be provided to the organization are covered by the TPSP's PCI DSS assessment and identify the PCI DSS requirements that were assessed to be in place. The Guidance provides a helpful list of documentation that an organization may wish to obtain from a TPSP in order to validate the TPSP's PCI DSS compliance and explains how such documentation should be reviewed by the organization.

If the TPSP has not attained compliance with PCI DSS, the organization must determine whether or not to accept the risk of engaging that TPSP. The organization should understand the gap and its impact on the organization's own environment. If the organization's environment is affected, the organization should establish a plan of action with the TPSP for remediation. The organization may wish to consult with its acquirer at this point to ensure the gap does not present any issues.

If an organization engages a TPSP that does not intend to validate PCI DSS compliance or that is not required to do so, the organization will be required to cover the applicable systems and processes of the TPSP under the organization's own PCI DSS compliance assessment.

Risk Assessment

The Guidance suggests that an organization perform a thorough risk assessment on its TPSPs based on an industry-accepted methodology. A high-level list of some of the questions and subject matter that may be appropriate for consideration in such a risk assessment – including security, governance and risk management, human resources practices, physical security, logical security and malware controls – is provided.

Documenting Results

An organization is encouraged to fully document the results of its due diligence of a TPSP's compliance status.


Following completion of due diligence, organizations are instructed to consider a number of specific items when first engaging a TPSP and during the term of the engagement, including:

  • Setting expectations with respect to the engagement, including with respect to the parties' respective PCI DSS compliance, the TPSP's responsibility to safeguard the organization's cardholder data in the possession of the TPSP in an agreed-upon manner, the services to be provided by the TPSP and the primary points of contact at both the organization and the TPSP
  • Gaining clarity and transparency of the scope of the TPSP's responsibility in safeguarding the organization's cardholder data or cardholder data environment and validating that the scope presented by the TPSP is applicable, appropriate and accurate
  • Establishing effective communication between the organization and the TPSP, including changes made by the TPSP
  • Requesting evidence to validate that changes made by the TPSP followed appropriate procedures and were subject to appropriate controls
  • Obtaining information about the TPSP's PCI DSS compliance status
  • Reviewing the engagement items set forth above on a regular basis and as changes occur
  • Mapping services to be provided by the TPSP to the applicable PCI DSS requirements so that the organization can determine the security impact to its cardholder data environment


Once due diligence has been completed and a TPSP has been selected for engagement, an organization is encouraged to document its agreement with the TPSP in writing.

Where a TPSP claims that its services are PCI DSS compliant, an organization should, according to the Guidance, document such compliance in its written agreement with the TPSP by attaching a copy (or a redacted copy) of the applicable validation documentation.

Where a TPSP has not established its own PCI DSS compliance, an organization will need to include some of the TPSP's cardholder data environment in the organization's own PCI DSS assessment. As a result, an organization should consider including in its agreement with the TPSP:

  • Processes and mechanisms that allow the organization to have access to systems, facilities and processes, along with the right to review the applicable policies, procedures and other documentation of the TPSP
  • Provisions to clarify which portions of the cardholder data environment managed by the TPSP are in-scope for the organization's PCI DSS compliance assessment and to allocate responsibility for handling and securing cardholder data in a compliant manner
  • The agreement between an organization and its TPSP should also reflect appropriate legal and regulatory requirements, industry-specific considerations, requirements mandated by an organization's acquirer related to engaging a TPSP and requirements mandated by the applicable payment card brand's compliance programs.

Other items highlighted in the Guidance for such agreements include:

  • The use of a "responsibility matrix" to set out in detail the respective roles and responsibilities of both parties
  • Data breach notification and followup obligations
  • Post-termination obligations of the TPSP, including storing or destructing cardholder data and keeping the organization's sensitive information confidential

Finally, an organization's agreement with a TPSP that claims its services are PCI DSS compliant should address what happens in the event the TPSP loses its PCI DSS compliant status. The Guidance urges an organization to consider mechanisms intended to keep it apprised of changes in the TPSP's compliance status and to allocate responsibility for loss of compliance status. Suggested mechanisms include notification of changes in compliance status being provided by the TPSP, plans and procedures for remediation by a set date, and other measures intended to help ensure accountability and responsibility for non-compliance. 


The Guidance emphasizes the importance of establishing and maintaining a program to monitor TPSP compliance. The purpose of the monitoring program is to allow an organization to monitor the compliance status of the applicable TPSP and determine whether a change in status requires a change in the relationship. The PCI SSC reminds all organizations that outsourcing services to a TPSP does not relieve an organization of its responsibility for the security of its cardholder data.

According to the Guidance, a TPSP monitoring program should be fully documented to ensure there is a common understanding of the program across the organization, facilitate delegating portions of the process if required and allow outside parties to review the process when necessary. The program should include processes, policies and procedures, and assignment of responsibility to specific people within the organization. Program documentation should be revisited regularly, reviewed at least on an annual basis and approved by management. The Guidance identifies a number of areas that should be covered by the program documentation, including defining the cardholder data environment scope and the role of each TPSP, maintaining a current list of TPSPs and setting out the TPSP monitoring procedure.


The Guidance assists organizations to better understand the requirements in PCI DSS version 3.0 dealing with managing service providers. 

An organization's procurement and risk functions should take note of the practical guidelines regarding the performance of due diligence on TPSP candidates.

An organization's legal function should familiarize itself with the portions of the Guidance that sets out items that should be considered for inclusion in agreements with TPSPs. While a number of the points are common to outsourcing agreements generally, there are other points covered in the Guidance that are unique to agreements with TPSPs, particularly those relating to compliance status.

Organizations that seek to engage with TPSPs should endeavour to investigate TPSPs and develop future agreements with the Guidance in mind.

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

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

Events from this Firm
13 Dec 2017, Seminar, Toronto, Canada

Class actions across Canada continue to grow in volume and complexity, triggering significant policy and financial implications for businesses in Canada. With the Law Commission of Ontario’s recent announcement that it is reactivating its comprehensive review of class actions in Ontario, we may see important law reform on the horizon to evolve with the changing landscape.

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
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 you may opt out by clicking here

    Terms & Conditions and Privacy Statement (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

    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’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.

    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 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

    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

    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

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

    By clicking Register you state you have read and agree to our Terms and Conditions