Source: http://docplayer.net/16986289-Payment-card-industry-pci-data-security-standard.html
Timestamp: 2018-11-14 18:14:04
Document Index: 207094186

Matched Legal Cases: ['art 1', 'art 1', 'art 1', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 3', 'arts 3', 'art 2', 'art 4', 'art 4', 'art 3', 'art 3', 'art 3', 'art 3', 'art 3', 'art 4', 'art 4']

2 Section 1: Assessment Information Instructions for Submission This Attestation of Compliance must be completed as a declaration of the results of the service provider s assessment with the Payment Card Industry Data Security Standard Requirements and Security Assessment Procedures (PCI DSS). Complete all sections: The service provider is responsible for ensuring that each section is completed by the relevant parties, as applicable. Contact the requesting payment brand for reporting and submission procedures. Part 1. Service Provider and Qualified Security Assessor Information Part 1a. Service Provider Organization Information Company Name: Peak 10, Inc DBA (doing business as): Contact Name: David Kidd Title: Vice President of Governance, Risk, and Compliance ISA Name(s) (if applicable): Not applicable Title: Not applicable Telephone: Business Address: 8809 Lenox Pointe Drive, Suite G City: Charlotte State/Province: NC Country: USA Zip: URL: Part 1b. Qualified Security Assessor Company Information (if applicable) Company Name: BrightLine CPAs & Associates, Inc. Lead QSA Contact Name: Jim Van Horn Title: Senior Associate Telephone: ext Business Address: 1300 N. West Shore Blvd, Suite 240 City: Tampa State/Province: FL Country: USA Zip: URL: PCI Security Standards Council, LLC. All Rights Reserved. Page 1
3 Part 2. Executive Summary Part 2a. Scope Verification Services that were INCLUDED in the scope of the PCI DSS Assessment (check all that apply): Name of service(s) assessed: Data Center Operations and Managed Cloud Services Type of service(s) assessed: Hosting Provider: Applications / software Hardware Infrastructure / Network Physical space (co-location) Storage Web Security services 3-D Secure Hosting Provider Shared Hosting Provider Other Hosting (specify): Managed Services (specify): Systems security services IT support Physical security Terminal Management System Other services (specify): Payment Processing: POS / card present Internet / e-commerce MOTO / Call Center ATM Other processing (specify): Account Management Fraud and Chargeback Payment Gateway/Switch Back-Office Services Issuer Processing Prepaid Services Billing Management Loyalty Programs Records Management Clearing and Settlement Merchant Services Tax/Government Payments Network Provider Others (specify): Note: These categories are provided for assistance only, and are not intended to limit or predetermine an entity s service description. If you feel these categories don t apply to your service, complete Others. If you re unsure whether a category could apply to your service, consult with the applicable payment brand PCI Security Standards Council, LLC. All Rights Reserved. Page 2
4 Services that are provided by the service provider but were NOT INCLUDED in the scope of the PCI DSS Assessment (check all that apply): Name of service(s) not assessed: Managed Services other than Cloud Type of service(s) not assessed: Hosting Provider: Applications / software Hardware Infrastructure / Network Physical space (co-location) Storage Web Security services 3-D Secure Hosting Provider Shared Hosting Provider Other Hosting (specify): Managed Services (specify): Systems security services IT support Physical security Terminal Management System Other services (specify): Payment Processing: POS / card present Internet / e-commerce MOTO / Call Center ATM Other processing (specify): Account Management Fraud and Chargeback Payment Gateway/Switch Back-Office Services Issuer Processing Prepaid Services Billing Management Loyalty Programs Records Management Clearing and Settlement Merchant Services Tax/Government Payments Network Provider Others (specify): Provide a brief explanation why any checked services were not included in the assessment: Peak 10 customers have the ability to administer their own guest systems so while Peak 10 may perform these services, the customer could potentially undo any of the configuration changes PCI Security Standards Council, LLC. All Rights Reserved. Page 3
5 Part 2b. Description of Payment Card Business Describe how and in what capacity your business stores, processes, and/or transmits cardholder data. Describe how and in what capacity your business is otherwise involved in or has the ability to impact the security of cardholder data. Not applicable, for the purposes of this assessment, Peak 10 did not process or maintain cardholder data and has no logical access to any customer system that may contain cardholder data. Peak 10 provides colocation and cloud services to clients. Peak 10 s colocation services allow clients to rent server rack space for server and infrastructure components. All configuration and management of the systems is the responsibility of the clients. Peak 10 provides physical security, electricity, environmental controls, and Internet connectivity only. Some of these controls fall under PCI compliance. Cloud computing services allow clients to maintain and access server and infrastructure components in a dedicated virtual environment in Peak 10 data centers. Peak 10 provides supporting infrastructure to clients including all the services provided in the colocation services and adds secure remote connections and management of hypervisors and associated hardware. Customers are still responsible for managing their own systems. Part 2c. Locations List types of facilities (for example, retail outlets, corporate offices, data centers, call centers, etc.) and a summary of locations included in the PCI DSS review. Type of facility: Number of facilities of this type Example: Retail outlets 3 Boston, MA, USA Location(s) of facility (city, country): Data Centers 25 (Atlanta I and II) Norcross, GA USA (Atlanta III) Alpharetta, GA USA (Charlotte I, II, and III) Charlotte, NC USA (Charlotte IV) Charlotte NC USA (Cincinnati I) Hamilton, OH USA (Jacksonville I and II) Jacksonville FL USA (Louisville II and III) Louisville, KY USA (Nashville I and IV) Brentwood, TN USA (Nashville II, and III) Franklin, TN USA (Raleigh I and II) Morrisville, NC USA PCI Security Standards Council, LLC. All Rights Reserved. Page 4
6 (Richmond I and II) Richmond, VA USA (South Florida I and II) Fort Lauderdale, FL USA (Tampa I and II) Tampa FL USA (Tampa III) Tampa FL Part 2d. Payment Applications Does the organization use one or more Payment Applications? Yes No Provide the following information regarding the Payment Applications your organization uses: Payment Application Name Version Number Application Vendor Is application PA-DSS Listed? PA-DSS Listing Expiry date (if applicable) Yes No Yes No Yes No Part 2e. Description of Environment Provide a high-level description of the environment covered by this assessment. For example: Connections into and out of the cardholder data environment (CDE). Critical system components within the CDE, such as POS devices, databases, web servers, etc., and any other necessary payment components, as applicable. Management infrastructure utilized to manage customer cloud environments which may or may not store, process, or transmit cardholder data. Additionally, colocation services for customers. Peak 10 utilizes Fortigate firewalls, Windows servers, and VMware ESXi servers to manage the cloud infrastruture Does your business use network segmentation to affect the scope of your PCI DSS environment? (Refer to Network Segmentation section of PCI DSS for guidance on network segmentation) Yes No Part 2f. Third-Party Service Providers Does your company have a relationship with one or more third-party service providers (for example, gateways, payment processors, payment service providers (PSP), web-hosting companies, airline booking agents, loyalty program agents, etc.) for the purpose of the services being validated? Yes No If Yes: Type of service provider: BAE Systems Description of services provided: Intrusion Detection / Prevention Monitoring and Management PCI Security Standards Council, LLC. All Rights Reserved. Page 5
7 Centralized Log Management and Monitoring File Integrity Monitoring Note: Requirement 12.8 applies to all entities in this list PCI Security Standards Council, LLC. All Rights Reserved. Page 6
8 Part 2g. Summary of Requirements Tested For each PCI DSS Requirement, select one of the following: Full The requirement and all sub-requirements of that requirement were assessed, and no subrequirements were marked as Not Tested or Not Applicable in the ROC. Partial One or more sub-requirements of that requirement were marked as Not Tested or Not Applicable in the ROC. None All sub-requirements of that requirement were marked as Not Tested and/or Not Applicable in the ROC. For all requirements identified as either Partial or None, provide details in the Justification for Approach column, including: Details of specific sub-requirements that were marked as either Not Tested and/or Not Applicable in the ROC Reason why sub-requirement(s) were not tested or not applicable Note: One table to be completed for each service covered by this AOC. Additional copies of this section are available on the PCI SSC website. Name of Service Assessed: Data Center Operations and Managed Cloud Services PCI DSS Requirement Requirement 1: Requirement 2: Requirement 3: Requirement 4: Full Partial None Details of Requirements Assessed Justification for Approach (Required for all Partial and None responses. Identify which sub-requirements were not tested and the reason.) Peak 10 customers were responsible for cardholder data flow diagrams No insecure services were identified No wireless connections to the environment Peak 10 does not store cardholder data No wireless connections to the environment No wireless connections to the enviornment All of requirement 3 except for 3.2.1, 3.2.2, and Peak 10 did not store, process, or transmit cardholder data. Peak 10 did not store, process, or transmit cardholder data. Requirement 5: Requirement 6: except for Peak 10 did not develop software applications that stored, processed, or transmitted cardholder data Requirement 7: Requirement 8: Requirement 9: 8.7-Peak 10 did not maintain any databases which stored cardholder data There were no publicly accessible network jacks Peak 10 did not maintain any media containing cardholder data. Backup services were not included PCI Security Standards Council, LLC. All Rights Reserved. Page 7
9 in the assessment. 9.9-Peak 10 did not maintain any card reading devices Requirement 10: Requirement 11: No wireless connections were allowed to connect to the environment No significant changes occurred in the last 12 months Requirement 12: Appendix A: A.1.3-Peak 10 customers were responsible for complying with logging requirements as they had the ability to enable logging on their exclusive virtual environment via the BAE Systems log management service PCI Security Standards Council, LLC. All Rights Reserved. Page 8
10 Section 2: Report on Compliance This Attestation of Compliance reflects the results of an onsite assessment, which is documented in an accompanying Report on Compliance (ROC). The assessment documented in this attestation and in the ROC was completed on: December 15, 2015 Have compensating controls been used to meet any requirement in the ROC? Were any requirements in the ROC identified as being not applicable ()? Yes Yes No No Were any requirements not tested? Yes No Were any requirements in the ROC unable to be met due to a legal constraint? Yes No PCI Security Standards Council, LLC. All Rights Reserved. Page 9
11 Section 3: Validation and Attestation Details Part 3. PCI DSS Validation Based on the results noted in the ROC dated December 15, 2015, the signatories identified in Parts 3b-3d, as applicable, assert(s) the following compliance status for the entity identified in Part 2 of this document as of December 15, 2015: (check one): Compliant: All sections of the PCI DSS ROC are complete, all questions answered affirmatively, resulting in an overall COMPLIANT rating; thereby Peak 10, Inc. has demonstrated full compliance with the PCI DSS. Non-Compliant: Not all sections of the PCI DSS ROC are complete, or not all questions are answered affirmatively, resulting in an overall NON-COMPLIANT rating, thereby Peak 10, Inc. has not demonstrated full compliance with the PCI DSS. Target Date for Compliance: An entity submitting this form with a status of Non-Compliant may be required to complete the Action Plan in Part 4 of this document. Check with the payment brand(s) before completing Part 4. Compliant but with Legal exception: One or more requirements are marked Not in Place due to a legal restriction that prevents the requirement from being met. This option requires additional review from acquirer or payment brand. If checked, complete the following: Affected Requirement Details of how legal constraint prevents requirement being met Part 3a. Acknowledgement of Status Signatory(s) confirms: (Check all that apply) The ROC was completed according to the PCI DSS Requirements and Security Assessment Procedures, Version 3.1, and was completed according to the instructions therein. All information within the above-referenced ROC and in this attestation fairly represents the results of my assessment in all material respects. I have confirmed with my payment application vendor that my payment system does not store sensitive authentication data after authorization. I have read the PCI DSS and I recognize that I must maintain PCI DSS compliance, as applicable to my environment, at all times. If my environment changes, I recognize I must reassess my environment and implement any additional PCI DSS requirements that apply PCI Security Standards Council, LLC. All Rights Reserved. Page 10
12 Part 3a. Acknowledgement of Status (continued) No evidence of full track data 1, CAV2, CVC2, CID, or CVV2 data 2, or PIN data 3 storage after transaction authorization was found on ANY system reviewed during this assessment. ASV scans are being completed by the PCI SSC Approved Scanning Vendor QualysGuard PCI Part 3b. Service Provider Attestation David A. Kidd David A. Kidd (Jan 12, 2016) Signature of Service Provider Executive Officer Service Provider Executive Officer Name: David Kidd Date: Jan 12, 2016 Title: Vice President of Governance, Risk, and Compliance Part 3c. QSA Acknowledgement (if applicable) If a QSA was involved or assisted with this assessment, describe the role performed: Independent Assessor Douglas W. Barbin Douglas W. Barbin (Jan 12, 2016) Signature of Duly Authorized Officer of QSA Company Duly Authorized Officer Name: Douglas W. Barbin QSA Company: BrightLine CPAs & Associates, Inc. Date: Jan 12, 2016 Part 3d. ISA Acknowledgement (if applicable) If an ISA was involved or assisted with this assessment, describe the role performed: Signature of ISA ISA Name: Date: Title: 1 Data encoded in the magnetic stripe or equivalent data on a chip used for authorization during a card-present transaction. Entities may not retain full track data after transaction authorization. The only elements of track data that may be retained are primary account number (PAN), expiration date, and cardholder name. 2 The three- or four-digit value printed by the signature panel or on the face of a payment card used to verify card-not-present transactions. 3 Personal identification number entered by cardholder during a card-present transaction, and/or encrypted PIN block present within the transaction message PCI Security Standards Council, LLC. All Rights Reserved. Page 11
13 Part 4. Action Plan for Non-Compliant Requirements Select the appropriate response for Compliant to PCI DSS Requirements for each requirement. If you answer No to any of the requirements, you may be required to provide the date your Company expects to be compliant with the requirement and a brief description of the actions being taken to meet the requirement. Check with the applicable payment brand(s) before completing Part 4. PCI DSS Requirement Description of Requirement Compliant to PCI DSS Requirements (Select One) YES NO Remediation Date and Actions (If NO selected for any Requirement) 1 Install and maintain a firewall configuration to protect cardholder data 2 Do not use vendor-supplied defaults for system passwords and other security parameters 3 Protect stored cardholder data Encrypt transmission of cardholder data across open, public networks Protect all systems against malware and regularly update antivirus software or programs Develop and maintain secure systems and applications Restrict access to cardholder data by business need to know Identify and authenticate access to system components Restrict physical access to cardholder data Track and monitor all access to network resources and cardholder data Regularly test security systems and processes Maintain a policy that addresses information security for all personnel PCI Security Standards Council, LLC. All Rights Reserved. Page 12