Meet standards. Strengthen cybersecurity.
Auditors ask for evidence.
Kodator supplies it.
Kodator scans source code, dependencies, containers and running applications, and turns the results into evidence for CRA, PCI DSS and SOC 2. Clause by clause, without flattering traffic lights.
- 11 Dec 2027CRA deadline
From then on all obligations of the Cyber Resilience Act apply. The duty to report actively exploited vulnerabilities has applied since 11 Sep 2026.
- Per clauseEvidence reports
For the CRA per product and release, for PCI DSS v4.0.1 per requirement: what is proven and what you have to contribute yourself. For SOC 2 a mapping to the criteria.
- 3 deployment modelsOnline · Hybrid · On-premises
You decide where the scans run. In hybrid and on-premises operation your code stays in your network.
What Kodator does
From scan to evidence
There are many scanners. Kodator relies on proven scan engines in pinned, checksum-verified versions and adds what they lack: one view of all findings, deadlines for remediation and reports an auditor can read.
01 · Scan
One scan for everything
Source code, secrets in code, dependencies, containers, infrastructure as code and the running web application, in one run or one at a time.
02 · Assess
One finding, one row
Kodator merges the results of all engines, removes duplicates and calculates an explainable risk score from CVSS, exploit probability and the flag for actively exploited vulnerabilities.
03 · Fix
Deadlines instead of lists
Findings get a remediation deadline by severity. Overdue items stand out; whoever accepts a risk needs a justification and an expiry date.
04 · SBOM
A bill of materials for every release
For every version Kodator freezes the SBOM and the state of the findings. When a new vulnerability becomes known, Kodator matches it daily against the stored bills of materials, without a new scan.
05 · Audit-proof
Tested regularly, documented cleanly
Scans run on a schedule and every run is recorded. The audit log is hash-chained and cannot be changed unnoticed.
06 · Evidence reports
Reports per clause
For PCI DSS v4.0.1 and the Cyber Resilience Act Kodator shows per requirement what is proven, what is only partly visible and what you have to contribute yourself.
- Proven
- Partly indicated
- Not covered
Connected to GitHub, GitLab, Azure DevOps and Bitbucket Cloud. Scans run on every pull request and can stop the pipeline.
Requirements
Three sets of requirements, one body of evidence
For each of them we show step by step what has to be done, and separate clearly what Kodator supplies from what stays with you.
EU regulation
Cyber Resilience Act
For manufacturers of software, devices and machinery with digital elements. All obligations apply from 11 Dec 2027, the reporting duty already since 11 Sep 2026.
Evidence report per product and release
Standard of the card brands
PCI DSS v4.0.1
For everyone who stores, processes or transmits card data. Kodator documents the secure development and maintenance of your own software.
Evidence report in the product
Attestation standard of the AICPA
SOC 2
For service providers whose customers ask for an audit report. Kodator contributes evidence on vulnerabilities and changes.
Mapping, no report of its own yet
Honest boundaries
Kodator supplies evidence. The responsibility stays with you.
No tool makes a company compliant. That is why every step here says who delivers it.
Kodator What can be measured: scans, bills of materials, known vulnerabilities, times to fix and a record of every decision.
Kodator helps Where findings only give indications: secure development, risk analyses and the technical documentation.
You What no scanner can do: risk assessment, policies, declaration of conformity and the audit itself.
Getting started
Six steps to the first scan
From access to the first report. Whether Kodator runs with us or the runner scans in your network mostly changes the third step.
Create the organisation
Get access and invite your team.
Create a project
Set business criticality and PCI scope.
Connect the code
Connect your Git hosting or register a runner in your own network.
Start the scan
By hand, on every pull request or on a schedule.
Review findings
Sorted by risk, with a remediation deadline.
Open the report
Download the evidence report and the SBOM.
Operated on your terms
Your code stays in your network.
The Kodator runner scans on your premises and sends only findings and bills of materials. Or you run Kodator entirely in-house.
- OnlineDashboard and runners at Kodator
- HybridDashboard at Kodator, runner at your site
- On-premisesEverything at your site
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.