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

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
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2391
Published: 2014-04-24
The password recovery service in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 makes an improper decision about the sensitivity of a string representing a previously used but currently invalid password, which allows remote attackers to obtain potent...

CVE-2014-2392
Published: 2014-04-24
The E-Mail autoconfiguration feature in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 places a password in a GET request, which allows remote attackers to obtain sensitive information by reading (1) web-server access logs, (2) web-server Referer log...

CVE-2014-2393
Published: 2014-04-24
Cross-site scripting (XSS) vulnerability in Open-Xchange AppSuite 7.4.1 before 7.4.1-rev11 and 7.4.2 before 7.4.2-rev13 allows remote attackers to inject arbitrary web script or HTML via a Drive filename that is not properly handled during use of the composer to add an e-mail attachment.

CVE-2011-5279
Published: 2014-04-23
CRLF injection vulnerability in the CGI implementation in Microsoft Internet Information Services (IIS) 4.x and 5.x on Windows NT and Windows 2000 allows remote attackers to modify arbitrary uppercase environment variables via a \n (newline) character in an HTTP header.

CVE-2012-0360
Published: 2014-04-23
Memory leak in Cisco IOS before 15.1(1)SY, when IKEv2 debugging is enabled, allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCtn22376.

Best of the Web