The Platform
Three workflow layers. One encrypted backbone. From asset inventory to threat-led risk and audit-ready evidence — engineered for regulated operators that need confidence today.
01
Capture every IACS asset — PLCs, HMIs, historians, engineering workstations, network gear, safety systems — and group them into isolated zones and conduits. Criticality, safety impact, exposure and ownership are first-class fields.
02
Model business, operational, supervisory, control and field zones as explicit trust boundaries. Every conduit is enumerated, classified, mapped to SL-T targets, and exportable as IEC 62443 evidence.
Level 5 — Enterprise
ERP, business systems, internet boundary
Level 4 — Site Business
Site IT, scheduling, reporting
Trust Boundary — Industrial DMZ
Patch servers, jump hosts, AV repositories
Level 3 — Site Operations
MES, historians, engineering workstations
Level 2 — Area Supervisory
HMI, SCADA, alarming
Level 1 — Basic Control
PLCs, DCS controllers, RTUs
Level 0 — Process
Sensors, actuators, instrumentation
03
AI accelerates risk work; it does not replace engineering judgement. Trausto separates AI assistance into two clearly bounded capabilities.
Generate plausible threat scenarios per zone and asset class. The co-pilot proposes; engineers approve, edit or reject. Every accepted scenario carries its provenance — which model proposed it and who approved it — reviewable, attributable and exportable.
Connect your own internal AI instance instead of a public one. Requests stay scoped to the project and run only against the endpoint you configure — including fully in-browser execution — and accepted results carry attributable provenance. Enterprise AI becomes part of the security process, not an unmanaged data-leakage channel.
04
Basic Risk Assessment — component-driven; suitable for first-pass site evaluations and gap analyses.
AI-assisted Risk Assessment — same data model; the co-pilot accelerates scenario generation and evidence drafting.
Detailed Risk · IEC 62443 security requirements · supplier evidence portals — for full operator-grade programmes.
Insight
Trausto runs as SaaS, operated from Switzerland. That is the whole offer: there is no on-premise edition to evaluate and no deployment matrix to negotiate. The reason is that the question on-premise exists to answer — who can read your assessments — is already answered earlier and more strongly, in the browser, before anything reaches us.
Multi-tenant SaaS, built and operated from Switzerland by a Swiss company on hardened cloud infrastructure. One code path, one set of controls, one thing to audit — for you and for us. Onboarding takes days, not a procurement cycle.
Every project carries its own encryption key, wrapped for each member and each device. Separation is enforced cryptographically, not only by a filter in a query — losing access is a key operation, not a flag in a table.
Ciphertext, plus the operational metadata the service needs in order to run: who holds an account, which project a record belongs to, when it last changed, how much storage you use. We itemise that surface below instead of claiming it away.
Disclosure
Encryption is half a promise until you say what stays unencrypted. This is the other half.
| Readable by us | Why it exists | |
|---|---|---|
| Assessment content | No — ciphertext only | Assets, zones, conduits, scenarios and evidence are encrypted on your device before upload. The one exception is the server-routed AI path below. |
| Uploaded evidence | No — ciphertext only | Supplier documents and attachments follow the same path as assessment content. |
| AI processing | Yes, for the duration of the request | If you use the server-routed AI assistant, the content of that one request passes through our worker in the clear to reach the provider you configured. Running the model in the browser avoids this — that is the honest reason the option exists. |
| AI operational telemetry | Yes — metadata | Which provider was called, whether it failed and how long it took. No request content. |
| SIEM export | Yes — audit metadata | If your org configures a SIEM webhook, audit events go to the endpoint you name. Assessment content is not part of that stream. |
| Account identity | Yes | Name and business email. Needed to authenticate you and to address you in support. |
| Project membership | Yes — structure, not content | Which record belongs to which project, and who has access to it. This is what enforces separation. |
| Timestamps | Yes | Created and last-changed times, so concurrent edits and version history work. |
| Audit log | Yes | Who did what, when. Required for the evidence trail the product exists to produce. |
| Usage volume | Yes | Storage consumed and record counts, for billing and capacity. |
Bring one real site — your zones, conduits and SL-T targets. In a single technical session we show how Trausto turns it into audit-ready IEC 62443 evidence, with your assessment content encrypted before it ever leaves the browser.