Products

Five checks.
One body of evidence.

Each check can be used on its own. Together they give you one list of findings, a bill of materials per application and reports an auditor can read. For each product this page says what it finds and what you get.

Checks

What Kodator checks

The checks run on vetted scan engines in pinned, checksum-verified versions. We keep extending the set of engines; the results always end up in the same list of findings.

  • SAST

    Source code analysis

    Checks your own source code for vulnerabilities without running it: on every pull request, on every push to the default branch or on a schedule.

    Coverage Our own rules for Python, JavaScript/TypeScript, Java, Go and C#/.NET. No rules yet for PHP, Kotlin, Ruby, Scala, Swift, Rust and C/C++.

    Finds
    SQL injection, cross-site scripting, command injection, path traversal, SSRF, weak cryptography, insecure deserialisation, disabled TLS and JWT checks, and further weaknesses.
    You get
    Findings with file and line, a CWE mapping and remediation advice. On the pull request a status and a comment in your Git hosting. The results of a scan as SARIF, too.
  • SCA · SBOM

    Dependencies and SBOM

    Records the open-source components of a repository as a software bill of materials (SBOM) and matches them against public vulnerability databases.

    Coverage Tested by us: npm, yarn and pnpm, Python, Maven and Gradle, Go modules. Also supported by the engines: NuGet, Composer, RubyGems, Cargo and more.

    Finds
    Known vulnerabilities in dependencies, with CVSS, exploit probability and a flag for actively exploited ones.
    You get
    A CycloneDX SBOM per asset. Kodator matches stored SBOMs against new vulnerabilities every day, without a new scan. SBOMs from suppliers (CycloneDX, SPDX) can be imported.
  • Secrets

    Secrets in code

    Searches the text files of a repository for credentials that do not belong there.

    Coverage Every text file, whatever the programming language.

    Finds
    Committed passwords, API keys and tokens.
    You get
    Findings with their location. The value found is masked before storage. In the risk score, secrets count as "high" at least.
  • Container · IaC

    Containers and infrastructure as code

    Checks container images for vulnerable packages and infrastructure as code for insecure settings.

    Coverage Images based on Debian, Alpine, RHEL and others. Terraform, Kubernetes and Dockerfile tested by us; Helm and CloudFormation supported by the engine.

    Finds
    Vulnerable operating system and language packages in the image. Insecure settings in Terraform, Kubernetes manifests and Dockerfiles.
    You get
    Findings with package and version, or with file and line. For images an SBOM as well.
  • DAST

    Testing the running web application

    Tests a running web application from the outside. Only domains whose ownership you have proven are tested: with a DNS record or a file on the server.

    Coverage Any web application, whatever the programming language.

    Finds
    Known vulnerabilities, exposed files and admin panels, misconfigurations, and weaknesses in TLS and security headers.
    You get
    Findings for the tested address, in the same list as the findings of all other checks. Scans by hand or on a schedule.

Evidence reports

Reports an auditor can read

Kodator produces reports from scans, findings and decisions. They document your work. They do not certify compliance.

  • PCI DSS v4.0.1

    PCI DSS evidence report

    For each requirement Kodator contributes to: figures, a short explanation and links to the findings. For all projects in PCI scope or for a single project. Available as PDF.

    Steps and evidence – PCI DSS evidence report
  • Cyber Resilience Act

    CRA evidence report per product and release

    The state of the evidence per clause: proven, partly indicated or not covered. It opens with what was examined and what was not. Frozen for a release, live for a product. Export as PDF is planned.

    Steps and evidence – CRA evidence report per product and release
  • SBOM

    SBOM report

    The bill of materials per asset as CycloneDX JSON and as PDF: summary, licences, components with open vulnerabilities and the full list of components.

In addition: finding reports as PDF per organisation, project or scan. Every PDF export is recorded in the audit log.

Platform

What applies to every check

These functions come with every product. They turn individual scan results into a body of findings you can work with.

  • One finding, one row

    Kodator brings the results of all engines into one format and removes duplicates. A finding keeps its fingerprint across scans; shifted lines do not create a new entry.

  • Risk score from 0 to 100

    Calculated from CVSS, exploit probability, the flag for actively exploited vulnerabilities, the scan type and the business criticality of the project. Every factor is explained on the finding.

  • Remediation deadlines

    Every finding gets a deadline by severity; you set the number of days yourself. Overdue items are visible. Whoever accepts a risk needs a justification and an expiry date.

  • Audit log

    Actions of users, the API and runners are recorded continuously and hash-chained. The log cannot be changed unnoticed.

  • Schedules

    Scans daily, weekly, monthly or by your own cron rule, with a time zone. Every planned start is recorded, including a missed one.

  • Git hosting and pipeline

    GitHub, GitLab, Azure DevOps and Bitbucket Cloud: scans on push and pull request, a status on the pull request, protection of the default branch. Plus a CLI and examples for common CI/CD systems.

Getting started

From zero to the first scan

Six steps lead from access to the first report. Where the deployment models differ, the step says so.

  1. Step 01

    Get access and create the organisation

    Signing up creates your organisation; whoever creates it is its owner. Further people join through an invitation link and get a role: viewer, member, admin or owner.

    Online · Hybrid
    You get access from us. The hosted environment in the EU is being set up; until then we show Kodator in a demo environment.
    On-premises
    First you install Kodator at your site: with Docker Compose or with the Helm chart for Kubernetes.
  2. Step 02

    Create a project

    A project groups what belongs together: repositories, container images and web applications. You set the business criticality and whether the project is in PCI scope. Both feed into the risk score.

  3. Step 03

    Connect the code

    Kodator needs a way to reach what is to be checked. Which one depends on the deployment model.

    Online
    Under "Integrations" you connect GitHub, GitLab, Azure DevOps or Bitbucket Cloud with an access token, or GitHub as an app. Then you add the webhook that is shown and import the repositories into the project.
    Hybrid
    Under "Runners" you create a registration token, which is shown only once, and use it to start the runner in your network: with Docker, Docker Compose or Helm. It needs outbound HTTPS only. It scans assets set to the execution mode "Hybrid runner" on site.
    On-premises
    As in online operation, but with your own installation. Internal Git servers can be connected as well.
    Without repository access
    The runner image scans inside your own CI/CD pipeline and uploads only findings and the SBOM.
  4. Step 04

    Start or schedule the scan

    You start the first scan on the project page, for one asset or for all of them. After that it runs by itself: on every push to the default branch, on every pull request or on a schedule. Before a web application can be tested, you prove ownership of its domain.

    Or with the CLI, also from a pipeline. It uploads the directory to Kodator for the scan.

    kodator scan . --project payments-api --wait --fail-on high
  5. Step 05

    Review the findings

    The list of findings shows the results of all checks together, critical ones first, with risk score and remediation deadline. For each finding you decide: fix it, mark it as a false positive, or accept the risk with a justification and an expiry date. When a later scan no longer reports a finding, it counts as fixed.

  6. Step 06

    Open the report

    Under "Compliance" you find the PCI DSS evidence report and the CRA evidence report per product. You download the SBOM on the asset and the finding report as PDF from the list of findings.

In development

Source code rules for PHP and Kotlin, sign-in through SSO, connections to Jira, Slack and Microsoft Teams, the CRA evidence report as PDF and fully offline operation of the engines are on the roadmap and are not part of the product today.

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.