Skip to main content
Lumiar
Home/ Services/ Architecture and engineering assurance
SERVICE

Architecture and engineering assurance

A security architecture that can be built and operated. We divide the facility into zones and conduits according to IEC 62443 and set requirements proportionate to the risk.

Typical situations

If one of these sounds familiar, it is worth a conversation.

You are building new or upgrading the OT/control system, and want security in from the start.
The network has grown organically for years, or inorganically, and no one has the full picture any more.
IT and OT are being connected more tightly, or you are adopting cloud services and IIoT, and you need clear boundaries.
A client, management or authority requires documented security and architecture according to IEC 62443 or regulations such as NIS2, CRA, and CER.

Delivery and method

We map the current architecture together with your people, divide the systems into zones and conduits, and set security level requirements based on the risk assessment. The result is a target picture with a realistic path to it, in steps that fit turnarounds and ordinary projects. Some set SL requirements too low, others too high and unrealistic. The art is finding the right, balanced level for the system as a whole, in the context it operates in. We make sure the whole chain holds together: the level needed, what can be delivered, how the requirements are set towards suppliers, how deliveries are followed up, and how the level is maintained in operations. Where cloud services and IIoT break with the layering in the Purdue model, we build on IEC PAS 62443-1-6.

01Zone model with conduits and SL requirements
02Target architecture and gaps against the current solution
03Prioritized action plan in feasible steps
04Basis for setting requirements towards vendors
05Development and adaptation of methods, processes, management systems, tools, and checklists
METHODOLOGICAL BASIS
IEC 62443-3-2 (zones, risk)
IEC 62443-3-3 (system requirements)
IEC 62443-2-4 and 4-2 (supplier requirements)
IEC PAS 62443-1-6 (IIoT and cloud services)
Offshore Norge 104, CSBR 11–13 and 20
The Purdue model
ARKITEKTUR · IEC 62443-3-2
Soner, conduits og skytjenester

Soner beskytter de essensielle funksjonene og gjør avhengighetene synlige.

AnleggSone · ITKontorsystemer og forretningsdataconduitSone · OT DMZHistorian-replika, fjernaksess, patchconduitSone · prosesskontrollEssensielle funksjoner: styring og overvåkingconduitSone · safetySIS: essensielle sikkerhetsfunksjonerskilt fra de andre sonene (ZCR3.3)Sone · skytjeneste ellerIIoTAnalyse og tjenester utenforanleggetconduitavhengighet utenfor anlegget
AnleggSone · ITKontorsystemer og forretningsdataSone · OT DMZHistorian-replika, fjernaksess, patchSone · prosesskontrollEssensielle funksjoner: styring ogovervåkingSone · safetySIS: essensielle sikkerhetsfunksjonerskilt fra de andre sonene (ZCR 3.3)Pilene er conduits mellom sonene.Sone · skytjeneste eller IIoTAnalyse og tjenester utenfor anleggetavhengighet utenfor anlegget (via conduitfra OT DMZ)

Grunnlag: IEC 62443-3-2:2020 (ZCR 3). Skytjenestedelen er informert av IEC PAS 62443-1-6:2025.

Lumiar-synteseLumiar
ARCHITECTURE · IEC 62443-3-2

Zones, conduits, and cloud services

Zones protect the essential functions and make dependencies visible.

PlantZone · ITOffice systems and business dataconduitZone · OT DMZHistorian replica, remote access, patchingconduitZone · process controlEssential functions: control and monitoringconduitZone · safetySIS: essential safety functionsseparated from the other zones(ZCR 3.3)Zone · cloud service or IIoTAnalytics and services outside theplantconduitdependency outside the plant
PlantZone · ITOffice systems and business dataZone · OT DMZHistorian replica, remote access,patchingZone · process controlEssential functions: control andmonitoringZone · safetySIS: essential safety functionsseparated from the other zones (ZCR 3.3)The arrows are conduits between the zones.Zone · cloud service or IIoTAnalytics and services outside theplantdependency outside the plant (via conduitfra OT DMZ)

Basis: IEC 62443-3-2:2020 (ZCR 3). The cloud service part is informed by IEC PAS 62443-1-6:2025.

Lumiar synthesisLumiar
BEREDSKAP · OFFSHORE NORGE 104, CSBR 20
Øymodus

Anlegget skal kunne kobles fra eksterne nett og fortsatt driftes trygt, om nødvendig med redusert optimalisering.

TilkobletEksterne nett og ITgrenseOT-miljøEssensielle funksjoner og prosessØymodusEksterne nett og ITeksterne forbindelser stoppergrenseOT-miljøEssensielle funksjoner og prosessredusert, men trygg driftEnkel frakobling som erlett å utføre (krav 20-3)Konsekvensene er kjent ogdokumentert (krav 20-2)Prosedyrer for bruk (krav20-4)Jevnlige øvelser (krav20-5)Trygg gjenoppkobling(veiledning)
TilkobletEksterne nett og ITOT-miljøEssensielle funksjoner og prosessØymodusEksterne nett og ITeksterne forbindelser stopperOT-miljøEssensielle funksjoner og prosessredusert, men trygg driftEnkel frakobling som er lett å utføre (krav20-3)Konsekvensene er kjent og dokumentert (krav20-2)Prosedyrer for bruk (krav 20-4)Jevnlige øvelser (krav 20-5)Trygg gjenoppkobling (veiledning)

Grunnlag: Offshore Norge 104 rev. 7, CSBR 20 (krav 20-1 til 20-5).

Lumiar-synteseLumiar
PREPAREDNESS · OFFSHORE NORGE 104, CSBR 20

Island mode

The plant must be able to disconnect from external networks and still operate safely, with reduced optimization if necessary.

ConnectedExternal networks and ITboundaryOT environmentEssential functions and processIsland modeExternal networks and ITexternal connections stopboundaryOT environmentEssential functions and processreduced but safe operationSimple, easy disconnection(requirement 20-3)Consequences known anddocumented (requirement20-2)Procedures for use(requirement 20-4)Regular exercises(requirement 20-5)Safe reconnection(guidance)
ConnectedExternal networks and ITOT environmentEssential functions and processIsland modeExternal networks and ITexternal connections stopOT environmentEssential functions and processreduced but safe operationSimple, easy disconnection (requirement20-3)Consequences known and documented(requirement 20-2)Procedures for use (requirement 20-4)Regular exercises (requirement 20-5)Safe reconnection (guidance)

Basis: Offshore Norge 104 rev. 7, CSBR 20 (requirements 20-1 to 20-5).

Lumiar synthesisLumiar

Engineering assurance in projects and operations

When technical choices have consequences, independent technical verification is needed. We support projects and operating organizations with design reviews, requirements for suppliers, supplier follow-up along the way, and resolution of deviations in OT security. The aim is solutions that can be built, operated and documented in the industrial reality, without measures that exist only on paper.

01Design review
02Supplier follow-up
03Technical queries and deviations
04Requirements traceability
05Verification before handover
06Transition to operations

Scope and format

DURATION
2 to 6 weeks
depending on the size of the facility and the quality of the documentation.
WAY OF WORKING
Workshops and document review
on site or remote. A site visit is recommended for the first review.
PREREQUISITES
Documentation and key personnel
network documentation at whatever level you have, and people who know the systems.

Frequently asked questions

Does the whole facility have to be done at once?
No. Many start with one sub-facility or production line, and reuse the model from there.
What if the documentation does not match reality?
That is common. We map what is there, and the deviations become part of the findings.
Can you set requirements towards our vendors?
Yes. The zone model and SL requirements are written so they can go into contracts and requirement specifications.