Definition
IEC 62443 is a series of industrial automation and control system (IACS) cybersecurity standards developed by the International Electrotechnical Commission (IEC), covering the entire lifecycle including security levels (SL 0–4), risk assessment, security requirements, security design, and security implementation and maintenance. The standard divides IACS into zones and conduits, defining security requirements such as defense-in-depth, least privilege, and strong authentication, and is applicable to industrial control systems and IoT device security in critical infrastructures such as power, oil & gas, manufacturing, and transportation.
Technical Features and Architecture
The IEC 62443 technical architecture includes: Security Levels (SL)—ranging from SL 0 with no protection to SL 4 resistant to nation-state attacks, with target SL determined based on asset value and threats; Zones and Conduits—systems are divided into security zones, communicating via conduits that must meet corresponding security requirements; Security Requirements—the SR series defines requirements for identification and authentication, access control, sensitive data protection, incident response, etc.; Products and Systems—security requirements are defined separately for components (EDR) and systems (SMS). Combined with internal network isolation, VPN, and Device Management Platform, a secure industrial IoT system compliant with IEC 62443 can be built.
In cross-border scenarios, multinational critical infrastructures need to meet each country's industrial control security requirements, and IEC 62443 provides an internationally recognized security framework.
Application in IoT and cross-border scenarios
IEC 62443 is widely applied to: Power industrial control—the security of industrial control systems in substations, microgrids, charging stations; Smart manufacturing—safety protection for production line PLCs, robots, equipment management systems; Oil, gas, and transportation—critical systems such as pipeline SCADA and rail transit CBTC; Cross-border infrastructure—security compliance of transnational power grids, cross-border pipelines, and cross-border charging networks. Industrial IoT of cross-border critical infrastructure must refer to IEC 62443 to achieve security classification and protection.
SimtoLink provides secure connectivity for industrial IoT devices, leveraging intranet, VPN, etc., to help implement IEC 62443 compliance.
What zones and conduits mean for a SIM connection
IEC 62443 divides an industrial control system into security zones. Traffic between zones is allowed only through conduits that have been assessed. For international IoT, a cellular link is one way to build a conduit. It has an entry, an exit, permitted protocols, and an acceptable threat level. It is not the single fact that "the device can reach the internet." A security level describes the attack capability that must be resisted, from no special protection up to an organized attacker. The target level follows the consequences for the asset. Installing an IoT SIM does not raise it by itself. Component requirements and system requirements are separate: a gateway that passed one component assessment does not mean the whole cross-border conduit meets the system requirement.
To use this framework, draw the zone boundaries first, then decide where SIM traffic is allowed to go. A field control zone should not expose management ports directly. A remote maintenance zone should be its own zone, entered through a jump host or a private network. A cross-border conduit should also state which country the data lands in, who holds the keys, and how certificates are revoked. Public roaming can be a conduit for low-consequence assets, but it should terminate on a boundary device before it enters a control zone, and that device should open the station-side connection. User accounts, device certificates, and the SIM identity are registered separately. Disabling one of them should not be treated as if all three had expired.
When security levels and public roaming do not line up
A common drift is to write "an encrypted tunnel is in use" as if a higher security level had already been reached. A tunnel protects confidentiality and integrity on the conduit. It does not handle account abuse inside the zone, a backdoor left on an engineering workstation, or firmware whose source was never checked. Another drift is to let remote maintenance and production data share one SIM and one access point. If the maintenance laptop is stolen, the attacker rides the same conduit as production traffic. Enable access for the maintenance window and withdraw it when the window ends, rather than leaving it open indefinitely.
Cross-border sites also tend to ignore the lifetime of a supplier's remote account: after the project the SIM is still billed and the supplier certificate was never revoked. During troubleshooting, do not temporarily disable the boundary policy just to go faster. When emergency isolation is required, prefer a defined remote lock or disconnect the conduit, and keep the audit record. The isolation action itself should land in a controlled zone, rather than having people on site share one super account. If a conduit crosses a subnet, write the policy down to the specific service and direction. "Intranet hosts may talk to each other" is not enough.
A review should be able to point to the entry device of each cross-border conduit, the protocols allowed through it, and how it is closed. A connection whose shutdown method cannot be stated is only a temporary debug path. It does not mean the zone model is in place. After a debug account expires, someone has to check that it can no longer connect.