
Assessment
PCI DSS Assessments
The QSA who scopes your assessment is the one who signs it. Here is what happens in between.
Who comes to us for this
Merchants and service providers whose acquirer, scheme or customers ask for a Report on Compliance: payment platforms, e-commerce companies, processors, contact centres, and businesses whose transaction volume has just pushed them off the self-assessment path. Some have done this many times. Some are on their first, and the first is the one where who you choose matters most.
What we do
One QSA, from scope to signature
01 · Prepare
What are we assessing?
Scoping
Agree what is in scope, and why.
Readiness
Answer each requirement in plain language, with evidence.
You describe, your QSA validates
02 · Assess
Where do we stand?
Gap analysis
Each requirement tested; gaps raised as findings.
Remediation
Findings worked to closure, together.
Your QSA tests, you close the gaps
03 · Report
Write it up.
Reporting and QA
Report on Compliance and Attestation of Compliance, quality-reviewed before signature.
Your QSA writes and signs
One continuous record
- Answers
- Evidence
- Determinations
- ROC & AOC
Scope first.
Before any requirement is assessed, we confirm the scope with you: every system in one of three places, the data flows, the segmentation controls named as the console names them, and the third parties with their responsibilities written down. A scope you stand behind is the one the report is written on.
Evidence, asked once.
Each piece of evidence is requested once, linked to every requirement it serves, with a one-line description of what good looks like. You submit it through the software we built for this, and we review it against the request, in minutes when it matches and with a precise note when it does not.
On site and remote.
Interviews, observation and testing of the controls that cannot be read from a file: the physical controls, the administrators’ screens, the processes that are supposed to be known and in use.
Findings as they are confirmed.
You hear about a finding when your QSA confirms it, with exactly what would close it, not in the report. Remediation rounds are agreed, with a cut-off. A concluded report with a clear plan is a better finish for both of us than another open round.
Quality review, then signature.
Before issuing, the report goes through our pre-issue review, which can and does change determinations, sometimes against you. Then the QSA who scoped the engagement signs the Report on Compliance and the Attestation.
What you do
Name one owner per finding. Submit once per requirement. Fix the configuration before you write the document about it. Tell us when you do not have something: a stated gap is quicker for both of us than a file we open only to rule it out.
What you receive
A scope confirmation you can reuse next year. Findings with what closes each. A status letter for your partners if your contracts need one, which says plainly that it is not an attestation. The Report on Compliance, the Attestation of Compliance, and a closing note with what to do before the next cycle.
What we will not do
- Sign a report that is not true.
- Accept a different control as a compensating control for a requirement it does not address.
- Let the report be written on a scope nobody has defined.
- Hand the engagement from the person who scoped it to someone who did not.
Keep reading
Related knowledge
PCI DSS4 min read
PCI DSS scoping: in, connected, or out
Every system in your estate is in one of three places. Most scoping mistakes come from treating "does not carry card data" as if it meant "out of scope", and from writing the scope by component type instead of by system.
PCI DSS3 min read
The findings we raise most often, and what closes each
Twelve findings from real assessments, none of them exotic. For each one, what it looks like in the room and the one thing that closes it.
Compliance Operations3 min read
How to file evidence so it gets reviewed in minutes
Six rules from our review notes on a first Report on Compliance. When a slot holds the right kind of file, we review it in minutes. When it does not, we open it only to rule it out, and the assessment slows for both of us.
Where it starts
A conversation with a QSA, not a salesperson.
How you take payments, who is asking for the report, what has been assessed before. Then a written proposal with scope, phases, the QSA who will lead, and a price that follows from the scope.
Talk to a QSAOr reach us directly
- +353 1 691 79 38
Dublin
- info@247cyberlabs.com
Read and answered by a QSA, not by a sales desk.