Skip to main content

security.compliance()

IEC 62443 Compliance & NIS2

operating context

When IEC 62443 and NIS2 remain abstract checklists

OT compliance is needed when the team must move from perceptions and checklists to a recognizable alignment programme, readable by management and traceable in audits.

01

Requirement reading

Issue

IEC 62443 and NIS2 remain abstract without operational translation into the real OT context.

Solution

Maps requirements, controls, current state and ownership in a single register.

02

Alignment sequence

Issue

Everything looks urgent: without priorities the alignment fragments into disconnected initiatives.

Solution

Sequences technical, organizational and documentary controls in manageable phases.

03

Evidence over time

Issue

Evidence exists but it is scattered: it does not survive turnover, audits or inspections.

Solution

Defines what is needed, who produces it and how it stays current.

operating method

How we work: 4 inspectable steps in sequence

01

Gap analysis

Evaluation of current state against applicable IEC 62443 and NIS2 requirements.

IEC 62443NIS2mapping
02

Compliance plan

Roadmap with prioritised actions, responsibilities, timelines and investments to close gaps.

gapcontrolspriorities
03

Implementation

Support in implementing technical and organisational measures: policies, procedures, controls.

roadmapownershipmilestones
04

Audit and certification

Preparation for certification or inspection: documentation, evidence, internal pre-audit.

evidenceauditmaintenance
expected output

The elements that give compliance real substance

We build an alignment path that holds up under inspections, internal governance and technical field work.

Mapping between required controls, current state, ownership and priority level.

tech spec

Technical spec

explorer
architecture/ 2
operations/ 2
requirements-map.md
// compliance.requirements

Requirements map

analisi: IEC 62443 requirements (relevant parts) and NIS2 obligations applicable to the context.
criticità: Abstract requirements, controls not linked to real assets.
output: Requirement → control → asset → ownership map.
IEC 62443NIS2mapping
// compliance.gap

Gap register

analisi: Current state of controls against requirements, with evidence level.
criticità: Gaps hidden behind undocumented compensating controls.
output: Trackable register with priority and ownership.
gapregisterpriorities
// compliance.roadmap

Control roadmap

analisi: Sequence of technical, organizational and documentary interventions.
criticità: Disconnected initiatives, unmanaged dependencies, ambiguous ownership.
output: Phased roadmap with milestones, costs and ownership.
roadmapmilestonesownership
// compliance.evidence

Evidence model

analisi: Type of required evidence, frequency, custodians and collection channel.
criticità: Scattered evidence, heterogeneous formats, manual maintenance.
output: Sustainable, inspectable evidence model.
evidenceauditmaintenance
architecture/requirements-map.md Markdown
next_step.initialize

Build OT compliance

IEC 62443 and NIS2 translated into a feasible, inspectable programme.