11:48 PM
Dark Reading
Dark Reading
Quick Hits
Connect Directly

Achieving Compliance In The Smart Grid

In the energy business, strict compliance mandates could be all that stands between business as usual and a catastrophic, long-term power outage

[Excerpted from "Achieving Compliance In The Smart Grid," a new report published this week in Dark Reading's Compliance Tech Center.]

Every industry poses a unique set of challenges for security pros, but of all the industry verticals that we interact with on a daily basis, can you think of one more important or vital to our national security interests than the energy sector? An abrupt, large-scale power outage would be devastating, causing significant loss of life and billions of dollars in damages. That's why compliance in this arena is so important.

While the Bulk Electric System (BES) is particularly vulnerable, any utility that’s controlled by IP-connected SCADA systems is potentially vulnerable to manipulation or attack with catastrophic effects. The Critical Infrastructure Protection (CIP) reliability standards define the cybersecurity-related aspects of how BES providers must protect their systems to maintain the reliability of the grid.

As compliance mandates go, CIP is one of the most stringent and labor-intensive you will come up against. With that said, CIP is also a treasure trove of best practices even if you work outside of the energy space. CIP is split into nine core sections, each including a mandate. The sections that specifically pertain to smart grid cybersecurity are CIP-002 through CIP-009.

For a deeper look at all of the security-related CIP requirements -- and best practices for complying with each of them -- download the free report on NERC/CIP compliance.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2014-07-11
Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.