Payment Processing Data Security Standards

What is the Payment Card Industry (PCI) Data Security Standard (DSS)?

In 2006 all major credit card companies joined forces to create the Payment Card Industry (PCI) Data Security Standard (DSS). It is the first unified data security standard that Visa, MasterCard, American Express, Discover and JCB released to address the growing problem of data security compromises in the payment card industry. Prior to its release, the credit card companies used proprietary tools to fight unauthorized data management. The best known among them are Visa’s Cardholder Information Security Program (CISP) and MasterCard’s Site Data Protection (SDP).

Who must comply with the PCI DSS?

PCI DSS requirements are applicable if a Primary Account Number (PAN) is stored, processed, or transmitted. If a PAN is not stored, processed, or transmitted, PCI DSS requirements do not apply. All merchants must comply with this standard and periodically review their compliance. Failing to do so can result in significant fines and, potentially, in cancellation of their merchant accounts.

What data can you store?

You can store the following data: primary account number, cardholder name*, service code*, expiration date*. All these items require protection. You are not allowed to store the following: full magnetic stripe, CVC2/CVV2/CID codes and the PIN.

* These data elements must be protected if stored in conjunction with the PAN. This protection must be consistent with PCI DSS requirements for general protection of the cardholder environment. Additionally, other legislation (for example, related to consumer personal data protection, privacy, identity theft, or data security) may require specific protection of these data or proper disclosure of a company’s practices if consumer-related personal data is being collected during the course of business. PCI DSS; however, does not apply if PANs are not stored, processed, or transmitted.

PCI DSS requirements.

The following requirements comprise the PCI DSS requirements:

• Install and maintain a firewall configuration to protect cardholder data. All systems must be protected from unauthorized access from the Internet, whether entering the system as e-commerce, employees’ Internet-based access through desktop browsers, or employees’ e-mail access. Often, seemingly insignificant paths to and from the Internet can provide unprotected pathways into key systems. Firewalls are a key protection mechanism for any computer network.
• Do not use vendor-supplied defaults for system passwords and other security parameters. Hackers (external and internal to a company) often use vendor default passwords and other vendor default settings to compromise systems. These passwords and settings are well known in hacker communities and easily determined via public information.
• Protect stored cardholder data. Encryption is a critical component of cardholder data protection. If an intruder circumvents other network security controls and gains access to encrypted data, without the proper cryptographic keys, the data is unreadable and unusable to that person. Other effective methods of protecting stored data should be considered as potential risk mitigation opportunities. For example, methods for minimizing risk include not storing cardholder data unless absolutely necessary, truncating cardholder data if full PAN is not needed and not sending PAN in unencrypted e-mails.
• Encrypt transmission of cardholder data across open, public networks. Sensitive information must be encrypted during transmission over networks that are easy and common for a hacker to intercept, modify, and divert data while in transit.
• Use and regularly update anti-virus software or programs. Many vulnerabilities and malicious viruses enter the network via employees’ e-mail activities. Anti-virus software must be used on all systems commonly affected by viruses to protect systems from malicious software.
• Develop and maintain secure systems and applications. Unscrupulous individuals use security vulnerabilities to gain privileged access to systems. Many of these vulnerabilities are fixed by vendor-provided security patches. All systems must have the most recently released, appropriate software patches to protect against exploitation by employees, external hackers, and viruses. Note: Appropriate software patches are those patches that have been evaluated and tested sufficiently to determine that the patches do not conflict with existing security configurations. For in-house developed applications, numerous vulnerabilities can be avoided by using standard system development processes and secure coding techniques.
• Restrict access to cardholder data by business need-to-know. This requirement ensures critical data can only be accessed by authorized personnel.
• Assign a unique ID to each person with computer access. Assigning a unique identification (ID) to each person with access ensures that actions taken on critical data and systems are performed by, and can be traced to, known and authorized users.
• Restrict physical access to cardholder data. Any physical access to data or systems that house cardholder data provides the opportunity for individuals to access devices or data and to remove systems or hard copies, and should be appropriately restricted.
• Track and monitor all access to network resources and cardholder data. Logging mechanisms and the ability to track user activities are critical. The presence of logs in all environments allows thorough tracking and analysis if something does go wrong. Determining the cause of a compromise is very difficult without system activity logs.
• Regularly test security systems and processes. Vulnerabilities are being discovered continually by hackers and researchers, and being introduced by new software. Systems, processes, and custom software should be tested frequently to ensure security is maintained over time and with any changes in software.
• Maintain a policy that addresses information security for employees and contractors. A strong security policy sets the security tone for the whole company and informs employees what is expected of them. All employees should be aware of the sensitivity of data and their responsibilities for protecting it.
• Merchant level definitions for PCI certification.

Level 1 are merchants processing over 6 million Visa or MasterCard transactions per year.Level 2 are merchants processing from 150,000 to 6 million Visa or MasterCard transactions per year.Level 3 are merchants processing from 20,000 to150,000 Visa or MasterCard transactions per year.Level 4 are all merchants not included in Levels 1, 2 or 3. PCI certification requirements by merchant level.

1. Level 1 merchants are required to undergo an annual on site review and quarterly security scans, performed by a certified third party.
2. Level 2 merchants are required to complete an annual self assessment questionnaire and to perform quarterly security scans, performed by a certified third party.
3. Level 3 merchants are required to complete an annual self assessment questionnaire and to perform quarterly security scans, performed by a certified third party.
4. Level 4 merchants are required to complete an annual self assessment questionnaire and quarterly security scans are recommended annually.

Author: Joe Cole
Article Source: EzineArticles.com
Provided by: Digital Camera News