ISA/IEC 62443FundamentalsSpecialist study guide Open the practice exam

62443 Fundamentals Specialist Study Guide

Condensed, original study notes for the ISA/IEC 62443 Cybersecurity Fundamentals Specialist exam (course IC32), with a matching practice exam in this repository. Not affiliated with or endorsed by ISA or IEC.

On this page
  1. Exam at a glance and a 7-day plan
  2. 1 · How an IACS differs from office IT
  3. 2 · Threats, attack paths and incidents
  4. 3 · The series, its roles and document types
  5. 4 · Core concepts: zones, conduits, security levels, requirements
  6. 5 · Lifecycles and maturity
  7. 6 · The security program: 2-1, 2-2 and 2-4
  8. 7 · Risk analysis basics
  9. 8 · Countermeasures and network security
  10. 9 · Operating securely
  11. 10 · Secure products, certification and regulation
  12. Exam traps, tie-breakers and sources

Exam at a glance and a 7-day plan

ItemDetail
CertificateISA/IEC 62443 Cybersecurity Fundamentals Specialist
CourseIC32, Using the ISA/IEC 62443 Standards to Secure Your Control Systems (self-paced: IC32M)
Format90 multiple-choice questions, closed book
Time2 hours
DeliveryMeazure Learning test center, or online with live remote proctoring
ResultPass or fail. ISA does not publish the passing score
What it unlocksPrerequisite for Risk Assessment (IC33), Design (IC34) and Maintenance (IC37). All four certificates earn the ISA/IEC 62443 Cybersecurity Expert designation

The Fundamentals exam is broad rather than deep. It checks that you know the vocabulary (zones, conduits, security levels, foundational requirements, maturity levels), which part of the series answers which question, how control systems differ from office IT, and the basics of risk, network security and secure operations. Many questions ask for the BEST or FIRST action, so learn the order of things (inventory before risk, assess before design, test before patching) as well as the definitions.

The practice app uses the same ten domains as this guide, one per section below. Its readiness meters show your accuracy per domain against an 80% target.

DayReadPractice
1IACS vs IT; threats and incidentsQuick 20 for a baseline, then domains 1–2
2The series and roles; core conceptsDomains 3–4
3Lifecycle and maturity; the security programDomains 5–6
4Risk basics; countermeasures and networksDomains 7–8
5Secure operations; products and certificationDomains 9–10
6Nothing newFull 90-question mock under time, then review misses
7Traps and tie-breakers; your two weakest domainsSecond mock. Aim for 80% or better in every domain

Original study notes, not ISA course material. Not affiliated with or endorsed by ISA or IEC. Check clause numbers against your licensed copies of the standards.

1 · How an IACS differs from office IT

An industrial automation and control system (IACS) is the people, hardware, software and policies that can affect the safe, secure and reliable operation of an industrial process. It includes DCS and SCADA systems, PLCs and RTUs, safety instrumented systems (SIS), HMIs, historians, engineering workstations and the networks that join them. Operational technology (OT) is the everyday name for the same territory. Note that the 62443 definition includes people and policies, not only technology.

ConcernOffice ITIACS
First priorityProtecting dataHealth, safety and environment (HSE), then keeping the process running
Usual orderingConfidentiality, integrity, availabilityAvailability, integrity, confidentiality, with safety above all three
Worst outcomeData breach, financial lossInjury, environmental release, equipment damage, lost production
Service lifeAbout 3–5 years15–20 years or more, so legacy operating systems are common
UptimeReboots and outages are routineRuns around the clock; outages wait for planned shutdowns
PatchingFrequent and automatedVendor-qualified, tested first, applied in maintenance windows
PerformanceThroughput; short delays are tolerableDeterministic and real time; delay or jitter can trip the process
ChangeFast, run by ITFormal management of change (MOC) with a safety review
ProtocolsMostly authenticated and encryptedMany legacy protocols (Modbus, classic DNP3) have neither
Endpoint toolsAgents everywhereLimited CPU and memory; tools need vendor approval
PeopleIT staffOperations and engineering, plus vendors and integrators on site

Essential functions are the functions needed to maintain HSE, equipment integrity and availability: control, safety functions, and the operator's ability to see and steer the process. Losing them is described as loss of view or loss of control. A security measure must not adversely affect an essential function unless a risk assessment supports it. The classic example is account lockout on an operator HMI: locking out the console during an upset could stop an operator from acting, so the usual answer is to alarm on failed logins and use other compensating measures instead.

Why IT practice cannot simply be copied:

Exam angle: when two answers are both secure, choose the one that keeps safety and availability intact. Never pick an option that disables a safety function or locks operators out of the process.

2 · Threats, attack paths and incidents

Threat sourceUsual motiveExample
Insider (employee or contractor)Grievance, money, or plain errorMaroochy Shire, 2000
Criminal groupMoney through ransomware or extortionColonial Pipeline, 2021
Nation-stateEspionage, sabotage, pressureStuxnet; Ukraine 2015 and 2016; Triton
HacktivistPublicity or protestTampering with internet-exposed PLCs and HMIs that keep default passwords
Untargeted malwareNone; it spreads to whatever it can reachSlammer at Davis-Besse, 2003; NotPetya, 2017

Common ways in: phishing and stolen credentials, remote access without multifactor authentication (MFA), vendor support tools, internet-exposed devices, removable media and visiting laptops, trojanized software updates (supply chain), unmanaged links that bypass the firewall, wireless and radio links, and insiders. Most serious IACS attacks begin in the business network and pivot into control.

Attack models

YearIncidentWhat happenedLesson
2000Maroochy Shire, AustraliaA former contractor employee used radio gear to command sewage pumping stations; raw sewage spilled into parks and waterwaysInsider threat; unauthenticated radio links; revoke access when people leave
2003Slammer worm, Davis-Besse nuclear plant, USThe worm came in through a contractor link that bypassed the firewall and disabled a safety display system for about five hours while the plant was offlineUntargeted malware; uncontrolled connections; patching
2010Stuxnet, Natanz, IranSpread by USB and Windows zero-days, reprogrammed PLCs driving centrifuges, and replayed normal values to the operatorsAn air gap is not a control; removable media; integrity of control logic
2015Ukraine distribution gridPhishing, stolen credentials and VPN access let attackers open breakers from the operators' own HMIs; about 225,000 customers lost power for hours; hosts were wiped and serial-to-Ethernet gateways bricked with bad firmwareMFA on remote access; segmentation; firmware integrity; manual fallback
2016Industroyer (CrashOverride), Kyiv transmission substationMalware spoke grid protocols (IEC 60870-5-101 and -104, IEC 61850, OPC DA) directly to switching equipmentAttackers automate with native industrial protocols; monitor OT traffic
2017Triton (Trisis), petrochemical plant, Saudi ArabiaAttackers tried to reprogram safety controllers; a fault tripped the plant to a safe state and exposed themSafety systems are targets; keep the SIS separate; keep controllers in run mode
2017NotPetyaA wiper spread through a hijacked accounting-software update and Windows exploits, halting global manufacturers and shippersSupply chain risk; segmentation; offline backups
2021Colonial Pipeline, USRansomware entered IT through a VPN account without MFA; the company shut down pipeline operations for several days as a precautionIT incidents stop OT; MFA; know OT's dependencies on IT

Exam angle: know which incident illustrates which lesson, and remember that an "isolated" network was the starting assumption in several of them.

3 · The series, its roles and document types

The 62443 series: four groups and the main parts in each

The series is developed by the ISA99 committee and published by both ISA (as ISA-62443) and IEC (as IEC 62443, through technical committee TC 65), which is why it is called ISA/IEC 62443. In 2021 IEC designated it a horizontal standard, meaning it applies across industry sectors rather than to one. Its four groups move from shared concepts (1-x), to the programs of the organizations that run and support an IACS (2-x), to requirements for the whole system (3-x), to requirements for single components and how they are developed (4-x).

PartWhat it gives youMain user
1-1Terminology, concepts and models, such as zones, conduits and the reference model (TS, 2009)Everyone
1-5Scheme for security profiles: how to select 62443 requirements for a sector or use case and map them to that context, without adding or changing requirements (TS, 2023)Sector groups, suppliers, assessors
2-1Security program requirements for asset owners: eight security program elements and a maturity model (edition 2, 2024). Edition 1 (2010) was Establishing an IACS security program, the CSMSAsset owners
2-2IACS security protection scheme: the technical, physical and process measures that protect an IACS in operation, rated with security protection ratings (IEC PAS and ISA technical report, 2025)Asset owners with their service providers
2-3Patch management in the IACS environment (TR, 2015)Asset owners and product suppliers
2-4Security program requirements for integration and maintenance service providers, SP.01–SP.12 (edition 2, 2023)Integrators and maintenance providers
3-1Security technologies for IACS: a survey of controls and their limits (TR, 2009)Anyone choosing countermeasures
3-2Security risk assessment for system design: zones and conduits, target security levels, the cybersecurity requirements specification (2020)Asset owners and integrators
3-3System security requirements and security levels: seven foundational requirements broken into system requirements and enhancements (2013)Integrators and system suppliers
4-1Secure product development lifecycle requirements: eight practices (2018)Product suppliers
4-2Technical security requirements for IACS components, by component type (2019)Product suppliers

Document types. An International Standard holds normative requirements you can be assessed against. A Technical Specification (TS) or Publicly Available Specification (PAS) is also normative but published before full consensus. A Technical Report (TR) is informative guidance with no requirements.

Principal roles

One organization can play several roles: an asset owner with its own engineers is also its own integrator and maintainer. The automation solution is the control system as delivered (hardware, software and configuration). The IACS adds the people, policies and procedures of the asset owner who runs it.

QuestionPart
How do we run security across our sites?2-1
How do we protect and rate an IACS in operation?2-2
How should we handle patches?2-3
What must our integrator or maintenance contractor do?2-4
How do we split the system into zones and set targets?3-2
What must the system be able to do for a given security level?3-3
How must the vendor develop its products?4-1
What must a PLC, switch, server or HMI application be able to do?4-2

Exam angle: "which part" questions are common. Tie the role to the group: owner to 2-1, service provider to 2-4, system design to 3-2 and 3-3, product supplier to 4-1 and 4-2.

4 · Core concepts: zones, conduits, security levels, requirements

Defense in depth stacks independent layers so that one failure does not expose the process: policies and awareness, physical security, network segmentation, host hardening, application and device security, then monitoring and response.

LevelReference-model nameExamples
4Enterprise business systemsERP, email, business planning
3Operations managementMES, historian, scheduling, site servers
2Supervisory controlHMIs, SCADA servers, engineering workstations
1Basic control, plus safety and protectionPLCs, DCS controllers, RTUs, safety controllers
0ProcessSensors, actuators, drives

A DMZ between levels 3 and 4 (sometimes called level 3.5) is a zone of shared services, such as a historian replica, patch server or jump host. No traffic should pass straight through it between the business and control networks.

Security levels (SL) describe the strength of attacker a zone, conduit, system or component can withstand.

SLProtects againstMeansResourcesSkillsMotivation
0No specific requirement or protection––––
1Casual or coincidental violation––––
2Intentional violationSimpleLowGenericLow
3Intentional violationSophisticatedModerateIACS-specificModerate
4Intentional violationSophisticatedExtendedIACS-specificHigh

The seven foundational requirements (FR) organize every technical requirement in 3-3 and 4-2.

FRNameShortCovers
1Identification and authentication controlIACIdentify and authenticate every user: people, software processes and devices
2Use controlUCEnforce what an authenticated user may do: authorization, session lock, mobile code, portable devices
3System integritySIPrevent unauthorized changes to software and data; malware protection; integrity checks
4Data confidentialityDCProtect information in transit and at rest; purge data from retired media
5Restricted data flowRDFSegment the network and limit flows between zones
6Timely response to eventsTREAudit logs, monitoring, and reporting of violations
7Resource availabilityRAWithstand denial of service; backup and recovery; least functionality

Because a level is set per FR, an SL is a vector of seven values written in FR order, for example SL-T = {2 2 2 1 3 1 2}. In 3-3 each FR breaks down into system requirements (SRs, such as SR 1.1) with requirement enhancements (REs) that add strength at higher levels. 4-2 mirrors them as component requirements (CRs), plus requirements specific to software applications, embedded devices, host devices and network devices.

Security is not safety. Functional safety (IEC 61508 and IEC 61511) guards against random and systematic failures and uses safety integrity levels (SIL). Security guards against deliberate attack and uses security levels. A SIL does not map to an SL.

Exam angle: SL-T belongs to zones and conduits, SL-C to products and systems, SL-A to what was built. An SL is a vector across the seven FRs, not one number.

5 · Lifecycles and maturity

Keep three lifecycles apart, because each belongs to a different role:

LifecycleOwnerPartsCovers
Product developmentProduct supplier4-1, 4-2Requirements, design, implementation, verification, release, security updates, end of support
Automation solutionIntegration and maintenance service providers2-4, 3-2, 3-3Design, integration, testing, commissioning, handover, then ongoing support
IACS in operationAsset owner2-1, 2-2, 2-3Operation, maintenance, change, incident response, decommissioning

The ISA certificate courses follow the IACS through three phases, each matching one of the later certificates:

  1. Identification and assessment (Risk Assessment, IC33): define the system under consideration, run a high-level risk assessment, partition it into zones and conduits, run detailed risk assessments, set target security levels, and record the requirements in a cybersecurity requirements specification (CRS).
  2. Design and implementation (Design, IC34): design countermeasures that meet the CRS, select products, build, test at the factory and on site, commission and hand over.
  3. Operations and maintenance (Maintenance, IC37): monitor, patch, back up, respond to incidents, manage change, audit, and finally decommission.

The lifecycle is a loop. Changes, new threats and vulnerabilities, incidents and audit findings all send you back to reassess. Decommissioning is a security step too: revoke accounts and remote access, sanitize or destroy storage media, and update the asset inventory and drawings.

Security is cheapest when built in early. Adding it after commissioning usually means outages, rework and compensating countermeasures.

Maturity levels measure how well an organization performs a process, not how strong a product is. 4-1 and 2-4 use four levels, adapted from CMMI; 2-1 (2024 edition) also defines a maturity model for asset owners.

MLNameWhat it looks like
1InitialAd hoc and often undocumented; results depend on individuals
2ManagedWritten policies and procedures; trained staff who can perform them, though there may be little evidence yet
3Defined (Practiced)The documented process is followed consistently, with evidence
4ImprovingThe process is measured and continuously improved
MeasureRatesExample
Security level (SL)Technical capability: what a zone, system or component can withstandA controller with SL-C 2 for FR 1
Maturity level (ML)Process: how consistently an organization does what it saysA service provider at ML 3 for patch management

Both matter: a capable product run by an immature process still fails. 2-2 brings the two together when it rates the protection of an IACS in operation.

Exam angle: "evidence that the documented process is followed" points to ML 3. "Ad hoc" points to ML 1. A question about a product's strength is about SL; a question about an organization's consistency is about ML.

6 · The security program: 2-1, 2-2 and 2-4

Security is a management process that never ends, not a project. Every program, whatever standard it follows, needs the same building blocks:

2-1 edition 1 (2010) called this a cybersecurity management system (CSMS) and grouped it into three categories:

CategoryElements
Risk analysisBusiness rationale; risk identification, classification and assessment
Addressing risk with the CSMSPolicy, organization and awareness: CSMS scope, organizing for security, staff training and awareness, business continuity plan, security policies and procedures. Selected countermeasures: personnel security, physical and environmental security, network segmentation, and access control (account administration, authentication, authorization). Implementation: risk management and implementation, system development and maintenance, information and document management, incident planning and response
Monitoring and improving the CSMSConformance; review, improve and maintain the CSMS

2-1 edition 2 (2024) speaks of an IACS security program instead. It regroups the requirements into eight security program elements (SPEs), removes overlap with an information security management system (ISMS) such as ISO/IEC 27001 by building on it rather than repeating it, and adds a maturity model for rating each requirement.

SPENameSub-elements
1Organizational security measures (ORG)Security organization and policies; security assessments and reviews; physical access
2Configuration management (CM)Inventory of IACS hardware, software and network communications
3Network and communications security (NET)System segmentation; secure wireless access; secure remote access
4Component security (COMP)Components and portable media; malware protection; patch management
5Protection of data (DATA)Protection of data
6User access control (USER)Identification and authentication; authorization and access control
7Event and incident management (EVENT)Event and incident management
8System integrity and availability (AVAIL)System availability and intended functionality; backup, restore and archive

2-2 (2025) describes the security protection scheme for an IACS in operation: the technical, physical and process measures that address its cybersecurity risks. It rates protection with security protection ratings in target, implemented and operated forms, and it covers the asset owner, integration and maintenance service providers and product suppliers across the lifecycle, including periodic revalidation in operation.

2-4 (edition 2, 2023) sets the security capabilities that integration and maintenance service providers must be able to offer asset owners. Its requirements fall into twelve functional areas, and capability in each is rated with maturity levels.

AreaTopicAreaTopic
SP.01Solution staffingSP.07Remote access
SP.02AssuranceSP.08Event management
SP.03ArchitectureSP.09Account management
SP.04WirelessSP.10Malware protection
SP.05Safety instrumented system (SIS)SP.11Patch management
SP.06Configuration managementSP.12Backup and restore

Asset owners often pick 2-4 requirements for their contracts, so a provider's capability becomes a purchasing condition.

Exam angle: the first step in building a program is management commitment backed by a business rationale. Personnel security includes removing access promptly when people leave, the lesson of Maroochy. 2-1 is the owner's program; 2-4 is the provider's.

7 · Risk analysis basics

Risk combines the likelihood that a threat exploits a vulnerability with the consequence if it does.

TermMeaning
ThreatAn actor or circumstance with the potential to cause harm
VulnerabilityA weakness a threat can exploit: a flaw, misconfiguration, missing control or procedural gap
ConsequenceThe outcome: HSE, production, equipment, financial, reputational, regulatory
LikelihoodHow probable the event is. For cyber events it is hard to base on statistics, so it is usually judged from threat capability and motivation, exposure and the vulnerability
CountermeasureAn action, device, procedure or technique that reduces risk
Unmitigated riskRisk before countermeasures are counted (also called inherent risk)
Residual riskRisk that remains after countermeasures
Tolerable riskThe level the organization accepts, set by its risk criteria, often drawn as a risk matrix

Ways to measure it

Treating risk: reduce it with countermeasures, avoid it by removing the activity (for example an unneeded connection), transfer or share it through insurance or contracts, or accept it formally. Risk is never zero; the aim is residual risk at or below the tolerable level, accepted by someone with the authority to do so, normally asset-owner management.

How 62443-3-2 applies risk to system design (the subject of the Risk Assessment certificate):

  1. Identify the system under consideration (ZCR 1).
  2. Run an initial, high-level risk assessment of worst-case consequences, assuming the attack succeeds (ZCR 2).
  3. Partition the system into zones and conduits (ZCR 3).
  4. Compare the initial risk with tolerable risk; if it is higher, continue (ZCR 4).
  5. Run a detailed risk assessment for each zone and conduit: threats, vulnerabilities, consequences, likelihood, target security level, countermeasures and residual risk (ZCR 5).
  6. Document the cybersecurity requirements, assumptions and constraints in the CRS (ZCR 6).
  7. Obtain asset-owner approval (ZCR 7).

Inputs include the asset inventory, network and data-flow diagrams, process hazard analysis (PHA or HAZOP) results, known vulnerabilities, threat intelligence, existing countermeasures and policies. The PHA tells you the worst credible consequence of losing or misusing a control function. A cyber PHA treats a cyberattack as one more cause of process deviations and asks whether the same attack could also defeat the safeguards. IEC 61511 requires a security risk assessment for safety instrumented systems.

ActivityPurpose
Gap assessmentCompare current practice with a standard or policy
Vulnerability assessmentFind weaknesses through documents, interviews, configuration review, passive monitoring, and scanning where safe
Penetration testExploit weaknesses to prove impact; in OT, only on test or offline systems, with approval
Risk assessmentCombine threats, vulnerabilities and consequences to rank and treat risk

Exam angle: risk is reduced to a tolerable level, never eliminated. Asset-owner management accepts residual risk. Likelihood is the hardest part to estimate in cybersecurity, which is why consequence-driven methods are common in OT.

8 · Countermeasures and network security

62443-3-1 surveys the toolbox in six families: authentication and authorization; filtering, blocking and access control; encryption and data validation; management, audit, measurement, monitoring and detection; computer software; and physical security. No single tool is enough, so layer them.

Firewalls

TypeLooks atUse and limits
Packet filter (stateless)Addresses, ports and protocol of each packetFast and simple; no idea of sessions
Stateful inspectionThe same, plus connection stateLets return traffic back only for sessions that started legitimately
Application-layer, deep packet inspectionProtocol content, such as Modbus function codesCan allow reads but block writes; common in industrial firewalls
Unidirectional gateway (data diode)Physics: hardware allows one direction onlyPushes data out of control, such as a historian replica, with no path back in

Good rule sets deny by default and permit by exception; name specific sources, destinations and ports (never "any to any"); record a business reason for each rule; filter outbound traffic as well as inbound; log denied traffic; and are reviewed regularly.

Segmentation

Remote access: route it through a jump host in the DMZ with multifactor authentication, named accounts, approved and time-limited sessions, and session monitoring or recording. Do not let a VPN land directly on level 1 or 2, and disable vendor access when it is not in use. A VPN protects data in transit, but the remote laptop at the other end becomes part of your network.

Hosts and devices: remove or disable unused services, ports, accounts and software; change default passwords; follow the vendor's hardening guide; control USB ports and removable media; enable logging. Antivirus needs signature updates and vendor approval, and scans can load old hardware. Application allowlisting lets only approved programs run, which suits OT hosts whose software rarely changes.

Access control: unique named accounts, role-based access control, least privilege, separation of duties, MFA for remote and privileged access, regular account reviews and prompt removal at termination. Physical security still matters: locked cabinets, controlled rooms, port blockers, and controller key switches kept in run mode.

Monitoring: a network intrusion detection system (IDS) listening passively on a SPAN port or tap suits OT. An inline intrusion prevention system (IPS) can block legitimate control traffic, so use it with care.

ProtocolDefault portBuilt-in security
Modbus/TCPTCP 502None: any client can write registers and coils. A TLS variant exists (TCP 802)
DNP3TCP/UDP 20000Optional Secure Authentication
EtherNet/IP (CIP)TCP 44818, UDP 2222Optional CIP Security
OPC Classic (DA)TCP 135 plus dynamic ports (DCOM)Weak; hard to firewall
OPC UATCP 4840Certificates, signing and encryption when enabled
IEC 60870-5-104TCP 2404None; IEC 62351 adds it
IEC 61850 MMSTCP 102IEC 62351 adds it; GOOSE runs as layer 2 multicast
BACnet/IPUDP 47808Optional BACnet Secure Connect

Wireless: put it in its own zone, use enterprise-grade encryption and authentication, and remember that radio can be jammed, so avoid it for functions that cannot tolerate loss.

Exam angle: deny by default; a VLAN is not a firewall; traffic ends in the DMZ; a data diode for one-way export; allowlisting for fixed-function hosts; passive monitoring before active scanning.

9 · Operating securely

Start with the asset inventory. You cannot protect, patch or recover what you do not know about. Record hardware, software and firmware versions, network connections, owners and criticality, and keep the record current through management of change.

Patch management (62443-2-3)

Backup and restore: back up controller logic, configurations, HMI and engineering projects, firmware, system images and historian data. Keep at least one copy offline and off site (the 3-2-1 rule: three copies, on two kinds of media, one off site), protect backups from tampering, and test restores regularly. A backup that has never been restored is a hope, not a control.

Incident response is planned before it is needed. The team includes operations, engineering, IT, safety, legal, communications and key vendors. NIST SP 800-61 Rev. 2 describes four phases: preparation; detection and analysis; containment, eradication and recovery; and post-incident activity, where lessons learned improve the program. (Rev. 3, 2025, reorganizes this guidance around the CSF 2.0 functions.) In OT, safety comes first: containment may mean isolating zones or switching to manual operation. Preserve evidence where you safely can, and meet any reporting duties.

Business continuity and disaster recovery: a business continuity plan keeps essential operations going, for example with manual procedures, spare parts and alternate sites. A disaster recovery plan restores the systems. Exercise both, for example with tabletop drills.

Management of change (MOC): every change to hardware, software, firmware, configuration, network, firewall rules or accounts is requested, assessed for safety and security impact, approved, tested, implemented and documented, with drawings, inventory and backups updated. Emergency changes are documented and reviewed afterward.

Monitoring and logging: collect security events, logins and configuration changes; synchronize clocks so events line up; centralize logs in a SIEM; review and alert; and keep them for as long as policy requires.

Account management: a joiner, mover and leaver process; periodic reviews of accounts and privileges; no default or unused accounts; controlled emergency (break-glass) accounts.

Removable media and visiting laptops: scan them at a kiosk before use, allow only approved devices, and log their use.

Audits: periodic audits check that policies are followed and controls work. Reassess risk after significant changes or incidents.

Decommissioning: sanitize or destroy storage media (NIST SP 800-88: clear, purge or destroy), then remove accounts, remote access and records.

Exam angle: inventory before patching, back up before changing, test before deploying, safety first in an incident, and every change goes through MOC, security changes included.

10 · Secure products, certification and regulation

62443-4-1: the eight practices of secure product development

#PracticeShortExamples
1Security managementSMDefined process and roles, security expertise, secure development environment, control of private keys, third-party components
2Specification of security requirementsSRProduct security context, threat model, security requirements and their review
3Secure by designSDSecure design principles, defense in depth, design reviews
4Secure implementationSISecure coding standards, implementation reviews
5Security verification and validation testingSVVRequirements and threat-mitigation testing, vulnerability testing, penetration testing, independent testers
6Management of security-related issuesDMReceive, assess, fix and disclose reported vulnerabilities
7Security update managementSUMQualify, document and deliver updates promptly
8Security guidelinesSGDefense-in-depth and hardening guidance, secure operation, account management and disposal

62443-4-2: what a component must be able to do

The supplier's security guidelines describe the environment and defenses the product expects and how to harden and configure it. A product used outside those assumptions may not deliver its stated capability.

Certification

ProgramCertifiesAgainst
ISASecure SDLAA supplier's development lifecycle process4-1
ISASecure CSAA component (successor of the older EDSA)4-2, with 4-1 development
ISASecure SSAA control system3-3, with 4-1 development
IECEE CB SchemeProducts and capabilities, through accredited bodiesSeveral parts of the series

ISASecure is run by the ISA Security Compliance Institute (ISCI). A certified component still has to be deployed securely: certification proves capability, not the security of your plant.

Security profiles (1-5) select 62443 requirements for a sector, application or product type and explain how each applies in that context. A profile may not add requirements or modify existing ones, it states the security level and maturity level that apply, and it is supported by a risk evaluation. Profiles make assessments comparable across a sector.

Related frameworks and regulations

FrameworkApplies toKey point
NIST Cybersecurity Framework 2.0 (2024)Any organizationSix functions: Govern, Identify, Protect, Detect, Respond, Recover
NIST SP 800-82 Rev. 3 (2023)OT operatorsUS guide to OT security; draws on 62443
NERC CIPBulk electric system in North AmericaMandatory and enforceable
EU NIS2 DirectiveEssential and important entities in the EUNational laws were due by October 2024
EU Cyber Resilience ActProducts with digital elements sold in the EUReporting duties apply from September 2026; most obligations from December 2027
IEC 61511 and ISA-TR84.00.09Safety instrumented systemsSecurity risk assessment of the SIS
ISO/IEC 27001Information security management systems2-1 (2024) builds on an ISMS

Exam angle: SDLA certifies the process, CSA the component, SSA the system. CCSC 4 ties 4-2 to 4-1. Profiles select and map requirements but never invent them.

Exam traps, tie-breakers and sources

Pairs that get mixed up

Easily confusedThe difference
SL, SIL, MLSecurity strength per FR; functional safety integrity; process maturity
SL-T, SL-C, SL-ANeeded by a zone or conduit; offered by a product or system; reached as built
Zone, conduitA group of assets; a group of communication channels between zones
2-1, 2-4, 4-1The owner's program; the service provider's program; the supplier's development process
2010 CSMS, 2024 SPEsThree categories of CSMS elements; eight security program elements with a maturity model
Standard, TRRequirements you can be assessed against; guidance only (2-3 and 3-1 are TRs)
SDLA, CSA, SSACertifies the process; the component; the system
VLAN, firewallSeparates traffic; enforces a security policy

First steps the exam likes to ask about

Tie-breakers for BEST answers

  1. Keep safety and availability intact; never block an essential function.
  2. Prefer the risk-based answer to a blanket rule.
  3. Prefer layered defense to any single control.
  4. Prefer passive and tested methods on live control systems.
  5. Give the decision to the role that owns it: the asset owner sets targets and accepts residual risk, the supplier provides capability, the integrator implements.
  6. In standards, "shall" is a requirement, "should" is a recommendation and "may" is a permission.

Incident shorthand: Maroochy, insider and radio. Slammer, untargeted worm through a contractor link. Stuxnet, USB and PLC logic with replayed values. Ukraine 2015, stolen credentials and remote HMI control. Industroyer, native grid protocols. Triton, the safety system. NotPetya, supply chain wiper. Colonial, IT ransomware that stopped OT.

Sources

These notes paraphrase and summarize. They do not reproduce the standards, so check details against your licensed copies.