Industrial control systems · OT cybersecurity

OT cybersecurity for systems that have to keep running.

Meridian helps operators, integrators and suppliers turn OT cybersecurity requirements into practical engineering work for industrial projects, product delivery and operational systems. That includes ICS risk, architecture and assurance, using IEC 62443 where it applies.

A 30-minute introductory call, with no obligation or payment required. Keep sensitive site details out of public forms.

Turn the requirement into defined engineering work.

The work starts with the installed system and the decision that has to be made, then turns that context into an agreed scope, usable records and evidence for delivery.

Define the work around

  • Scope and system boundary
  • Installed architecture and required communications
  • Operating constraints and project interfaces
  • Responsibilities across the owner, integrator and suppliers
  • Available design, process and verification evidence

Produce decisions and evidence

  • Defined work package and responsibility split
  • Risk, architecture or requirements records
  • Review comments and accountable actions
  • Verification, FAT/SAT or handover evidence
Explore technical capabilities

See how the work is evidenced.

Explore illustrative engineering methods and output records, or review Meridian's capabilities before making an enquiry.

Illustrative examples

Engineering methods and output records

See worked examples of common OT cybersecurity questions and the records that support engineering decisions. These illustrate an approach, not completed client engagements.

Explore worked examples

Company capabilities

Meridian capability statement

Review the areas of support, typical deliverables and engagement approach to help establish whether Meridian fits your requirement.

Read the capability statement

IEC 62443 starts with your responsibility and scope.

The applicable requirements depend on your role, system or product boundary and lifecycle stage. Asset owners, integrators, product developers and machine builders may have different responsibilities; the service you need depends on the decision or work ahead.

Explore organisational roles and IEC 62443 context
Frameworks used where applicableIEC 62443NCSC CAFNIS and sector requirementsClient cybersecurity specifications

Industrial context matters.

The detail changes by sector, but uptime, safety, legacy assets, supplier dependencies and controlled change shape what can be done and how it should be evidenced.

From first discussion to agreed actions.

  1. 01

    Arrange a discovery call

    Start with a 30-minute introductory discussion about your system, requirement and project stage. No obligation or payment is required for the call.

  2. 02

    Agree the scope

    Define the system boundary, available evidence, operational constraints and expected deliverables before work begins.

  3. 03

    Review and report

    Assess the evidence, discuss findings with the relevant teams and document practical actions with clear ownership.

How an engagement works

Discuss your OT cybersecurity requirement

Whether you have a specific question or a project that needs engineering support, an introductory call can help clarify the requirement and next steps. Keep sensitive site details out of the booking form.