KIT / Secure / Free template

Zones and conduits worksheet (Excel)

An Excel workbook for doing a first zones and conduits design the IEC 62443-3-2 way: list zones and their target security levels, then every conduit and flow, including new AI and cloud connections.

Download Excel template Excel · 31 KB · free, no sign-up · 1-2 days per site to complete

CONTENTS

What is inside

  • Instructions

    A short method based on IEC 62443-3-2 for a first pass with a small team.

  • Zones

    Zone ID, name, Purdue level, assets, owner, criticality, SL-T and current SL estimate with a gap formula.

  • Conduits

    Conduit ID, the zones it connects, protocols, direction, controls and remote access details.

  • Data flows

    Every allowed flow, including historian, MES, AI and cloud flows, with justification and approval status.

  • Worked examples

    Rows marked EXAMPLE for a packaging line, a safety zone, the IDMZ and a cloud analytics flow.

PROCEDURE

How to use it

  1. 01

    Start from your OT asset inventory and network drawings, even if they are out of date.

  2. 02

    Group assets into zones by function, criticality and location, and keep the safety system in its own zone.

  3. 03

    List every conduit between zones and every flow through it, with direction and protocol.

  4. 04

    Set a target security level per zone with operations and engineering, then estimate today's level.

  5. 05

    Use the gap column to prioritize firewall rules, remote access changes and segmentation projects.

  6. 06

    Run any new AI or cloud data flow through the Data flows sheet before go-live.

FAQ

Frequently asked questions

Do we need a full IEC 62443-3-2 risk assessment first?

Not to start. A first zone and conduit map from a half-day workshop already shows the biggest exposures, such as flat networks and permanent vendor access. Use it as the input to a more formal risk assessment later.

How many zones should a mid-market plant have?

Enough to separate what has different risk and owners, and few enough to manage. Typical first designs have an enterprise zone, an IDMZ, a site operations zone, one zone per line or cell group and a safety zone. Over-segmenting early creates rules nobody maintains.

Where should AI and cloud analytics sit?

Usually outside the control zones. Data should leave through the IDMZ, ideally from a historian replica or broker, with no inbound path to controllers. Edge AI devices that must sit on a line go in that line's zone with tight conduit rules.

Read alongside