Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Power Industry Gets Security Standard

As the continent sweats, North America's electrical utilities will begin implementing new protective measures

Move over HIPAA, SOX, and PCI. There's a new security compliance standard in town.

After nearly three years of consideration, the North American Electric Reliability Council (NERC) has finalized its Critical Infrastructure Protection (CIP) specifications, which require all major utilities on the continent to meet a set of security standards or face financial penalties. The first compliance deadlines are set for the second quarter of 2009.

The new requirements, officially known as CIP 002-009, were completed in May and quietly enacted last month. They will apply to any company, large or small, that is part of the continent's bulk electric power grid. Distributors will not be held to the new standard, but suppliers and contractors to the major utilities may have to comply with some aspects.

More rigorous regulations have been in demand for some time, particularly in light of terrorist attacks around the globe. In 2005, The Washington Post interviewed Patrick Wood III, the chairman of the Federal Energy Regulatory Commission, after officials at the Energy Department's Idaho National Laboratory showed him a skilled hacker could cause serious problems. "I wished I'd had a diaper on," Wood told the newspaper.

This will be the first time that American power companies have been subject to mandatory security standards with penalties, according to Lynn Costantini, CIO at NERC and a chief contributor to the specifications. A previous guideline, called Cyber Security Standard 1200, was self-regulated and only applied to the largest power generators.

"Those guidelines were very basic, really more on the order of best practices," says Costantini. "We've significantly expanded the scope of the requirements." Under CIP, NERC will conduct an audit of each utility every three years, and an independent contractor will audit NERC's audits, she says.

The CIP standards do not specify products, but they do require that utilities deploy certain categories of security technology, such as antivirus software, patch management tools, and intrusion detection systems. Power companies will be required to conduct a vulnerability assessment at least once a year.

The first standard of the suite, CIP-002, requires power companies to conduct a risk assessment of their security environments and identify all of the systems and devices that need to be protected. CIP-003 requires the utilities to build a security governance program, documenting ownership of assets, authority to make changes, and policies for maintaining security. CIP-004 defines security training requirements.

While CIP-006 defines requirements for physical and building security, IT people will probably spend most of their time working on CIP-005, which defines electronic perimeter defenses, and CIP-007, which outlines requirements for protecting servers and implementing tools such as patch management and IDS. The standards don't specify the functionality of those devices, but they do require power companies to prove those systems are in place and operational.

CIP-008 and CIP-009 outline requirements for reporting, responding, and recovering in the event of a security incident.

NERC has not yet set its guidelines for auditing, so it's not clear how stringent those audits will be, Costantini says. The financial penalties also have not yet been defined, but there will be four levels of violation. "A Level 1 violation would be considered less serious, and the penalty would be smaller," she says. "A Level 4 violation would be considered very serious." The group hasn't decided whether to levy graduated penalties based on the size of the utility.

"The goal of the whole project is to keep the power on," Costantini says. "We think this will help. We have some utilities that are very ready now, and others that still have a long way to go. But they've all known about the coming requirements for some time, and from what I've seen, they're all committed to making the deadlines."

— Tim Wilson, Site Editor, Dark Reading

  • North American Electric Reliability Council

    Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    Sodinokibi Ransomware: Where Attackers' Money Goes
    Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
    Data Privacy Protections for the Most Vulnerable -- Children
    Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
    State of SMB Insecurity by the Numbers
    Ericka Chickowski, Contributing Writer,  10/17/2019
    Register for Dark Reading Newsletters
    White Papers
    Current Issue
    7 Threats & Disruptive Forces Changing the Face of Cybersecurity
    This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
    Flash Poll
    2019 Online Malware and Threats
    2019 Online Malware and Threats
    As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    PUBLISHED: 2019-10-22
    A stack-based buffer overflow in the processPrivilage() function in IOS/process-general.c in nipper-ng 0.11.10 allows remote attackers (serving firewall configuration files) to achieve Remote Code Execution or Denial Of Service via a crafted file.
    PUBLISHED: 2019-10-21
    Authenticated SQL Injection in interface/forms/eye_mag/js/eye_base.php in OpenEMR through 5.0.2 allows a user to extract arbitrary data from the openemr database via a non-parameterized INSERT INTO statement, as demonstrated by the providerID parameter.
    PUBLISHED: 2019-10-21
    The unoconv package before 0.9 mishandles untrusted pathnames, leading to SSRF and local file inclusion.
    PUBLISHED: 2019-10-21
    In libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an integer overflow in a bounds check, enabling an attacker to specify an arbitrary (out-of-bounds) offset for a subsequent memory read. A crafted SSH server may be able to disclose sensitive information or cause a ...
    PUBLISHED: 2019-10-21
    In FusionPBX up to 4.5.7, the file app\fifo_list\fifo_interactive.php uses an unsanitized "c" variable coming from the URL, which is reflected in HTML, leading to XSS.