Skip to content
Trausto

IEC 62443-3-2 · for OT operators · Swiss company

IEC 62443 risk assessments your auditor can follow.

Trausto is the software for your IEC 62443-3-2 risk assessment: zones, conduits, risks and SL-T in one project, through to the report.

Where you lower a rating, Trausto asks for the reason and prints it in the report. Assessment content and uploaded evidence are encrypted in your browser before upload.

For operators where one person owns the OT risk assessment — and assembles the evidence from spreadsheets and Word templates today.

Where assessments get stuck, and what Trausto does instead

Asset lists, zone diagrams and risk tables sit in separate files, and every change has to be carried into each of them by hand.
In Trausto they are one project: the zone diagram and the report are generated from the same data.
A year later, nobody can say why a zone got SL-T 2 and not 3.
Trausto proposes the SL-T from the detailed risks. Setting it lower needs a written reason, and the report prints the proposal, the decision and the reason.
A review means comparing file versions and collecting comments from e-mails.
A reviewer reads the project and comments on it without changing the analysis; each comment is kept with its author and time.
Network diagrams and asset lists end up in tools never meant for sensitive architecture data.
Assessment content and uploaded evidence are encrypted in your browser before upload. What we hold in the clear is stated further down this page.

How an assessment comes together

Three steps on one data set. What you enter once carries through to the report.

01

Define the system

Create assets, zones and conduits — or let the AI import read them from the documents you already keep. Criticality, business and safety impact are fields, not notes in a margin.

02

Assess the risk

Initial and detailed risk assessments under the methodology your project carries: threats, vulnerabilities, countermeasures and residual risk.

03

Review and document

A reviewer reads the project and comments without changing the analysis; each detailed risk is approved by name and date. The report names the methodology and its version.

All seven steps of an IEC 62443 project →

What comes out

The sample project
A fictional plant from the system under consideration to the approval, as Trausto models it.
Report and export
A report as PDF, DOCX or HTML, generated in your browser; it names the methodology and its version. The project as JSON that can be imported again, and as an archive that adds the uploaded documents, the AI history and the earlier versions. A downloaded report or export is no longer encrypted.
The review trail
Each comment of a reviewer is kept with its author and time; each detailed risk carries who approved it and when.

In the product today

Assets and their connections · functional groups and initial risk · zones, conduits and the zone diagram · security level targets (SL-T) per zone and conduit, proposed from the detailed risks · requirements mapped to FR1–FR7 · tasks with an owner and a due date · earlier versions of a project, with restore · access to a single project for an auditor or a contractor, as viewer, reviewer or editor · the interface in English, German, French and Italian · ISO/IEC 27005 or the CLC/TS 50701 rail profile as a project’s methodology · an organisation-wide ISMS risk register · audit log for your tenant administration.

What we can read, and what we cannot

In short, as the whitepaper states it:

  • Assessment content and uploaded evidence are encrypted in your browser before upload. Our server stores them as ciphertext.
  • We hold metadata in the clear, among them your email address, the names of your organisations and tenant, who has access to what, timestamps and the audit log. The table is section 7 of the whitepaper.
  • The optional platform AI is a separate path: what you confirm in its consent dialog goes in the clear through our server to the one model you chose.
  • The operator is a Swiss company. The platform’s databases and object storage are at Cloudflare, a US provider, in its EU jurisdiction, not in Switzerland; that is why assessment content is encrypted before it leaves your browser.
  • The code that encrypts and decrypts runs in your browser, and our server delivers it. Section 8 of the whitepaper states this limit and what else the design does not protect against.
  • Someone who has lost both passkey and recovery phrase cannot recover the account through the product; what was encrypted only to that account stays unreadable, for us too.
  • Single sign-on (SSO) is not offered today.

Security Whitepaper

Trausto is a hosted service; there is no on-premise version. Instead, Trausto encrypts in your browser: our server stores your assessment content as ciphertext.

Trausto is alpha software. Neither the software nor the whitepaper has been reviewed externally yet. An external penetration test and an external review of the whitepaper will take place in 2027 at the earliest.

See Trausto on a sample project

In a single technical session we work through a fictional sample plant — its zones, conduits and security level targets (SL-T) — and show how Trausto turns it into IEC 62443 evidence an auditor can follow. No data from your own plant is needed; if you want to discuss your installation, we agree on how separately, not through the contact form.