- 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 == 0and scan commit equals release commit- Also required by
- ISO/IEC 27001 A.8.28PCI DSS 6.2.4CRA Annex IInternal SSDLC-07
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.
See it as
- Know what to prove.
- Collect it at the source.
- Validate it once.
- Reuse it everywhere.
Stop chasing screenshots. Scan results land on the controls they prove.
See the evidence →| Finding | Control | Status | Next |
|---|---|---|---|
| Outdated library in api | A.8.8 | Ticket in progress | Retest · next release |
| Weak TLS config on edge | A.8.24 | Fixed | Retest · 6 d |
| Secret in build log | A.8.12 | Closed | Evidence validated |
No score. Every number opens the controls and evidence behind it.
Requirement packs in preparation
Map a framework once. The activities and evidence follow.
See how it works →| Requirement | Control | Expected evidence | Due |
|---|---|---|---|
| PCI DSS 6.3.3 | Patch management | Dependency scan | 17 d |
| ISO/IEC 27001 A.5.18 | Access review | Signed review record | 32 d |
| EU CRA Annex I | SBOM per release | SBOM | Next release |
No score. Every number opens the controls and evidence behind it.
Connectors in development
Upload pipeline output once. It proves every control that relies on it.
See where evidence comes from →| Source | Evidence | Status | Collected |
|---|---|---|---|
| CI · release/4.2 | SBOM | Validated | Uploaded |
| CI · release/4.2 | Dependency scan | Validated | Uploaded |
| Ticket | Bump library to 2.14.1 | Open | Assigned to api team |
No score. Every number opens the controls and evidence behind it.
Know where you stand today, not at the next audit.
See the reporting →| Framework | Open gaps | Evidence missing | Next activity |
|---|---|---|---|
| ISO/IEC 27001:2022 | 6 | 9 | Access review · 32 d |
| PCI DSS v4.0.1 | 4 | 3 | External scan · 17 d |
| EU Cyber Resilience Act | 9 | 11 | SBOM · next release |
| ISO/IEC 42001:2023 | 7 | 14 | Management review · 41 d |
No score. Every number opens the controls and evidence behind it.
Trace every conclusion to its evidence and the person who reviewed it.
See the model →| Conclusion | Evidence | Provenance | Reviewer |
|---|---|---|---|
| A.8.8 operating effectively | 3 items | CI · 2026-09-28 | Named person |
| 6.3.3 requirement met | Dependency scan | CI · 2026-09-28 | Named person |
| A.5.18 under review | Access review | Ticket export | Pending |
No score. Every number opens the controls and evidence behind it.
The problem
Compliance work is fragmented.
Every framework asks for proof, and every request starts from scratch.
- Scattered Evidence sits in scanners, pipelines, tickets, documents and spreadsheets.
- Asked again Different teams ask engineering for the same information, again.
- Copied by hand The same scan result is copied by hand into several assessments.
- Stale on arrival Reports are out of date on the day they are issued.
- 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.
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.
P · Plan
Know what must be true, and how you meet it
Map every obligation once to reusable controls, so a PCI DSS program, CRA readiness and ISO/IEC work share the same controls instead of copied spreadsheets.
P · Plan
Requirement
An obligation from a regulation, standard or internal policy, recorded once and scoped to the assurance programs it applies to.
P · Plan
Control
A reusable implementation that meets one or more requirements, so one change shows its impact across every framework it serves.
D · Do
Run the work and capture proof as it happens
Activities operate the controls once or on a schedule, and evidence lands on the record with its source and time, not as last-minute screenshots.
D · Do
Activity
Work done once or on a schedule to operate a control, with an owner and a due date.
D · Do
Evidence
Proof the activity happened, from a person or a system, stored with its source, time, scope and SHA-256 hash.
C · Check
Test the evidence before anyone relies on it
Deterministic checks run first. Where judgment is needed, a named reviewer decides. Tool and AI output stays candidate evidence until a person adjudicates it.
C · Check
Validation
Checks flag missing, stale or invalid evidence; reviewers confirm or reject it under their own name.
A · Act
Close the gaps and decide on the record
Gaps become owned actions, and decisions and reports are drawn from the same record, so each conclusion traces back to its evidence.
A · Act
Finding and remediation
Gaps become owned actions with deadlines and acceptance criteria, and are checked again when they close.
A · Act
Decision and report
Decisions are made against recorded criteria. Every report is a view of the record, never a hand-edited copy.
P · Plan · Secure SDLC
Requirements → Requirement, Control
Security and compliance requirements for a product become requirements in its assurance program, linked to the controls that meet them.
P · Plan · Secure SDLC
Design → Control
Threat models and design reviews are recorded against the controls they support.
D · Do · Secure SDLC
Build → Activity, Evidence
Secure coding, static analysis and dependency analysis run as activities. Their reports are recorded as evidence with source, time and hash. Pipeline connectors are in development.
C · Check · Secure SDLC
Verify → Validation
Dynamic testing, penetration tests and security reviews produce candidate evidence. A named reviewer adjudicates it before anything is relied on.
A · Act · Secure SDLC
Release → Decision and report
The release gate is a decision about recorded criteria. It is not proof that a product is secure.
A · Act · Secure SDLC
Operate and respond → Finding and remediation
New vulnerabilities and incidents become findings with owners, and feed fresh requirements into the next Plan.
- P · PlanRequirementAn obligation from a regulation, standard or internal policy.
- P · PlanControlA reusable implementation that meets one or more requirements.
- D · DoActivityWork done once or on a schedule to operate the control.
- D · DoEvidenceProof the activity happened, from a person or a system.
- C · CheckValidationDeterministic checks, then human review where judgment is needed.
- A · ActFinding & remediationGaps become owned actions with deadlines and acceptance criteria.
- A · ActDecision & reportConclusions and every report are views of the same record.
Your secure SDLC, on the same record
- P · 01RequirementsSecurity requirements, abuse cases
- P · 02DesignThreat modelling, architecture
- D · 03BuildSecure coding, SAST, SCA
- C · 04VerifyDAST, penetration test, review
- A · 05ReleaseGate on recorded criteria
- 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
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.
- 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.
- Source
- CI/CD · pipeline job
- System
- payment-api
- Commit
- 9c1e4b7
- Components
- 412 · vulnerable 3
- SHA-256
- 3f9a0c…e41b
- Controls
- A.8.8 · PCI 6.3.3 · CRA Annex I
One scan supports three controls in three frameworks.
- Source
- CSV export · identity system
- Period
- Q3 2026
- Accounts
- 87 reviewed · 5 revoked
- Reviewer
- Named person
- SHA-256
- c04f8a…7d12
- Controls
- A.5.18 · PCI 7.2.4
One review supports two controls in two frameworks.
- Source
- CI/CD · release/4.2
- System
- payment-api
- Release
- 4.2.0
- Components
- 412
- SHA-256
- 8e33b1…aa40
- Controls
- CRA Annex I Part II
Collected per release. Due again at the next release.
- Source
- PDF upload
- Title
- Secure development policy
- Version
- 3.1 · approved
- Owner
- Named person
- Review due
- 2027-03-01
- Controls
- A.5.1 · A.8.25 · SDL-01
One policy supports three controls. Flagged when its review lapses.
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.
Evidence
Controls
Frameworks
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.
| Activity | Frequency | Expected evidence | Accountable | Due | State | Frameworks |
|---|---|---|---|---|---|---|
| Annual penetration test | Annually | Test report and retest record | Security | 2026-09-26 4 days overdue | ! overdue | PCI DSS · EU CRA · ISO/IEC 27001 |
| External vulnerability scan | Quarterly | Scan export | Security | 2026-10-17 in 17 days | • due no evidence linked | PCI DSS |
| Access review | Quarterly | Signed review record | IT operations | 2026-11-01 in 32 days | ○ scheduled | ISO/IEC 27001 · PCI DSS |
| SBOM generation | On event | SBOM of the release | Engineering | 2026-09-01 event · REL-2026.11 | ✓ done version 12, 2026-09-01 | EU CRA |
| Dependency scan review | Monthly | Reviewed scan report | Engineering | 2026-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.
- Artefact
sast-report.sarif- Source
- CI pipeline · release 2026.10
- Collected
- 2026-10-03 09:14 UTC
- SHA-256
3f9a0c…e41b
One shape for every source
Facts, not file formats
Scanner output, documents and tickets become the same kind of fact, so a rule never depends on which tool produced it.
- Kind
- Static analysis (SAST)
- High results
- 2
- Medium results
- 5
- Location
- Both high results in
/admin/* - From
3f9a0c…e41b
Fail closed
Same input, same result
Rules are visible and deterministic. Missing or invalid evidence is never read as compliance; it is reported as missing.
- Hash re-check
- Match
- Rule result
- Fail 2 high results
- Next
- Sent to human review
Human adjudication
A named person decides
Scanner and AI output is candidate evidence. AI may suggest a decision; the reviewer makes it, under their own name.
- AI suggestion
- Accept as an exception (proposal only)
- Decision
- Exceptions 2 high results accepted until 2026-11-15
- Justification
- Both results are in an unreachable admin path; fix scheduled for 2026.11.
- Reviewer
- Named security reviewer · 2026-10-03 · v2
Explainable
Every status can answer “why?”
The answer is a trail that ends at evidence. When nothing can be concluded, the status says so.
- Status
- Exceptions
- Why
- Reviewer decision v2 → rule
SDL-04→ SAST facts →3f9a0c…e41b - Re-checked
- When the exception expires on 2026-11-15
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
Every configured criterion passed for the recorded target, scope and window.
No blocking failure remains; each condition has an owner and a due date.
A blocking criterion failed or was not assessed.
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.