PCI/DSSCYBERSECURITY

CHEAT SHEET

Payment Card Compliance

Continue reading on next page >

CRAIG PETERSØN.COM

PCI

/DSS

CY

BER

SECU

RIT

Y C

HEA

T S

HEE

T16

PCI Overview

The Payment CardIndustry Data SecurityStandard (PCI DSS) is aset of dataprotection mandates

1

2

© 2019 Craig Peterson. All Rights Reserved.

developed by the major payment cardcompanies and imposed on businessesthat store, process, or transmitpayment card data. As part of theircontracts with the card companies,merchants and other businesses thathandle card data may be subject tofines if they fail to meet therequirements of PCI DSS compliance.

Install and maintain afirewall configuration toprotect cardholder data.Create custom passwordsand other unique securitymeasures rather than using.

The Big "12" of PCI/DSS 3

the default setting from your vendorsProtect stored cardholder data.Encrypt transmission of cardholder dataacross open, public networks.Use and regularly update anti-virussoftware.Develop and maintain secure systems andapplications.Restrict access to cardholder data bybusiness need-to-know. Assign a unique ID to each person withcomputer access. Restrict physical access to cardholder data.Track and monitor all access to networkresources and cardholder data.Regularly test security systems andprocesses.Maintain a policy that addressesinformation security.

Every retailer is required to comply.Depending on the e-commercetechnology and backend theychoose to use, PCI compliance canbe an easy check on a long list ofthings retailers need to do to

ensure their customers are transacting securely.Or it can be a big pain –– costing ample time,resources and money.

PCI DSS outlines 12 requirementsfor compliance. While that seemslike it might be simple and straightforward once you check throughtheir online documentation you willfind that maintaining PCI

Seems Easy -- not so fast4

(CONTINUED)

CRAIG PETERSØN.COM

© 2019 Craig Peterson. All Rights Reserved.

compliance is onerous, complex and frustrating —those 12 requirements contain a total of 251 sub-requirements with which you must comply to fullyaddress the growing threats to customer paymentinformation.

PCI/DSSCYBERSECURITY CHEAT SHEET

The information and content in this document is provided for informational purposes only and is provided “as is” with no warranty of any kind, eitherexpress or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and non-infringement. Weare not liable for any damages, including any consequential damages, of any kind that may result from the use of this document. The information isobtained from publicly available sources. Though reasonable effort has been made to ensure the accuracy of the data provided, we make no claim,

promise or guarantee about the completeness, accuracy, recency or adequacy of information and is not responsible for misprints, out-of-dateinformation, or errors. We make no warranty, express or implied, and assumes no legal liability or responsibility for the accuracy or completeness of

any information contained in this document.If you believe there are any factual errors in this document, please contact us and we will review your concerns as soon as practical.