PCI DSS v4.0.1 · Standard of the card brands
PCI DSS examines your software.
Kodator documents the work on it.
Whoever handles card data has to show that their own software is developed, reviewed and maintained securely. Kodator collects the technical evidence for that: for the assessment by your assessor, not in its place.
- v4.0.1Version
The evidence report in Kodator refers to PCI DSS v4.0.1.
- 8 rowsIn the report
Requirements 6.2.3, 6.2.4, 6.3.1, 6.3.2, 6.3.3, 6.4.1/6.4.2, 11.3.1 and 12.3.1.
- Not an ASVBoundary
External vulnerability scans under 11.3.2 stay with an Approved Scanning Vendor.
Scope
Who PCI DSS applies to
PCI DSS is not a law but a security standard of the card brands. It becomes binding through contracts with the acquiring bank and the card brands.
Merchants
Companies that accept card payments and store, process or transmit card data in doing so.
Service providers
Payment, hosting and software providers that process card data for others or can affect its security.
Banks and payment institutions
Issuers and acquirers with their own systems in the cardholder data environment.
Development teams
Whoever develops software for the cardholder data environment falls under Requirement 6. This is where Kodator focuses.
How you have to demonstrate compliance, by self-assessment or by an on-site assessment, is set by the card brands and your acquiring bank.
Step by step
The road to validation, and who contributes what
PCI DSS has twelve principal requirements. Kodator supplies evidence for parts of Requirements 6, 11 and 12. Everything else stays with you.
How to read the steps
Kodator 2 / 13Kodator produces the evidence from scans and remediation.
Kodator helps 6 / 13Kodator supplies part of the evidence. The task stays with you.
You 5 / 13Outside of what a scanner can give evidence for.
Define the cardholder data environment
Which systems, applications and people touch card data or can affect its security?
- Kodator supplies
- Projects can be marked as "in PCI scope"; the report then counts only those.
- Stays with you
- Define and document the scope.
Agree the form of validation with the acquirer
Depending on what is required, a self-assessment is enough, or an assessor examines on site.
- Kodator supplies
- No contribution.
- Stays with you
- Coordination with the acquiring bank and the card brands.
Review your own code before release
Bespoke and custom software is reviewed for vulnerabilities before it is released.
- Kodator supplies
- Source code and secrets scan on every pull request, with a gate before merging. The report shows which repositories were reviewed in the last 90 days.
- Stays with you
- Define the review process, fix findings and take responsibility for the release.
Prevent common attack classes
Engineering techniques prevent or mitigate common attacks such as injection and cross-site scripting.
- Kodator supplies
- Scan rules mapped to CWE and OWASP Top 10; open weaknesses by severity and the most frequent CWEs in the report.
- Stays with you
- Secure engineering practices, developer training and remediation.
Identify vulnerabilities and rank them by risk
New vulnerabilities are identified from recognised sources and ranked by risk.
- Kodator supplies
- Daily matching against public vulnerability databases; an explainable risk score from 0 to 100 per finding. When the vulnerability data is stale, the report says that current evidence is missing.
- Stays with you
- Describe your own risk-ranking procedure.
Keep an inventory of bespoke and third-party components
An inventory of bespoke software and the third-party components it contains.
- Kodator supplies
- A CycloneDX SBOM per asset, as JSON and as PDF.
- Stays with you
- Make sure every application in scope is registered as an asset.
Fix critical and high vulnerabilities in time
Security patches are installed within defined time frames.
- Kodator supplies
- Remediation deadlines per severity, overdue findings, mean time to remediate and findings without a deadline.
- Stays with you
- Patch and roll out.
Protect public-facing web applications
Web applications on the internet are protected against attacks on an ongoing basis.
- Kodator supplies
- Automated testing of the running application on a schedule, only for domains with verified ownership.
- Stays with you
- A solution that detects and blocks attacks automatically (for example a web application firewall) is outside the product.
Internal vulnerability scans at least quarterly
Internal scans at least every three months and after significant changes; high and critical findings are fixed and rescanned.
- Kodator supplies
- Scheduled scans and scans on every change; the report shows the last complete scan per asset, and failed and incomplete runs.
- Stays with you
- Scans of networks and systems outside the applications, which Kodator does not cover.
External scans by an approved vendor
External vulnerability scans have to come from an Approved Scanning Vendor (ASV).
- Kodator supplies
- No contribution.
- Stays with you
- Engage an ASV. Kodator is not an ASV.
Analyse and justify risks specifically
Whoever accepts a risk documents the analysis behind it.
- Kodator supplies
- Risk acceptance per finding with justification and expiry date (twelve months at most); expired and unjustified acceptances are shown.
- Stays with you
- The risk analysis itself and its approval.
Implement all other requirements
Network security, protection of stored card data, access control, logging, physical security, policies and training, and control of the scripts on payment pages (6.4.3).
- Kodator supplies
- No contribution.
- Stays with you
- Implementation of and evidence for these requirements.
Have it assessed and attested
At the end stands the self-assessment or the report of an assessor with the attestation of compliance.
- Kodator supplies
- The evidence report as PDF for your records.
- Stays with you
- The assessment by a Qualified Security Assessor or your Internal Security Assessor.
In the product
PCI DSS evidence report
For each requirement the report summarises what Kodator measured: figures, a short explanation and links to the evidence, for all projects in PCI scope or for a single project.
- Figures
- Explanation
- Evidence
- The indications per requirement are derived from scan coverage, findings and triage decisions. They are not an assessment by an assessor.
- A scan counts only for the scan types that ran completely.
- Available as PDF; every export is recorded in the audit log.
- Card numbers detected in findings are masked before storage (first six, last four digits).
What Kodator is not
The report supports your work on PCI DSS v4.0.1. It is not a PCI DSS assessment, not a Report on Compliance and not an Attestation of Compliance, and it does not replace the assessment by a Qualified Security Assessor or your Internal Security Assessor. Kodator is not an Approved Scanning Vendor (ASV).
Next step
See Kodator on your own code.
Tell us which product and which requirement you are dealing with. In a demo we show you which evidence Kodator supplies for it, and which it does not.