ANSI/ISA-62443-3-3-2013 — System security requirements and security levels

What the authority record establishes

Part 3-3 defines system security requirements and security levels for industrial automation and control systems.

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 helps structure system-level requirements, but capability marketing and certification labels need exact scope, version, and scheme evidence.

Affected operating stages

• Requirements
• Architecture
• Design
• Verification
• Operation

Capabilities to examine

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.

Industrial Firewall And Policy Enforcement

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 industrial firewall and policy enforcement.

Unidirectional Transfer And Network Isolation

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 unidirectional transfer and network isolation.

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.

Endpoint Allowlisting And Malware Prevention

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 endpoint allowlisting and malware prevention.

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.

Affected buyer audiences

• asset owners
• integrators
• product suppliers
• assurance teams

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 product can support requirements without establishing a system security level or organization-specific conformity.