Skip to main content

Security controls

Implemented, bounded, and still challengeable.

The controls Veriom operates today, the evidence behind each, and the boundaries we still track, so a reviewer never confuses product behaviour with certification.

Control map

Every control with its evidence and its limit.

Release gates stay visible until they are actually complete.

IsolationWorkspace-scoped accessImplemented

What it does

Workspace permissions scope access to the active workspace and its members.

Evidence

Permission checks, access reviews and cross-workspace isolation tests.

Known boundary

Access depends on current membership, role and the scope of the requested action.

DataEnvelope-encrypted evidenceImplemented

What it does

Source snapshots and raw artifacts are encrypted with workspace-scoped keys.

Evidence

Encryption, integrity verification and protected evidence storage.

Known boundary

Ask about key-management requirements as part of your security review.

AIBounded model contextImplemented

What it does

AI-assisted reviews receive selected workspace evidence and bounded permissions. Merging, accepting risk and approving compliance exceptions always need a person.

Evidence

Evidence-scope checks, citation validation and review history.

Known boundary

Model assistance does not grant permission to publish or merge changes.

ExecutionBounded evidence collectionImplemented

What it does

Repository content is treated as untrusted evidence. Audits do not execute customer builds, tests, hooks or package scripts.

Evidence

Source-access checks, archive validation and recorded coverage.

Known boundary

A static review does not establish runtime behaviour. Missing evidence remains a coverage gap.

OperationsMetadata-only operational telemetryImplemented

What it does

Operational logs carry identifiers, states, latency and diagnostic codes, without source, prompts, completions, headers, request bodies or database parameters.

Evidence

Data-minimisation checks and documented retention controls.

Known boundary

Optional website analytics stay consent-controlled and separate from product evidence and model telemetry.

AssuranceIndependent penetration testRelease gate

What it does

External customer repository onboarding stays gated until independent security testing and release evidence are complete.

Evidence

Accepted-risk register and launch readiness gate.

Known boundary

Veriom does not claim a certification or a completed independent assessment it has not earned.

Compliance programs

Your frameworks, traced to the same evidence.

Adopt a versioned control library, and every control’s status shows the evidence, findings and exceptions behind it. A qualified assessor still decides certification or attestation. On Free Trial, Growth and Enterprise.

Compliance / ISO 27001:2022 · library v3Sample data
  • A.5.15Access controlSupported
  • A.8.24Use of cryptographySupported
  • A.8.16Monitoring activitiesPartial
  • A.8.28Secure codingException until 30 Nov
  • A.5.23Cloud servicesGap

Statuses come from accepted evidence and open findings, not from a checkbox.

Pinned library versions

A newer control library arrives as an upgrade diff to adopt on purpose. Past assessments are never rewritten.

Supported means supported

A control is supported only with fresh, accepted, non-conflicting evidence and no unresolved mapped finding.

Exceptions need a second person

An exception is time-bounded, approved by someone other than the proposer, and expires back to the evidence-derived status.

Gaps stay visible

Partial, gap and unknown keep missing or uncertain inputs in view instead of rounding them up.

Ask for the evidence behind a control.

We will show you the current controls, accepted risks, data boundaries and deletion behaviour, with the evidence behind them.