PCI Compliance

"The PCI Security Standards Council is an open global forum, launched in 2006, that is responsible for the development, management, education, and awareness of the PCI Security Standards, including the Data Security Standard (PCI DSS), Payment Application Data Security Standard (PA-DSS), and PIN Transaction Security (PTS) requirements. "

"Founded by five global payment brands -- American Express, Discover Financial Services, JCB International, MasterCard Worldwide, and Visa Inc. -- who have agreed to incorporate the PCI DSS as the technical requirements of each of their data security compliance programs. "

More  here


Important rules:
"If you are a merchant that accepts payment cards, you are required to be compliant with the PCI Data Security Standard."
"The standards apply to all organizations that store, process or transmit cardholder data – with guidance for software developers and manufacturers of applications and devices used in those transactions."

The keystone is the PCI Data Security Standard (PCI DSS), which provides an actionable framework for developing a robust payment card data security process -- including prevention, detection and appropriate reaction to security incidents.
Very useful PCI DSS quick reference.

Some notes:

  • The goal is to protect cardholder data from thieves
  • definiton of PAN – the primary account number printed on the front of a payment card (card #)
  • In general, no cardholder data should ever be stored unless it’s necessary to meet the needs of the business
  • You can store it if required but be sure its really necessary. If stored PAN must be unreadable but Cardholder Name, Exp dt and Code do not have to be unreadable.
  • Card numbers should not be displayed (screen, logs, etc) but can be shown masked, "the first six and last four digits are the maximum number of digits you may display".More. Similar restrictions exist for other card data such as name, exp and cvv. 
  • Chip information or magnetic strip data cannot be stored.
  • Card information transferred must be protected (e.g. ssl encrypted).
  • Billing and shipping address and other Account information such as personal profile are not subject to the standard (but should sent over ssl)
  • best practice: on web page set autocomplete="off" on html elements for payment card information.

All Fluid clients expect PCI compliance. One of the best ways to adhere to the standard is to ensure that Credit Card information is not stored on the Clients servers or even transmitted to the clients servers.  If Payment info is transmitted it must be over ssl.

Merchants are classified into different levels and each level requires meeting certain PCI requirements. All levels require a periodic network scan by an outside party.

 This is a good guide

Comments

Popular posts from this blog

deep dive into Material UI TextField built by mui

angular js protractor e2e cheatsheet

react-router v6.4+ loaders, actions, forms and more