IEC 62443 Foundational Requirements (FR 1-7)
IEC 62443 organizes technical system and component requirements into seven Foundational Requirements (FRs). Use this section to map each FR to QuantLayer controls, deployment patterns, and audit evidence.
Overview
Foundational Requirements (FRs) are the backbone of IEC 62443 technical requirements. Each FR includes baseline requirements and enhancements by Security Level (SL). QuantLayer helps implement these controls consistently across IT/OT/IoT while keeping enforcement operationally safe for production environments.
FR quick map
- FR 1 — Identification & Authentication Control (IAC)
- How QuantLayer implements FR1
- FR 2 — Use Control (UC)
- How QuantLayer implements FR2
- FR 3 — System Integrity (SI)
- How QuantLayer implements FR3
- FR 4 — Data Confidentiality (DC)
- How QuantLayer implements FR4
- FR 5 — Restricted Data Flow (RDF)
- How QuantLayer implements FR5
- FR 6 — Timely Response to Events (TRE)
- How QuantLayer implements FR6
- FR 7 — Resource Availability (RA)
- How QuantLayer implements FR7
FR detail pages
Related pages
- FR 1 — Identification & Authentication Control (IAC)
How QuantLayer implements IAC controls with OT-safe enforcement and audit-ready evidence.
- FR 2 — Use Control (UC)
Least privilege policy, personas, and session logging for approved actions.
- FR 3 — System Integrity (SI)
Detect tampering, log configuration drift, and quarantine compromises.
- FR 4 — Data Confidentiality (DC)
Encrypt control planes, protect artifacts, and keep evidence confidential.
- FR 5 — Restricted Data Flow (RDF)
Segment zones/conduits, allow approved flows, and contain suspected compromises.
- FR 6 — Timely Response to Events (TRE)
Correlate identity, device, and network signals to drive OT-safe response.
- FR 7 — Resource Availability (RA)
Keep systems resilient with staged enforcement, guardrails, and rollback history.
Evidence checklist
- Identity evidence: device enrollment, attestation results, credential lifecycle, and authentication events.
- Authorization evidence: policy versions, access decisions, least-privilege rules, and exceptions with approvals.
- Integrity evidence: secure boot/firmware checks, tamper alerts, configuration drift, and remediation actions.
- Segmentation evidence: zone/conduit policy, allowed flows, blocked flows, and change history.
- Response evidence: alert triage, containment actions, incident timelines, and post-incident reviews.