Skip to main content

Security

Boundaries you can inspect. Approvals you control.

How Veriom keeps every review bounded to your workspace and backed by evidence, and why merging, deploying and accepting risk stay with your team.

Boundaries

Your system stays inside its workspace boundary.

Sources and tokens are scoped to one workspace, untrusted content stays data, and nothing reaches your repository without an approval: a reviewer's, or a policy your admins set.

What crosses your workspace boundary, and the control at each crossing4 steps
  1. 01Workspace-scoped accessSources, API tokens and MCP connections belong to one workspace, and access is checked against its roles.
  2. 02Evidence, not instructionsTools submit typed evidence through the governed MCP gateway. They never send instructions to agents.
  3. 03Read-only collectionCloud collectors run read-only inventory commands in your environment, and provider credentials stay there.
  4. 04People keep the decisions that matterAgents prepare typed, cited proposals. A fix opens as a draft only once a reviewer or a policy your admins set approves it, and merging, reports and accepted risk stay with a person.

Who decides each step of a fix.

By default Veriom starts audits, confirms merged fixes and publishes each audit's report on its own. Policies that approve work are off until an admin turns them on, and every automatic step is in the activity log.

Prepare a fixA person or a policy
Someone asks for a fix, or a policy your admins turn on prepares fixes after an audit. Veriom then rescans the patch on its own.
Open a draft pull requestA person or a policy
A reviewer approves the fix, or a policy an admin turns on approves it within limits the admin sets. By default: low severity, up to 3 files and 40 lines, no CI, auth or dependency files. A critical finding always needs a reviewer. A policy approval waits 30 minutes by default, and a reviewer can withdraw it; the draft then opens on its own.
Approve the pull requestAlways a person
Your team reviews the draft on GitHub. Veriom never approves a pull request.
MergeAlways a person
Your team merges on GitHub. No policy lets Veriom merge.
DeployAlways your team
Your own pipeline ships the change. Veriom never deploys; the next audit checks the merged code.
Accept a riskAlways a person
Only a person can accept the risk of a finding or approve a compliance exception.

Identity and access

Access follows the way your organisation already works.

Sign-in, provisioning and session rules follow your identity provider and the policy you set. A new role or a new API token appears in the workspace activity log.

Settings / Identity and accessSample data
  • SAML single sign-onEnterpriseOkta · example.com verifiedConnected
  • SCIM provisioningEnterpriseMembers and groups sync from OktaOn
  • Require two-factorGrowthFor every member of the workspaceOn
  • IP allowlistApplies to sign-in and the API3 ranges
  • Idle timeoutSign members out after inactivity30 min
  • Audit log streamingGrowthSplunk HTTP Event CollectorStreaming

SAML single sign-on and SCIM

People sign in through your identity provider; joiners and leavers follow your directory.

Enterprise

Required two-factor sign-in

A second factor becomes a policy every member must meet.

Growth and Enterprise

IP allowlist and idle timeout

Limit sign-in to your networks and end sessions idle for 15 minutes to 8 hours.

Least-privilege API tokens

Expiring workspace tokens carry only the scopes an integration needs, chosen from 25.

Every plan

Audit log streaming

Send the workspace activity log to your SIEM.

Growth and Enterprise

Role-bound approvals

Report approval and remediation stay decisions by people with the right role.

Every plan

Data handling

Know what is kept, for how long, and how to take it back.

These measures come from Annex II of our data processing agreement and the limits your plan enforces, so a reviewer can check each one against the contract.

A small graphite architectural model sealed inside a glass display case on a stone plinth, with a fine yellow thread entering through a brass ring in the glass.
to choose from for each expiring API token
25scopes
of audit log on Growth; Enterprise has no plan limit
1,095days
to cancel a workspace deletion before it runs
7days
the shortest idle timeout a workspace can set
15minutes

Encrypted, per workspace

TLS in transit, encrypted managed storage and per-workspace source data keys.

Secrets stay masked

Secret values are masked in logs and in evidence views.

Retention you choose

Audit logs kept for 90, 365 or 1,095 days on Free Trial, Starter and Growth. Enterprise has no plan limit.

Export and deletion

Export a whole workspace, and cancel a deletion during its seven-day grace period.

Bounded model context

Models receive the selected evidence a task needs, not the whole workspace.

No training on your data

Veriom does not use customer data to train its own general-purpose models.

Talk to us about your review.

Bring your questionnaire; we will walk through the controls and the evidence with your team.