ISA/IEC 62443MaintenanceSpecialist study guide Open the practice exam

62443 Maintenance Specialist Study Guide

Condensed, original study notes for the ISA/IEC 62443 Cybersecurity Maintenance Specialist exam (course IC37), 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 · The maintain phase and who does what
  3. 2 · Monitoring, alarms, event logs and SIEM
  4. 3 · Intrusion detection
  5. 4 · Network diagnostics and troubleshooting
  6. 5 · Patch and vulnerability management
  7. 6 · Malware protection, application control and hardening
  8. 7 · Backup, restore and recovery
  9. 8 · Account and access management
  10. 9 · Incident response and recovery
  11. 10 · Management of change, configuration management and audits
  12. Exam traps, tie-breakers and sources

Exam at a glance and a 7-day plan

ItemDetail
CertificateISA/IEC 62443 Cybersecurity Maintenance Specialist
CourseIC37, IACS Cybersecurity Operations & Maintenance (self-paced: IC37M)
Format100 multiple-choice questions, closed book
Time2 hours, about 72 seconds per question
DeliveryMeazure Learning test center, or online with live remote proctoring
ResultPass or fail. ISA does not publish the passing score
PrerequisiteThe Fundamentals Specialist certificate
Counts towardThe ISA/IEC 62443 Cybersecurity Expert designation, with Fundamentals, Risk Assessment and Design

This exam is about running an IACS securely, day after day. ISA's published objectives cover network diagnostics and troubleshooting; reading device alarms and event logs; backup and restore; the patch management lifecycle; antivirus management; the basics of application allowlisting, network and host intrusion detection and security information and event management (SIEM); putting an incident response plan and a management of change procedure into practice; and carrying out a basic security audit.

The course labs name Snort for intrusion detection. A partner version of the course also lists Microsoft WSUS for patching, PLC backup and configuration management, a management of change form, log monitoring, vulnerability scanning, packet capture analysis, and troubleshooting and forensics. Expect practical questions: what to check first, which log or tool shows a given event, the right order for a patch or a restore, and how to respond to an alert without harming the process.

DayReadPractice
1The maintain phase; monitoring and logsQuick 20 for a baseline, then domains 1–2
2Intrusion detection; network diagnosticsDomains 3–4
3Patching; malware protection and application controlDomains 5–6
4Backup and recovery; accounts and accessDomains 7–8
5Incident response; change, configuration and auditsDomains 9–10
6Nothing newFull 100-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 details against your licensed copies of the standards and your vendors' documentation.

1 · The maintain phase and who does what

The IACS lifecycle runs from identification and assessment, through design and implementation, to operations and maintenance. The last phase is by far the longest, often decades, and it is where security either holds or quietly erodes.

Security drift. After handover, configurations change, temporary fixes become permanent, accounts pile up, patches lag, firewall rules loosen and drawings go stale. The achieved security level (SL-A) slides below the target (SL-T) unless maintenance work keeps pulling it back.

ActivityPurposeWhere the requirements live
Monitoring and loggingNotice attacks and failures early62443-3-3 FR 6; 2-1 EVENT; 2-4 SP.08
Patch and vulnerability managementClose known holes safely62443-2-3; 2-1 COMP 3; 2-4 SP.11
Malware protection and application controlStop malicious code from running2-1 COMP 2; 2-4 SP.10
Backup and restoreRecover from failure or attack2-1 AVAIL 2; 2-4 SP.12
Account and remote access managementKeep access appropriate and controlled2-1 USER and NET 3; 2-4 SP.07 and SP.09
Incident responseContain, eradicate and recover2-1 EVENT 1
Management of change and configuration managementKeep every change controlled and documented2-4 SP.06
Audits and reassessmentVerify that controls still work2-1 ORG 2

Roles in operation

What maintainers need to hand: the asset inventory, network and zone and conduit drawings, the CRS, configuration baselines, backup records, and procedures for patching, backup and restore, incident response and management of change, plus the vendors' hardening guides.

A configuration baseline is the approved, documented configuration of a device or system (firmware, settings, rules, accounts). Comparing the running configuration with it is how drift is found.

Exam angle: maintenance keeps SL-A at SL-T over time; the asset owner stays accountable; service providers deliver what the contract specifies; vendors supply updates and information; the documentation must stay current.

2 · Monitoring, alarms, event logs and SIEM

Where security-relevant events come from

SourceExamples
Controllers and devicesRun or program mode changes, logic downloads, firmware changes, CPU load spikes, communication faults, unexpected restarts
HMI, SCADA and DCS journalsLogins, operator actions, setpoint changes, alarm acknowledgments
Operating systemsWindows Security, System and Application logs; Linux syslog
Network devicesFirewall allow and deny logs, switch ports going up or down, new MAC addresses, VPN logins
Security toolsAntivirus and allowlisting alerts, IDS alerts, backup job results
Physical systemsBadge readers, cabinet door switches

Early indicators of an attack, or of a failure that looks like one: logins at odd times or from odd places, bursts of failed logins, new accounts or services, cleared logs, unknown devices, unusual protocols or connections (an engineering protocol coming from an HMI, say), controller mode changes outside maintenance, unexpected firmware downloads, rising network load, and security tools switched off.

Windows event IDMeaning
4624Successful logon
4625Failed logon
4720User account created
4740Account locked out
4688New process created
7045New service installed (System log)
1102Security audit log cleared
Syslog severityName
0Emergency
1Alert
2Critical
3Error
4Warning
5Notice
6Informational
7Debug

SIEM. A security information and event management system collects logs centrally, normalizes them, correlates events across sources, alerts, and retains them. Correlation is the point: a VPN login, a new process on an HMI and a controller mode change are each minor alone and alarming together. A SIEM needs synchronized clocks, a baseline of normal behavior, tuning to cut false positives, defined use cases, and people to respond. In OT, collect logs within each zone or in the DMZ and let them flow outward through the conduits; the SIEM should not open connections into control zones.

Good log management

Exam angle: 4625 is a failed logon and 1102 a cleared audit log, a classic sign of an intruder covering tracks; synchronized time makes correlation possible; logs flow out of control zones, not the other way.

3 · Intrusion detection

TypeWatchesStrengthsLimits
Network IDS (NIDS)Copies of traffic from a SPAN port or network tapPassive; covers many devices at once, including PLCs that cannot run agentsCannot read encrypted payloads or see activity that stays inside a host; needs good placement
Host IDS (HIDS)Files, logs, processes and settings on one hostSees local changes such as new services or altered filesNeeds an agent, vendor approval and host resources; not for embedded devices

How detection works

IDS or IPS? An IDS only alerts. An intrusion prevention system (IPS) sits inline and blocks, so a false positive can cut legitimate control traffic. Inside control zones, prefer passive detection; inline blocking is easier to justify at the boundary between business and control networks.

Getting traffic to the sensor

OptionProsCons
SPAN (port mirroring) on a switchConfiguration only; no new hardwareCan drop packets under load; can be changed or misconfigured
Hardware network tapPassive copy of every packet; cannot be reconfigured remotelyMust be installed in the link, usually during a short outage

Place sensors at conduits and chokepoints: the DMZ, the boundary between supervisory and control networks, and core switches inside control zones.

Snort is an open-source network IDS and IPS, and the tool named in ISA's IC37 labs. A rule has a header (action, protocol, source address and port, direction, destination address and port) and options in parentheses (message, content to match, signature ID, revision). An illustrative rule:

alert tcp !$HMI_HOSTS any -> $PLC_NET 502 (msg:"Modbus write from non-HMI host"; content:"|06|"; offset:7; depth:1; sid:1000001; rev:1;)

It alerts when any host outside the HMI group sends Modbus function code 6 (write single register) to the PLC network; in Modbus/TCP the function code follows the 7-byte header. Locally written rules use signature IDs of 1,000,000 and above. Similar open-source tools include Suricata and Zeek.

Tuning and triage

Exam angle: IDS is passive and IPS is inline; anomaly detection suits stable OT traffic; taps do not drop packets the way a busy SPAN port can; know the parts of a Snort rule.

4 · Network diagnostics and troubleshooting

Work methodically: start at the physical layer and work up; divide the network to isolate the fault; compare with the known-good baseline; change one thing at a time; coordinate with operations and have a rollback; record changes through management of change. Keep both possibilities open: a "network fault" may be an attack, and an "attack" may be a fault.

ToolShowsNotes for OT
pingReachability and round-trip timeICMP may be blocked by design, and some devices rate-limit it
traceroute or tracertThe path, hop by hopShows where traffic stops
arp -aIP-to-MAC mappings on a hostChanging or duplicate entries suggest an IP conflict or ARP spoofing
netstat or ssListening ports and open connections on a hostUnknown listeners or connections are red flags
ipconfig or ip addrA host's addresses, mask and gatewayCheck for duplicates and wrong gateways
Switch counters and logsCRC errors, collisions, ports going up and downPoint to cabling, duplex or hardware faults
Packet capture (Wireshark)Every packet in detailPassive; filter on industrial protocols
SNMP network managementDevice status, bandwidth, interface errorsUse SNMPv3, which adds authentication and encryption; v1 and v2c send community strings in clear text

Common problems and their signs

ProblemWhat you see
Network loop or broadcast stormVery high utilization, everything slow, switch CPUs high; looks like a denial-of-service attack
Duplicate IP addressIntermittent connectivity; ARP entries flipping between two MAC addresses
Duplex mismatchCRC errors and late collisions on one link; poor throughput
Multicast flooding, for example EtherNet/IP I/O without IGMP snoopingDevices overloaded by traffic they did not ask for
A scan or misbehaving deviceControllers dropping connections; bursts of resets
A firewall change gone wrongSpecific flows fail right after the change

Early indicators worth investigating: unexplained changes in traffic volume, new talkers or protocols, repeated connection resets, rising broadcast rates and devices restarting.

Packet capture analysis

Securing management itself: put management interfaces on a separate management network, use SSH and HTTPS instead of Telnet and HTTP, change default SNMP community strings, and prefer SNMPv3.

Exam angle: physical layer first; loops and broadcast storms can look like attacks; arp for spoofing, netstat for unknown connections; SNMPv3 over v1 and v2c.

5 · Patch and vulnerability management

62443-2-3, a technical report, describes patch management for IACS: the roles of the asset owner and the product supplier, the patch lifecycle, and a common format in which suppliers report which patches they have tested with their products.

The asset owner's patch cycle

  1. Inventory: know the hardware, software and firmware versions installed.
  2. Monitor: vendor advisories, CISA ICS advisories, the NVD and the KEV catalog.
  3. Assess: does it apply here? How exposed is the asset? Is the flaw being exploited? What is the consequence? Then decide: patch now, patch at the next window, mitigate and defer, or accept.
  4. Vendor qualification: wait for the control system supplier to confirm compatibility.
  5. Test: functional and performance tests on a representative test system.
  6. Back up and plan the rollback.
  7. Deploy through management of change in a maintenance window, in stages: the standby of a redundant pair first, then switch over; less critical systems before critical ones.
  8. Verify: the process runs normally, the patch is installed and security functions still work.
  9. Record: update the inventory, the configuration baseline and the patch records.

Firmware for controllers, switches and other devices is usually riskier than an operating system patch: it often needs an outage and can change behavior. Check the digital signature or hash of every firmware or software package before installing it.

WSUS. Windows Server Update Services lets the owner approve specific Microsoft updates and distribute them from an internal server, so OT hosts never contact the internet. A common design places a downstream WSUS server in the DMZ or an OT management zone, synchronized from an upstream server on the business side. Approve only vendor-qualified updates, group computers by zone and criticality, and use the compliance reports.

When a patch cannot be applied (no vendor approval yet, no outage window, or an unsupported product), use compensating countermeasures: tighter segmentation, disabling the vulnerable service, allowlisting, IDS signatures for the exploit, stricter access and closer monitoring. Document the decision and a review date. An end-of-life product will never be patched again, so plan its replacement.

Vulnerability scanning in operation

Useful measures: patch compliance per zone, time from release to deployment, and the number of deferred patches covered by compensating controls.

Exam angle: back up and test before deploying; only vendor-qualified patches; stage the rollout; verify integrity before installing; compensate and document when you cannot patch.

6 · Malware protection, application control and hardening

ApproachHow it worksStrengthsWeaknesses
AntivirusBlocks files matching known-bad signatures, plus some heuristicsCatches known malware; familiar to staffNeeds frequent signature updates; misses new malware; scans can load old hosts; needs vendor approval
Blocklisting (denylisting)Blocks programs that are on a listSimple to startAnything not on the list still runs
Application allowlistingOnly approved programs, identified by hash, signature or path, may runStops unknown malware; no daily updates; suits fixed-function OT hostsMust be updated with every legitimate change; needs a clean baseline and vendor support

Running antivirus in OT

Running allowlisting

  1. Build the baseline on a known-clean system.
  2. Run in audit mode first to see what would be blocked, then switch to enforcement.
  3. Update the allowlist through management of change whenever software changes, including patches, or the update will be blocked.
  4. Protect the agent's settings so only administrators can change them.

Removable media and USB ports

Hardening hosts and devices

Exam angle: allowlisting suits static hosts but must be updated with each change; antivirus needs vendor-qualified settings and an internal update source; control removable media technically, not just by policy; least functionality is the heart of hardening.

7 · Backup, restore and recovery

What to back upNotes
Controller logic and configuration (PLC, DCS, SIS, RTU)After every change, with version history
Network and security device configurationsSwitches, firewalls, VPN and wireless; export after each change
HMI and SCADA projects, graphics, alarm databasesThe engineering projects needed to rebuild them
Workstation and server imagesFull images allow a fast rebuild
Historian and batch dataOften replicated as well as backed up
Firmware, installation media, license keysNeeded to rebuild from bare hardware
DocumentationInventory, drawings and procedures, with an offline copy

Principles

Configuration management for controllers. Keep approved versions of every controller program, and compare the running logic with the latest approved version on a schedule. Differences reveal unauthorized or undocumented changes, whether from an attacker or from a shortcut during a night shift.

Restoring after an incident

  1. Choose a backup that predates the compromise, and check it: compare hashes and scan it, or you may restore the attacker too.
  2. Rebuild in order: network and time services, authentication, servers, then workstations and HMIs, then verify the controller logic.
  3. Validate with operations before returning each part to service, and keep spares and matching firmware for critical hardware.
  4. Follow written, tested procedures that list the media, licenses and securely stored credentials needed.

In 62443-3-3, backup is SR 7.3 and recovery and reconstitution is SR 7.4; for service providers it is 62443-2-4 SP.12, and for asset owners 62443-2-1 AVAIL 2.

Exam angle: test restores; keep an offline copy; RPO is data loss, RTO is downtime; restore only from a backup known to be clean; back up after every change; compare running logic with the approved version.

8 · Account and access management

The account lifecycle follows people: a joiner's request is approved by the system owner and provisioned with least privilege; a mover's rights change with the new role; a leaver's access is disabled on the day they leave, and the account is removed after the retention period. Periodic reviews catch what the process missed.

Account typeUsed forControls
Named userDay-to-day workOne per person; role-based rights; MFA where practical
Shared console loginSome HMIs need a station login that survives shift changesA documented exception, with physical control of the room, application-level logging of individual actions and other compensating measures
AdministratorSystem administrationSeparate from the person's everyday account; few in number; MFA; logged and reviewed
ServiceRunning services and applicationsNo interactive logon; strong unique credentials; a named owner
Vendor or remoteSupport sessionsDisabled by default, enabled for an approved and time-limited session, monitored
Emergency (break-glass)When normal access failsSealed credentials; any use raises an alert and a review; changed after use
DefaultShipped with the productChanged or disabled at commissioning

Authentication. Prefer long passwords to complex short ones and never reuse them; use MFA for remote and privileged access. On operator consoles, avoid controls that could slow an emergency response, such as lockouts; rely on physical security, role-based rights and alerting instead.

Authorization. Use role-based access control (operator, engineer, administrator, vendor), least privilege and separation of duties: the person who changes controller logic should not also approve the change. Limit write access to controllers to engineering roles.

Remote access sessions in operation

  1. The vendor or engineer requests a session; the owner approves it for a stated purpose and window.
  2. The account or connection is enabled only for that window, with MFA, through a jump host in the DMZ.
  3. The session is monitored or recorded.
  4. Access is disabled at the end, and the logs are reviewed.

Reviews and credentials. Review accounts and privileges regularly, for example quarterly, and compare them with HR leaver lists; disable accounts that have not been used for a defined period. Give devices unique passwords where possible, keep them in a password vault, and change shared credentials when staff or vendors leave.

Physical access is access too: badges, cabinet keys and controller key switches need the same joiner and leaver discipline.

In 62443-3-3 these controls map to SR 1.1 to 1.3 (identification, authentication and account management), SR 1.5 and 1.7 (authenticators and password strength), SR 1.11 (unsuccessful login attempts), SR 1.13 (access via untrusted networks) and SR 2.1 (authorization enforcement).

Exam angle: disable leavers at once; keep administrator accounts separate; vendor access stays off until approved; shared accounts only as documented exceptions; least privilege and separation of duties.

9 · Incident response and recovery

Incident response lifecycle after NIST SP 800-61 Rev. 2: four phases with OT notes

What an OT incident response plan contains

Containment options in OT each have trade-offs, so decide them with operations and process safety:

OptionEffect
Cut the conduit between business and control networksControl keeps running while isolated from the infection
Isolate the affected zoneLimits spread; neighbors keep running
Disable compromised accounts or remote accessRemoves the attacker's way in
Switch to manual or local controlKeeps the process safe while systems are cleaned
Keep running under close watchAvoids causing the outage an attacker wanted, where it is safe to do so

Pulling cables from controllers at random can do more harm than the attack.

Evidence and forensics. Where it is safe, collect the most volatile data first: memory and live network connections before disk images and logs. Capture network traffic, hash everything, record the chain of custody and keep a timeline. For controllers, compare logic and firmware with the approved versions, with vendor help if needed.

Eradication and recovery. Find the root cause and entry point, remove the malware and any persistence, reset credentials, fix the exploited weakness, rebuild from known-good images and backups, verify controller logic, restore in stages, and watch closely afterward.

Post-incident activity. Hold a lessons-learned review soon after, update the plan, the risk assessment and the controls, track measures such as time to detect, contain and recover, and share information with your ISAC where appropriate. NIST SP 800-61 Rev. 3 (2025) reorganizes this guidance around the CSF 2.0 functions, but the activities are the same.

Exercises. Tabletop exercises and drills that include operations and vendors find the gaps before a real incident does.

Exam angle: safety comes first; containment is decided with operations; preserve evidence where safe; restore only from clean backups and verify the logic; lessons learned close the loop.

10 · Management of change, configuration management and audits

Management of change (MOC) keeps every change controlled, including security changes.

  1. Request: what, why, who, when, and which systems and zones are affected.
  2. Assess impact on safety, security (a new port, account, connection or zone boundary?), operations and compliance; reassess risk if the change is significant.
  3. Approve by the people authorized for that class of change.
  4. Plan and test: test off production, take a backup, write the rollback plan, book the window.
  5. Implement by an authorized person, following the plan.
  6. Verify that it works and that security controls are intact.
  7. Document and close: update the inventory, drawings, baselines, backups and, if needed, the CRS.
MOC form fieldWhy it is there
Description and reasonMakes the purpose reviewable
Affected assets and zonesShows the scope of impact
Safety, security and production impactForces the questions to be asked before, not after
Test, backup and rollback planMakes failure recoverable
ApprovalsShows the change was authorized
Verification resultsProves the change worked
Documentation updatedPrevents drift between records and reality

Classes of change. Standard changes are pre-approved, low-risk and routine, such as a tested signature update. Normal changes follow the full process. Emergency changes get fast approval and are documented and reviewed afterward.

Configuration management (62443-2-4 SP.06) keeps approved baselines and version histories of controller programs and device configurations, and compares running configurations with them. An unexplained difference is an unauthorized change until proven otherwise, and a possible incident.

A basic cybersecurity audit

AreaWhat to check
AccountsLeavers disabled; privileged accounts reviewed; shared or default accounts only as documented exceptions
PatchingStatus against policy; deferred patches covered by compensating controls
BackupsRecent and complete, with an offline copy and restore-test records
Malware protectionSignatures current; allowlisting enforced
Firewall rulesEach rule justified and reviewed; no any-to-any rules
Remote accessSessions approved and logged; vendor accounts disabled when idle
Change controlChanges found on systems match approved MOC records
LoggingLogs collected, time-synchronized and reviewed

Useful measures: share of systems patched within target, time to detect, accounts reviewed on schedule, backup success and restore tests, and unauthorized changes found.

Exam angle: every change goes through MOC, security changes included; emergency changes are reviewed afterward; compare running configurations with approved baselines; audit findings need criteria, evidence and tracked corrective action.

Exam traps, tie-breakers and sources

Pairs that get mixed up

Easily confusedThe difference
IDS and IPSAlerts from a copy of the traffic; sits inline and blocks
NIDS and HIDSWatches network traffic; watches one host's files, logs and processes
SPAN and tapSwitch configuration that can drop packets under load; passive hardware that copies everything
Signature and anomaly detectionKnown patterns; departures from a learned baseline
Antivirus, blocklisting, allowlistingKnown-bad signatures; a list of banned programs; only approved programs run
RPO and RTOHow much data you can lose; how long you can be down
Incremental and differential backupChanges since the last backup of any kind; changes since the last full backup
Authenticated and unauthenticated scanLogs in and reads versions; sees only what the network exposes
Audit and risk assessmentChecks conformance with criteria; judges risk
Standard and emergency changePre-approved routine change; fast approval with review afterward
SNMPv1 or v2c and SNMPv3Clear-text community strings; authentication and encryption

First steps the exam likes to ask about

Tie-breakers for BEST answers

  1. Safety and availability come first.
  2. Passive methods before active ones on live systems.
  3. Test off production and back up before changing anything.
  4. Every change goes through management of change.
  5. Use vendor-qualified patches, antivirus settings and tools.
  6. If it is not documented, it did not happen: records, baselines and evidence matter.

Event shorthand: 4624 logon, 4625 failed logon, 4720 account created, 4740 lockout, 4688 new process, 7045 new service, 1102 audit log cleared. Syslog runs from 0 (emergency) to 7 (debug).

Sources

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