ISASecure and IEC 62443, explained with the numbers
What each certification program actually evaluates, how the security levels and device types change the scope, and where the common points of confusion come from — written by the assessors who run these evaluations.
Filteractive
38 articles match your filters
After the certificate: ACSSA surveillance in years one and two, recertification in year three
How an ISASecure ACSSA certificate stays valid: 36 months, surveillance in years one and two, recertification in year three, nonconformities and suspension.
IEC 62443-2-1 audit evidence in an ACSSA evaluation: documents, interviews and inspection, never testing
How an ISASecure ACSSA evaluator gathers evidence on an installed IACS: documents, interviews and configuration inspection, never testing or device access.
The ACSSA assessment process: four phases and the report you receive
How an ISASecure ACSSA evaluation runs: the plan you approve, the four ACSSA-304 phases from risk assessment to report, and how to read the ACSSA-303 report.
An asset owner's installed IACS: IEC 62443 asset owner certification scope under ISASecure ACSSA, and the six documents that define it
ISASecure ACSSA certifies an asset owner's installed IACS, bounded by six change-controlled documents: who may apply, what is in scope and what is carved out.
IEC 62443-2-1 maturity level 2 vs 3: why ISASecure ACSSA certification needs level 3 on every requirement
In ISASecure ACSSA, maturity level 2 means a requirement is documented and level 3 means it is practised. Certification needs level 3 on every requirement.
IEC 62443 target security levels in ACSSA: the asset owner's level decides what is checked, and nothing is awarded
How ACSSA uses each zone's target security level from the asset owner's IEC 62443-3-2 risk assessment to decide what is checked, and why no level is awarded.
Service providers in ACSSA: IEC 62443-2-4, delegated tasks and the VIC shortcut
How ISASecure ACSSA evaluates an asset owner's service providers against IEC 62443-2-4: who counts, delegated tasks, the agreed list, NR-A and the VIC result.
ACSSA evaluation results: ten result types, and the one that fails
ACSSA records ten result types across four IEC 62443 parts. Only Not met fails; three others pass only with approved documentation; unsampled zones get none.
CCSC explained: the four IEC 62443-4-2 constraints that apply to every component
IEC 62443-4-2 has a second axis beyond the seven foundational requirements: four common component security constraints. What each means for a CSA certificate.
The four IEC 62443-4-2 component types, and why the type determination decides your CSA scope
Software application, embedded device, host device or network device: which IEC 62443-4-2 component types apply to your product, and how they set CSA scope.
Independent testing in ISASecure CSA: what the lab must test itself
ISASecure CSA flags 34 of its 166 functional requirements for testing by the lab itself. What the flag means, what happens to the rest, and what to prepare.
SDA-C, FSA-C and VIT-C: what each ISASecure CSA assessment stream proves
The ISASecure CSA assessment process, stream by stream: what SDA-C, FSA-C and VIT-C each prove, the five result outcomes, the pass rule and the certificate.
The SDLA prerequisite: why ISASecure CSA needs it, and what the SDA-C artifact review adds
ISASecure CSA requires a valid SDLA certificate. What the process certificate covers, what the component-level SDA-C review adds, and what to prepare.
CSA security levels 1 to 4: what each level actually adds
IEC 62443 security levels explained through ISASecure CSA: what SL 1 to SL 4 are built to resist, how many requirements each adds, and how to pick a target.
ISASecure vulnerability identification testing: how the pass threshold scales with security level
ISASecure VIT pass criteria: one severity band is added per security level, the scan is identical at every level, and a pass never requires zero findings.
CSA vs ICSA: which ISASecure scheme fits your device
CSA certifies the four IEC 62443-4-2 component types by security level; ICSA certifies IIoT devices and gateways by Core or Advanced tier. How to choose.
Cloud links, wireless radios and the per-interface rule in ISASecure ICSA
In ISASecure ICSA, cloud and wireless links are ordinary accessible interfaces. How the per-interface rule and the untrusted-network declaration set the effort.
ISASecure ICSA Core vs Advanced: what the higher tier actually adds
ICSA Core vs Advanced explained: what each tier is for, how 158 requirements become 182, which 24 are added and which the lab tests, and how to choose.
IIoT device or IIoT gateway: how the two ISASecure ICSA types decide your scope
Which of ISASecure ICSA's two IIoT types your product is, how the IEC 62443-4-2 families split between device and gateway, and why one product can carry both.
SDA-IC: the 93 lifecycle requirements checked per IIoT component, and the five ICSA-only practices
What ICSA's SDA-IC review checks per IIoT component: 93 of the 118 IEC 62443-4-1 lifecycle requirements, 16 IIoT-specific rows and five ICSA-only practices.
The Security Maintenance Audit: how an ISASecure ICSA certificate stays valid
How the ISASecure ICSA Security Maintenance Audit works: four IEC 62443-4-1 requirements, four topics, when audits fall, findings, suspension, withdrawal.
The 24 IIoT-specific requirements ISASecure ICSA adds to IEC 62443-4-2
ISASecure ICSA adds 24 IIoT-specific requirements to the IEC 62443-4-2 base: 18 at both tiers, 6 at Advanced only. What they cover and how to prepare.
IIoT vulnerability testing: how ISASecure ICSA's two tiers set the pass threshold
ISASecure ICSA vulnerability testing: Core must address critical and high findings, Advanced adds medium. One scan, two filters; a pass is never zero findings.
Independent testing in ISASecure ICSA: the 47 requirements the lab exercises
ISASecure ICSA flags 47 of its 182 functional requirements for testing by the lab itself, 40 of them at Core. What the flag means and what to prepare.
SDLA certificate validity and recertification: how an ISASecure SDLA certificate is kept
How long an ISASecure SDLA certificate lasts, 36 or 12 months, how a recertification audit renews it, and why the scheme has no surveillance or suspension.
IEC 62443-4-1 defect and update management: the SDLA practices product certifications come back to
How ISASecure SDLA evaluates IEC 62443-4-1 defect and update management: 15 rows, most seen only in the process audit, and the four requirements ICSA revisits.
Full or readiness evaluation: the SDLA choice that sets your certificate at 36 or 12 months
ISASecure SDLA has two evaluation methods. One requirement passed by readiness evaluation sets the certificate at 12 months, not 36. The 21 rows that decide it.
What counts as a major nonconformity in an IEC 62443-4-1 audit: the 31 SDLA minimum requirements
In an ISASecure SDLA audit a finding is major when no evidence exists, or when one of 31 minimum requirements is applied inconsistently. The full list.
IEC 62443-4-1 certification levels: why ISASecure SDLA has none and every requirement must pass
ISASecure SDLA carried certification levels until 2018. Today it has none, and no maturity level either: every applicable IEC 62443-4-1 requirement must pass.
The SDLA prerequisite for CSA, ICSA and SSA: one process audit, three product schemes
ISASecure CSA, ICSA and SSA each require a valid SDLA certificate. What the process audit settles once, what every product scheme re-checks, and how to plan.
IEC 62443-4-1 security guidelines and hardening: the SDLA practice with the most minimum requirements
ISASecure SDLA and the IEC 62443-4-1 security guidelines practice: 7 requirements, 17 rows, 10 minimum requirements, no mandatory artifacts, examined twice.
One certificate, several levels: how ISASecure SSA assigns a capability security level per zone
How ISASecure SSA assigns an IEC 62443 capability security level to each zone of a system, why one certificate can carry several levels, and how to specify it.
IEC 62443-3-3 requirements: how ISASecure SSA evaluates all 100 clauses in FSA-S
ISASecure SSA's FSA-S stream covers every clause of IEC 62443-3-3: 51 system requirements and 49 enhancements, laid out as 116 rows and scored zone by zone.
How to read an ISASecure SSA certificate and report: zones, levels and user-enforced mitigations
How to read an ISASecure SSA certificate and its SSA-303 report: capability levels per zone, the ten report sections, and the mitigations the user must apply.
SSA SDA-S artifacts: the 74 lifecycle rows ISASecure checks for a system, and why fuzz and load results are among them
ISASecure SSA's SDA-S stream re-checks 74 assessable rows of the SDLA-312 lifecycle catalogue for the system as sold, fuzz and load coverage included.
A system as sold: IEC 62443-3-3 system certification scope under ISASecure SSA, and what falls outside it
ISASecure SSA certifies a control-system product as sold, at a version, in a fixed or scalable layout: the four eligibility criteria and what falls outside.
ISASecure SSA vulnerability testing: the scan where each zone sets its own pass threshold
How VIT-S works in ISASecure SSA: one known-vulnerability scan of every IP-addressed component, with the pass threshold set per component by its zone's level.
Independent testing in ISASecure SSA: eleven flagged requirements, one scan, one reference system
ISASecure SSA flags 11 of its 116 assessable rows for lab testing, plus one vulnerability scan on one reference system. What the lab tests and reviews.
Have a product or system to certify?
Talk to the assessors who wrote these articles about what applies to you.