PCI DSS & Payment Security Services Saudi Arabia
PCI DSS is the one standard where arguing with the requirement rarely works. We define the scope precisely, shrink it where we can, close the gaps, and hand your assessor evidence they can accept.
Where organisations get stuck
- The validation level and the right reporting route are unclear.
- Scope has never been formally defined, so the whole network may be in it.
- v4.0's future-dated requirements are now in force and were not planned for.
- Compensating controls from a previous assessment were never resolved.
- An acquirer deadline is approaching and remediation has not started.
What we deliver
Scope definition
Data-flow mapping to establish exactly what the cardholder data environment contains.
Scope reduction
Tokenisation, segmentation and redirect models to take systems out of scope.
v4.0 gap assessment
Requirement-by-requirement review, including the newer customised approach.
Remediation delivery
Closing the gaps, not just listing them.
Segmentation testing
Proving the boundary holds, at the cadence your level requires.
Evidence preparation
Assembling the artefacts a QSA will ask for, before they ask.
Assess → Remediate → Secure → Assure
Assess
Understand your risk and compliance position.
Remediate
Close gaps with prioritized solutions.
Secure
Deploy the right technologies and controls.
Assure
Maintain continuous compliance and resilience.
Not sure where you stand? A short scoping call establishes what applies to you and what the work would involve. No obligation. Discuss PCI DSS Requirements →
Knowing your route to validation
| Merchant levels | Transaction volume determines whether you self-assess or need a full report. |
| Service provider levels | Different thresholds and generally stricter testing expectations. |
| SAQ types | The right questionnaire depends on how you accept and process payments. |
| Report on Compliance | Required at higher levels and issued by a Qualified Security Assessor. |
What you receive
- Documented scope and data-flow diagrams
- Validation route and SAQ determination
- Requirement-level gap register
- Scope-reduction plan with effort estimates
- Segmentation test report
- QSA-ready evidence pack
Related services and insights
Frequently asked questions
Do you issue the PCI DSS certificate?
No. A Report on Compliance is issued by a Qualified Security Assessor and an Attestation of Compliance is signed by the entity. We prepare you to pass and work alongside your QSA. Where a licensed or specialist partner is required, we say so and structure the delivery accordingly.
What changed in v4.0 that catches people out?
Mostly the requirements that were future-dated at release and have since become mandatory, plus the greater emphasis on documented, continuous processes rather than point-in-time evidence. Organisations that passed comfortably under the previous version often have genuine gaps under v4.0.
Can PCI DSS and NCA ECC be done together?
Yes, and it is usually cheaper. The control sets overlap considerably on logging, access control, vulnerability management and testing. We map them once so a single piece of evidence satisfies both, rather than running two parallel evidence collections.
How much can scope realistically be reduced?
Often substantially. Moving to a redirect or iframe checkout, tokenising stored data and segmenting properly can take most of an estate out of scope. We size the reduction before committing to a remediation plan, because it frequently changes which plan makes sense.
Ready to start?
Tell us where you are and we will tell you what the work actually involves — scope, sequence and timeline, before any commitment.
Discuss PCI DSS Requirements