Scope
Map payment flows, account data, connected systems, people, locations, service providers, segmentation, and validation obligations.
PCI DSS consultancy practice
Practical PCI DSS v4.0.1 support across scope, assessment, architecture, implementation, evidence, remediation, validation preparation, and continuous compliance.
Discuss a PCI DSS programme ↗PCI DSS / FIT
End-to-end support
The programme can begin at any stage. We establish the validation route and current state first, then connect technical remediation, operating evidence, and assessor expectations.
Map payment flows, account data, connected systems, people, locations, service providers, segmentation, and validation obligations.
Evaluate each applicable requirement, control design, implementation state, evidence quality, dependencies, and material gaps.
Turn gaps into architecture decisions, technical controls, procedures, ownership, acceptance criteria, and implementation work.
Build an evidence model that traces each requirement to owners, operating records, samples, testing, exceptions, and review cadence.
Prepare SAQ or ROC evidence, coordinate QSA and ASV dependencies, resolve questions, manage findings, and verify closure.
Maintain recurring controls, targeted risk analyses, scans, tests, training, supplier evidence, metrics, and management decisions.
Complete requirement coverage
The work is organised around real payment services and control ownership, not a detached checklist. Each domain connects policy, technical implementation, operation, evidence, and validation.
Network security controls, segmentation, system configuration, inventories, hardening, and change control.
Data discovery, retention, masking, encryption, key management, transmission security, and deletion.
Malware protection, vulnerability management, patching, secure development, change security, and public-facing applications.
Need-to-know access, identity lifecycle, strong authentication, privileged access, visitor controls, and media protection.
Audit logs, time synchronization, alerting, reviews, scans, penetration testing, change detection, and control validation.
Policies, roles, risk analyses, awareness, incident response, third parties, annual scope confirmation, and programme oversight.
Typical PCI DSS programme outputs
Last reviewed 31 August 2026
The practice is maintained against PCI SSC source material. Scope, validation method, reporting form, and assessor involvement are confirmed for each entity before work begins.
Share the entity type, payment channels, service-provider relationships, current scope, validation method, previous findings, assessor status, and target date.
Discuss a PCI DSS programme ↗