Security and compliance
Security in IRIS
Every request passes one access check for the user's role and factory. A work order sign-off needs the person's own password.
- ISO 27001 certified
- GDPR compliant
- IEC 62443 aligned
- Sign-in
- Verified
- Role in Plant A
- Maintenance lead
- CMMS
- View allowed
M. Novak opens CMMS work orders in Plant A.
Access
Who sees which data
IRIS checks access in one place, before a request reaches any module.
Data kept per factory
Data is separated by factory. The access layer sets the factory on each request from the permission it has checked.
One check for every request
Every request from the app goes through one access layer, which checks the user's role. Roles are set per factory in Admin.
The assistant only reads
The assistant reads plant data and documents within the user's role and cannot change records. Each document lists who may read it.
What an API key reads
An API key reads IoT data in its own factory only. It never gets more access than the role of the person who issued it.
Operators at the kiosk
Operators sign in at the kiosk with a PIN or a card. The session covers one factory and one station and lasts up to 12 hours.
Records
What you can show an auditor
Each module keeps its own signatures and registers, with the person and the time.
Work order sign-off
To sign off a finished CMMS work order, a person enters the password of their own IRIS account again. A kiosk PIN is not enough.
E-signatures in QMS
Each plant chooses which QMS decisions need an e-signature: closing an NCR, confirming that a CAPA worked, approving a document.
NIS2 incident register
IoT tracks the 24-hour, 72-hour and 30-day deadlines for each incident. Your team records what it reported. IRIS does not report to CSIRT or ENISA.
Device software lists
Upload a device's SBOM as CycloneDX or SPDX and search devices by CVE ID. IRIS does not scan devices itself.
AI uses and decisions
Data & AI keeps decision traces and a register of AI uses and high-risk decisions.
Who opened payroll data
The People module logs every read of payroll data. Employees can see that log for their own data.
Shop floor
The connection to machines
Machine data comes in through Data Bridge. Commands to equipment go out only from Data Bridge.
Device certificates
Data Bridge runs the plant's own certificate authority. Each device creates its own private key, which never passes through the server.
No direct polling
IRIS does not open connections to PLCs or meters. Readings arrive over MQTT or HTTP, usually through a gateway.
Not a safety function
A command from Data Bridge is an ordinary integration message. IRIS does not control machine safety.
Staged firmware updates
Firmware goes out in stages: a canary group, then 25%, 50% and 100%. A device counts as updated once it confirms.
Deployment
Where your data lives
SaaS
IRIS runs in our cloud, and each factory's data is kept separate.
Private cloud
A dedicated private cloud for plants with strict data residency rules.
On-premise
IRIS runs in your own data center, and production data stays in the environment you choose.
Questions from your IT team
Leave your email and tell us how you plan to deploy IRIS, and we will send answers for your IT team.
Questions from your IT team?
Read the security overview, or send your questions to our team.