Scenario · Viktor, IT security

Viktor has to prove security. Not just claim it.

Viktor is responsible for IT security. He knows nobody means harm; everyone just wants to get their work done quickly. With Omnisnap there is exactly one way to change software, and every step along it is reviewed and logged.

1way in: the ticket through the DevOps Gateway
Four eyesa named engineer reviews every change
Zurichprivate cloud, 3 zones, europe-west6
Minutesto roll back to an archived version
The story in three sentences

What changes for Viktor.

  1. The problem

    Customer lists in outside AI tools, files in private clouds, firewall rules someone switched off.

  2. The turn

    Every change goes through the Omnisnap airlock: reviewed by AI and an engineer, signed off on staging.

  3. The result

    Access, versions and sign-offs are logged. Viktor answers questions with a report, not a promise.

Viktor · IT security

The story, chapter by chapter.

For reading rather than watching: each chapter of the film as a short text.

Chapter 01The problem

Data everywhereNobody means harm. Yet the company is at stake.

A customer list in an outside AI tool, contracts in a private cloud, an invoice that is really an .exe. Each of these shortcuts saves someone ten minutes. Viktor usually only sees the consequences.

Data everywhere
Employeesjust want to get things done
!Outside AI toolscustomer list pasted
!Private cloudscontracts uploaded
!Invoice.exeopened

Nobody means harm. And still the company is at stake.

Chapter 02The turn

One way inOnly what goes through the airlock can be changed.

Every customer runs in their own closed private cloud in Zurich. There is exactly one way to change something: the ticket through the Omnisnap DevOps Gateway. The AI checks the request against the existing source code, and guardrails block anything harmful. Development happens in an isolated environment with test data.

“There is no back door. So I don’t have to guard one.”
Viktor, IT security
Chapter 03The turn

Rules in the systemRules the system enforces and documents.

Viktor’s policies no longer live only in the handbook. Roles, sign-offs and access rights are built into the processes: whoever may sign something off sees the button. Whoever may not, does not. Every sign-off is recorded with the person, the time and the reason.

“The rule isn’t in the wiki. It’s in the process.”
Viktor, IT security
Chapter 04The result

The day before the auditEvidence ready at any time.

Access to production data is the exception: Named engineers only, only as far as operations and support require, with multi-factor sign-in and every access logged. Every version is archived, and every change has a ticket, a reviewing engineer and a sign-off. What used to take weeks of preparation, Viktor exports the evening before.

The day before the audit
Viktor The ISO 27001 audit is tomorrow. Where do we stand?
Omnisnap All controls met, logs complete. The report is ready.
Viktor And access over the last 90 days?
Omnisnap Here — complete, with a reason for every grant. ✓

What used to take weeks is a walk in the park.

Chapter 05The result

Security and speedThe teams are faster. And the rules hold.

At the quarterly review, management asks whether everything the teams are building is secure. Viktor shows the access report. Built fast is not the same as run securely: at Omnisnap, one is the condition for the other.

“The report is the answer. Not a promise.”
Viktor, IT security
The Omnisnap airlock

One way in. Five checks. No other route.

This is the path every change takes before it reaches Viktor’s production. There are no other ways in.

How the airlock works
The platform behind it

What Viktor relies on

No marketing promises. Set down in the SLA, described technically on the security and technology pages.

The Omnisnap airlock

One way in, five checks: AI, guardrails, isolated development, the four-eyes principle and your sign-off on staging.

The airlock in detail

Production data

On request, the Omnisnap Cloud runs in your own cloud or on-premise, with an interface from production to development: our engineers then never see your production data.

Access to production data

AI with clear limits

AI in your processes is Google Gemini via Vertex AI, processed in Zurich, contractually without training on your data. For programming, AI works with source code only, never with your customer data.

AI and data on the technology page

Certified infrastructure

On ISO/IEC 27001 and SOC 2/3 certified infrastructure · revFADP · GDPR. Data encrypted at rest (AES-256) and in transit (TLS). Customer data is stored and processed in Zurich. Keys and secrets sit in a key vault in Zurich.

More on the infrastructure
Contact

What will your next audit ask you?

Send us your list of questions. We answer it within one working day, point by point.

Get in touch