-
Notifications
You must be signed in to change notification settings - Fork 14
Expand file tree
/
Copy pathDrupalPCICompliance.html
More file actions
557 lines (341 loc) · 58.3 KB
/
DrupalPCICompliance.html
File metadata and controls
557 lines (341 loc) · 58.3 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Drupal PCI Compliance White Paper</title>
<meta name="generator" content="TextMate http://macromates.com/">
<meta name="author" content="Rick Manelius">
<style type="text/css" media="all">@import url("css/style.css");</style>
<style type="text/css" media="screen">@import url("css/screen.css");</style>
<style type="text/css" media="print">@import url("css/print.css");</style>
</head>
<body><h1>Drupal PCI Compliance White Paper</h1>
<p><em>Authors:</em></p>
<ul>
<li>Rick Manelius</li>
<li>Greg Knaddison</li>
<li>Ned McClain</li>
</ul>
<p>v1.2</p>
<p>August 25th, 2014</p>
<p>Updated to PCI-DSS 3.0</p>
<h2>Introduction</h2>
<p>This document provides a high level overview regarding Payment Card Industry Data Security Standard (PCI DSS) compliance specifically for Drupal eCommerce solutions. The intended audiences include: Drupal developers; companies providing Drupal products, services, and hosting; and businesses evaluating Drupal as part of their eCommerce solution. Goals of this document: to emphasize the importance of PCI compliance; to summarize the options available in becoming and maintaining compliance; to provide clear next steps and additional resources.</p>
<h2>Executive Summary</h2>
<p>eCommerce volume continues to grow by double digit percentages each year<sup><a href="#cite-1">1</a></sup> as more and more businesses are supplementing their existing revenue models and/or creating new streams <sup><a href="#cite-2">2</a>,<a href="#cite-3">3</a></sup>. Simultaneously, Drupal has seen a 21% rise in the number of reported eCommerce installations in 2013 across its very large installation base <sup><a href="#cite-4">4</a></sup>.</p>
<p>Drupal is an attractive eCommerce platform for many reasons: Its Open Source licensing eliminates one time and recurring costs to own and use, it is extremely modular and flexible, and it has a large, passionate, and world wide community that is continually contributing to and growing the platform. The Drupal community also makes a concerted effort when it comes to ensuring the platform is secure. There is a security team, weekly security advisories, venues to discuss security best practices, a collection of tools to help detect security vulnerabilities, and many other security focused strengths. The result is that Drupal is one of the most secure content management and eCommerce solutions available to merchants today.</p>
<p>However, while it is possible to make a Drupal-based eCommerce environment PCI DSS compliant through proper planning, usage, maintenance, and management, the mere use of Drupal by itself <em>IS NOT</em> sufficient to ensure the level of security necessary to become compliant. First, it’s possible to make Drupal insecure through the use of inappropriate configurations and site mismanagement. Second, Drupal is only a single component of the cardholder data environment (CDE). Hosting servers, networks, and other factors play a significant role in securing the entire end-to-end process.</p>
<p>How and where the credit card data is processed, transmitted, and stored determines the size, complexity, and risk associated with the cardholder data environment, which directly impacts the time, resources, and expertise required to achieve and maintain compliance. Whenever possible, wholly-outsourced and shared-management implementations can make it easier to complete this process. Merchant-managed solutions are the most cost prohibitive for all but enterprise level companies, and should be avoided unless the business needs require them.</p>
<p>Regardless of the selected approach, it’s always necessary to adhere to the complete PCI DSS standard because a single exploit can undermine a company's PCI compliance, opening the company up to the financial and legal liabilities associated if the exploit where to be breached. Finally, the standard is becoming more stringent with each new version; therefore, what is optional today is likely to become a requirement in the near future.</p>
<h2>Definitions</h2>
<p>The following terms are used extensively throughout this document and are provided here for convenience.</p>
<ul>
<li><strong>ASV:</strong> Acronym for “Approved Scanning Vendor.” Company approved by the PCI SSC to conduct external vulnerability scanning services.</li>
<li><strong>Cardholder Data:</strong> At a minimum, cardholder data consists of the full PAN (primary account number). Cardholder data may also appear in the form of the full PAN plus any of the following: cardholder name, expiration date and/or service code</li>
<li><strong>CDE:</strong> Acronym for “cardholder data environment.” The people, processes and technology that store, process or transmit cardholder data or sensitive authentication data, including any connected system components.</li>
<li><strong>Credit Cards:</strong> The term "credit cards" is used in this paper for brevity, but the advice also applies to any debit or prepaid "payment cards."</li>
<li><strong>DSS:</strong> Acronym for “Data Security Standard” and also referred to as “PCI DSS.”</li>
<li><strong>QSA:</strong> Acronym for “Qualified Security Assessor,” company approved by the PCI SSC to conduct PCI DSS on-site assessments.</li>
<li><strong>Payment Cards:</strong> For purposes of PCI DSS, any payment card/device that bears the logo of the founding members of PCI SSC (i.e. Visa, Mastercard).</li>
<li><strong>PCI:</strong> Acronym for “Payment Card Industry.”</li>
<li><strong>ROC:</strong> Acronym for “Report on Compliance,” which contains details documenting an entity’s compliance status with the PCI DSS.</li>
<li><strong>SAQ:</strong> Acronym for “Self-Assessment Questionnaire,” a checklist that you must complete and adhere to in order to obtain and maintain PCI compliance.</li>
<li><strong>SSC:</strong> Acronym for “Security Standards Council,” it is the governing organization and open forum responsible for the development, management, education, and awareness of PCI Security Standards.</li>
</ul>
<p>A full list of definitions can be found in the PCI document titled <em>Glossary of Terms, Abbreviations, and Acronyms</em> <sup><a href="#cite-5">5</a></sup>.</p>
<h2>Why Does PCI Compliance Matter for Drupal?</h2>
<p>PCI compliance is important for the industry as a whole as well as companies specifically using Drupal as part of their eCommerce solution. Here are several key areas to underscore the recommendation and requirement to adhere to PCI compliance.</p>
<h3>Trust</h3>
<p>Online credit card transactions have become so common and accepted in our society that it's easy to forget what is at stake. When a thief goes after physical credit cards the amount of financial loss to a financial institution or merchant is limited in size and quantity because each card has to be stolen one at a time. However in the case of electronic payments, a single computer hacker can potentially breach multiple websites with the same exploit and steal hundreds, thousands, or even millions of credit cards. The financial loss by a financial institution and the number of people affected in a website compromise can be staggering.</p>
<p>While these scenarios do in fact happen, their frequency is far outweighed by the volume of transactions that are handled securely. This is in part because of the set of security standards set forth by the Payment Card Industry. When properly applied, the risk level for transactions goes down significantly, which leads to more consumer trust in merchants, the process, and the industry as a whole can continue to expand. However, if this trust is broken, consumers will lose this confidence and seek other merchants and means of payment.</p>
<h3>Privilege</h3>
<p>A merchant's ability to accept credit card payments is a privilege, not a right. The Payment Card Industry has established a system of payment that is convenient for consumers and business owners. It is their system and they get to set the requirements. Anyone accepting online payments must sign a contract and/or accept a terms of use agreement that explicitly states the merchants responsibility to adhere to these requirements (unfortunately this isn't always emphasized in the sign up process, so be sure to read through the fine print). If a merchant fails to adhere to these requirements their ability to accept credit cards as a form of payment can be suspended.</p>
<h3>Distributed Components</h3>
<p>Every component between a customer’s browser window and the payment processor makes up the Cardholder Data Environment (CDE). If one only focuses on securing a single component, the weakest link in the chain can be the source of an exploit. Therefore it’s not enough to simply secure Drupal. The PCI standard provides guidance on how to make sure all components are secured.</p>
<p><em>Author's Note: It's important to note that ALL systems connected to the same network that's behind the same stateful firewall as the eCommerce server are also considered part of the CDE. Therefore, a common strategy is to segment the network such that only the eCommerce relevant components are together in a carefully protected network, thus reducing the overall scope for PCI DSS compliance.</em></p>
<h3>Distributed Companies</h3>
<p>It’s not common for one company to control the entire end-to-end process of handling a credit card transaction. Therefore, it’s important to know exactly how these companies distribute the responsibility as well as liability for ensuring this process is secure.</p>
<h3>Financial</h3>
<p>If you ever face a security breach and credit card information is stolen, having a proven record of your PCI compliance can protect you from the financial penalties (ranging from $25 to $215 per compromised card<sup><a href="#cite-6">6</a></sup>). Major corporations, such as Heartland Payment Systems, have faced fines as large as $12.5 million<sup><a href="#cite-7">7</a></sup>. In addition to fines, your organization and brand can suffer financially due to a breach. Target Brands, Inc. attributed a portion of its 5.3% loss in sales and a 46% drop in profit during the 4th quarter of 2013 to its security breach in November of that year, which resulted in 40 million compromised credit card records<sup><a href="#cite-8">8</a></sup>. Small companies are equally at risk, accounting for 80% of all instances of unauthorized access<sup><a href="#cite-9">9</a></sup>. And while a smaller company might have a low quantity of transactions (and therefore a smaller fine), any company that has a reported breach on their record must undergo mandatory Report On Compliance audits, which alone can cost tens of thousands of dollars.</p>
<h3>Public Relations</h3>
<p>Beyond the financial burden of dealing with a breach, the loss of trust for a company's website, business, and brand can be staggering. The Sony PlayStation breach put more than 77 million credit card numbers at risk <sup><a href="#cite-10">10</a></sup>. The ramifications of alerting a user base and requiring that many users to change their cards and/or put a freeze on their credit cards can quickly lose current and future customers. These transactions can also impact customer credit scores if they unknowingly overdraft or miss a payment they were not expecting.</p>
<h3>Summary</h3>
<p>While developers and businesses may see this standard as a nuisance, it’s important to realize that these standards allow the industry as a whole to provide the level of security and trust necessary to keep it growing. The PCI DSS should be considered a baseline, minimal level of security for sites handling sensitive information - your site very well may need security controls that exceed this standard. Also adhering to the standards helps ensure protection for the business (legal, PR, and financial), as well as your customers (legal, financial).</p>
<h2>The Standard Itself</h2>
<p><em>Note: This paper specifically excludes PA-DSS because Drupal is Open Source Software and (whether right or wrong) falls outside the PA-DSS standard.</em></p>
<p>The PCI-DSS standard covers 12 requirements across 5 overarching categories<sup><a href="#cite-11">11</a></sup>. Rather than restate what is already provided in the materials from the PCI council, the focus here is to specifically identify why each requirement directly affects the security of Drupal within the context of a complete CDE.</p>
<h3>Requirement 1. Install and Maintain a Firewall</h3>
<p>The integrity of a Drupal code base can only be maintained if access to the server is restricted and protected by a stateful firewall. A lax or nonexistent firewall policy provides more ways for an attacker to find a vulnerability, gain access to the server, and modify the code on the system, which opens the door for harvesting credit card numbers.</p>
<h3>Requirement 2. Do Not Use Vendor Supplied Default Passwords</h3>
<p>This should be obvious, but any component of your system that has a known default password can be vulnerable if it’s not reset immediately. A Drupal specific example is the Commerce Kickstart installation profile. By default, it sets the main administrator username and password to “admin.” This should only be used for testing/evaluation purposes and should never be used for a live site.</p>
<h3>Requirement 3. Protect Stored Data</h3>
<p>Ideally credit cards are not being stored on a Drupal website at all. If they are stored, they must be encrypted (e.g. using a hardware security module or an encryption key management solution) in such a manner that anything with access to the database, server, or network cannot decode the information in a manner that is not intended. Achieving this is non-trivial and should only be attempted after gaining close familiarity with the PCI SAQ D standard (see the section <em>Self-Assessment Questionnaire</em> for definitions of the SAQ validation types).</p>
<h3>Requirement 4. Encrypt transmission of cardholder data across open, public networks</h3>
<p>The data leaving the Drupal application travels through many routers and networks on the way to the payment processor. Unencrypted data would allow any component along that path to copy cardholder data and other sensitive information. Therefore, encryption with a trusted SSL certificate is a requirement.</p>
<h3>Requirement 5. Use and regularly update anti-virus software or programs</h3>
<p>If malware is installed on a server running Drupal, it can be difficult or impossible to verify the integrity of the codebase, which opens the door for access to credit card data.</p>
<h3>Requirement 6. Develop and maintain secure systems and applications</h3>
<p>It’s simply not enough to “set it and forget it” when it comes to all components of the CDE. A single discovered vulnerability at the network, server, and/or Drupal app layer has the potential for exploitation. Drupal security advisories are posted every Wednesday and should be watched regularly for any updates affecting Drupal core and/or contributed modules a site is using. Likewise, critical operating system and support software (Apache, PHP, MySQL, and other server software.) patches must be applied within 30 days of release.</p>
<h3>Requirement 7. Restrict access to cardholder data by business need-to-know</h3>
<p>This requirement impacts not only application design, but also account and server management. For example, the server that houses your eCommerce site should not be used as a place where anyone can connect via FTP using a shared password and upload photos from the company picnic. Any one of those individuals’ machines could be used to gain authorized access to the CDE code base and/or card data itself.</p>
<h3>Requirement 8. Assign a unique ID to each person with computer access</h3>
<p>Sharing usernames and passwords leaves less detail for actions occurring for each individual user. It also generally leads to other bad practices, such as creating weak passwords and sharing them over insecure channels like email. Never share your “user 1” or root login information between staff.</p>
<h3>Requirement 9. Restrict physical access to cardholder data</h3>
<p>Similar to Requirement 1, access to the server must be protected at all times. If a person without proper clearance can physically access a server, they can potentially gain root/administrator access and compromise the database and Drupal application layer. If you outsource hosting, ensure the provider is PCI DSS compliant.</p>
<h3>Requirement 10. Track and monitor all access to network resources and cardholder data</h3>
<p>Audit trails are critical for identifying changes in the system because a single code or configuration alteration can open up a security vulnerability. Having the ability to identify exactly what changed and who changed it is very important for verifying the integrity of a system.</p>
<h3>Requirement 11. Regularly test security systems and processes</h3>
<p>It’s not enough to have a system that works in theory. Periodic vulnerability scans and full penetration tests are necessary to prove that the system responds as expected. These tests have to be run regularly (at least quarterly) and are ideally run whenever there is a configuration or code change that could introduce a new vulnerability. Ensure you are using an officially Authorized Scanning Vendor (ASV) as listed on the PCI site<sup><a href="#cite-12">12</a></sup>.</p>
<h3>Requirement 12. Maintain a policy that addresses information security for all personnel</h3>
<p>All the hardware testing, security scans, and audits in the world will not help if people are allowed to use insecure passwords or send full credit card numbers via unencrypted channels like email. The human element is often the weakest link in the security chain. A security policy is required to ensure ALL employees know and understand what is acceptable and what is not with respect to maintaining compliance.</p>
<h2>Self-Assessment Questionnaire</h2>
<p>Knowing how to get started can seem overwhelming at first. Thankfully, the PCI council has provided detailed reference guides and instructions<sup><a href="#cite-13">13</a></sup>. All of these materials culminate to your Self-Assessment Questionnaire. This form is essentially a checklist that you must complete and adhere to in order to obtain and maintain PCI compliance.</p>
<p>Your credit card processor and acquiring bank are required to ask you for annual SAQ forms - if they haven’t asked yet, they will soon!</p>
<p>The key is determining which SAQ you should be filling out because they vary wildly in terms of quantity of responsibilities and the amount of time and effort it takes to complete them. SAQ A has 14 items and usually can be completed in under a day if not within a couple of hours. SAQ D contains between 326 and 347 items and can take months of time and millions of dollars to achieve<sup><a href="#cite-14">14</a></sup>. The following section will help you make sense of these different levels and how you can select the method that balances your business needs with your ability to achieve compliance.</p>
<h3>Determining Your Responsibilities</h3>
<p>The quantity and difficulty of your PCI responsibilities are a result of your merchant level (which is based on the volume of transactions) and your validation type (which is based on how you’re conducting transactions).</p>
<h3>Merchant Level</h3>
<p>The PCI council has defined 4 levels of transaction volume (Figure 1)</p>
<p><img src="images/figures/PCI-levels-visa-cardbrand-2013-06-10.png" alt="" title="A table showing the 4 levels of PCI compliance transaction volumes for VISA card brand."></p>
<p><em>Figure 1. The 4 levels of transaction volumes for VISA card brand. Other card brands (e.g. MasterCard, American Express.) have different reporting and validation requirements. Image Source <a href="http://usa.visa.com/merchants/risk_management/cisp_merchants.html">http://usa.visa.com/merchants/risk_management/cisp_merchants.html</a></em></p>
<p>There are a few important points to emphasize for the Visa card brand:</p>
<ul>
<li>Compliance begins at transaction #1.</li>
<li>Even though validation is optional at level 4, compliance is still mandatory.</li>
<li>If a breach occurs and is reported, a company immediately moves to level 1 regardless of its transaction volume.</li>
<li>Level 1 validation involves more stringent auditing process, including a mandated third-party audit, which adds additional time and money to stay compliant.</li>
</ul>
<h3>Validation Type</h3>
<p>The PCI council defines 8 different validation types:</p>
<p><img src="images/figures/PCI-saq-breakdown.png" alt="" title="Breakdown of PCI types as a function of merchant’s activities."></p>
<p><em>Figure 2. Breakdown of PCI-DSS version 3.0 SAQ types as a function of merchant activities.</em></p>
<p>For the purposes of a typical Drupal eCommerce site, the SAQ A, A-EP, and D are the most relevant types<sup><a href="#footnote-A">A</a>, <a href="#footnote-B">B</a></sup>. It is also extremely important to understand which type the system falls into because there is a large difference in time, effort, risk, and expense in achieving compliance.</p>
<p><img src="images/figures/PCI-typical-costs-per-saq-type.png" alt="" title="Approximate PCI compliance costs per SAQ type. Factors include audits ($30,000-$100,000), time spent meeting each requirement, and more."></p>
<p><em>Figure 3. Approximate PCI compliance costs per SAQ type. Factors include audits ($30,000-$100,000), time spent meeting each requirement, and more.</em></p>
<p>For many eCommerce stores, selecting a payment method that places them in type C or D can be cost prohibitive. However, achieving SAQ A or A-EP is not always possible given the available payment gateway options that can satisfy a business's feature requirements, which drives the expansion or reduction of the CDE and ultimately determines the validation type.</p>
<h3>Drupal Specific Examples</h3>
<p>The shopping cart selected (Drupal Commerce, Ubercart, Pay, Stripe, etc) and the payment method within that shopping cart (hosted payment page, direct post, iframe, onsite.) are usually the most significant factors in expanding or reducing the CDE, which directly impacts the SAQ type. Here are some situations that may force one into SAQ D:</p>
<ul>
<li>A client that wants complete control over the checkout process may shy away from hosted payment pages, which may be the only viable shared-management option for a particular payment gateway<sup><a href="#footnote-C">C</a></sup>.</li>
<li>A client sometimes must use a particular payment gateway because of an existing contract/business relationship, and that gateway may offer no shared-management options.</li>
</ul>
<h2>Overview of Payment Methods</h2>
<p>The PCI council defines 3 types of payment methods: Merchant-managed, Shared-management, and Wholly-outsourced.</p>
<h3>Merchant-managed</h3>
<p>A general guideline is that if the company’s servers store, transmit, or handle cardholder data, then it’s merchant managed. An example would be customer submitting a payment directly on a Drupal site using Ubercart connected to Authorize.Net because a customer’s payment information passes through the merchant’s webserver on the way to being sent to Authorize.Net. It does not matter if the merchant is storing the data on their servers, since a hacker could gain access if they were able to compromise the server.</p>
<p>Onsite payments posted directly back to Drupal (i.e. an HTTP POST request containing the cardholder data is submitted to the Drupal application, which results in a bootstrap and the passing of the cardholder data through the form API) immediately fall into SAQ D.</p>
<p>Merchant-managed examples:</p>
<ul>
<li>Authorize.Net Automated Recurring Billing (ARB)</li>
<li>Authorize.Net Customer Information Manager (CIM)</li>
<li>PayPal Payments Standard (PPS)</li>
</ul>
<h3>Shared-management</h3>
<p>In a shared-management approach, the credit card information never touches the server that is running the Drupal application. This is generally accomplished by one of 3 approaches:</p>
<ul>
<li>Hosted Payment Page (HPP)</li>
<li>Direct Post</li>
<li>Inline Frame (iframe)</li>
</ul>
<p>A HPP approach is where a user is redirected from a Drupal site to a third-party site in order to enter their payment details. If the transaction is successful, the customer is redirected back to the Drupal site with the payment authorization details. Depending on the specific payment gateway's security requirements, these payment authorization details may get sent back to the payment gateway's API to further validate the payment.</p>
<p>Example HPP solutions:</p>
<ul>
<li>Authorize.Net Server Integration Method (SIM)</li>
<li>PayPal Payments Standard (PPS)</li>
<li>PayPal Express Checkout (EC)</li>
</ul>
<p>A direct post approach is where the customer remains on the website, but their card data is submitted directly from the customer’s browser to the payment gateway and a response is sent directly back to the customer with a one time authentication code or "token" that is then used by Drupal to immediately communicate with the payment gateway's API to validate the payment. There are two flavors of direct post: setting an HTML form's action attribute to a 3rd party API endpoint or achieving the same with Javascript.</p>
<p>Example direct post solutions:</p>
<ul>
<li>Authorize.Net Direct Post Method (DPM)</li>
<li>Braintree Payments</li>
<li>Stripe</li>
</ul>
<p>An iframe approach is where the payment details portion of the checkout form is loaded through an iframe directly from the payment processor. Similar to a direct post strategy, an iframe gives the customer the impression they are always on site while the credit card details are sent directly to the payment gateway.</p>
<p>Example iframe solutions:</p>
<ul>
<li>Hosted PCI</li>
<li>Authorize.Net Hosted Customer Information Manager (CIM)</li>
<li>PayPal Payments Advanced (PPA)</li>
<li>PayPal Payflow Link (PFL)</li>
</ul>
<p>The common denominator in all shared-management configurations is that the checkout process begins on Drupal website (a component of the CDE) managed by the merchant, but the customer is technically sending their credit card credentials directly to the payment processor’s CDE. This occurs by redirection (HPP), loading a payment form from their servers (iframe), or posting the form directly through JavaScript or the action attribute on an HTML form (direct post).</p>
<p>One might assume that a shared-management approach would qualify them for SAQ A. However, section 3.4.3 in the <em>PCI DSS eCommerce Guidelines Supplement</em> document makes it clear that each shared-management method has vulnerabilities <sup><a href="#cite-15">15</a></sup>, which are described in more detail below. Furthermore, <em>Understanding the SAQs for PCI DSS v3.0</em> (in addition to the SAQ A and SAQ A-EP v3.0 forms) specifically states that direct post solutions cannot qualify for SAQ A and must use SAQ A-EP<sup><a href="#cite-16">16</a></sup>.</p>
<p>Frustrating as this may be for those wanting to achieve PCI SAQ A, the good news is that using a direct post or hosted payment page solution can still qualify as SAQ A-EP, which is much easier to achieve in comparison to SAQ D because a significant amount of the responsibility can still be considered outsourced.</p>
<h3>Wholly Outsourced</h3>
<p>In a wholly outsourced solution, everything regarding the Drupal application is hosted, managed, and under the responsibility (emphasis added) by a third-party vendor. Please note that most hosting services and Drupal vendors do not explicitly take on that responsibility, so be sure to do your due diligence and ensure that they are equally aware of the repercussions of taking on that responsibility. If the third-party vendor does take on that responsibility, you may be eligible for completing SAQ A<sup><a href="#footnote-D">D</a></sup>.</p>
<h3>Version 3.0 Disclaimer</h3>
<p>Version 3.0 eliminated much of the confusion that existed in version 2.0 with respect to selecting the appropriate SAQ form for each shared-management solution. Previously, one could formulate a strong argument for SAQ A, SAQ C, or some arbitrary hybrid of the two. And given the large difference in the implications for each SAQ type (see Figure 2), it was difficult to confidently make a final determination about each of these shared-management solutions. SAQ A-EP not only introduced a middle ground, but the requirements for SAQ A and SAQ A-EP made it clear with respect to which solution was appropriate for each—iframe and hosted payment page methods are compatible with SAQ A while direct post methods are not.</p>
<p>The decision to allow iframe solutions into SAQ A is not without controversy because one can still make the case that a breach of the Drupal application layer can compromise the delivery of the iframe. Therefore, while the final recommendations of this paper are to use iframe and hosted payment page solutions in order to fall within the scope of SAQ A, it is also recommended to always comply with SAQ A-EP (at a minimum) for security reasons and to future proof your Drupal site against the next versions of the PCI-DSS standard.</p>
<p>There are other important changes introduced in the 3.0 standard, such as the requirement to have all components of the CDE documented with an explicit determination of responsibility for each component. Also noteworthy is that SAQ C is no longer applicable for eCommerce channels, which means that all merchant-managed solutions must comply with the more rigorous SAQ D. For a full list of changes, please see the <em>Version 3.0 Change Highlights</em> and <em>Summary of Changes from PCI DSS Version 2.0 to 3.0</em> documents<sup><a href="#cite-17">17</a>,<a href="#cite-18">18</a></sup>.</p>
<h2>Selecting the Appropriate Method</h2>
<p>SAQ A is obviously desirable and recommended because of its lower risk, time, and cost to implement. However, a company’s business needs may require a solution that is more customizable and that may rule out a wholly outsourced or even shared-management solution.</p>
<h3>Example: Recurring Payments for Ubercart on Drupal 7</h3>
<p>As of July 2014, there is no wholly-outsourced or shared-management solution for a Drupal 7 website using Ubercart with a recurring billing requirement. To store a customer’s credit card information directly on Authorize.Net’s servers, one must use the included Ubercart Authorize.Net module and enable the customer information manager (CIM) option. Unfortunately, the way Ubercart implements CIM requires the credit card information to pass through the Drupal application. Therefore this is a Merchant-managed solution, which requires one to adhere to every control item in SAQ D.</p>
<p><em>Author's Note: payment processors like Authorize.Net have the ability to use third-party iframes to integrate with their CIM service and adding this new functionality into the existing Ubercart modules (core or contrib) would make it significantly easier for merchants to achieve compliance. However, requests to add this functionality for Authorize.Net and other payment gateways have been made with no indication that they will be added to a development roadmap<sup><a href="#cite-19">19</a></sup>.</em></p>
<h2>Additional Considerations</h2>
<p>One of the easiest ways to use a shared-management approach is to redirect to a hosted payment page. However, website owners are often resistant to doing this because customers are not always keen on being sent to a third-party site. Additionally, third-party HPPs are not always as customizable in terms of look and feel. Finally, HPP solutions are often more difficult to develop against because one needs to be developing on a public facing URL or IP address in order to get the response back appropriately.</p>
<p>With respect to direct post methods using JavaScript (JS), there is always the consideration that a user may have disabled JS by default and therefore be unable to enter a payment at all without prompting them to adjust their browser security settings.</p>
<p>There are considerations with respect to which shopping cart method to use (or continue to use) on top of Drupal. Drupal Commerce is much more popular for Drupal 7 and popularity brings more people to fix bugs and contribute modules. However, there is still a significant user base using Ubercart, and while Ubercart has far fewer shared-management payment gateway modules that are publicly available, there is nothing precluding the community from creating them in order to address the newer and more stringent PCI-DSS requirements. The possibility of additional costs to become compliant with Ubercart should be a consideration when evaluating the two solutions.</p>
<p>There are also other payment methods on Drupal, such as the stand alone Stripe and Pay modules, which offer a simpler and smaller feature set than Ubercart and Drupal Commerce and may be more appropriate for one time payment solutions.</p>
<h2>Recommendations</h2>
<p>There is no one-size-fits-all solution. Each company will have to balance the resources available to become compliant with the features necessary for the business. However, there are some general recommendations that apply across the board. The first is to use Drupal Commerce over Ubercart because Drupal Commerce is more developer focused and has a more consistent code base. It also has more shared-management payment solutions, and that trend is likely to continue. Finally, whenever possible, use a shared-management solution (SAQ A-EP compatible) over a merchant managed solution (SAQ D required) in order to significantly reduce the number of potential security exploits as well as the amount of security controls one has to meet in order to achieve compliance. If available, select an iframe solution (SAQ A compatible) because it further reduces the number of requirements necessary for compliance. However, it's still recommended for those using an iframe or hosted payment page solution to adhere to SAQ A-EP because it'll future proof the CDE as well as adhere to many best practices, which should be implemented regardless.</p>
<h2>Drupal Specific Exploits</h2>
<p>To further emphasize the importance of adhering to the PCI standard (for both merchant-managed and shared-management payment solutions), we created a list of the many ways in which a compromised website could be configured in order to steal cardholder data.</p>
<ul>
<li><strong>Direct module manipulation.</strong> The codebase could be altered in such a way to email, log, or display cardholder data upon form submission.</li>
<li><strong>Hook alters.</strong> Any module could implement a form alter hook to add in additional validation and/or submission functions to grab the cardholder data.</li>
<li><strong>Scripting language.</strong> A Flash or JavaScript keylogger or scraper could be used to harvest information as it is typed in and send it to an external server.</li>
<li><strong>HTTPS disabling.</strong> A single configuration change can remove HTTPS and user data would be passed unencrypted.</li>
<li><strong>Changing credentials.</strong> Hackers could substitute in their own gateway credentials to collect information into a different account.</li>
<li><strong>Modifying a direct post.</strong> Modification of the form action or JavaScript code could send the payment information to an alternative server that harvests cardholder data.</li>
<li><strong>Modifying an iframe.</strong> Modification of iframe code could be set to load a payment form from another website acting as a man-in-the-middle attack.</li>
<li><strong>Modifying a Hosted Payment Page.</strong> Modification of the hosted payment page URL could redirect a customer to an alternative version of the payment site.</li>
</ul>
<p>For specific ways that the Drupal application can be compromised, please visit DrupalSecurityReport.org.</p>
<h2>Locking Down Drupal for PCI SAQ D</h2>
<p>This is a non-exhaustive list of ways in which you can harden security at the Drupal level.</p>
<ul>
<li><strong>PCI ASV Scans.</strong> The results will alert you to areas of the site you may have looked over.</li>
<li><strong>Hacked module.</strong> This module will download a copy of each module and run a diff against them to ensure the code matches what was provided from Drupal.org.</li>
<li><strong>MD5 Check module.</strong> This module will run a checksum of each module and provide a security alert if anything has changed.</li>
<li><strong>Deploy full codebase with each release.</strong> This will ensure that any tampered files get replaced.</li>
<li><strong>Storing security configurations in code.</strong> Example: one can force secure pages to always be enabled by adding its system variables into the settings.php.</li>
<li><strong>Removing credentials from settings.php.</strong> One can include a settings.local.php file within settings.php to ensure that sensitive information is not distributed.</li>
<li><strong>Security Updates.</strong> Always keep up with the Drupal Security Advisories, which are released every Wednesday.</li>
<li><strong>Paranoia and Security Review Modules.</strong> These modules provide and review your Drupal configurations to ensure they adhere to best security practices.</li>
<li><strong>Security Kit Module.</strong> This module provides Drupal with various security hardening options. This lets you mitigate the risks of exploitation of different web application vulnerabilities.</li>
<li><strong>Holistic approach to compliance.</strong> Consider PCI DSS compliance as part of the bigger picture of your organization’s compliance requirements. Often organizations will have overlapping compliance requirements from standards such as NIST 800-53, ISO27002, HIPAA, FISMA, and others.</li>
</ul>
<h2>Drupal’s Security Team</h2>
<p>The Drupal security team is a volunteer group of developers who are passionate about keeping Drupal secure. You can follow them by visiting <a href="http://drupal.org/security">http://drupal.org/security</a>, subscribing to their RSS feeds, joining their group on groups.drupal.org, (see <a href="https://www.drupal.org/security-team">https://www.drupal.org/security-team</a> for more information).</p>
<h2>Final Message to Drupal Developers</h2>
<p>The security of a website largely depends on the quality of your work and your attention to detail. Whenever creating custom code, be sure that it complies with best practices. When using other people’s code, be sure to review it to ensure that it is also stable, secure, and community supported. When configuring a site, be sure to leverage modules like Security Review and Coder Review to ensure you are not accidentally opening up a security hole.</p>
<p>While you are not necessarily the one responsible for achieving and maintaining a site’s PCI compliance, you are responsible for educating yourself about it as well as notifying your employer and/or client when their decisions will impact the site’s overall security posture.</p>
<h2>Final Message to Drupal Shops</h2>
<p>Your responsibility is to protect your business. It is up to you to be exceedingly clear with respect to who is responsible for PCI compliance before, during, and after a site launch. Any service agreements should also include language regarding each party's PCI-DSS compliance responsibilities as well as links to reference materials that provide clients with a means of understanding the implications of these responsibilities.</p>
<p>This conversation will ultimately lead to a greater focus on security for all delivered websites. This not only can be a valuable upsell to current clients, but it can become a competitive advantage and even attract new business.</p>
<p>Finally, if you are a service provider that offers hosting or managed services for a site that handles credit cards and you agree to take on the PCI DSS responsibilities for your clients, you must comply with all PCI DSS requirements and complete SAQ D as a Service Provider, no matter what shopping cart solutions your clients have implemented.</p>
<h2>Final Message to Site Owners</h2>
<p>Your decisions about how you handle credit card data affect the livelihood of your business. While achieving PCI compliance may seem cost prohibitive, the reality is that a security breach could potentially bankrupt a small to medium-size business. Beyond that, the decisions you make also affect the credit of your customers because identity theft can cost thousands of dollars and take months to years to reconcile. Finally, there can be legal and PR consequences that occur as a result of a breach, further affecting your ability to sustain and grow your business.</p>
<h2>Next Steps</h2>
<p>Getting started can seem like a daunting task. However, breaking it down into small steps can make this a very manageable process.</p>
<ul>
<li><strong>Assess current setup.</strong> Questions to ask: Do you have a site already or are you starting from scratch? Are you using Drupal Commerce or Ubercart? Are you willing to migrate between them if necessary? Are you willing to outsource completely if sales and/or budgets cannot justify an alternative?</li>
<li><strong>Assess requirements.</strong> Questions to ask: Which is more important: cost or features? Do you need any complex interactions or feature sets during checkout? Or can you suffice with using a PayPal button and calling it a day?</li>
<li><strong>Reduce CDE Scope.</strong> Questions to ask: Is it possible to segment your network so that non-related servers are not maintained behind the same stateful firewalls as your eCommerce servers?</li>
<li><strong>Assess options.</strong> Now that you know what you have to work with and what the goals are, evaluate the cost/effort/risk of 2-3 scenarios.</li>
<li><strong>Decide on a method.</strong> Ultimately the business owner must pick a specific method balancing all the factors.</li>
<li><strong>Determine responsibilities.</strong> Once a decision is made, it’s required to clearly articulate who is responsible for what at each stage in the development cycle. There should also be clear sign off points established.</li>
<li><strong>Complete the relevant SAQ:</strong> The Self-Assessment Questionnaire is your key tool for performing a gap analysis and determining whether you are currently compliant.</li>
<li><strong>Prioritize PCI responsibilities.</strong> Becoming compliant can take a long time, but some responsibilities are more critical than others. The PCI industry created a document titled The Prioritized Approach to Pursue PCI DSS Compliance, which gives clear guidance on what should be done first to minimize risk during the entire process.</li>
<li><strong>Create plan and execute.</strong> Once you’ve identified what needs to be done and created a plan, it’s time to make consistent progress toward checking off items on the list.</li>
</ul>
<p>At any stage, you also may wish to hire a professional to help expedite the process and ensure that your plan is sound. Specifically, you would want to locate a QSA (Qualified Security Assessor), which are organizations that have been qualified by the PCI Council to have their employees assess compliance to the PCI DSS standard.</p>
<h2>Top 8 Drupal PCI Compliance Myths</h2>
<p><em>Author’s Note: This is a trimmed down summary from a longer article<sup><a href="#cite-20">20</a></sup>.</em></p>
<h3>Drupal is PCI compliant.</h3>
<p>This is incorrect by itself because Drupal is only one piece of the cardholder data environment (CDE). However, when Drupal is up to date with all of its security patches and when it’s configured properly to meet its portion of the PCI-DSS requirements, then Drupal is PCI <em>compatible</em>. PCI compliance can only be achieved at the CDE level once each component of the CDE has met all the requirements within their area of responsibility.</p>
<h3>Ubercart and Drupal Commerce are PCI compliant.</h3>
<p>This is also incorrect in and of itself simply because it’s a component of a larger system. However, the particular payment method chosen within each eCommerce solution can greatly influence how easy it is to become compliant.</p>
<h3>I use HTTPS, therefore my Drupal website is secure.</h3>
<p>Securing the transaction from the Drupal application to the payment gateway addresses only one of the 12 sections of the PCI standard. There are a significant number of other vulnerabilities that can exist at the server, network, and application level.</p>
<h3>I can store numbers/CCV.</h3>
<p>Storing the 3-4 digit security code is never allowed under any circumstances. Storing the full credit card number at the Drupal layer is extremely risky and should not be done without a considerable amount of attention and expertise.</p>
<h3>Shared-management Methods are 100% foolproof.</h3>
<p>This is false because modifying code at the Drupal application layer can result in a man-in-the-middle attack, the introduction of a keylogger, and other exploits.</p>
<h3>I can achieve PCI compliance using shared hosting.</h3>
<p>Shared hosting is simply not secure enough for PCI SAQ A-EP or D because there are simply too many users (both customers and employees of the hosting company) that have access to the server and you simply do not have enough control in locking down the system. Technically an iframe solution (SAQ A compatible) could get by on shared hosting, but we strongly recommend against it.</p>
<h3>I can achieve PCI compliance using cloud hosting.</h3>
<p>As of July 2014, we are seeing a growing number of reputable hosting providers introducing PCI compliant cloud hosting options. However, you must do your due diligence before immediately accepting their claims. As part of the version 3.0 standard, each party must explicitly agree to the particular sections of the standard that they assume responsibility. Not only should the cloud hosting provider explicitly state that their solution is PCI compliant and they will assume the responsibilities within their jurisdiction, but the cloud hosting provider should also be able to provide documentation (upon request) to validate their claims.</p>
<p>Regardless of if you choose to use a cloud or dedicated hardware solution, you must use a PCI DSS certified service provider if you are outsourcing hosting for eCommerce servers.</p>
<h3>I can set it and forget it.</h3>
<p>PCI compliance is not a single event that is checked off a list and never revisited. Rather, it’s a continually changing state. If a security exploit is discovered and disclosed for Drupal or the OS running the server Drupal is hosted on, then your site is not PCI compliant. Therefore PCI compliance is a continual process that needs to be maintained through vigilance.</p>
<h2>Summary</h2>
<p>Drupal makes it trivial to get an eCommerce site up in minutes, PCI compliance can take months if not setup correctly. And while PCI compliance has many nuances and complexities, it’s a mandatory requirement for the 10’s of thousands of reported Drupal eCommerce installations. Small, incremental steps in learning and implementation are key in achieving and maintaining compliance, protecting your business, customers, and development.</p>
<h2>Sponsors</h2>
<h3>AppliedTrust</h3>
<p><img src="images/sponsors/logo-appliedtrust.png" alt="" title="AppliedTrust Logo"></p>
<p>AppliedTrust provides IT infrastructure, security, and opensource consulting services. The company serves clients in a variety of industries, including healthcare, financial services, recreation and government. AppliedTrust is a PCI DSS Qualified Security Assessor.</p>
<p><a href="http://www.appliedtrust.com">http://www.appliedtrust.com</a></p>
<h3>Card.com</h3>
<p><img src="images/sponsors/logo-card.png" alt="" title="Card.com"></p>
<p>CARD.com creates Fair, Fashionable and Fun online payments solutions. CARD.com prepaid Visa cards are your connection to what you love. With FDIC insured accounts, ATM acces, smartphone apps and online tools to manage your account, CARD.com provides full service payment solutions. We are always looking for great brands with large communities looking to extend their connection via branded debit cards or other interesting ideas in the payments industry. Our team is growing, see CARD.com/careers.</p>
<p><a href="https://www.card.com">https://www.card.com</a></p>
<h3>CrossFunctional</h3>
<p><img src="images/sponsors/logo-crossfunctional.png" alt="" title="CrossFunctional"></p>
<p>CrossFunctional is a Sydney-based online solutions provider with proven expertise in Drupal, WordPress and other open source systems. In operation since 2008, we have grown to provide services at multiple levels and across multiple industries.</p>
<p><a href="http://crossfunctional.net">http://crossfunctional.net</a></p>
<h3>Commerce Guys</h3>
<p><img src="images/sponsors/logo-commerce-guys.png" alt="" title="Commerce Guys"></p>
<p>Commerce Guys is the software company behind Drupal Commerce, the eCommerce solution that capitalizes on the virtues and power of Drupal, the premier open-source content management system. We focus our knowledge and expertise on providing online merchants with the powerful, responsive, innovative eCommerce solutions they need to thrive.</p>
<p><a href="http://commerceguys.com">http://commerceguys.com</a></p>
<h3>NEWMEDIA</h3>
<p><img src="images/sponsors/logo-newmedia.png" alt="" title="NEWMEDIA"></p>
<p>We love web design, whatever you call it nowadays. UI/UX, interface design, you name it. Our clients are not just in Denver, CO, but also all over the USA; many are even overseas. We don't just make websites look pretty, though; we develop complicated websites in-house as well. Yes, we may well be the most established provider of Drupal web development services in Colorado.</p>
<p><a href="http://www.newmediadenver.com">http://www.newmediadenver.com</a></p>
<h3>Townsend Security</h3>
<p><img src="images/sponsors/logo-townsend-security.png" alt="" title="Townsend Security"></p>
<p>Townsend Security creates encryption and key management solutions that help organizations meet compliance requirements and mitigate the risk of data breaches. Over 3,000 companies worldwide trust Townsend Security’s NIST and FIPS 140-2 validated solutions to meet the requirements in PCI DSS, HIPAA, FISMA, and other regulations. Learn more about <a href="http://www.townsendsecurity.com/drupal?utm_campaign=Drupal%20PCI%20White%20Paper&utm_source=Drupal%20PCI%20White%20Paper">Key Connection for Drupal</a> or join our <a href="http://info.townsendsecurity.com/developer-partner-request?utm_campaign=Drupal%20PCI%20White%20Paper&utm_source=Drupal%20PCI%20White%20Paper">Drupal Developer program</a>.</p>
<p><a href="http://www.townsendsecurity.com">http://www.townsendsecurity.com</a></p>
<h3>Hosted PCI</h3>
<p><img src="images/sponsors/logo-hosted-pci.png" alt="" title="Hosted PCI"></p>
<p>HostedPCI eliminates the risk associated with handling credit cards by delivering state of the art transaction processing technology that achieves 100% Continuous PCI Compliance, quickly and painlessly. HostedPCI allows merchants of any size to guarantee total protection against credit card theft for their online checkout, call center and mobile transactions.. It’s fast & easy to implement, and extremely cost-effective compared to traditional methods.</p>
<p><a href="http://www.hostedpci.com">http://www.hostedpci.com</a></p>
<h3>Copperly</h3>
<p><img src="images/sponsors/logo-copperly.png" alt="" title="Copperly"></p>
<p>Copperly educates businesses in the Drupal community and beyond about cost-effective credit card processing options. We work with businesses to identify the pricing model and implementation best suited to their needs.</p>
<p><a href="http://www.copperly.com">http://www.copperly.com</a></p>
<h2>References</h2>
<ol>
<li><a name="cite-1"></a><a href="http://goo.gl/s6e7F">US Census Bureau News CB13-78</a> - <a href="http://goo.gl/s6e7F">http://goo.gl/s6e7F</a></li>
<li><a name="cite-2"></a><a href="http://goo.gl/DlMff">Global eCommerce sales will top $1.25 trillion by 2013</a> - <a href="http://goo.gl/DlMff">http://goo.gl/DlMff</a></li>
<li><a name="cite-3"></a><a href="http://goo.gl/2uAoo">Introduction to the E-commerce & Internet Business</a> - <a href="http://goo.gl/2uAoo">http://goo.gl/2uAoo</a></li>
<li><a name="cite-4"></a><a href="http://goo.gl/lEbTH">Drupal Usage trends</a> - <a href="http://goo.gl/lEbTH">http://goo.gl/lEbTH</a></li>
<li><a name="cite-5"></a><a href="http://goo.gl/IE0Fb">PCI DSS - Glossary of Terms, Abbreviations, and Acronyms</a> - <a href="http://goo.gl/IE0Fb">http://goo.gl/IE0Fb</a></li>
<li><a name="cite-6"></a><a href="http://goo.gl/EoEp6">2010 Annual Study: U.S. Cost of a Data Breach</a> - <a href="http://goo.gl/EoEp6">http://goo.gl/EoEp6</a></li>
<li><a name="cite-7"></a><a href="http://goo.gl/t0lQT">Heartland Data Breach: MasterCard, Visa Impose Hefty Fines</a> - <a href="http://goo.gl/t0lQT">http://goo.gl/t0lQT</a></li>
<li><a name="cite-8"></a><a href="http://goo.gl/aKjIOI">Data-breach costs take toll on Target profit</a> - <a href="http://goo.gl/aKjIOI">http://goo.gl/aKjIOI</a></li>
<li><a name="cite-9"></a><a href="http://goo.gl/aGYbq">In Data Leaks, Culprits Often Are Mom, Pop</a> - <a href="http://goo.gl/aGYbq">http://goo.gl/aGYbq</a></li>
<li><a name="cite-10"></a><a href="http://goo.gl/Um5cE">Sony PlayStation suffers massive data breach</a> - <a href="http://goo.gl/Um5cE">http://goo.gl/Um5cE</a></li>
<li><a name="cite-11"></a><a href="http://goo.gl/Z1lUr">Official PCI Security Standards Council Site</a> - <a href="http://goo.gl/Z1lUr">http://goo.gl/Z1lUr</a></li>
<li><a name="cite-12"></a><a href="http://goo.gl/FzzH6">Approved Scanning Vendors</a> - <a href="http://goo.gl/FzzH6">http://goo.gl/FzzH6</a></li>
<li><a name="cite-13"></a><a href="http://goo.gl/H5jOK">Navigation PCI DSS</a> - <a href="http://goo.gl/H5jOK">http://goo.gl/H5jOK</a></li>
<li><a name="cite-14"></a><a href="http://goo.gl/YnjkJZ">New! More! A First Look at the PCI DSS 3.0 SAQs</a> - <a href="http://goo.gl/YnjkJZ">http://goo.gl/YnjkJZ</a></li>
<li><a name="cite-15"></a><a href="http://goo.gl/R21rw">Information Supplement: PCI DSS E-commerce Guidelines</a> - <a href="http://goo.gl/R21rw">http://goo.gl/R21rw</a></li>
<li><a name="cite-16"></a><a href="http://goo.gl/V8ZrVF">Understanding the SAQs for PCI DSS v3.0</a> - <a href="http://goo.gl/V8ZrVF">http://goo.gl/V8ZrVF</a></li>
<li><a name="cite-17"></a><a href="http://goo.gl/XDBzkz">Version 3.0 Change Highlights</a> - <a href="http://goo.gl/XDBzkz">http://goo.gl/XDBzkz</a></li>
<li><a name="cite-18"></a><a href="http://goo.gl/7nR1Gt">Summary of Changes from PCI DSS Version 2.0 to 3.0</a> - <a href="http://goo.gl/7nR1Gt">http://goo.gl/7nR1Gt</a></li>
<li><a name="cite-19"></a><a href="http://goo.gl/rvOfz">Integrate Authorize.net (Hosted) CIM</a> - <a href="http://goo.gl/rvOfz">http://goo.gl/rvOfz</a></li>
<li><a name="cite-20"></a><a href="http://goo.gl/phZcg1">Top 12 Drupal PCI Compliance Myths</a> - <a href="http://goo.gl/phZcg1">http://goo.gl/phZcg1</a></li>
</ol>
<h2>Footnotes</h2>
<ul>
<li><a name="footnote-A"></a>A. If you qualify as a service provider (SP), you must be SAQ D-SP compliant and you must undergo a full ROC audit by a qualified QSA. Basically, services providers are treated the same as being Level 1, no matter how small of a hosting shop you are.</li>
<li><a name="footnote-B"></a>B. Be advised that a simple matter of handing transactions via fax, terminal, and email in addition to your Drupal site can and often will increase your CDE scope.</li>
<li><a name="footnote-C"></a>C. It should be noted that the stigma against hosted payment pages continues to fade away as it becomes a more common and accepted form of transaction, particularly in the EU.</li>
<li><a name="footnote-D"></a>D. Visit <a href="http://www.visa.com/splisting">http://www.visa.com/splisting</a> to confirm whether or not a vendor is a valid Service Provider.</li>
</ul>
<h2>Reviewers</h2>
<p>The authors of this paper would like to thank the following individuals for reviewing the paper and providing feedback to improve its accuracy and utility. In alphabetical order: Ryan Cross (rcross), Robert Douglass (robertdouglass), Trent Hein (thein), Michael Hess (mlhess), Dave Long (longwave), Alex Knoll (arknoll), Ryan Szrama (rszrama), Peter Wolanin (pwolanin).</p>
<h2>Appendix</h2>
<h3>Additional Resources</h3>
<p>The following is a list of documents that can be found directly from the <a href="https://www.pcisecuritystandards.org/">Official PCI Security Standards Council Site</a>:</p>
<ul>
<li><a href="http://goo.gl/sH1Jx">PCI Standards - All Documents</a> - <a href="http://goo.gl/sH1Jx">http://goo.gl/sH1Jx</a></li>
<li><a href="http://goo.gl/lpnno">Navigation PCI DSS</a> - <a href="http://goo.gl/lpnno">http://goo.gl/lpnno</a></li>
<li><a href="http://goo.gl/Z3UZ7">PCI DSS Quick Reference Guide</a> - <a href="http://goo.gl/Z3UZ7">http://goo.gl/Z3UZ7</a></li>
<li><a href="http://goo.gl/SFZtL">The Prioritized Approach to Pursue PCI DSS Compliance</a> - <a href="http://goo.gl/SFZtL">http://goo.gl/SFZtL</a></li>
<li><a href="http://goo.gl/TVtxS">Ten Common Myths of PCI SSC</a> - <a href="http://goo.gl/TVtxS">http://goo.gl/TVtxS</a></li>
<li><a href="http://goo.gl/ab348">PCI DSS Glossary of Terms, Abbreviations, and Acronyms</a> - <a href="http://goo.gl/ab348">http://goo.gl/ab348</a></li>
<li><a href="http://goo.gl/rQbVs">PCI Security Standards Council - Overview</a> - <a href="http://goo.gl/rQbVs">http://goo.gl/rQbVs</a></li>
<li><a href="http://goo.gl/RX0qZ">PCI DSS Self-Assessment Questionnaire (SAQ) Instructions and Guidelines</a> - <a href="http://goo.gl/RX0qZ">http://goo.gl/RX0qZ</a></li>
<li><a href="http://goo.gl/HCvY1">PCI DSS SAQ C V2.0</a> - <a href="http://goo.gl/HCvY1">http://goo.gl/HCvY1</a></li>
</ul>
<h3>Disclaimer</h3>
<p>The authors are not lawyers and the contents of this document do not constitute legal advice. The authors are not responsible or liable for any loss or damages you and/or your business may incur as a result of reading this document. Everyone’s PCI compliance needs will be unique to their specific configurations and business needs. It is up to the reader to due their own due diligence and keep up with the latest information found at the PCI Security Standards Council Site.</p>
<h3>License</h3>
<p>This document is Copyright 2013-2014 Rick Manelius, Greg Knaddison, and Ned McClain—CreativeCommons Attribution-No Derivative Works 3.0 Unported <a href="http://creativecommons.org/licenses/by-nd/3.0">http://creativecommons.org/licenses/by-nd/3.0</a> <a href="http://drupalpcicompliance.org/">http://drupalpcicompliance.org/</a>. You may share and re-post the PDF on other sites without modification as long as you clearly link to <a href="http://drupalpcicompliance.org/">http://drupalpcicompliance.org/</a>.</p>
</body>
</html>