What are the PCI DSS rules / requirements?
PCI DSS (the international standard from the PCI Security Standards Council) organizes compliance into essential requirements — in practice, the classic 12 rules card brands expect to see covered:
- Install and maintain network security controls (firewalls / segmentation).
- Do not use vendor-supplied defaults for passwords and other parameters.
- Protect stored account data.
- Protect cardholder data with strong cryptography during transmission over open/public networks.
- Protect systems against malware and keep anti-malware updated.
- Develop and maintain secure systems and applications.
- Restrict access to cardholder data by business need to know.
- Identify users and authenticate access to system components.
- Restrict physical access to cardholder data.
- Log and monitor all access to network resources and cardholder data.
- Test security systems and processes regularly (includes scans and penetration testing).
- Maintain an information security policy that addresses PCI DSS.
BCP maps these requirements in your environment, pinpoints gaps and runs the cycle on our own platform through readiness and annual renewal.
Do you perform penetration testing?
Yes. Penetration testing is a PCI DSS requirement (requirement 11). BCP runs pentests in the certification cycle, produces evidence and pinpoints exactly what your technical team needs to fix — without applying patches in the environment ourselves.
Does “hands-on” mean BCP logs into servers to fix things?
Not for remediation: we pinpoint exactly where to fix; your technical team applies patches and changes. For pentest (a PCI requirement), the engagement is authorized testing and reporting — different from operating or maintaining infra day to day.
Does PCI DSS need to be renewed every year?
Yes. Every year card brands require a new PCI DSS cycle. BCP supports renewal and helps clients stay certified — with checklist, evidence, pentest when applicable and quarterly scans on the right cadence.
Do you follow quarterly scans?
Yes. We keep the quarterly scan cadence (ASV/scans) through the end of the certification cycle, organizing evidence and what your technical team needs to address between scans.
Do you help with brand updates?
Yes, when the scenario requires it. We align the documentation and update track with card brands to the PCI DSS certification pace, so onboarding does not stall.
Is PCI DSS an international certification?
Yes. PCI DSS is the international standard from the PCI Security Standards Council. In Brazil, brands (Visa, Mastercard, Elo, Amex and others) require this compliance to operate and renew — BCP prepares your company for the global requirement and the local track.
Do you have a platform to manage certification?
Yes. BCP built an internal platform to manage the full PCI DSS cycle: scope, gaps, remediation checklist, evidence, pentest, quarterly scans and annual renewal — with clear status from kickoff through continuity.
How long does it take? Do you handle urgency?
Yes — on an urgent track, the typical cycle is under 30 days. When there is a brand or acquirer deadline, we accelerate scope, checklist, evidence and pentest on our platform. Final timing also depends on how fast your technical team remediates and, if any, the external assessor — but BCP’s design is built to fit in under a month.
I already operate as a sub-acquirer. Does this make sense?
Yes. We review scope, map non-conformities with precision, organize renewal, pentest and, if needed, brand updates — so renegotiation or product expansion does not stall. Environment fixes stay with your team.
Are you specialists in Service Provider?
Yes. BCP specializes in PCI DSS Service Provider certifications — sub-acquirers, SPs and gateways. We master SAQ D-SP framing, CDE scope and what the market requires from companies that process cards for others, including urgent cycles (under 30 days).