PCI DSS dissected – How do you scope cardholder data?

Compliance with PCI DSS should be considered the minimal level of security and does not ensure that an organisation is secure. However, compliance should ensure that an organisation has in place the procedures, policies and work practices that will reduce the possibility of a cardholder data breach, and, improve the effectiveness of an investigation of a breach.

Within the PCI DSS standard it refers to a ‘trusted’ network, which is the environment within which the cardholder’s data is identified as being either processed, stored or transmitted. A key point about the standard and its related standards and guidelines is that they have been written to protect cardholder data as it is processed, stored or transmitted and, not necessarily to protect the entire infrastructure of an organisation from all security threats as it is a very specific and focused standard.

Scope of PCI compliance

The best method to making the process of implementing and gaining compliance with the PCI DSS standard easier, is to reduce the scope of the implementation – which is the size of the environment involved with cardholder data. This can be achieved by reducing the footprint of cardholder data within your organisation’s environment by analysis of where cardholder data is stored, processed or transmitted. Reducing the amount of locations within the organisations environment where cardholder data is handled and segregating the cardholder data from other areas of the organisations environment, creates a trusted environment making the rest of the infrastructure and the internet a non-trusted environment – doing this reduces the scope for implementing the standard. In fact, if it is possible, completely remove cardholder data from the environment. This will take the environment completely out of the scope. However, if third parties are handling cardholder data for you, the responsibility for ensuring they are doing so within the requirements of the standard remains with your organisation.

Any part of an organisation, including its infrastructure where cardholder data is processed, stored or transmitted will be within scope, is known as the cardholder data environment (CDE) and is required to be protected (becomes trusted). Any part of the organisation and infrastructure that is out of scope, and the public internet, is considered untrusted.

CDE and the untrusted environment

The standard looks at the protection between the CDE and the untrusted environment. The standard covers all aspects of providing protection, not only technical controls but policies about those employees who have access to the cardholder data and the trusted environment, as well as measures to help with the investigation of breaches.

In order to identify where cardholder data is within your organisations environment, it is necessary to track the flow of data across the infrastructure which requires up to date network documentation and knowledge of the processes within the organisation. You need to examine the data flow, starting from where it enters your environment; this can be through a gateway from the internet onto the network, via phone lines, the postal system or via fax. Following the movement of the data from its entry point(s), through the organisation, until it permanently leaves organisation or is destroyed, will identify all the components that are involved in the processing, storage and transmission of the cardholder data.

Factors involved in handling card holder data

At the PCI Foundation Course I am teaching, I always stress the point that the systems involved in handling cardholder data not only include the hardware and software of the infrastructure, but everything connected to the CDE. This means they include the employees of the organisation who handle the data processing, phone calls, post, fax, maintenance of the infrastructure, administration of servers etc. It will also cover your own organisation as well as any third party organisations (known as service providers) who may be processing, storing or transmitting cardholder data on your behalf, such as, IT support organisations who have administrator rights to firewalls, routers or servers.

Data Flow Analysis

Analysis of the data flow should not only cover the active processing, storage or transmission of cardholder data, but include the storage and processing of the backup media that may contain cardholder data including those that are stored off-site.

Upon completion of the analysis of the flow of cardholder data through the organisation, it would be desirable to reduce the scope of the CDE by segregating the environment where the cardholder data is, from the rest of the environment. As well as reducing the number of systems and processes where cardholder data is handled.

In addition to identifying where cardholder data is expected to be, steps should be taken to ensure that cardholder data is not located in places where it is not expected to be; i.e. in a spreadsheet on the desktop of a data analyst who generated a report on a database containing cardholder data. In order to examine the whole environment of an organisation for unknown locations of cardholder data, techniques from e-Discovery can be used. All of the identified locations should match the data flow analysis results; any mismatch shows cardholder data is being held in unidentified locations that are not part of the normal data flow.

Conducting a scoping exercise is only part of the story. The documentation of the reasons for identifying the CDE and, reducing the scope from covering the whole organisation to a sub-set of the organisation (trusted network), needs to be kept for reference by any auditor. It is typical of the requirements within the PCI DSS that not only is evidence of controls required, but the business decisions behind those controls need to be captured in the PCI-DSS documentation.

In the following blog entries I will be examining the requirements of the PCI DSS in turn.

For professional advice on PCI DSS compliance contact IT Governance on 0845 070 1750 or by email to servicecentre@itgovernance.co.uk.

Share now…

Share on Twitter Share on Facebook Share on LinkedIn