What Trausto covers of IEC 62443-3-2, and what stays yours
This page maps the zone and conduit requirements (ZCR) of IEC 62443-3-2 to what Trausto records and prints in its report. It claims no compliance or conformity with the standard; whether a project’s results are adequate is for you and your auditor to judge.
“Covered” says only that the data has a place and reaches the report, not that what was entered is correct. The titles in the first column are our own short titles, not the wording of the standard.
Checked against the product on 14 November 2026
What stays yours
- The Cybersecurity Requirements Specification (CRS). Trausto supplies the risk-assessment part in its report; it has no CRS template.
- A statement on the threat environment of the system as a whole. Trausto records source, type and origin per threat.
- Your organisation’s security policies and the regulatory requirements that apply to you. You can upload them in step 6, and the report lists them.
- External dependencies, accountable organisations and physical access points. No field holds them; a zone’s or conduit’s description, which the report prints in full, can.
- The formal sign-off. The report says that it is not recorded in Trausto and ends with an empty signature block; the asset owner signs on paper.
Requirement by requirement
- Covered:
- you can record it, and the report prints it.
- Partly:
- part of it has a place; the text says which part does not.
- Stays yours:
- no field carries it; the text says where you can record it instead.
ZCR 1 · System under consideration
| Requirement | Status | What Trausto does |
|---|---|---|
| 1.1 System under consideration identified | Covered | Step 1 holds the system’s scope, boundaries and assumptions next to the project’s name and description. The report prints them and marks an empty one as not stated. |
| 1.1 Security perimeter | Partly | It follows from zones of the type “external”, from each conduit’s answer whether it crosses the system boundary, and from the boundaries written in step 1. The diagram draws crossing conduits dashed; it draws no perimeter line. |
| 1.1 Access points | Partly | Each conduit records whether it crosses the system boundary, and the report prints the answer. Physical access points have no field. |
| 1.1 Inventory of the system | Covered | Step 1 lists the assets and their connections. The report prints both, each asset with its type, criticality and device details. |
ZCR 2 · Initial risk assessment
| Requirement | Status | What Trausto does |
|---|---|---|
| 2.1 Per functional group | Covered | Step 2 rates each functional group’s worst case, with a consequence per dimension, and the report names the group’s assets. A likelihood set below the maximum without a reason, or the highest consequence rating, sends the zone to the detailed assessment. |
| 2.1 Per zone | Covered | A zone takes the rating of its assets’ groups, or an override with a reason. The report prints the value, where it comes from and the reason. |
| 2.1 For the system as a whole | Covered | Step 4 and the report’s title block show the worst group rating as the system’s initial risk. |
ZCR 3 · Zones and conduits
| Requirement | Status | What Trausto does |
|---|---|---|
| 3.1 Establish zones and conduits | Covered | Step 3 builds the zones and conduits, by hand or from an optional proposal per functional group. It counts assets in no zone and connected zones without a conduit. The report prints zones, conduits and the diagram. |
| 3.2 Business and control assets apart | Partly | You record it through the zone type, and the report prints it. Nothing checks the assignment. |
| 3.3 Safety-related assets apart | Partly | A functional group can be marked as performing a safety function, and the zone proposal puts its assets in safety zones of their own. The report notes a safety zone whose SL-T is below that of a zone it connects to. Nothing checks a zone’s content afterwards. |
| 3.4 Temporarily connected devices | Stays yours | No field. Record such devices as assets in a zone of their own and describe them in its description, which the report prints in full. |
| 3.5 Wireless devices | Partly | A conduit of the type “wireless” carries it into the report and the diagram. A device has no wireless flag. |
| 3.6 Devices on external networks | Partly | A conduit to an external zone crosses the system boundary, and such a conduit always needs the detailed assessment. Nothing checks which devices belong in the zone. |
ZCR 4 · Initial risk against tolerable risk
| Requirement | Status | What Trausto does |
|---|---|---|
| 4.1 Is a detailed assessment needed? | Covered | Step 4 decides it for each zone and conduit and gives the reason. In doubt, and with the highest consequence rating, it is needed. Skipping a zone needs a written reason, and the report states every decision. |
ZCR 5 · Detailed risk assessment
| Requirement | Status | What Trausto does |
|---|---|---|
| 5.1 Threats | Covered | Step 5 goes through every catalogue threat and the project’s own threats for each zone or conduit: a risk, not applicable with a reason, or undecided. The report counts them and names the undecided ones. |
| 5.2 Vulnerabilities | Covered | Entered or imported (there is no scanner), linked to assets and risks, and listed in the report. |
| 5.3 Consequences | Covered | Each risk records an impact with a reason and its effect on confidentiality, integrity and availability. The report prints them. |
| 5.4 Unmitigated likelihood | Covered | A person sets likelihood and impact before a risk can be saved, and the report prints the reason. |
| 5.5 Unmitigated risk | Covered | Calculated from likelihood and impact on the methodology’s scale, and printed. |
| 5.6 SL-T per zone and conduit | Covered | Trausto proposes an SL-T and shows where it comes from. You decide; a lower value needs a reason, and the report prints the proposal, its derivation, the decision and the reason. |
| 5.7 Unmitigated risk against tolerable risk | Covered | Once your organisation has confirmed the tolerable risk, each risk is marked as within or above it. |
| 5.8 Existing countermeasures | Covered | Countermeasures carry an implementation status, and each zone and conduit a 62443-3-3 status. Each risk names its countermeasures. |
| 5.9 Re-evaluated likelihood and impact | Covered | A person rates the residual risk after the countermeasures, and the report prints the rating. |
| 5.10 Residual risk | Covered | Each risk can record a residual risk today and one after the planned countermeasures. The report prints both and the band the 62443-3-3 status supports; a residual rated below that band needs a reason. |
| 5.11 Residual risk against tolerable risk | Covered | Each zone and conduit gets a verdict against the tolerable risk. A residual above it counts as accepted only once it is approved with a reason, and the approval lapses when the rating or the reason changes. |
| 5.12 Additional countermeasures | Partly | Step 6 and the report list, for each zone and conduit, every gap with its status, reason and open task. The report’s list of security requirements does not say where each one applies. |
| 5.13 Document and communicate | Partly | Trausto produces the report (PDF, DOCX, HTML) and the project export. A reviewer, also an outside auditor invited by link, reads and comments. Handing the results over stays yours. |
ZCR 6 · Documentation
| Requirement | Status | What Trausto does |
|---|---|---|
| 6.1 Cybersecurity requirements specification | Partly | The CRS is your document. Trausto supplies the risk-assessment part in the report, which lists the documents you uploaded in step 6. |
| 6.2 Description of the system | Partly | The report prints the system description, or the project description if there is none. |
| 6.3 Zone and conduit drawings | Covered | Step 3 draws the diagram, for download as SVG or PNG, and the report embeds it with each SL-T. |
| 6.4.1 Name | Covered | Zones and conduits have names, used as headings in the report. |
| 6.4.2 Accountable organisations | Stays yours | No field. Write it in the description, which the report prints in full. |
| 6.4.3 Logical boundary | Partly | The zone’s assets and its description. |
| 6.4.4 Physical boundary | Partly | No field of its own: a physical asset (a site, a building, a cabinet) in the zone, and the description. |
| 6.4.5 Safety designation | Partly | The zone type “safety”, in the report and the diagram. Conduits have none. |
| 6.4.6 Logical access points | Partly | They follow from the conduits that end in the zone, each with its boundary answer. |
| 6.4.7 Physical access points | Stays yours | No field. Write them in the zone’s description. |
| 6.4.8 Data flows | Covered | The connections of step 1 and each conduit’s protocols, ports and direction are printed under the conduit. |
| 6.4.9 Connected zones and conduits | Covered | Each conduit names the two zones it connects, in the report and the diagram. |
| 6.4.10 Assets, classification and value | Partly | Assets with their criticality and device details. Business value is rated per functional group, not per asset. |
| 6.4.11 SL-T | Covered | See 5.6. |
| 6.4.12 Applicable security requirements | Partly | For each zone and conduit: the level reached per foundational requirement and every gap with its status and reason. Requirements that are met are counted, not listed. |
| 6.4.13 Applicable security policies | Stays yours | No policy field. A countermeasure aimed at the zone can name one, and the report shows it with the zone. |
| 6.4.14 Assumptions and external dependencies | Stays yours | No field per zone or conduit; use the description. Assumptions for the whole system are in step 1. |
| 6.5 Assumptions about the operating environment | Partly | Step 1 holds them, and the report prints them. |
| 6.6 Threat environment | Partly | Per threat only: its source, type and origin. There is no statement for the system as a whole. |
| 6.7 Organisational security policies | Stays yours | They stay yours. Upload them in step 6, and the report lists them. |
| 6.8 Tolerable risk | Covered | Set or confirmed by your organisation and used in step 4. The report gives the level, its source and when it was confirmed. |
| 6.9 Regulatory requirements | Stays yours | They stay yours. “Legal and regulatory” is only a consequence dimension in step 2. Upload them in step 6, and the report lists them. |
ZCR 7 · Approval
| Requirement | Status | What Trausto does |
|---|---|---|
| 7.1 Asset owner’s approval | Partly | Step 7 records who approved each risk and when, with a reason where one is needed. The report prints the date and the reason, and the approver when you switch that on for the export; it says that the formal approval is not recorded in Trausto, and ends with an empty signature block: the asset owner signs on paper. |
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.