Jump to content

 

CS-Carter

Member Since 07 Sep 2010
Offline Last Active Sep 17 2010 01:04 PM
-----

Topics I've Started

PCI-DSS Simplified

10 September 2010 - 05:33 PM

There are 12 mandated security requirements to PCI-DSS.

1. Install and maintain a firewall configuration to protect data
2. Do not us vendor-supplied defaults for system passwords and other security parameters
3. Protect stored data
4. Encrypt transmission of cardholder data and sensitive information across public networks (i.e. SSL)
5. Use and regularly update anti-virus software
6. Develop and maintain secure systems and applications
7. Restrict access to data by business need-to-know
8. Assign a unique ID to each person with computer access
9. Restrict physical access to cardholder data
10. Track and monitor all access to network resources and cardholder data
11. Regularly test security systems and processes
12. Maintain a policy that addresses information security.

https://www.pcisecur....agreement.html

This type of CC data CAN BE STORED on your PCI-DSS compliant server (all methods require security protection)

a. Account Number
b. Cardholder Name
c. Expiration Date
d. Service Code

The following CC data CAN NOT BE STORED FOR ANY REASON to be PCI-DSS compliant

a. Magnetic Strip
b. CVV, CCV, CVVC, CVC, CSC, CVD (This is the 3 digit code or 4 digit verification code on the CC itself)
c. PIN Data (Debit Card PIN or CC Cash Advance PIN)

What can happen to you if you are not in compliance?

1. Fines up to $500,000 per incident
2. Remediation costs estimated at $90 to $302 per record
3. Potential customer lawsuits
4. Company reputation and brand damage

Should you be afraid?

In my opinion not at all. You just need to be aware and follow the PCI-DSS protocol.

Merchant Levels:

Level 1 = (This is the highest level and requires the most scrutiny. Unless you are a Wal-Mart you don’t have to fear) Def: More than 6 million transactions annually across all channels, including e-commerce. Req: Annual Onsite PCI Data Security Assessment and Quarterly Network Scans

Level 2 = Def: 1,000,000 – 5,999,999 transactions annually (You will defiantly need to have a dedicated server and some beefy security but I assume you can afford to hire a specialist to handle this all for you by then if not you should probably not be doing this) Req: Annual Self-Assessment and Quarterly Network Scans

Level 3 = Def: 20,000 – 1,000,000 e-commerce transactions annually. Req: Annual Self-Assessment and quarterly Network Scans. (Some of you may fall into this category. If you do you should be on a VPS or Dedicated Server with a company that guarantees PCI-DSS compliance or run and maintain your own servers) NOTE: You will also see that Level 3 is specific about e-commerce as most fraud with CC is online so this focuses in on the bulk of the fraud they deal with.

Level 4 = Def: Less than 20,000 e-commerce transactions annually, and all merchants across channel up to 1,000,000 VISA transactions annually. Req: Annual Self-Assessment and Annual Network Scans. (Most mom & pop e-commerce sites will fall into this category however it was meant to also encompass brick and mortar stores who are getting into the e-commerce game, many of these already perform a lot of transaction but up until now they have all been in their stores. This makes PCI-DSS simpler to start even if you are a big merchant)

What is a SAQ (Self-Assessment Questionnaire)?

INFO: When PCI-DSS was new there use to be just one questionnaire that everyone had to fill out. That was chaos and since 2008 they have created 4 different questionnaires based on the different types and sizes of merchants. Here they are:

SAQ A: Addresses requirements applicable to merchant who have outsourced all processing, transmission and storage of cardholder data. (This would be the PayPal, Gateways, or similar users out there who do not store any CC data in their store databases or on file in their office)

SAQ B: Created to address requirements pertinent to merchants who process cardholder data via imprint machines or stand-alone dial-up terminals only. (If you have or seen the old machines that imprinted the CC data onto the hand forms you know what they are talking about). This type of questionnaire was not designed for e-commerce.

SAQ C: Constructed to focus on requirements applicable to merchants whose payment applications systems are connected to the internet. (Terminals via the Internet and not a phone line, built in card swipes via QuickBooks, you get the idea all data transmitted over the internet and not by mail or telephone line.)

SAQ D: Designed to address requirements relevant to all service providers defined by a payment brand as eligible to complete an SAQ and those merchants who do not fall under the types addressed by SAQ A, B or C. (This is tricky so if you are an e-commerce merchant who uses a payment gateway but you still store the CC data on your server for customer convenience or you have a mixed environment. Best way to think of this is if you do not fit A, B or C definitions then you are a D)

Instructions for SAQ V1.1 and V1.2 here: https://www.pcisecur....ructions.shtml

Network Vulnerability Scans:

The PCI Standard requires merchants to scan all outward facing IP addresses. These IP addresses are not protected by a firewall and can be hacked through an open port. The SAQ identifies and mitigates risk from the inside (behind the firewall) while the IP scans identify and mitigate risk from the outside.

See Demo Video from an ASV: http://www.qualys.co...s/pci/demo.html
(note: I am not affiliated nor have I ever used Qualys before but it's a good demo)

How to get started:

1. Identify the individuals that will be responsible for PCI compliance in your organization and assemble a team that includes member from each area. (Mom & Pops this will be yet another hat for you to wear by yourself unless you hire someone)
2. Determine your merchant level (1-4)
3. Determine with SAQ your organization will need to complete
4. Evaluate whether your organization will try to achieve compliance internally or engage with a QSA (Qualified Security Assessor)
5. Engage with an ASV (Approved Scanning Vendor) to start the required external IP vulnerability scans.
6. Make sure that your organization has an Information Security Policy and that it is being enforced
7. Immediately address any significant deficiencies discovered during the assessment or scan
8. Retain record of self-assessments, scans, and follow-up activities. Be prepared to provide these documents upon request.

What should you do if you are breached? – (Immediate Action Required)

1. Contain and limit the exposure. Conduct a thorough investigation of the suspected or confirmed loss or theft of account information within 24 hours of the compromise
2. Alert all necessary parties. Be sure to notify:

a. Your Merchant Account Provider (i.e. PayPal)
b. Visa Fraud Control Group @ 1-(650)-432-2978
c. Local FBI Office
d. U.S. Secret Service (if Visa payment data is compromised)

3. Provide the compromised Visa accounts to Visa Fraud Control Group within 24 hours.
4. Within four business days of the reported compromise, provide Visa with an incident report. (Here is a step by step from Visa: http://usa.visa.com/....mpromised.html )

I realize many out there this is overwhelming but if you just take the time to understand the basics and know what questions to ask you can master this and put it behind you.

If you are using a HOSTED server be certain to ask your provider a few questions:

1. Are they PCI-DSS compliant
2. If so what LEVELS of compliance are they
3. Also if so do they have specific instructions on how to make sure your site is PCI-DSS compliant on their servers.

CS-Cart is PCI-DSS compliant but with any software it’s going to have to be testing on your installation. You will have to pass a PCI-DSS scan and if you do not you will have to fix the issue and get scanned again. Once you pass you just have to pass the scans when they are required for you type of business.

Here are a few links that may assist you in your research.

PCI Quick Reference Guide: https://www.pcisecur....uick_guide.pdf
Docs for PCI DSS V1.2:
PCI Security Standards Council Site: https://www.pcisecur...org/index.shtml
PCI Compliance for DUMMIES (FREE DOWNLOAD): http://www.qualys.co.../pcifordummies/
ASV (Approved Scanning Vendor) that provides the free eBook: http://www.qualys.co...s/qg_suite/pci/

You can use any ASV you wish I only noted the above because they have the FREE book.

Good luck on your TREK!

Required Products Add-on question.

07 September 2010 - 11:54 PM

I am trying to utilize the Required Products function of CS-Cart and am having difficulties.

When I set this up and I go to Store/Customer view then add more than one product that has Required Product it only adds quantity 1 of the required product.

I need the behavior of Required Products to add an equal quantity of product to Required Product.

Example1: Qty 2 of PRODUCT A adds Qty 2 of Required Product.
Also
Example2: Qty1 of PODUCT A and Qty1 of PRODUCT B that share the same Required Product will add Qty2 of Required Product.

Not only does Required Product need to be dependent on the products existence in the cart but also the quantities of the products themselves.

Has anyone else modified this to work for them? Any ideas?