> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/regulatory-framework-mappings/iec-62443/iec-62443.md).

# IEC 62443

## Dispel’s Alignment With IEC 62443

### Looking for our mapping? Download it here:

{% file src="/files/Sa8g6jmum3LnzRRSyION" %}

![](https://2668873066-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LqlTpechIfonX0FqSV8%2Fuploads%2F9PYrlZxJtoblicS0g4Q2%2FIEC%2062443.jpg?alt=media\&token=4eac441f-8fde-45ed-b386-5da45f8cc59e)

## Introduction

Industrial automation and control system (“IACS”) organizations increasingly use commercial off-the-shelf (“COTS”) networked devices that are inexpensive, efficient, and highly automated. Control systems are also increasingly interconnected with non-IACS networks for valid business reasons. These devices, open networking technologies, and increased connectivity elevate the theoretical cyber risk of control system hardware and software. This, in turn, has raised concerns over Health, Safety and Environmental (“HSE”), financial, and/or reputational consequences from cyberattacks on deployed control systems.

IEC 62443 is not a proscriptive guide. The goal of the IEC 62443 series is to provide a flexible framework that facilitates addressing current and future vulnerabilities in IACSs and applying necessary mitigations in a systematic, defensible manner through an IACS Security Program (an “IACS SP”). For those readers working in Corporate, the reports you receive on Security Program efficacy are based off of Security Program Ratings (“SPRs”) – quantified assessments of the SP efficacy.

### IEC 62443 in Context

Much like the interrelationship between the National Institute of Standards and Technology (“NIST”) Cyber Security Framework (the “CSF”) Version 1.1 and the NIST Special Publications (the “NIST SP”s), IEC 62443 is structured as a series of interleaving modular documents. These documents are categorized into four series, with the designation structure of IEC 62443-\[series]-\[sub document number].

The **IEC 62443-1** series exists to define the terms and frameworks off of which the rest of the documents and recommendations contained in IEC 62443 rely.

The **IEC 62443-2** series is used to define the roles, responsibilities, requirements, and audit mechanisms for the organizational structure and management of the IACS SP. As such, the IEC 62443-2 series is the one that you are most likely to encounter first if coming over from Corporate or serving in an advisory capacity to a firm that follows IEC 62443. However, with the exception of IEC 62443-2-4, the rest of IEC 62443-2 is not the series of direct relevance to assessing products or services going into an IACS.

As a point of clarification, while new readers of the IEC 62443-2 series will notice that it generally references the IEC 62443-3 series when discussing product capabilities, they will also notice that some sections, such as §8.4 of IEC 62443-2-1, have documentation requirements which implicitly require any productized solution to have a set of underlying features. While true, with the exception of IEC 62443-2-4, sections throughout the rest of the series, including §8.4 of IEC 62443-2-1, are still cross-referenced over to IEC 62443-3.

**IEC 62443-2-4** serves as a guide for third parties interacting with an IACS on what to request at an organizational and procedural level from the IACS owner. IEC 62443-2-4 is the exception to the rest of the IEC 62443-2 series in that, regrettably, it does not provide a cross referencing structure as of the time of this document’s printing.

The **IEC 62443-3** series is most usefully perceived as the mapping series within the broader IEC 62443 structure from objectives to practical implementation at a technological level. Here, Framework Requirements (“FR”s) are aligned with System Requirements (“SR”) for control systems.

The **IEC 62443-4** series serves as a guide for suppliers of systems that form, or form a part of, a control system. As with IEC 62443-3, Framework Requirements (“FR”s) are aligned with System Requirements (“SR”) for control systems. **IEC 62443-4-1** is primarily focused on applying a standardized process to the development, deployment, and sustainment of product.  **IEC 62443-4-2** is primarily focused on defining the security attributes and capabilities that should be present within a control system, or a supporting component thereto.

Based upon the above summary, the remainder of this document is focused on Dispel’s coverage with respect to IEC 62443-3 and IEC 624430-4.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dispel.com/regulatory-framework-mappings/iec-62443/iec-62443.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
