Perimeter
4/9/2012
11:01 AM
Commentary
Commentary
Commentary
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
Cartoon
Current Issue
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-2184
Published: 2015-03-27
Movable Type before 5.2.6 does not properly use the Storable::thaw function, which allows remote attackers to execute arbitrary code via the comment_state parameter.

CVE-2014-3619
Published: 2015-03-27
The __socket_proto_state_machine function in GlusterFS 3.5 allows remote attackers to cause a denial of service (infinite loop) via a "00000000" fragment header.

CVE-2014-8121
Published: 2015-03-27
DB_LOOKUP in nss_files/files-XXX.c in the Name Service Switch (NSS) in GNU C Library (aka glibc or libc6) 2.21 and earlier does not properly check if a file is open, which allows remote attackers to cause a denial of service (infinite loop) by performing a look-up while the database is iterated over...

CVE-2014-9712
Published: 2015-03-27
Websense TRITON V-Series appliances before 7.8.3 Hotfix 03 and 7.8.4 before Hotfix 01 allows remote administrators to read arbitrary files and obtain passwords via a crafted path.

CVE-2015-0658
Published: 2015-03-27
The DHCP implementation in the PowerOn Auto Provisioning (POAP) feature in Cisco NX-OS does not properly restrict the initialization process, which allows remote attackers to execute arbitrary commands as root by sending crafted response packets on the local network, aka Bug ID CSCur14589.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.