Perimeter
4/9/2012
11:01 AM
Commentary
Commentary
Commentary
Connect Directly
RSS
E-Mail
50%
50%

How Much Money Do You Need To Lose Before You Start Monitoring?

At what point does turning a blind eye to the loss of revenue spark the inevitable conversation: 'Maybe we should be monitoring this infrastructure more closely?'

A new blog post by Brian Krebs states that the FBI has released a cyberintelligence bulletin claiming that a series of hacks perpetrated against smart-meter installations over the past several years may cost a Puerto Rican electric utility upward of $400 million annually.

According to the post, the FBI said it believes former employees of the meter manufacturer and employees of the utility were altering the meters in exchange for cash and training others to do so. "These individuals are charging $300 to $1,000 to reprogram residential meters, and about $3,000 to reprogram commercial meters," the alert states.

The FBI also said another method of attacking the meters involves placing a strong magnet on the devices, which causes it to stop measuring usage, while still providing electricity to the customer. The article also stated that the hacks described by the FBI did not work remotely and require physical access to the devices.

What I don't understand is how something like this could have gone undetected. If a house, building, or complex has a baseline of usage that suddenly changes (without an associated work order), that's what we in the SIEM world call an anomaly. Why are utilities deploying "smart meters" without accompanying smart monitors?

I'm not saying that the utilities have to use a SIEM product, per se, but they should be implementing some monitoring controls for their environments. If a company is buying the metering technology, then shouldn’t it be pushing for a way to effectively manage and monitor said technology? If an anomaly detection technology or analytical engine was laid atop the company’s usage and billing system, then I would think it would be fairly obvious to notice that something was wrong and that someone should be dispatched to investigate.

Getting down to brass tacks here, monitoring the smart infrastructure would enable the company to protect its infrastructure investment, customer base, and competitive edge, as well as its ability to generate (and collect) revenue. I mean, really, at what point does losing $400 million per year become a problem to the business?

Andrew Hay is senior analyst with 451 Research's Enterprise Security Practice (ESP) and is an author of three network security books. Follow him on Twitter: @andrewsmhay

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0972
Published: 2014-08-01
The kgsl graphics driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not properly prevent write access to IOMMU context registers, which allows local users to select a custom page table, and consequently write ...

CVE-2014-2627
Published: 2014-08-01
Unspecified vulnerability in HP NonStop NetBatch G06.14 through G06.32.01, H06 through H06.28, and J06 through J06.17.01 allows remote authenticated users to gain privileges for NetBatch job execution via unknown vectors.

CVE-2014-3009
Published: 2014-08-01
The GDS component in IBM InfoSphere Master Data Management - Collaborative Edition 10.0 through 11.0 and InfoSphere Master Data Management Server for Product Information Management 9.0 and 9.1 does not properly handle FRAME elements, which makes it easier for remote authenticated users to conduct ph...

CVE-2014-3302
Published: 2014-08-01
user.php in Cisco WebEx Meetings Server 1.5(.1.131) and earlier does not properly implement the token timer for authenticated encryption, which allows remote attackers to obtain sensitive information via a crafted URL, aka Bug ID CSCuj81708.

CVE-2014-3534
Published: 2014-08-01
arch/s390/kernel/ptrace.c in the Linux kernel before 3.15.8 on the s390 platform does not properly restrict address-space control operations in PTRACE_POKEUSR_AREA requests, which allows local users to obtain read and write access to kernel memory locations, and consequently gain privileges, via a c...

Best of the Web
Dark Reading Radio