
Each industry has its own risks and its own rules. We start there.
A wheel loader, a PLC, a pacemaker and a substation controller are all connected products, but they face different attackers, run for different lifetimes and answer to different regulators. Generic security advice ignores those differences and wastes effort.
We organise our work by industry so the first conversation already speaks your language: the systems you build or run, the rules that apply to them and the evidence your customers and authorities expect.

Manufacturers
Telematics, remote diagnostics and over-the-air updates open machines to attacks that reach whole fleets.
CRA, Machinery Regulation, RED, ISO 24882
Learn more
Manufacturers, integrators
PLCs and drives with long lifetimes face attack frameworks built for industrial protocols.
CRA, IEC 62443-4-1 and 4-2
Learn more
OEMs and suppliers
Dozens of ECUs, connected services and chargers, with threat analyses repeated for every variant.
UN R155 and R156, ISO/SAE 21434, TISAX
Learn more
Manufacturers
Long device lifetimes and shared components, in hospital networks under constant ransomware pressure.
MDR, IEC 81001-5-1, FDA 524B
Learn more
Operators and suppliers
IT and OT run together with remote access for many providers, now under NIS2 accountability.
NIS2, KRITIS, IEC 62443-2 and 3
Learn more
Operators and equipment makers
Distributed wind, solar and grid assets managed through vendor clouds and remote links.
NIS2, IEC 62443, IEC 62351, CRA
Learn moreDifferent sectors, the same core questions. These are the topics we meet in every industry.
Regulation
The CRA now sits on top of sector rules such as UN R155, the MDR or the Machinery Regulation.
Lifetime
Vehicles, machines and grid assets outlive the software they were built with.
Suppliers
Components, software and services from many suppliers must meet the same requirements.
Remote access
Remote diagnostics and updates create value and a direct way in.
Variants
Product families need analyses that can be reused instead of repeated.
Reporting
The CRA and NIS2 set deadlines measured in hours, not weeks.
Safety
Where machines move or patients depend on devices, a cyber attack becomes a safety risk.
Evidence
Customers, assessors and authorities expect traceable, consistent documentation.
Step 1
Your systems, markets and customer requirements.
Step 2
Which rules and standards apply to which product or site.
Step 3
What must be done first, and what can wait.
Step 4
Consulting, AITIGRITY or both, with a clear first step.
Very likely. The method is the same for any connected product or industrial system. Tell us what you build or run.
Contact usYes. Manufacturers need secure products and conformity; operators need secure plants and NIS2 compliance. We cover both, often in the same supply chain.
That depends on the product, its connections and its market. The CRA Readiness Check gives a clear answer per product.
Regulatory readinessTell us about your product and the rule you are facing. You talk to an engineer from the first call.