Posted in

How do I ensure the security of data transmitted by a wired remote water meter?

Hey there, Wired Remote Water Meter

If you’re here, chances are you’re either running a water utility, managing a commercial property, or just someone who’s noticed those sleek, wire-connected water meters popping up everywhere lately. (No judgment—they’re kind of hard to miss.) As the guy who’s been selling and supporting wired remote water meters for over 8 years now, I get a lot of the same question: “How do I make sure the data these things send is actually secure? Because if that gets hacked, it’s not just a hassle—it could mess with billing, leak detection, even critical water infrastructure.”

Fair question. Let’s cut the corporate jargon for a sec—no “end-to-end encryption synergies” or “paradigm-shifting security frameworks” here. We’re talking real, actionable stuff that actually works, because I’ve seen what happens when security gets an afterthought (spoiler: it’s not pretty, and half the time it’s the meter supplier that ends up fielding 2 a.m. calls).

First off, let’s set the scene: wired remote water meters aren’t like your home Wi-Fi camera that’s broadcasting over the public airwaves. They’re wired—usually to a local gateway, a utility’s internal server, or a private network, not the open internet. But that doesn’t mean they’re invisible to bad actors. Wires get tapped. Gateways get misconfigured. Default passwords get left on. I’ve had a client last year who almost had a leak go undetected because some kid in a neighboring office building tapped their meter’s data line to mess with their bill. Oops.

So how do we (as a supplier) and our customers lock this down? Let’s break it down by what we control and what you (the operator) can handle too—because security’s a two-way street, not something we just “set and forget.”

Starting with the hardware and communication layer, which is our job as the meter maker. First off, we don’t use plaintext for data transmission. Ever. Back in the day, some old wired meters just sent numbers as unscrambled signals—super easy to intercept. Now, every single one of our meters uses AES-128 encryption for data in transit. Wait, before you zone out: AES is the same standard the US government uses for classified info, so it’s not like we’re using some off-the-shelf stuff you can crack in 5 minutes. But here’s the thing—we don’t just turn it on and leave it. Every meter ships with a unique encryption key, not a generic one for all 10,000 units we send out that quarter. That’s a big one. If all meters had the same key, one leak and every single unit’s data is toast. Unique keys mean if someone gets a key for one meter, it doesn’t put the rest at risk.

Then there’s the wire itself. We don’t use regular ethernet cable for our main line meters—we use shielded twisted-pair (STP) that’s rated for industrial environments. Why? Because regular unshielded cable is susceptible to electromagnetic interference (EMI) from power lines, and worse, it’s way easier to tap. Shielding blocks EMI so your data stays intact and unreadable to anyone snooping around. Plus, the connectors are keyed—you can’t just plug any random wire into the meter port. It takes a specialized tool to even open the enclosure’s communication port, so nosy techs or random contractors can’t mess with it on a job site. I had a project manager tell me last year that this stopped a plumbing apprentice who was curious about “how the smart water thing worked” from accidentally unplugging a line and causing a whole neighborhood’s data to go down. Win.

Next up, the gateway—this is the middleman between the meter and your utility’s system, right? We work specifically with gateways that support mutual TLS authentication, which is a fancy way of saying the gateway and the meter both have to prove who they are to each other before they talk. No “hey, random device, send me your data” nonsense. If a rogue device tries to connect, the meter just ignores it. We also pre-configure gateways to only accept data from our meters’ unique IDs, so even if someone gets on the local network, they can’t trigger a fake data feed or tamper with readings.

Now, let’s talk about what I always emphasize to customers that’s not our job, but is just as important. First, change the default credentials. Every single device we send—meters, gateways, servers—has a default admin password out of the box. I know, it’s tedious, but so many people just leave “admin” or “password123” on because they’re in a rush. Last month, we had a client’s gateway get hacked because the maintenance team never changed the default login, and a script kiddie found it on a public IP (another no-no, by the way—we recommend putting gateways on a private LAN, not a public one, with a VPN if they need remote access). VPNs are non-negotiable for any off-site access to meter data. If someone needs to check readings from home or a truck, they shouldn’t just log into the gateway’s IP directly—they should use a encrypted VPN tunnel. That way, even if someone sniffs the network, all they get is gibberish.

Then there’s regular firmware updates. This is something we do remotely now, but a lot of old wired meters required a tech to show up and plug in a cable to update. We push over-the-wire (OTW) firmware updates that are signed with our encryption keys, so the meter knows it’s a real update, not a malicious one. We send these out quarterly, sometimes faster if we find a security gap (knock on wood, that’s only happened twice in 8 years). But here’s the catch—customers have to actually install them. I once had a small municipality that put off an update for 6 months, and it turned out there was a tiny flaw that would’ve let someone spoof water usage. We caught it, pushed the patch, and when they finally installed it, they said it saved them from a potential $10k in fraud. Worth the 10 minutes it takes, right?

Another thing that’s super specific to water meters is data minimization. Wait, what does that mean? Don’t send more data than you need. A lot of systems send meter readings every 15 minutes, but if you only need monthly billing and weekly leak alerts, send data once an hour. The less data you transmit, the less there is to intercept. We let customers set the data interval, so they can tweak it based on their needs without sacrificing security. No point in sending extra bytes that just give bad actors more to work with.

Let’s also talk about physical security, because wired meters aren’t immune to physical tampering. Sure, they’re usually installed in utility boxes or underground vaults, but not always. We build our meter enclosures with tamper alerts that send a signal the second someone pries open the cover. And that signal is encrypted, so even if someone intercepts it, they can’t turn off the tamper alert remotely. We also have a feature that locks the meter’s internal settings—you can only change the reading or configuration via the gateway, not by messing with the unit itself. So if someone does get physical access, they can’t just reset the meter to hide a leak or manipulation.

I get it—when you’re running a water utility, you’re juggling a million things: billing, maintenance, emergency repairs. Security can feel like an afterthought, but over the years, I’ve learned that the meters that get targeted are the ones that cut corners on security. That’s why we built our system to be secure by design, not secure as an add-on. No fancy expensive upgrades needed, just standard protocols that work for the real world.

Wait, one more thing I should mention: testing. We do third-party security audits every year, not just internal checks. We send our code, hardware, and communication protocols to independent firms to hack at for a month, and if they find a flaw, we fix it immediately. We post the results (anonymized, of course) on our support portal so our customers can see we’re not just saying we’re secure—we’re proving it. If you’re working with a supplier that won’t share audit results, that’s a red flag. Run, don’t walk.

At the end of the day, securing wired remote water meter data isn’t rocket science. It’s about using proven encryption, unique keys, physical safeguards, and making sure everyone (supplier AND customer) is on the same page about not cutting corners. I’ve seen it work, I’ve seen it fail, and trust me—taking the small steps early saves you from the big headaches later.

If you’re looking to upgrade your water metering system and want to talk through how we can tailor security to your specific needs—whether you’re a small municipal utility, a large commercial campus, or something in between—hit us up for a procurement chat. We’re not the kind of supplier that just sends a price list and disappears. We’ll walk you through every security feature, answer all your random questions (we don’t mind the “what if this happens” stuff), and make sure you feel confident that your data is locked down tight.

Don’t let security be an afterthought. Your water system deserves better, and so do you.

Wired Remote Water Meter References:
NIST Special Publication 800-150: Guide to Securing Smart Grid Systems
International Electrotechnical Commission (IEC) 62351: Power systems management and associated information exchange – Data and communications security
Water Environment Federation (WEF) Utility Cyber Security Guidelines


Shandong Chengze Instrument Co., Ltd.
We’re well-known as one of the leading wired remote water meter manufacturers in China, featured by quality products and good service. Please rest assured to buy high-grade wired remote water meter for sale here from our factory. Also, customized service is available.
Address: No.7, Wensi Road North Industrial Park, Liguan Town, Lanshan District, Linyi City, Shandong Province, China
E-mail: czwatermeter@163.com
WebSite: https://www.cz-watermeter.com/