Documentation You are here: start » primer » security

This is an old revision of the document!


Don't Be Insecure. Be Afraid.

One of the most important requirements to e-commerce is security. Unfortunately, there's no magic bullet that will make you secure, nor is there a way to fully outsource your security (though you can radically reduce your burden by using a hosted e-commerce platform like FoxyCart). This chapter exists to inform you about potential threats, common insecure practices, and best-practices.

Security is for EVERYBODY

One of the common complaints we hear from people getting started with e-commerce is:

I couldn't care less about this technical stuff. Security isn't my job! That's what I'm paying you for!

If only it were so easy. The simple fact is that anybody with access or even knowledge of an e-commerce website can potentially put the security of the entire system at risk. For example, many people use the same password for their email, website administration, and on random sites they visit. If any one of those sites is compromised, a malicious user could potentially reroute all your hard earned sales to their own bank account. So even though we at FoxyCart take our security very, very seriously, you could still create problems if you aren't familiar with basic security concerns.

Companies both giant and teensy get attacked every day. If you have a website available to the public, we'd bet dollars to donuts that it's getting attacked by bots on a daily basis. An ounce of prevention is worth a pound of cure, and a security breach averages between $150-$200+ per stolen customer record 1) 2) (though various state and federal fines can easily double or triple that figure, depending on the residencies of the impacted customers and the nexuses of the breached company).

So, yes, we're paranoid. But that doesn't mean they're not out to get us all.

PCI DSS: What It Is and What It Means To You

What Is the PCI DSS?

If you've been looking at e-commerce or gateway solutions for more than a few minutes, odds are that you've seen references to PCI DSS. While we can't give you specific advice relating to your own compliance requirements, we can help you understand some of the more important pieces of PCI DSS compliance.

First, it's important to know that the Payment Card Industry Security Standards Council (PCI SSC) is made up of the major card payment brands like Visa, MasterCard, AmericanExpress, and a few others.3) They put together the Data Security Standard (DSS), giving us PCI DSS. There are a few different levels of PCI compliance, and determining your level of compliance can sometimes be tricky. The multiple levels of PCI compliance is further complicated by the considerable amount of FUD and outright misinformation that is used to try to make a sale, sometimes for a product or service that you may not need as a merchant.

What Are the Requirements for PCI DSS?

The two “deliverable” requirements of PCI DSS are:

  1. The Self-Assessment Questionnaire (SAQ), ranging from SAQ A through SAQ D. The SAQ A is very short, while the SAQ D has over 200 questions and requirements.
  2. The Security Scan from an Approved Scanning Vendor (ASV).

You may be told by your merchant account provider or gateway that you are required to purchase a security scan through them in order to be PCI compliant, or that paying for a service will make you compliant. That is dangerously misleading information; simply paying for a service will not make you PCI compliant, as compliance can involve things like security training, paper shredding, and business policies and procedures that simply cannot be addressed by paying a 3rd party a monthly fee. So while the SAQ and the scan from an ASV are the pieces that are required to show compliance, they aren't simply things you pay for and magically become compliant.

What Are Your Compliance Requirements?

Though we cannot tell you with certainty what your compliance requirements may be, we can offer a set of guidelines that may help you discern when you do actually need to pay for a service to become compliant (and conversely, when you're being sold misinformation or FUD). This is not an exhaustive list of scenarios, and more information is available at the PCI DSS site if you need clarification.

If you're being told by your merchant account provider or gateway that you need to pay a fee to become compliant, be sure to understand the actual requirements. In many cases you may not need a scan at all, and your SAQ requirements may be quickly and easily completed without paying any additional fees.

SAQ Required Scan Required How you collect payments
None No
  • Payments are only handled on a 3rd party system such as through PayPal Express Checkout through FoxyCart or Google Checkout. (These types of payment methods are fundamentally different than a “real” gateway in that the funds are transferred first to the 3rd party (ie. PayPal), then transferred to you. PCI DSS generally only applies to merchants with a Merchant ID, receiving payments directly.)
SAQ A No
  • Payments are handled through your store's FoxyCart checkout using a “real” gateway (ie. a gateway that doesn't redirect the customer to their own hosted payment page).
  • Payment card details are never handled on the phone or using FoxyCart's Unified Order Entry or with any other virtual terminal.
  • No cardholder data storage, ever. (ie. You never store card numbers, anywhere, ever, at all.)
  • No fees should be charged by your merchant account provider if you fall under PCI SAQ A (unless breach insurance is required, which is discussed below).
SAQ B No
  • Payments are handled through standalone terminals or are swiped using a machine.
  • No cardholder data storage, ever. (ie. You never store card numbers, anywhere, ever, at all.)
  • No fees should be charged by your merchant account provider if you fall under PCI SAQ B (unless breach insurance is required, which is discussed below).
SAQ C Yes…
  • The SAQ C isn't really intended to be used for e-commerce, but rather for individual retail stores.
  • Payments are entered with a payment system connected to the internet. Systems used to access the virtual terminal may need to be scanned by an ASV.
  • No cardholder data storage, ever. (ie. You never store card numbers, anywhere, ever, at all.)

| SAQ C-VT | No… |

  • This is new as of PCI DSS 2.0, but it explicitly states “e-commerce merchants will never qualify for this version of the SAQ”, so we won't cover it here. If you're interested though…
  • Payments are entered into a web browser-based virtual terminal, “via a computer that is isolated in a single location, and is not connected to other locations or systems within your environment (this can be achieved via a firewall or network segmentation to isolate the computer from other systems)”.

|

SAQ D Yes, on applicable systems
1)
“Data breach costs top $200 per customer record”, NetworkWorld.com
2)
Data Loss Calculator by Tech-404.com

Site Tools