Answerable to your OT team, not only your IT team.
This page is written to be read by the person whose signature a pilot needs. It states where Muono runs, what it reaches, what it records, and which certifications we hold today, which is none of them yet. Where a claim is not settled, the clause says so rather than implying otherwise.
Four models, and your security review picks one: your own cloud tenancy on Azure or AWS, Muono-hosted, fully on-premise, or hybrid with an edge collector on site and the model in the cloud. The matrix below reads down each column.
Read the clause→Access posture is set per connector and agreed at deployment rather than asserted here. Historians and business systems are read on a schedule you set. Where a connector would reach further than reading, it is scoped, written down and signed before it is enabled.
Read the clause→The region is fixed at deployment and does not move afterwards. GDPR obligations are supported in every deployment model, including subject access and deletion. On-premise and hybrid keep the raw side inside your own perimeter.
Read the clause→Your existing directory, with roles mapped to the authority levels an agent may act under. Irreversible actions hand off to a named approver rather than to a queue, and the level an agent runs at is a decision your team makes deliberately.
Every agent action is recorded against the person who authorised it, with the readings and documents it relied on. Runs are replayable after the fact and their side-effects reversible. Model state is viewable at any past date, so a submission can be reconstructed as it stood.
Read the clause→SOC 2, ISO 27001 and IEC 62443 alignment are in progress. We are not certified against them today and will not claim otherwise, including by implication. When that changes this clause changes with it, and the revision above will say so.
Read the clause→If a clause does not clear your policy, that is worth knowing before a pilot is scoped rather than after.