Transcription
Payment Card Industry (PCI)Data Security StandardAttestation of Compliance forOnsite Assessments – Service ProvidersVersion 3.2.1June 2018Clicksign af3e3889-e463-4f41-8acf-40239dadaa7a
Section 1: Assessment InformationInstructions for SubmissionThis Attestation of Compliance must be completed as a declaration of the results of the service provider’sassessment with the Payment Card Industry Data Security Standard Requirements and SecurityAssessment Procedures (PCI DSS). Complete all sections: The service provider is responsible forensuring that each section is completed by the relevant parties, as applicable. Contact the requestingpayment brand for reporting and submission procedures.Part 1. Service Provider and Qualified Security Assessor InformationPart 1a. Service Provider Organization InformationCompany Name:Vindi Tecnologia eMarketing S.ADBA (doingbusiness as):VindiContact Name:Teógenes Paula PanellaJúniorTitle:Head of InformationSecurity - CISOTelephone: 55 (11) ness Address:Rua do Paraíso, 148 LiberdadeCity:São brCountry:Zip:04103000Part 1b. Qualified Security Assessor Company Information (if applicable)Company Name:AuditSafe Auditoria e Consultoria em Riscos Corporativos Ltda.Lead QSA Contact Name:Fernando Nicolau FreitasFerreiraTitle:Founder & CEOTelephone: 55 11 usiness Address:Rua Duarte de Azevedo,431 – SantanaCity:Rua Duarte de Azevedo, 431– auditsafe.com.brCountry:PCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7a02036-021June 2018Page 1
Part 2. Executive SummaryPart 2a. Scope VerificationServices that were INCLUDED in the scope of the PCI DSS Assessment (check all that apply):Name of service(s) assessed:Payment GatewayType of service(s) assessed:Hosting Provider:Managed Services (specify):Payment Processing:Applications / softwareSystems security servicesPOS / card presentHardwareIT supportInternet / e-commerceInfrastructure / NetworkPhysical securityMOTO / Call CenterPhysical space (co-location)Terminal Management SystemATMStorageOther services (specify):Other processing (specify):Account ManagementFraud and ChargebackPayment Gateway/SwitchBack-Office ServicesIssuer ProcessingPrepaid ServicesBilling ManagementLoyalty ProgramsRecords ManagementClearing and SettlementMerchant ServicesTax/Government PaymentsWebSecurity services3-D Secure Hosting ProviderShared Hosting ProviderOther Hosting (specify):Network ProviderOthers (specify):Note: These categories are provided for assistance only, and are not intended to limit or predeterminean 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 applicablepayment brand.PCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aJune 2018Page 2
Part 2a. Scope Verification (continued)Services that are provided by the service provider but were NOT INCLUDED in the scope ofthe PCI DSS Assessment (check all that apply):Name of service(s) not assessed:Services that are not listed aboveType of service(s) not assessed:Hosting Provider:Applications / softwareHardwareInfrastructure / NetworkPhysical space (co-location)StorageWebSecurity services3-D Secure Hosting ProviderShared Hosting ProviderOther Hosting (specify):Managed Services (specify):Systems security servicesIT supportPhysical securityTerminal Management SystemOther services (specify):Payment Processing:POS / card presentInternet / e-commerceMOTO / Call CenterATMOther processing (specify):Account ManagementFraud and ChargebackPayment Gateway/SwitchBack-Office ServicesIssuer ProcessingPrepaid ServicesBilling ManagementLoyalty ProgramsRecords ManagementClearing and SettlementMerchant ServicesTax/Government PaymentsNetwork ProviderOthers (specify):Provide a brief explanation why any checked serviceswere not included in the assessment:N/A.Part 2b. Description of Payment Card BusinessDescribe how and in what capacity your businessstores, processes, and/or transmits cardholder data.Vindi Tecnologia e Marketing S.A – Vindi offersthe online payment infrastructure service acting asa payment gateway. Vindi works with all creditcard brands accepted in the national territory.Through Vindi APIs, customers can buildtransparent checkouts and take advantage of thebest form of conversion, offering invisible andperformance payments at their checkout.Card brands accepted by VindiAll brands accepted in the national territory.Describe how and in what capacity your business isotherwise involved in or has the ability to impact thesecurity of cardholder data.Vindi only transmits and processes the cardholderdata, the company does not store cardholder datain its system components. The information that isstored is described in the previous item. Whereonly the first 6 numbers and the last 4 numbers ofthe card.PCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aJune 2018Page 3
Vindi is responsible only for providing anetwork infrastructure for secure capture andtransmission, via HTTPs connection, returninga token that represents this cardPart 2c. LocationsList types of facilities (for example, retail outlets, corporate offices, data centers, call centers, etc.) and asummary of locations included in the PCI DSS review.Number of facilitiesType of facility:Location(s) of facility (city, country):of this typeExample: Retail outlets3Amazon AWSBoston, MA, USA1Ashburn, VA, USAPart 2d. Payment ApplicationsDoes the organization use one or more Payment Applications?YesNoProvide the following information regarding the Payment Applications your organization uses:Payment ApplicationNameVersionNumberApplicationVendorIs applicationPA-DSS Listed?PA-DSS Listing Expirydate (if applicable)GatewayN/AVindiYesNoNot ApplicableRecurrentN/AVindiYesNoNot ApplicableVaultN/AVindiYesNoNot ApplicableYesNoYesNoYesNoYesNoYesNoPart 2e. Description of EnvironmentProvide a high-level description of the environmentcovered by this assessment.For example: Connections into and out of the cardholder dataenvironment (CDE). Critical system components within the CDE, such as POSdevices, databases, web servers, etc., and any othernecessary payment components, as applicable.This assessment coverd the cloud servicetechnologies(AWS), AWS RDS DatabaseServers, File Integrity Monitoring (FIM),Tokenization Methods, Host IntrusionPrevention System(HIPS), OperationsSystems, Application Servers, LoadBalancer Solution, AWS Stateful SecurityGroup, Log Concentrator Solution,Vulnerability Scanner Solutions, WebApplication Servers, HomegrownPCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aJune 2018Page 4
Applications, Queue ManagerTechnologies.Also, it covered a review of thecommunications:- Vindi to payment gateway using HTTPS withTLSv1.2 with AES 256-bit.Does your business use network segmentation to affect the scope of your PCI DSSenvironment?(Refer to “Network Segmentation” section of PCI DSS for guidance on networksegmentation)PCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aYesNoJune 2018Page 5
Part 2f. Third-Party Service ProvidersDoes your company have a relationship with a Qualified Integrator & Reseller (QIR) forthe purpose of the services being validated?YesNoYesNoIf Yes:Name of QIR Company:Not ApplicableQIR Individual Name:Not ApplicableDescription of services provided by QIR:Not ApplicableDoes your company have a relationship with one or more third-party service providers (forexample, Qualified Integrator Resellers (QIR), gateways, payment processors, paymentservice providers (PSP), web-hosting companies, airline booking agents, loyalty programagents, etc.) for the purpose of the services being validated?If Yes:Name of service provider:Description of services provided:All Acquirer, Bank and BrandsAcquirerAmazon Web ServerCloud ServicesNote: Requirement 12.8 applies to all entities in this list.PCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aJune 2018Page 6
Part 2g. Summary of Requirements TestedFor 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 “NotApplicable” 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” inthe ROC Reason why sub-requirement(s) were not tested or not applicableNote: One table to be completed for each service covered by this AOC. Additional copies of this section areavailable on the PCI SSC website.Name of Service Assessed:Payment GatewayDetails of Requirements AssessedJustification for ApproachPCI DSSRequirementFullRequirement 1:PartialNone(Required for all “Partial” and “None” responses. Identify whichsub-requirements were not tested and the reason.)1.2.2 - Not Applicable - There are no routers in theassessed scope.1.2.3 - Not Applicable - There are no wirelesstechnologies in the assessed scope.Requirement 2:2.1.1 - Not Applicable - There are no wirelesstechnologies in the assessed scope.2.2.3 - Not Applicable - There are no insecureservices, protocols, or daemons in the assessedscope.2.6 - Not Applicable - Vindi is not a Shared ServiceProvider.Requirement 3:3.4.1 - Not Applicable - Vindi does not use DiskEncryption for protection of stored cardholder data.3.6.6 - Not Applicable - Vindi uses AWS KMS forsistematicly management of Keys.Requirement 4:4.1.1 - Not Applicable - There are no wirelesstechnologies in the assessed scope.Requirement 5:Not Applicable - Vindi does not use commonlyaffected systems by malwares in its scope (PaaS).Requirement 6:PCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aJune 2018Page 7
Requirement 7:Requirement 8:8.1.5 - Not Applicable - Vindi does not provideaccess in its systems to third parties.8.5.1 - Not Applicable - Vindi does not provideaccess in its systems to third parties.8.6 - Not Applicable - Vindi does not provide othermechanisms for authentication.Requirement 9:9.9.1 - Not Applicable - Vindi does not use any POSdevice.9.9.2 - Not Applicable - Vindi does not use any POSdevice.9.9.3 - Not Applicable - Vindi does not use any POSdevice.Requirement 10:10.5.5 - Not Applicable - Vindi uses serverlesstechnologies in its scope (PaaS).Requirement 11:11.3.2 - Not Applicable - Vindi uses serverlesstechnologies in its scope (PaaS).11.5 - Not Applicable - Vindi uses serverlesstechnologies in its scope (PaaS).11.5.1 - Not Applicable - Vindi uses serverlesstechnologies in its scope (PaaS).Requirement 12:Appendix A1:Not Applicable. Vindi is not a Shared HostingProviderAppendix A2:Not Applicable. Vindi does not use any POSdevices.PCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aJune 2018Page 8
Section 2: Report on ComplianceThis Attestation of Compliance reflects the results of an onsite assessment, which is documented in anaccompanying Report on Compliance (ROC).The assessment documented in this attestation and in the ROC was completedon:May 4th,2021Have compensating controls been used to meet any requirement in the ROC?YesNoWere any requirements in the ROC identified as being not applicable (N/A)?YesNoWere any requirements not tested?YesNoWere any requirements in the ROC unable to be met due to a legal constraint?YesNoPCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aJune 2018Page 9
Section 3: Validation and Attestation DetailsPart 3. PCI DSS ValidationThis AOC is based on results noted in the ROC dated May 4th, 2021 .Based on the results documented in the ROC noted above, the signatories identified in Parts 3b-3d, asapplicable, assert(s) the following compliance status for the entity identified in Part 2 of this document(check one):Compliant: All sections of the PCI DSS ROC are complete, all questions answered affirmatively,resulting in an overall COMPLIANT rating; thereby Vindi has demonstrated full compliance with thePCI DSS.Non-Compliant: Not all sections of the PCI DSS ROC are complete, or not all questions areanswered affirmatively, resulting in an overall NON-COMPLIANT rating, thereby (Service ProviderCompany Name) 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 ActionPlan 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 alegal restriction that prevents the requirement from being met. This option requires additional reviewfrom acquirer or payment brand.If checked, complete the following:Affected RequirementDetails of how legal constraint prevents requirement being metPart 3a. Acknowledgement of StatusSignatory(s) confirms:(Check all that apply)The ROC was completed according to the PCI DSS Requirements and Security AssessmentProcedures, Version 3.2.1, and was completed according to the instructions therein.All information within the above-referenced ROC and in this attestation fairly represents the results ofmy assessment in all material respects.I have confirmed with my payment application vendor that my payment system does not storesensitive authentication data after authorization.I have read the PCI DSS and I recognize that I must maintain PCI DSS compliance, as applicable tomy environment, at all times.If my environment changes, I recognize I must reassess my environment and implement anyadditional PCI DSS requirements that apply.PCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aJune 2018Page 10
Part 3a. Acknowledgement of Status (continued)No evidence of full track data1, CAV2, CVC2, CID, or CVV2 data2, or PIN data3 storage aftertransaction authorization was found on ANY system reviewed during this assessment.ASV scans are being completed by the PCI SSC Approved Scanning Vendor Clone Systems, Inc. -Active-Now Clone Guard PCI #4262-01-14Part 3b. Service Provider AttestationSignature of Service Provider Executive Officer Date: May 4th, 2021Service Provider Executive Officer Name: Teógenes PaulaTitle: Head of Information Security -Panella JúniorCISOPart 3c. Qualified Security Assessor (QSA) Acknowledgement (if applicable)If a QSA was involved or assisted with thisassessment, describe the role performed:QSA performed Quality Assurance of the Report OnComplianceSignature of Duly Authorized Officer of QSA Company Date: May 4th, 2021Duly Authorized Officer Name: Fernando Nicolau FreitasQSA Company: AuditSafe Auditoria eFerreira - PCI QSA 205-240Consultoria em Riscos CorporativosLtda.Part 3d. Internal Security Assessor (ISA) Involvement (if applicable)If an ISA(s) was involved or assisted withthis assessment, identify the ISA personneland describe the role performed:Not Applicable1Data encoded in the magnetic stripe or equivalent data on a chip used for authorization during a card-present transaction. Entitiesmay not retain full track data after transaction authorization. The only elements of track data that may be retained are primaryaccount number (PAN), expiration date, and cardholder name.2The three- or four-digit value printed by the signature panel or on the face of a payment card used to verify card-not-presenttransactions.3Personal identification number entered by cardholder during a card-present transaction, and/or encrypted PIN block presentwithin the transaction message.PCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aJune 2018Page 11
Part 4. Action Plan for Non-Compliant RequirementsSelect the appropriate response for “Compliant to PCI DSS Requirements” for each requirement. If youanswer “No” to any of the requirements, you may be required to provide the date your Company expects to becompliant 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 DSSRequirementDescription of RequirementCompliant to PCIDSS RequirementsRemediation Date andActions(Select One)(If “NO” selected for anyRequirement)YES1Install and maintain a firewallconfiguration to protect cardholder data2Do not use vendor-supplied defaults forsystem passwords and other securityparameters3Protect stored cardholder data4Encrypt transmission of cardholder dataacross open, public networks5Protect all systems against malwareand regularly update anti-virus softwareor programs6Develop and maintain secure systemsand applications7Restrict access to cardholder data bybusiness need to know8Identify and authenticate access tosystem components9Restrict physical access to cardholderdata10Track and monitor all access to networkresources and cardholder data11Regularly test security systems andprocesses12Maintain a policy that addressesinformation security for all personnelAppendix A1Additional PCI DSS Requirements forShared Hosting ProvidersAppendix A2Additional PCI DSS Requirements forEntities using SSL/early TLS for CardPresent POS POI Terminal ConnectionsNOPCI DSS v3.2.1 Attestation of Compliance for Onsite Assessments – Service Providers, Rev. 1.0 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved.Clicksign af3e3889-e463-4f41-8acf-40239dadaa7aJune 2018Page 12
Datas e horários em GMT -03:00 BrasiliaLog gerado em 05 de maio de 2021. Versão v1.2.1.AuditSafe Vindi - PCI-DSS-v3 2 1-AOC-ServiceProviders.pdfDocumento número ogenes Paulo Panella JuniorAssinouFernando Nicolau Freitas FerreiraAssinouLog05 mai 2021, 13:54:53Operador com email lidiane.sapienza@auditsafe.com.br na Conta 42c915e1-3d1a-42d1-bd9be3d3c8a8f95f criou este documento número af3e3889-e463-4f41-8acf-40239dadaa7a. Datalimite para assinatura do documento: 29 de maio de 2021 (11:30). Finalização automática após aúltima assinatura: habilitada. Idioma: Português brasileiro.05 mai 2021, 13:56:06Operador com email lidiane.sapienza@auditsafe.com.br na Conta 42c915e1-3d1a-42d1-bd9be3d3c8a8f95f adicionou à Lista de Assinatura:teogenes.panella@vindi.com.br, para assinar, com os pontos de autenticação: email (via token);Nome Completo; CPF; endereço de IP. Dados informados pelo Operador para validação dosignatário: nome completo Teogenes Paulo Panella Junior.05 mai 2021, 13:56:51Operador com email lidiane.sapienza@auditsafe.com.br na Conta 42c915e1-3d1a-42d1-bd9be3d3c8a8f95f adicionou à Lista de Assinatura:fernandoferreira@auditsafe.com.br, para assinar, com os pontos de autenticação: email (viatoken); Nome Completo; CPF; endereço de IP. Dados informados pelo Operador para validaçãodo signatário: nome completo Fernando Nicolau Freitas Ferreira.05 mai 2021, 13:57:01Operador com email lidiane.sapienza@auditsafe.com.br na Conta 42c915e1-3d1a-42d1-bd9be3d3c8a8f95f alterou o processo de assinatura. Data limite para assinatura do documento: 29de maio de 2021 (11:30).05 mai 2021, 13:59:20Fernando Nicolau Freitas Ferreira assinou. Pontos de autenticação: emailfernandoferreira@auditsafe.com.br (via token). CPF informado: 265.117.128-00. IP:189.79.103.220. Componente de assinatura versão 1.109.2 disponibilizado emhttps://app.clicksign.com.05 mai 2021, 14:17:51Teogenes Paulo Panella Junior assinou. Pontos de autenticação: emailteogenes.panella@vindi.com.br (via token). CPF informado: 220.454.388-80. IP: 160.238.109.253.Componente de assinatura versão 1.110.0 disponibilizado em https://app.clicksign.com.05 mai 2021, 14:17:51Processo de assinatura finalizado automaticamente. Motivo: finalização automática após aúltima assinatura habilitada. Processo de assinatura concluído para o documento númeroaf3e3889-e463-4f41-8acf-40239dadaa7a.Hash do documento original (SHA256): c52bce77caf5b7Este Log é exclusivo ao, e deve ser considerado parte do, documento número af3e3889-e463-4f41-8acf-40239dadaa7a, com os efeitosaf3e3889-e463-4f41-8acf-40239dadaa7aPágina 1 de 2
Datas e horários em GMT -03:00 BrasiliaLog gerado em 05 de maio de 2021. Versão v1.2.1.prescritos nos Termos de Uso da Clicksign disponível em aa7aPágina 2 de 2
Servers, File Integrity Monitoring (FIM), Tokenization Methods, Host Intrusion Prevention System(HIPS), Operations Systems, Application Servers, Load Balancer Solution, AWS Stateful Security Group, Log Concentrator Solution, Vulnerability Scanner Solutions, Web Application Servers, Homegrown Clicksign af3e3889-e463-4f41-8acf-40239dadaa7a
