ISA/IEC 62443DesignSpecialist study guide Open the practice exam

62443 Design Specialist Study Guide

A condensed guide to the ISA/IEC 62443 Cybersecurity Design Specialist exam, written to go with the practice exam in this repository. Last reviewed October 2026.

Not affiliated with or endorsed by ISA or IEC. This guide summarizes the standards in its own words; it doesn't replace them.

On this page
  1. Exam at a glance and a 7-day game plan
  2. The ISA lifecycle and where design fits
  3. From risk assessment to CRS (62443-3-2)
  4. Security levels and system requirements (62443-3-3)
  5. Components and suppliers (4-1, 4-2, 2-4, ISASecure)
  6. Conceptual vs detailed design
  7. Network segmentation and firewalls
  8. Secure remote access
  9. System hardening
  10. Intrusion detection and monitoring
  11. Testing: CFAT, CSAT and SL-A validation
  12. Exam traps and tie-breakers
  13. Sources

Exam at a glance and a 7-day game plan

You must pass 100 closed-book multiple-choice questions in 2 hours, about 72 seconds each. ISA reports only pass or fail.

ItemWhat to expect
Questions100 multiple choice, closed book
Time2 hours (72 s per question on average)
DeliveryMeazure Learning test center, or online with live remote proctoring (LRP)
ResultPass or fail; a failed attempt shows % correct per domain, not a score
PrerequisiteFundamentals Specialist certificate already earned
RetakesAllowed inside the 6-month eligibility window; USD 120 (members) or 150 (non-members) each
Content basisIC34 IACS Cybersecurity Design & Implementation learning objectives

Sources: ISA certificate FAQ · ISA exams and testing · IC34 course page. Fees and policies change; check ISA's site.

Pacing. Take a first pass at about 50 s per question and flag anything that runs past 90 s. That leaves about 30 minutes for flagged items and a final check. Answer every question; a blank can only cost you.

What gets tested. The IC34 objectives: interpret risk assessment results, write a CRS, build a conceptual design from it, explain the security development lifecycle, configure and commission a basic firewall, design secure remote access, write a hardening specification, deploy a basic network IDS, and plan and run a CFAT or CSAT.

Practice exam. The practice exam in this repository has 203 original questions across ten domains: timed 100-question mocks, drills by domain, and a retake list of every miss. Progress saves in the browser you use.

7-day plan

DayStudyPractice in the exam app
1Skim this guide end to end40-question baseline across all domains; note your 3 weakest
262443-3-2 workflow, CRS, zones and conduitsRisk results & CRS
3Security levels; 62443-3-3 FRs, SRs, REsSecurity levels & requirements
462443-4-1, 4-2, 2-4; conceptual vs detailed designSupplier SDL; Conceptual & detailed design
5Firewalls, remote access, hardening, IDSThose four domains, then full timed mock #1
6CFAT, CSAT, SL-A validationTesting domain, then review every missed question
7Traps section and the key tables onlyFull mock #2 early in the day, then stop

If the exam is sooner, merge days 2 to 4 and keep at least one full timed mock. For LRP, run Meazure's system check and reread the invitation instructions a day early.

The ISA lifecycle and where design fits

Design is the Develop & Implement phase: it turns the CRS from the Assess phase into countermeasures. It then proves them in CFAT and CSAT before handing over to Maintain.

PhaseKey stepsMain outputs
AssessIdentify the SUC; initial (high-level) risk assessment; zones and conduits; detailed risk assessment; document requirementsZone and conduit model, SL-T per zone and conduit, CRS
Develop & ImplementConceptual design; detailed design; procure or build; install and commission; verify and validate (CFAT, CSAT)Design specifications, hardening specs, firewall rule sets, test plans and reports, SL-A
MaintainOperate, monitor, patch, back up, manage change, respond to incidents, reassess, decommissionLogs, MOC records, audit results, updated risk assessment

Who does what

RoleResponsibility in designMain parts
Asset ownerAccountable for IACS risk throughout. Sets tolerable risk; approves the CRS, residual risk and handover2-1, 3-2
Integration service providerDesigns, implements and verifies the automation solution against the CRS2-4, 3-3
Maintenance service providerKeeps countermeasures effective in operation2-4
Product supplierBuilds products with security capabilities (SL-C) under a secure development lifecycle; ships updates and guidelines4-1, 4-2

One organization can hold several roles, but accountability for the IACS stays with the asset owner.

Parts you must place instantly

PartTitleUse in design
1-1Terminology, concepts and modelsZones, conduits, SLs, FRs, reference model
2-1Security program requirements for IACS asset ownersOwner policies the design must follow
2-3Patch management in the IACS environmentPatch strategy
2-4Security program requirements for IACS service providersIntegrator capabilities, SP.01 to SP.12
3-1Security technologies for IACSTechnology categories to choose from
3-2Security risk assessment for system designZCR 1 to 7, SL-T, CRS
3-3System security requirements and security levelsSRs and REs per SL; SL-C and SL-A
4-1Secure product development lifecycle requirementsSupplier SDL, 8 practices
4-2Technical security requirements for IACS componentsCRs for the four component types

Principles that decide close answers

From risk assessment to CRS (62443-3-2)

62443-3-2 has seven zone and conduit requirements (ZCRs). The designer's input is ZCR 6, the CRS, which the asset owner approves in ZCR 7.

62443-3-2 workflow: ZCR 1 to ZCR 7, with ZCR 4 deciding whether the detailed assessment in ZCR 5 runs

ZCR 4 decides whether the detailed assessment runs. Either way, the documented CRS is what the asset owner approves and the designer builds from.

ZCRRequirementOutput
1Identify the SUC (1.1: perimeter and access points)SUC boundary and access points
2Initial cybersecurity risk assessmentWorst-case unmitigated risk
3Partition the SUC into zones and conduits (3.1 to 3.6)Zone and conduit model
4Compare initial risk to tolerable riskWhether a detailed assessment is needed
5Detailed cybersecurity risk assessment (5.1 to 5.13)Residual risk, SL-T, extra countermeasures
6Document cybersecurity requirements, assumptions and constraints (6.1 to 6.9)The CRS
7Asset owner approvalApproved results

ZCR 3: what must be separated (3.2 to 3.6). Business from IACS assets; safety-related assets; temporarily connected devices; wireless devices; devices connected via external networks. Memory hook: B-S-T-W-E.

ZCR 5: the 13 detailed steps, in order

  1. Identify threats
  2. Identify vulnerabilities
  3. Determine consequence and impact
  4. Determine unmitigated likelihood
  5. Determine unmitigated cybersecurity risk
  6. Determine SL-T
  7. Compare unmitigated risk with tolerable risk
  8. Identify and evaluate existing countermeasures
  9. Reevaluate likelihood and impact
  10. Determine residual risk
  11. Compare residual risk with tolerable risk
  12. Identify additional countermeasures
  13. Document and communicate results

SL-T is set at step 6, before existing countermeasures are credited.

ZCR 6: what the CRS contains (6.1 to 6.9). The CRS itself; SUC description; zone and conduit drawings; zone and conduit characteristics; operating environment assumptions; threat environment; organizational security policies; tolerable risk; regulatory requirements.

Zone and conduit characteristics (6.4) include the name or ID, accountable organization, logical and physical boundaries, safety designation, access points, data flows, connected zones and conduits, asset list and criticality, SL-T, applicable requirements and policies, assumptions and external dependencies.

Reading a CRS as a designer

Security levels and system requirements (62443-3-3)

Each zone and conduit gets an SL-T vector across the seven FRs. The design passes when SL-A meets SL-T in every FR, using component capability (SL-C) plus compensating countermeasures.

SLProtects againstAttacker profile
0No specific requirementNone
1Casual or coincidental violationAccidents, errors
2Intentional violation, simple meansLow resources, generic skills, low motivation
3Intentional violation, sophisticated meansModerate resources, IACS-specific skills, moderate motivation
4Intentional violation, sophisticated meansExtended resources, IACS-specific skills, high motivation

Three SL types

The SL vector is written in FR order {IAC UC SI DC RDF TRE RA}, for example SL-T = {3 3 2 1 3 2 3}. Compare FR by FR; never average or take the maximum.

FRNameSRsTypical countermeasures
1 IACIdentification and authentication control1.1 to 1.13Domain accounts, MFA for remote users, PKI, password policy
2 UCUse control2.1 to 2.12RBAC, session lock, audit events, timestamps
3 SISystem integrity3.1 to 3.9Antimalware, allowlisting, integrity checks, input validation
4 DCData confidentiality4.1 to 4.3Encryption in transit and at rest, purging on disposal
5 RDFRestricted data flow5.1 to 5.4Segmentation, firewalls, DMZ, unidirectional gateways
6 TRETimely response to events6.1 to 6.2Log access, continuous monitoring, IDS and SIEM
7 RAResource availability7.1 to 7.8DoS protection, backup and recovery, least functionality, inventory

There are 51 SRs in total.

High-yield SRs and REs: the SL where each first appears

RequirementFirst required at
SR 1.1 RE1 Unique identification and authentication of human usersSL2
SR 1.1 RE2 MFA for untrusted networksSL3
SR 1.1 RE3 MFA for all networksSL4
SR 1.2 Software process and device identification and authenticationSL2
SR 1.13 RE1 Explicit access request approval (untrusted networks)SL2
SR 2.1 RE1 Authorization for all users; RE2 permission mapping to rolesSL2
SR 2.1 RE3 Supervisor overrideSL3
SR 2.1 RE4 Dual approvalSL4
SR 2.6 Remote session terminationSL2
SR 2.7 Concurrent session controlSL3
SR 2.8 RE1 Centrally managed, system-wide audit trailSL3
SR 2.12 Non-repudiationSL3
SR 3.1 RE1 Cryptographic integrity protectionSL3
SR 3.2 RE1 Malicious code protection on entry and exit pointsSL2
SR 3.2 RE2 Central management and reporting of malicious code protectionSL3
SR 4.1 RE1 Confidentiality at rest or in transit via untrusted networksSL2
SR 4.1 RE2 Confidentiality across zone boundariesSL4
SR 5.1 RE1 Physical network segmentationSL2
SR 5.1 RE2 Independence from non-control system networksSL3
SR 5.1 RE3 Logical and physical isolation of critical networksSL4
SR 5.2 RE1 Deny by default, allow by exceptionSL2
SR 5.2 RE2 Island mode; RE3 Fail closeSL3
SR 5.3 RE1 Prohibit all person-to-person communicationsSL3
SR 6.2 Continuous monitoringSL2
SR 7.1 RE1 Manage communication loadsSL2
SR 7.3 RE1 Backup verificationSL2
SR 7.3 RE2 Backup automationSL3
SR 7.8 Control system component inventorySL2

Pattern: SL2 brings unique identities, deny-by-default and monitoring. SL3 brings MFA from untrusted networks, central audit and antimalware, cryptographic integrity, island mode and fail close. SL4 brings MFA everywhere, dual approval and confidentiality across zone boundaries.

Compensating countermeasure: used instead of, or in addition to, a missing inherent capability. Example: a legacy PLC with no authentication sits behind a conduit firewall with protocol inspection, plus physical access control. Document it, test it, and get the asset owner to accept the residual risk.

Essential functions: security must not stop a safety function, operator view or control. That is why fail close (SR 5.2 RE3) must not interfere with the SIS, and why operator HMIs often alarm instead of locking accounts.

Components and suppliers (4-1, 4-2, 2-4, ISASecure)

Suppliers prove their process with 62443-4-1 and their products with 62443-4-2. Integrators prove their capabilities with 62443-2-4.

62443-4-1: eight practices

#PracticeIDsRemember
1Security managementSM-1 to SM-13Process, roles, expertise, dev environment, private keys, third-party components
2Specification of security requirementsSR-1 to SR-5Product security context, threat model, requirements review
3Secure by designSD-1 to SD-4Secure design principles, defense in depth design, design review
4Secure implementationSI-1 to SI-2Implementation review, secure coding standards
5Security verification and validation testingSVV-1 to SVV-5Requirements, threat mitigation, vulnerability and penetration testing; independent testers
6Management of security-related issuesDM-1 to DM-6Receive, review, assess, address, disclose
7Security update managementSUM-1 to SUM-5Qualify, document and deliver updates; timely patches
8Security guidelinesSG-1 to SG-7Defense in depth, expected environment, hardening, disposal, operation, accounts

The integrator consumes SG-2 (defense in depth measures expected in the environment) and SG-3 (hardening guidelines) in the design. SUM-1 (update qualification) is why you install only vendor-qualified patches.

Maturity levels (4-1 and 2-4)

MLNameMeaning
1InitialAd hoc, often undocumented; unpredictable results
2ManagedWritten, controlled process; trained staff; may not yet be practiced
3Defined (Practiced)Practiced and repeatable across the organization, with evidence
4ImprovingEffectiveness measured and continuously improved

62443-4-2: four component types

TypePrefixExamples
Software applicationSARHMI or SCADA software, historian application, antivirus
Embedded deviceEDRPLC, DCS controller, safety controller, IED
Host deviceHDREngineering workstation, operator station, server
Network deviceNDRSwitch, router, firewall, wireless access point

62443-2-4: 12 service provider areas. SP.01 Solution staffing · SP.02 Assurance · SP.03 Architecture · SP.04 Wireless · SP.05 SIS · SP.06 Configuration management · SP.07 Remote access · SP.08 Event management · SP.09 Account management · SP.10 Malware protection · SP.11 Patch management · SP.12 Backup/restore.

ISASecure certifications

CertificationCertifiesBasis
SDLAA supplier's development process4-1
CSAAn off-the-shelf component, at a capability level4-2
SSAA control system, at a capability level3-3

In procurement, ask for the SL-C per FR, any ISASecure certificate, the supplier's security guidelines, its patch qualification process and its support lifecycle.

Conceptual vs detailed design

Conceptual design says which kind of countermeasure goes where for every CRS requirement. Detailed design says which product, configured how, in enough detail to build and test.

Conceptual designDetailed design
InputApproved CRS: SL-T, zones and conduits, assumptions, policiesApproved conceptual design
AnswersWhat type of control, in which zone or conduitWhich product, which settings
Typical contentZone and conduit architecture, control per zone and conduit, remote access and monitoring approach, gaps and compensating measuresDrawings and IP plan, firewall rule sets, hardening spec per component, account and role matrix, backup design, IDS placement, bill of materials, procedures
Vendor specificNoYes
Used forBudget, early review, owner approvalProcurement, build, CFAT and CSAT test cases
DocumentConceptual design specificationDetailed design specification

Technology categories (62443-3-1)

Selecting a technology

Traceability and approval

Network segmentation and firewalls

Traffic between enterprise and control networks terminates in a DMZ. Every zone boundary denies by default, and every allowed flow has a documented reason.

Reference architecture: enterprise, DMZ, operations, control and SIS zones separated by three firewall layers

Enterprise users read the DMZ replica, the historian pushes to it, and remote users reach only named targets through the jump host. The SIS keeps its own zone and conduit.

LevelContentsTypical zone
4 to 5Enterprise IT, business systems, internetEnterprise
3.5Historian replica, patch and antivirus relays, jump hostDMZ
3Site operations: historian, OT domain controllers, MESOperations
2Supervisory: HMI, SCADA, engineering workstationsControl
1Basic control: PLCs, DCS controllers; SIS logic solversControl; separate SIS zone
0Process: sensors and actuatorsField

DMZ rules

Rule-base design

Commissioning a firewall

  1. Load vendor-qualified firmware, change default credentials, disable unused services and interfaces.
  2. Restrict management access; set NTP; send logs to the central log server or SIEM.
  3. Load the approved rule set; back up the configuration under change control.
  4. Test that each permitted flow works and that sample denied flows are blocked and logged.
  5. Verify failover or fail-close behavior as designed; record the results.

Other boundary and network controls

Secure remote access

Remote users never land in the control zone directly. They authenticate with MFA into a remote-access zone, then reach only approved targets through a jump host, inside an approved time window, with the session logged.

Reference path

  1. The user requests access for a task and time window, and the asset owner approves it (SR 1.13 RE1).
  2. An encrypted VPN or secure gateway terminates in a remote-access zone at the DMZ, never inside the control zone. External connections are their own zone (ZCR 3.6).
  3. MFA at the gateway (SR 1.1 RE2 for untrusted networks).
  4. The user works from a hardened jump host, which breaks the protocol path. No tunnel reaches Level 2 or 1.
  5. The inner firewall allows only jump host to named target on named ports.
  6. Sessions are monitored or recorded, time out (SR 2.5) and can be terminated (SR 2.6).
  7. Access is disabled when the window closes; logs go to the SIEM and are reviewed.

Design rules

System hardening

A hardening specification states, per component type, the approved baseline: what is removed, disabled, changed and enabled. It derives from the supplier's hardening guidelines (4-1 SG-3) and is verified at CFAT.

What a hardening spec contains

By component type

ComponentKey hardening steps
Windows hostRemove unneeded roles and software; disable unused services and ports; operators as standard users with separate admin accounts; vendor-qualified antimalware or allowlisting; disable AutoRun; restrict USB storage; audit logging, NTP, log forwarding; lock BIOS or UEFI and enable secure boot
Network deviceChange defaults; replace Telnet, HTTP and SNMPv1/v2c with SSH, HTTPS and SNMPv3; shut unused ports and park them in an unused VLAN; port security; central AAA with individual accounts; banner, syslog, NTP; back up the config
Controller (PLC, DCS)Use the mode switch or protection levels to block remote program changes; disable unused services (web, FTP, SNMP); set passwords; load only vendor firmware with integrity checks

Removable media policy and procedure

Antimalware vs allowlisting

AntivirusApplication allowlisting
Works bySignatures of known malwareOnly approved executables run
NeedsFrequent, vendor-qualified signature updatesUpdating the allowlist through MOC when software changes
Best fitHosts where updates are manageableStatic OT hosts such as HMIs and engineering stations

Patching (62443-2-3)

Intrusion detection and monitoring

In control zones, use a passive network IDS fed by TAPs or SPAN ports at conduits and core switches. Alerts go to a SIEM with synchronized time. Avoid inline blocking where a false positive could stop the process.

Placement

SPAN (mirror port)Network TAP
HowThe switch copies traffic to a portPassive hardware copies the link
ProsNo extra hardware; flexibleSees every packet, adds no switch load, cannot inject traffic
ConsCan drop packets under load; uses switch resources; easy to misconfigureExtra hardware; installing it in line needs an outage
Signature-basedAnomaly-based
DetectsKnown attack and malware patternsDeviations from a learned baseline: new hosts, connections, function codes
StrengthFew false positives on known threatsFinds novel attacks; suits predictable OT traffic
WeaknessMisses new attacks; needs rule updatesLearning period; alerts after legitimate changes

IDS vs IPS. An IDS listens and alerts. An IPS sits in line and blocks, which adds latency and a failure point, and a false positive can drop control traffic. Keep blocking to less critical boundaries, if used at all.

Logging and time

Snort rule anatomy (header, then options):

alert tcp !10.10.3.20 any -> 10.10.2.0/24 502 (msg:"Modbus/TCP from non-historian host"; sid:1000001; rev:1;)

Action, protocol, source IP and port, direction, destination IP and port, then options. Local rules use SIDs of 1,000,000 and above. Tune after a baseline period, and give every alert an owner and a triage procedure.

Testing: CFAT, CSAT and SL-A validation

CFAT proves the system as built meets the CRS before it ships. CSAT proves the installed, connected system still meets it on site. Together they establish SL-A against SL-T.

CFATCSAT
Where and whenIntegrator facility or staging, before shipmentOn site, after installation and integration, before handover
ProvesThe system as built and configured meets the CRS and designThe installed system, with site connections and services, still meets them
Typical testsHardening baselines, accounts and roles, firewall rules on the staged network, malware protection, patch level, backup and restore, logging and time, vulnerability scanBoundary firewalls to site networks, remote access path, site directory accounts, IDS and SIEM feeds, physical security, anything untestable at the factory, re-checks of items changed during installation
Active scanningAcceptable on the staged systemOnly before start-up or with owner approval; prefer passive methods on live systems

What a test plan contains

Validating SL-A with 62443-3-3

  1. For each zone and conduit, go FR by FR through the SRs and REs that its SL-T requires.
  2. Test or inspect each one.
  3. The SL-A for an FR is the highest level whose SRs and REs are all met, natively or through compensating countermeasures.
  4. Where SL-A falls short of SL-T: fix it, add a compensating countermeasure, or have the asset owner formally accept the residual risk.
RequirementTestPass criterion
SR 1.11 Unsuccessful login attemptsEnter a wrong password one more time than the limitAccount locks (or alarms on a critical HMI) and the event is logged
SR 5.2 RE1 Deny by defaultSend an unapproved protocol from an enterprise host to a control hostBlocked and logged
SR 3.2 Malicious code protectionCheck engine and signature versions; drop the EICAR test file on a test hostDetected and reported
SR 7.3 and 7.4 Backup and recoveryRestore a server from backup onto spare hardwareReturns to a known secure state

Exam traps and tie-breakers

When two answers look right, pick the one that is risk-based, documented, approved by the asset owner, and keeps essential functions running.

Tie-breakers

Traps

Sources

Other details are summarized from the 62443 standards. Check anything doubtful against your licensed copies.