Industrial controllers, connected products and AI models now sit inside regulated business processes, and none of them accept an endpoint agent. IrisInfosec secures them on their own terms: IoT and OT security built to IEC 62443 and the EU Cyber Resilience Act, and AI security tested against the OWASP LLM Top 10 and MITRE ATLAS.
Most security programmes assume a laptop: an agent installs, a patch lands in a maintenance window, a log reaches the SIEM. Industrial controllers, connected products and AI models break all three assumptions, and regulators have stopped treating that as an excuse. NIS2 asks operators to secure industrial networks. The Cyber Resilience Act asks manufacturers to secure what they ship and to report what gets exploited. The EU AI Act asks providers to make high-risk systems robust against manipulation. We design inside those constraints first, then produce the evidence in the shape the regulation asks for. Governance sits alongside in cyber risk and compliance, and proof in independent testing.
Two disciplines, one accountable team
Engage one discipline or run both as a single programme. Each links to a page with full scope, method and deliverables.
Secure what runs the plant and what you ship. ICS and SCADA assessment to IEC 62443, industrial protocol and firmware analysis, and Cyber Resilience Act readiness for products with digital elements.
Test the model, not just the application around it. LLM and agent red teaming against the OWASP LLM Top 10, adversarial testing for poisoning and extraction, and security across the AI supply chain.
A short scoping call reads your industrial estate or your AI systems against the duties that apply, and tells you which work comes first.
How we work
A measured five-stage approach that respects what the environment can tolerate and ends in evidence a regulator will accept.
Inventory the controllers, devices and models actually in production, including what was deployed without a security review.
Threat model to IEC 62443 zones and conduits, or to MITRE ATLAS and the OWASP LLM Top 10, depending on the system.
Passive and out-of-band methods first, active testing only where the process or the model tolerates it.
Segmentation, secure update paths, monitoring and guardrails designed for an estate you cannot rebuild.
Produce the technical file, the reporting path and the review cadence the regulation expects.
Regulations & frameworks
We design and test against the standards your auditors, your notified body and your regulator actually use, so one piece of work answers the operational question and the compliance question together.
One estate, several regimes. A connected product sold into the EU can carry Cyber Resilience Act, Radio Equipment Directive and sector duties at once. We map them once, not three times.
Primary sources, not hearsay. We work from the regulation and the standard as written, and cite the article or clause that applies to your system.
Safety sets the rules of engagement. In operational environments, process safety and availability constrain the test plan. That is a design input, not an obstacle.
| Regulation or framework | What we align to | |
|---|---|---|
| EU Cyber Resilience Act | Product security duties, SBOM in technical documentation, and the vulnerability reporting clock | |
| NIS2 | Risk management and incident reporting duties for essential and important entities | |
| IEC 62443 | Zones, conduits and security levels for industrial automation and control systems | |
| EU AI Act | Accuracy, robustness and cybersecurity duties for high-risk AI systems | |
| OWASP LLM Top 10 & MITRE ATLAS |
Test coverage for LLM applications and adversarial AI techniques | |
| ETSI EN 303 645 & EN 18031 |
Consumer IoT baseline and the RED cybersecurity harmonised standards |
What you receive
Practical artefacts, written so the people who answer to a regulator and the people who run the systems both find them useful.
Every controller, connected device and AI system in production, with owner, exposure and criticality.
Zones and conduits for industrial estates, MITRE ATLAS techniques for AI systems.
Evidence a vendor cannot argue with and an engineer can act on, ranked by exploitability and consequence.
Segmentation, brokered remote access, update paths and guardrails scoped to the estate you actually have.
Cyber Resilience Act documentation, SBOM and a vulnerability handling process that survives an audit.
Detection tuned for industrial and AI telemetry, and the incident reporting path each regime expects.
Turn hard-to-secure systems into evidence you can present
Share your industrial estate or your AI systems and the regimes you report against. We will send a
prioritised plan with dates, usually within 3 business days.
Why teams choose us
Most firms sell either industrial engineering or security consulting. We hold the regulation and
the engineering together, so the design and the evidence come from the same team.
The people who read the Cyber Resilience Act are the people who write the test plan, so nothing is lost in translation.
We assess live industrial estates without becoming the incident, using passive capture, lab replicas and agreed abort criteria.
We work with the plant that runs the equipment and the firm that builds it, so both sides of a duty are understood.
EU, US and India understood as peer markets, so one design carries across the regimes you sell and operate in.
Security and regulation are the whole job, so you get depth a broad consultancy struggles to match.
Delivery is backed by an ISO/IEC 27001 certified partner network, so capacity does not limit your timeline.
Questions, answered
Clear answers to what security and product leaders ask us most. Need something
specific to your sector? Ask us directly.