PCI FAQs - Revision history

Dohtur: /* What if a merchant refuses to cooperate? */

2013-10-10T09:04:12Z

‎What if a merchant refuses to cooperate?

Dohtur: /* See also */

2013-08-13T10:59:05Z

‎See also

Dohtur: /* See also */

2013-08-13T10:56:43Z

‎See also

Dohtur at 09:14, 13 August 2013

2013-08-13T09:14:53Z

Dohtur at 09:08, 13 August 2013

2013-08-13T09:08:19Z

Admin: /* What does a small-to-medium sized business (Level 4 merchant) have to do in order to satisfy the PCI requirements? */

2011-07-07T12:44:24Z

‎What does a small-to-medium sized business (Level 4 merchant) have to do in order to satisfy the PCI requirements?

Admin: /* Is it allowed to store CVC2/CVV2 codes? */

2011-07-07T12:39:09Z

‎Is it allowed to store CVC2/CVV2 codes?

Admin: /* What are the PCI compliance ‘levels’ and how are they determined? */

2011-06-30T12:29:30Z

‎What are the PCI compliance ‘levels’ and how are they determined?

Admin at 10:56, 23 June 2011

2011-06-23T10:56:13Z

Admin: /* Do states have laws that requiring data breach notifications to the affected parties? */

2011-06-23T10:55:56Z

‎Do states have laws that requiring data breach notifications to the affected parties?

@@ Line 147: / Line 147: @@
 ==What if a merchant refuses to cooperate?==
-PCI is not, in itself, a law. The standard was created by the major card brands such as Visa, MasterCard, Discover, AMEX, and JCB. At their acquirers/service providers discretion, merchants that do not comply with PCI DSS may be subject to fines, card replacement costs, costly forensic audits, brand damage, etc., should a breach event occur. For a little upfront effort and cost to comply with PCI, you greatly help reduce your risk from facing these extremely unpleasant and costly consequences.
+PCI is not, in itself, a law. The standard was created by the major card brands such as Visa, MasterCard, Discover, American Express, and JCB. At their acquirers/service providers discretion, merchants that do not comply with PCI DSS may be subject to fines, card replacement costs, costly forensic audits, brand damage, etc., should a breach event occur. For a little upfront effort and cost to comply with PCI, you greatly help reduce your risk from facing these extremely unpleasant and costly consequences.
 ==If I’m running a business from my home, am I a serious target for hackers?==

@@ Line 168: / Line 168: @@
 * [[X-Cart:PCI-DSS | X-Cart:PCI DSS]]
-* [[X-Payments:PCI_DSS_implementation_guide | X-Payments:PCI DSS implementation guide]]
+* [[X-Cart_Payments:PCI_DSS_implementation_guide | X-Cart Payments:PCI DSS implementation guide]]
 * [http://www.braintreepaymentsolutions.com/assets/308/PCI-Compliance.pdf Braintree PCI DSS compliance Quick Guide]
 [[Category:PCI DSS]]

@@ Line 168: / Line 168: @@
 * [[X-Cart:PCI-DSS | X-Cart:PCI DSS]]
-* [[X-Payments:PA-DSS_implementation_guide | X-Payments:PA-DSS implementation guide]]
+* [[X-Payments:PCI_DSS_implementation_guide | X-Payments:PCI DSS implementation guide]]
 * [http://www.braintreepaymentsolutions.com/assets/308/PCI-Compliance.pdf Braintree PCI DSS compliance Quick Guide]
 [[Category:PCI DSS]]

← Older revision		Revision as of 09:14, 13 August 2013
Line 171:		Line 171:
	* [http://www.braintreepaymentsolutions.com/assets/308/PCI-Compliance.pdf Braintree PCI DSS compliance Quick Guide]		* [http://www.braintreepaymentsolutions.com/assets/308/PCI-Compliance.pdf Braintree PCI DSS compliance Quick Guide]

−	[[Category:PCI-DSS]]	+	[[Category:PCI DSS]]

@@ Line 1: / Line 1: @@
 ==   What is PCI?  ==
-The Payment Card Industry Data Security Standard (PCI DSS) is a set of requirements designed to ensure that ALL companies that process, store or transmit credit card information maintain a secure environment. Essentially any merchant that has a Merchant ID (MID). The Payment Card Industry Security Standards Council (PCI SSC) was launched on September 7, 2006 to manage the ongoing evolution of the Payment Card Industry (PCI) security standards with focus on improving payment account security throughout the transaction process. The PCI DSS is administered and managed by the PCI SSC (www.pcisecuritystandards.org), an independent body that was created by the major payment card brands (Visa, MasterCard, American Express, Discover and JCB.). It is important to note, the payment brands and acquirers are responsible for enforcing compliance, not the PCI council. A copy of the PCI DSS is available [[X-Cart:PCI-DSS|here]].
+The Payment Card Industry Data Security Standard (PCI DSS) is a set of requirements designed to ensure that ALL companies that process, store or transmit credit card information maintain a secure environment. Essentially any merchant that has a Merchant ID (MID). The Payment Card Industry Security Standards Council (PCI SSC) was launched on September 7, 2006 to manage the ongoing evolution of the Payment Card Industry (PCI) security standards with focus on improving payment account security throughout the transaction process. The PCI DSS is administered and managed by the PCI SSC (www.pcisecuritystandards.org), an independent body that was created by the major payment card brands (Visa, MasterCard, American Express, Discover and JCB.). It is important to note, the payment brands and acquirers are responsible for enforcing compliance, not the PCI council. A copy of the PCI DSS is available [[X-Cart:PCI DSS|here]].
 ==To whom does PCI apply?==
@@ Line 122: / Line 122: @@
 * New PCI Level 4 merchants (including new locations of existing relationships) may not use vulnerable payment application versions – those that store prohibited cardholder data. January 1, 2008
-* New PCI Level 4 merchants using third-party payment software must be either PCI DSS-compliant or use PA-DSS validated compliant payment applications. October 1, 2008
+* New PCI Level 4 merchants using third-party payment software must be either PCI DSS compliant or use PA-DSS validated compliant payment applications. October 1, 2008
 * ALL PCI Level 4 merchants (new and existing) using third-party software must use validated applications. July 1, 2010
@@ Line 163: / Line 163: @@
 ==Is it allowed to store CVC2/CVV2 codes?==
-No, PCI-DSS forbids storage of sensitive authentication data including CVC2/CVV2. Please refer to [https://www.pcisecuritystandards.org/pdfs/pci_fs_data_storage.pdf PCI Data Storage Do's and Don'ts] for the details.
+No, PCI DSS forbids storage of sensitive authentication data including CVC2/CVV2. Please refer to [https://www.pcisecuritystandards.org/pdfs/pci_fs_data_storage.pdf PCI Data Storage Do's and Don'ts] for the details.
 ==See also==
-* [[X-Cart:PCI-DSS | X-Cart:PCI-DSS]]
+* [[X-Cart:PCI-DSS | X-Cart:PCI DSS]]
 * [[X-Payments:PA-DSS_implementation_guide | X-Payments:PA-DSS implementation guide]]
-* [http://www.braintreepaymentsolutions.com/assets/308/PCI-Compliance.pdf Braintree PCI-DSS compliance Quick Guide]
+* [http://www.braintreepaymentsolutions.com/assets/308/PCI-Compliance.pdf Braintree PCI DSS compliance Quick Guide]
 [[Category:PCI-DSS]]

@@ Line 46: / Line 46: @@
 To satisfy the requirements of PCI, a merchant must complete the following steps:
-. Identify your Validation Type as defined by PCI DSS – see below . This is used to determine which Self Assessment Questionnaire is appropriate for your business.
+'''1.''' Identify your Validation Type as defined by PCI DSS – see below . This is used to determine which Self Assessment Questionnaire is appropriate for your business.
 : [[Image:Pci_faqs_saq.gif|515px|Image:Pci faqs saq.gif]]]
-. Complete the Self-Assessment Questionnaire according to the instructions in the Self- Assessment Questionnaire Instructions and Guidelines.
+'''2.''' Complete the Self-Assessment Questionnaire according to the instructions in the Self- Assessment Questionnaire Instructions and Guidelines.
-. Complete and obtain evidence of a passing vulnerability scan with a PCI SSC Approved Scanning Vendor (ASV). Note: scanning does not apply to all merchants. It is required for Validation Type 4 and 5 – those merchants with external facing IP addresses. Basically if you electronically store cardholder information or if your processing systems have any internet connectivity, a quarterly scan by an approved scanning vendor is required.
+'''3.''' Complete and obtain evidence of a passing vulnerability scan with a PCI SSC Approved Scanning Vendor (ASV). Note: scanning does not apply to all merchants. It is required for Validation Type 4 and 5 – those merchants with external facing IP addresses. Basically if you electronically store cardholder information or if your processing systems have any internet connectivity, a quarterly scan by an approved scanning vendor is required.
-. Complete the relevant Attestation of Compliance in its entirety.
+'''4.''' Complete the relevant Attestation of Compliance in its entirety.
-. Submit the SAQ, evidence of a passing scan (if applicable), and the Attestation of Compliance, along with any other requested documentation, to your acquirer.
+'''5.''' Submit the SAQ, evidence of a passing scan (if applicable), and the Attestation of Compliance, along with any other requested documentation, to your acquirer.
 ==I’m a small merchant with very few card transactions; do I need to be compliant with PCI DSS?==

@@ Line 15: / Line 15: @@
 All merchant that stores, processes or transmits cardholder data must be compliant now. However, as a Level 4 merchant, you will have to refer to your merchant bank for their specific validation requirements and deadlines. All deadline enforcement will come from your merchant bank. You may also find more information on Visa’s Website: [http://usa.visa.com/download/merchants/payment_application_security_mandates.pdf http://usa.visa.com/download/merchants/payment_application_security_mandates.pdf].
-==What are the PCI compliance ‘levels’ and how are they determined?==
+==What are the PCI compliance levels and how are they determined?==
 All merchants will fall into one of the four merchant levels based on Visa transaction volume over a 12-month period. Transaction volume is based on the aggregate number of Visa transactions (inclusive of credit, debit and prepaid) from a merchant Doing Business As (‘DBA’). In cases where a merchant corporation has more than one DBA, Visa acquirers must consider the aggregate volume of transactions stored, processed or transmitted by the corporate entity to determine the validation level. If data is not aggregated, such that the corporate entity does not store, process or transmit cardholder data on behalf of multiple DBAs, acquirers will continue to consider the DBA’s individual transaction volume to determine the validation level.
@@ Line 21: / Line 21: @@
 '''Merchant levels as defined by Visa:'''
-{|
+{| class="prettytable"
-| align="center" | Level
+! Level
-| Description
+! Description
 |-
 | align="center" | 1
@@ Line 34: / Line 34: @@
 | Any merchant processing 20,000 to 1M Visa e-commerce transactions per year.
 |-
-| align="center" | '''4'''
+| align="center" | 4
-| '''Any merchant processing fewer than 20,000 Visa e-commerce transactions per year, and all other merchants -- regardless of acceptance channel -- processing up to 1M Visa transactions per year.'''
+| Any merchant processing fewer than 20,000 Visa e-commerce transactions per year, and all other merchants -- regardless of acceptance channel -- processing up to 1M Visa transactions per year.
 |}

← Older revision		Revision as of 10:56, 23 June 2011
Line 160:		Line 160:

	Absolutely. California is the catalyst for reporting data breaches to affected parties. The state implemented breach notification law in 2003 and there are now over 38 states that have similar laws in place. See [http://www.privacyrights.org/ http://www.privacyrights.org] for more detail on state laws.		Absolutely. California is the catalyst for reporting data breaches to affected parties. The state implemented breach notification law in 2003 and there are now over 38 states that have similar laws in place. See [http://www.privacyrights.org/ http://www.privacyrights.org] for more detail on state laws.
−

	==Is it allowed to store CVC2/CVV2 codes?==		==Is it allowed to store CVC2/CVV2 codes?==

← Older revision		Revision as of 10:55, 23 June 2011
Line 160:		Line 160:

	Absolutely. California is the catalyst for reporting data breaches to affected parties. The state implemented breach notification law in 2003 and there are now over 38 states that have similar laws in place. See [http://www.privacyrights.org/ http://www.privacyrights.org] for more detail on state laws.		Absolutely. California is the catalyst for reporting data breaches to affected parties. The state implemented breach notification law in 2003 and there are now over 38 states that have similar laws in place. See [http://www.privacyrights.org/ http://www.privacyrights.org] for more detail on state laws.
		+
		+
		+	==Is it allowed to store CVC2/CVV2 codes?==
		+
		+	No, PCI-DSS forbids storage of sensitive authentication data including CVC2/CVV2.

	==See also==		==See also==