Evidence-driven continuous assurance

Continuous assurance, built on real evidence.

Turn regulatory and security requirements into recurring controls, validated evidence, remediation and audit-ready reporting. Validate evidence once and reuse it across frameworks.

  • Know what to prove.
  • Collect it at the source.
  • Validate it once.
  • Reuse it everywhere.

Know where you stand today, not at the next audit.

See the reporting →

The problem

Compliance work is fragmented.

Every framework asks for proof, and every request starts from scratch.

  1. Scattered Evidence sits in scanners, pipelines, tickets, documents and spreadsheets.
  2. Asked again Different teams ask engineering for the same information, again.
  3. Copied by hand The same scan result is copied by hand into several assessments.
  4. Stale on arrival Reports are out of date on the day they are issued.
  5. No current view Management sees documents, not the current state of assurance.

The Dokimos model

From requirement to verified evidence.

One connected record, organised into assurance programs and run on the Plan, Do, Check, Act cycle used across ISO management systems. Every conclusion can be followed back to the evidence it rests on.

Plan · 01Requirement Plan · 02Control Do · 03Activity Do · 04Evidence Check · 05Validation Act · 06Finding and remediation Act · 07Decision and report

Explore the cycle

Plan, do, check, act. Then again.

Select a phase, a step or a secure SDLC stage to see how Dokimos helps at that point. Act feeds the next Plan.

  1. P · PlanRequirementAn obligation from a regulation, standard or internal policy.
  2. P · PlanControlA reusable implementation that meets one or more requirements.
  3. D · DoActivityWork done once or on a schedule to operate the control.
  4. D · DoEvidenceProof the activity happened, from a person or a system.
  5. C · CheckValidationDeterministic checks, then human review where judgment is needed.
  6. A · ActFinding & remediationGaps become owned actions with deadlines and acceptance criteria.
  7. A · ActDecision & reportConclusions and every report are views of the same record.

Your secure SDLC, on the same record

  1. P · 01RequirementsSecurity requirements, abuse cases
  2. P · 02DesignThreat modelling, architecture
  3. D · 03BuildSecure coding, SAST, SCA
  4. C · 04VerifyDAST, penetration test, review
  5. A · 05ReleaseGate on recorded criteria
  6. A · 06Operate and respondVulnerabilities, incidents

Operate and respond feeds new requirements into the next Plan.

Assurance programs hold it together: a PCI DSS program, CRA readiness, AI governance or a customer due-diligence request, each with its own scope, systems and frameworks. An assessment is one activity inside a program.

Compliance knowledge

Turn regulatory language into operational work.

Dokimos does more than reproduce the text of a standard. Each requirement is broken down into a control with what to do, how often, who usually owns it, what evidence is expected, what is acceptable and how it is checked.

  • What is required, and why
  • What to do and how often
  • Who should own it
  • Which evidence proves it, and from which system
  • Which other frameworks rely on the same control
  • What happens when it fails
SDL-04 Static analysis on every releaseDemo data
What to do
Run static analysis on the release commit and resolve or accept every critical result before release.
Frequency
Per release
Owner
Engineering lead
Expected evidence
SAST result for the release commit, with build identifier and collection time
Validation
critical_open == 0 and scan commit equals release commit
Also required by
ISO/IEC 27001 A.8.28PCI DSS 6.2.4CRA Annex IInternal SSDLC-07

Evidence sources

Evidence already exists. Dokimos puts it to work.

Upload what people produce and connect the systems that already record your engineering and security work. Each item becomes normalised facts a control can be checked against: which system, which build, when, what was found and whether the file is still the one that was collected.

Available Also uploaded: audit reports, attestations, screenshots and CSV, tool output and run manifests.

In development Also connected: static analysis (SAST), cloud configuration, ticketing, vulnerability scanners, SIEM. Categories, not a list of finished integrations. Tell us which systems you use.

Normalised evidence · penetration test reportDemo data
Source
PDF upload · external tester
System
payment-api · edge
Tested
2026-09-14 → 09-18
Findings
high 1 · medium 4
SHA-256
b71e2d…09ac
Controls
A.8.8 · PCI 11.4.1

One report supports two controls in two frameworks.

Evidence reuse

Collect once. Prove many.

Controls and frameworks have a many-to-many relationship. One validated piece of evidence can support several controls, and one control can meet requirements in several frameworks. Nobody uploads, reviews or explains the same scan four times.

When evidence goes stale, is replaced or fails validation, the conclusions that depend on it are flagged, across every framework that relied on it.

Assurance calendar Available

Compliance has a schedule.

Assurance is not a once-a-year document. Dokimos tracks what must happen, how often, who owns it, when it is due, what evidence is expected and which frameworks are affected if it slips.

Assurance calendar · next 90 daysDemo data
ActivityFrequencyExpected evidenceAccountableDueStateFrameworks
Annual penetration testAnnuallyTest report and retest recordSecurity2026-09-26
4 days overdue
! overduePCI DSS · EU CRA · ISO/IEC 27001
External vulnerability scanQuarterlyScan exportSecurity2026-10-17
in 17 days
• due
no evidence linked
PCI DSS
Access reviewQuarterlySigned review recordIT operations2026-11-01
in 32 days
○ scheduledISO/IEC 27001 · PCI DSS
SBOM generationOn eventSBOM of the releaseEngineering2026-09-01
event · REL-2026.11
✓ done
version 12, 2026-09-01
EU CRA
Dependency scan reviewMonthlyReviewed scan reportEngineering2026-10-09
in 9 days
• due
no evidence linked
PCI DSS · EU CRA

A row is done only through a link to evidence; a skipped row is a gap, not done. Continuous activities have no dated occurrence and are listed apart. No score.

Validation

Automation where possible. Human judgment where necessary.

Checks are deterministic and visible. Where judgment is needed, a named reviewer decides, and the decision is recorded with the evidence it used. Follow one control through each stage.

Evidence integrity

Hashed when it is collected

Each artefact is hashed on arrival and checked again before anything relies on it. A changed file is a different piece of evidence.

Raw evidenceDemo data
Artefact
sast-report.sarif
Source
CI pipeline · release 2026.10
Collected
2026-10-03 09:14 UTC
SHA-256
3f9a0c…e41b

AI proposes; it does not decide. It can help interpret requirements, suggest mappings, extract facts from documents and draft summaries.

Reporting

One assurance state. Every report you need.

A report is a view of the assurance state, not a separate source of truth. Reports change; the evidence base stays the same.

  • Technical remediation reportFindings, owners, deadlines and reproduction for engineering and security.Available
  • Release gate decisionGO, GO WITH CONDITIONS, NO-GO or NO VERDICT against criteria agreed before testing.Available
  • Audit evidence packEvidence index, requirement mappings, review decisions, timestamps and hashes.Available
  • Framework readiness reportsISO/IEC 27001, PCI DSS, CRA and ISO/IEC 42001 views of the same record.In development
  • Executive summaryMaterial risks, overdue obligations, readiness and remediation trends.In development
  • Due-diligence packA controlled external view for customers, partners and acquirers.In development
  • Machine-readable outputJSON, CSV and Markdown alongside HTML and PDF.Available
Release gate. A decision about recorded criteria.
Finding. Raw severity and adjudicated rating, side by side.
Evidence index. Every finding ends at a hashed artefact.
GO

Every configured criterion passed for the recorded target, scope and window.

GO WITH CONDITIONS

No blocking failure remains; each condition has an owner and a due date.

NO-GO

A blocking criterion failed or was not assessed.

NO VERDICT

Input was incomplete or invalid, so no decision is issued.

Report screens come from a fictional worked example. A GO is a decision about recorded criteria, not proof that a product is secure.

Dokimos helps you operationalise requirements, collect and validate evidence, assess readiness and report. It does not certify organisations, replace auditors, guarantee compliance or provide legal advice.

Stop rebuilding compliance from spreadsheets.

Build an assurance program that can be checked at any time, backed by the evidence your organisation already produces. Dokimos is developed by CyberTwierdza and is in early access.