Water metering security spans devices, networks, platforms and people. A practical plan defines which functions each role needs, how credentials are managed and how changes can be traced throughout the service life.
Map data and permissions
Identify meter identifiers, consumption records, customer links and any control functions. Assign access by operational responsibility and review it when roles change. Reading consumption, changing configuration and operating a valve are different privileges. Separate them where the system supports it and record who is accountable for each action.
For a WE RICH product comparison, the Head End System (HES) brings collected readings and communication status into an operational view, with interfaces agreed for the project.
For a WE RICH product comparison, the LoRaWAN gateway forms part of the communication path between compatible meters and the application; coverage and backhaul must be planned for the site.
Manage credentials over time
Define secure provisioning, storage, rotation and revocation for device and application credentials. Avoid putting secrets in shared spreadsheets or public documentation. Clarify which party can recover service after staff or supplier changes. Require evidence for the actual security configuration rather than assuming a radio protocol name establishes end-to-end protection.
Prepare for investigation and continuity
Keep audit records for important configuration and account changes. Define backup, export and incident-response responsibilities, and test restoration using an agreed procedure. If remote control exists, document authorization and failure handling separately. Review applicable privacy obligations with the organization’s responsible team; technical features alone do not establish legal compliance.
Practical checklist
- Inventory roles and data flows.
- Document credential ownership.
- Test backup and recovery.
Frequently asked questions
Does encryption alone make the system secure?
No. Access, credentials, operations and recovery also matter.
Should all users be administrators?
Access should reflect each role’s actual responsibilities.
Does consumption data need governance?
Yes. Define permitted uses, retention, access and export responsibilities.
Related articles
References and technical reading
Product capabilities depend on the model and its documentation. Confirm installation and performance requirements for the project.