ANSI/ISA-62443-2-1-2024 — Security program requirements for IACS asset owners

What the authority record establishes

Part 2-1 defines security-program requirements for asset owners across governance, risk, implementation, maintenance, and continuous improvement of IACS security.

Not law by itself

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

It creates an owner-specific program lens that product capability lists cannot satisfy by themselves.

Affected operating stages

• Program Governance
• Risk Assessment
• Implementation
• Operation
• Maintenance
• Improvement

Capabilities to examine

Asset Criticality And Operational Context

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for asset criticality and operational context.

Configuration, Baseline, And Change Monitoring

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for configuration, baseline, and change monitoring.

Secure Remote Access And Vendor Session Control

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for secure remote access and vendor session control.

Privileged Access, Credential, And Identity Governance

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for privileged access, credential, and identity governance.

Compliance Mapping And Control Evidence

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for compliance mapping and control evidence.

Incident Response And Recovery Support

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for incident response and recovery support.

Multi-Site Sensor, Data, And Policy Management

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for multi-site sensor, data, and policy management.

Device And Product Software-Supply-Chain Risk

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for device and product software-supply-chain risk.

Affected buyer audiences

• IACS asset owners
• OT security program owners
• auditors
• integrators

Implementation questions

• Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
• What is binding, what is guidance, and what is a technical or consensus standard?
• Which publication, adoption, effective, application, transition, and enforcement dates differ?
• Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
• How will a source revision affect open work and historical decisions?

Interpretation boundary

A provider mapping or tool feature is not proof that an asset-owner security program conforms to the standard.