PCI DSS compliance readiness
How the readiness assessment runs, the SAQ path, the 51-control checklist and what to prepare.
See the service →
PCI DSS v4.0.1 readiness sample
Every deliverable from a PCI DSS v4.0.1 readiness assessment of a fictional retailer with store POS terminals and an online store: executive report, technical findings, risk register, roadmap and workbook.

Written for owners and CFOs
A readiness score, the eight Critical risks, the decisions leadership needs to make and a funded 180-day plan, in plain language.

Evidence your IT team can use
Each finding names the PCI DSS v4.0.1 requirement, what we observed, the business impact, the fix and the closure evidence your assessor will ask for.
Our deliverables
A PCI DSS readiness assessment is only worth paying for if leadership can decide from it and the people doing the work can act on it. This sample shows every deliverable we hand over at the end of a PCI DSS v4.0.1 readiness assessment, slide by slide, so you can judge the depth before you book. It covers all 12 requirements across store POS terminals, an e-commerce payment page, the cardholder data environment network, servers and databases, encryption keys, user and vendor access, logging, vulnerability management, physical security and the policies that hold it together.
OC Security Audit runs these assessments for retailers, restaurants, e-commerce businesses, SaaS and service providers from Irvine, on-site across Orange County, Los Angeles and Southern California, and remotely nationwide. We review evidence, configurations and documents and interview your control owners; nothing in your environment is changed.
Sample notice. Contoso Retail Inc. is a fictional organization. Every name, account, address and figure in these pages is invented for illustration and describes no real customer. The structure, depth and format are the same as the reports our clients receive.
Deliverable 1 of 5 · PDF and Word · 9 pages
The report leadership reads first. It turns 200 control results into a readiness score, the business risks that could lead to stolen card data, the decisions leadership needs to make and a 180-day plan, written so an owner or CFO can act on it without a technical background.
Who uses it
Owner or CEO, CFO and finance, the executive owner for PCI DSS, and the board or partners who approve the budget.
What is included
SAMPLE · Contoso Retail Inc. (fictional)
1 / 8








Click the page in the centre to open it full size and zoom in.
Deliverable 2 of 5 · PDF and Word · 69 pages
The working document for whoever does the fixes. Every finding shows the PCI DSS v4.0.1 requirement, what was observed, the business impact, the exact recommendation, the closure evidence and the owner and target date, grouped into 10 areas and ordered by severity.
Who uses it
IT team or managed service provider, e-commerce developers, the network and security engineers, and the compliance lead who prepares the SAQ or the QSA evidence.
What is included
SAMPLE · Contoso Retail Inc. (fictional)
1 / 14














Click the page in the centre to open it full size and zoom in.
Deliverable 3 of 5 · PDF and Word · 25 pages · landscape
The 142 findings rolled up into 24 business risks, each scored for likelihood and impact on card data, card acceptance and the business, with an owner, a treatment, a target rating and a target date. It doubles as the starting point for the targeted risk analyses PCI DSS v4.0.1 asks for.
Who uses it
The executive owner for PCI DSS, the GRC or compliance manager at the monthly risk review, your acquiring bank or processor contact if they ask, and your cyber insurance broker.
What is included
SAMPLE · Contoso Retail Inc. (fictional)
1 / 9









Click the page in the centre to open it full size and zoom in.
Deliverable 4 of 5 · PDF and Word · 15 pages
The order of work. 35 actions in four phases over 180 days, grouped into eleven projects with one owner each, today’s measures against 30-day and 180-day targets, the expected drop in risk and the operating rhythm that keeps the evidence current for validation.
Who uses it
The executive owner and finance for budgeting, the IT team or MSP for scheduling, and the compliance lead for tracking progress toward formal validation.
What is included
SAMPLE · Contoso Retail Inc. (fictional)
1 / 9









Click the page in the centre to open it full size and zoom in.
Deliverable 5 of 5 · Excel · 7 sheets
Everything in the reports as filterable data: every finding, every risk, every roadmap action and all 200 controls, with yellow status, owner and due-date columns your team fills in. The summary tables update as items close.
Who uses it
The IT team or MSP for daily tracking, the compliance lead for evidence, and the next assessor for a fast follow-up comparison.
What is included
SAMPLE · Contoso Retail Inc. (fictional)
1 / 7







Click the page in the centre to open it full size and zoom in.
How the deliverables connect
Every item keeps the same ID in all five deliverables, so nobody has to re-read a 69-page report to know what happens next. Here is one example from the sample.
Finding
Technical Security Report: card numbers in the order database and two file shares are stored in clear text. PCI DSS 3.5.1, rated Critical (20).
Risk
Risk Register: stored card numbers readable if stolen. Likelihood 4 × impact 5 = 20, Critical, owned by the Data Protection Lead, target score 5.
Action
Roadmap: restrict access to the shares and exports in the first 7 days, then tokenize or encrypt the stored card numbers and purge the clear-text copies by day 30.
Tracking
Workbook: the Findings, Risk Register and Remediation Plan sheets carry the same IDs, with owner, status and due date until the item closes.
What the assessment covers
The table shows how the sample’s 200 controls spread across the 12 requirements, how many were compliant, partial or a gap at the fictional retailer, and one example of what was found under each.
| PCI DSS v4.0.1 requirement | Controls | Compliant / partial / gap | Example from the sample |
|---|---|---|---|
| 1Install and maintain network security controls | 14 | 6 / 4 / 4 | No default-deny rule; order database reachable from the DMZ |
| 2Apply secure configurations | 20 | 5 / 9 / 6 | Standards not applied at build; vendor defaults on databases and cloud services |
| 3Protect stored account data | 24 | 9 / 8 / 7 | Card numbers in clear text in the database, file shares, logs and exports |
| 4Protect cardholder data in transmission | 10 | 2 / 5 / 3 | A batch transfer and two partner APIs unencrypted; expired certificates |
| 5Protect against malicious software | 5 | 2 / 2 / 1 | Anti-malware can be switched off on POS terminals and servers |
| 6Develop and maintain secure systems and software | 26 | 5 / 13 / 8 | Payment page scripts not inventoried or integrity-checked |
| 7Restrict access by business need to know | 5 | 1 / 3 / 1 | Access granted without documented business need |
| 8Identify users and authenticate access | 16 | 6 / 5 / 5 | Password-only access to the back-office payment application |
| 9Restrict physical access to cardholder data | 21 | 6 / 9 / 6 | No POS device inventory; store network closets unlocked |
| 10Log and monitor all access | 18 | 5 / 7 / 6 | Time synchronization and alerting on control failures missing |
| 11Test security of systems and networks regularly | 16 | 4 / 6 / 6 | No application-layer penetration test of the e-commerce site |
| 12Support security with policies and programs | 25 | 7 / 11 / 7 | No executive owner for PCI DSS; incident response plan never tested |
| Total | 200 | 58 / 82 / 60 | Readiness score 50.5; none of the 12 requirements fully met yet |
A readiness assessment measures progress toward PCI DSS v4.0.1 and prepares the evidence for validation. It is not a Report on Compliance, an Attestation of Compliance or a completed Self-Assessment Questionnaire, and OC Security Audit does not issue them. Formal validation depends on your merchant or service provider level and your acquiring bank’s requirements. PCI DSS is a standard of the PCI Security Standards Council.
Related

How the readiness assessment runs, the SAQ path, the 51-control checklist and what to prepare.
See the service →
Starting price, what changes the fee and what is included in a written scope.
See pricing →
Compare this PCI DSS sample with our HIPAA, Microsoft 365, network, firewall and Active Directory samples.
Browse sample reports →
Who prepares the report
Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Every PCI DSS readiness assessment is evidence-based and written so the owner, the finance team and the IT team can all act on it.
We stay independent: we assess and advise, and your IT team or provider carries out the fixes, with our help if you want it.
FAQ
No. Contoso Retail Inc. is a fictional organization, and every name, account, address and figure in the sample is invented. We never publish client data. The structure, depth and format are the same as the reports our clients receive.
The full set shown here is an Executive Security Report, a Technical Security Report, a Risk Register, a Next Steps and Security Roadmap, and a Technical Findings Workbook in Excel. The scope and the deliverables are confirmed in writing before the work starts; the PCI DSS readiness pricing page explains what drives the fee.
No. This is a readiness (gap) assessment that measures progress toward PCI DSS v4.0.1. It is not a Report on Compliance, an Attestation of Compliance or a completed Self-Assessment Questionnaire. Formal validation depends on your merchant or service provider level and on what your acquiring bank or payment brand requires.
The sample assesses 200 controls covering all 12 PCI DSS v4.0.1 requirements, grouped into 10 areas such as network security, data protection, encryption, access control and secure development. Each control is rated compliant, partial or gap and scored for likelihood and impact.
Yes. The sample checks the payment page script inventory, script integrity and change- and tamper-detection on the payment page, the controls in requirements 6.4.3 and 11.6.1 that target e-skimming. In the sample, both appear as findings with a fix, an owner and a target date.
We review documents, configurations and evidence and interview your control owners, using read-only access where systems are reviewed directly. Nothing in your environment is changed during the assessment. Your IT team or provider carries out the fixes in the roadmap.
Yes. OC Security Audit is based in Irvine and works on-site across Orange County, Los Angeles and Southern California, and remotely with merchants and service providers nationwide.

Tell us how you take cards: stores, online, phone or a payment provider. We will confirm the scope, the deliverables and a written fee before any work starts.
Or call 949-777-5567
This website uses essential cookies for security and operation. Optional analytics and advertising cookies help measure site use and outreach. Choose Allow or Deny. You can change your choice at any time.