All resources
Blog · 17 Nov 2026 · 6 min read · smoc.cloud team

Security questions first: what IT and compliance will ask about your metering platform

Metering platforms touch critical infrastructure and customer data. A good evaluation answers the hard security questions before anyone looks at features.

Security comes before features

If you lead a utility operations team, your IT and compliance colleagues will ask about security long before they ask about dashboards. They should. Metering platforms connect to critical infrastructure and hold customer data.

The questions to expect

  • How is the platform secured? Encryption in transit and at rest, network isolation and hosting location
  • How are tenants and data separated? Especially if a provider runs several utilities
  • Who can do what? Role-based access, least privilege and approval for high-impact commands
  • How are meter keys managed? Lifecycles, rotation and evidence of who used which key
  • What evidence can you produce? An audit trail that stands up to regulators
  • How does it fit our protocols? DLMS/COSEM, IEC CIM and the head-end systems you already run

Proof before a pitch

Operations teams increasingly read the technical detail before they ever book a call. That is a healthy sign, and it is why smoc.cloud publishes its security approach and multi-tenant security architecture openly, with no form to fill in.

A simple evaluation order

  1. Read the security documentation
  2. Bring IT and compliance to the first demo
  3. Ask for the audit evidence a regulator would request

Then, and only then, look at features. Request a demo when you are ready.

How smoc.cloud helps

Security teams need proof, not promises. smoc.cloud gives IT and compliance a live view of the security posture of the metering estate and the evidence to answer their questions.

  1. Spot it

    See security events across vendors

    Tamper alarms, failed authentications, key changes and unusual command activity from every head-end appear in one security view.

  2. Find the root cause

    Tie the event to its source

    Correlation separates a genuine attack pattern from a misconfigured device or an expired key, and shows which meters, tenants and users are involved.

  3. Fix it

    Act and evidence it

    Role-based access, tenant isolation and an immutable audit trail let you contain the issue and produce audit evidence on demand for IT, compliance and regulators.

What this means for you

As operators of critical national infrastructure, DNOs should ask first about incident reporting and how security events from every head-end reach one view.

DNOs: how smoc.cloud helps
The Metering Operations Brief

One email a month with new articles, whitepapers and field notes on running smart metering estates. Unsubscribe at any time.

Join the conversation on LinkedIn

Open on LinkedIn
Nov 18, 2026

Customers never see your head-end. They see their bill. A commissioning that stalls. A meter that quietly stops reading. A register that drifts. None of it reaches the customer straight away. Weeks later it arrives as an estimated bill and a call to the contact centre. Our new whitepaper follows five moments that shape the customer experience, from installation to support, and shows where operations decide whether each one goes right. Which stage generates most of your metering complaints? #CustomerExperience #SmartMetering #Utilities

Nov 18, 2026

Two meters. Both fully DLMS/COSEM compliant. Different object lists, different event codes for the same power failure, different load profile settings. Compliance gives you a common language. It doesn't give you a common vocabulary. That's the gap the DLMS UA Generic Companion Profile closes: standard objects and behaviours that every model implements the same way. Fewer custom integrations, faster onboarding of new models, less lock-in. Our new whitepaper explains what it means for the metering business, not just the engineers. #DLMS #SmartMetering #Standards

Nov 14, 2026

How to walk into a budget meeting with metering ROI that survives questions. Start with your estate size. Under 100k meters runs differently from 100k to 1M, and both differ from over 1M. The math changes at each tier. Then map your operations to the cost lines: reads, exceptions, field visits, compliance effort. Then put numbers on each one. Provable beats impressive every time. #UtilityOperations #SmartMetering #EnergySector

next_step

See your estate in smoc.cloud.

A demo walks through your utility types, your vendors and your compliance obligations — not a generic slide deck.