Urgent.News

What's breaking now, across thousands of outlets.

Tech

CIP-007 system security management: what generator owners need to know

CIP-007 is the standard most people picture when they think of NERC CIP day to day: closing ports, tracking patches, keeping malware protection current, reviewing logs and managing passwords. It is also the standard that produces a steady flow of evidence, because most of its parts run on a clock. For solar, wind and battery storage owners, there is an earlier question to answer first: does…

CIP-007 is the standard most associate with NERC CIP day-to-day operations, including closing ports, tracking patches, maintaining malware protection, reviewing logs, and managing passwords. This standard generates a consistent flow of evidence due to its clock-based approach. However, for solar, wind, and battery storage owners, the first question to ask is whether CIP-007 applies to their operations.

According to CIP-007-6, the standard applies to Generator Owners and Operators, but section 4.2.3.5 exempts Responsible Entities with no BES Cyber Systems categorized as high or medium impact according to CIP-002-5.1 identification and categorization processes. In simpler terms, if all BES Cyber Systems are low impact, CIP-007 does not apply, and cyber security obligations fall under CIP-003.

If there is at least one medium or high impact BES Cyber System, CIP-007 applies to that system and its associated Electronic Access Control or Monitoring Systems, Physical Access Control Systems, and Protected Cyber Assets. The applicability depends on the site's CIP-002 categorization.

For medium impact systems, CIP-007-6 outlines various requirements, including enabling only necessary logical ports if the system has external routable connectivity (ERC), protecting unnecessary physical ports at control centers, implementing patch management, preventing malicious code, logging security events, generating alerts, maintaining logs for 90 days, and reviewing logs every 15 days.

For high impact systems, additional requirements include enforcing authentication at control centers or with ERC, managing generic accounts, default passwords, password rules, limiting or alerting on failed logins. The standard provides flexibility for devices without port disabling options, focusing on device-level requirements.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

More from Monday 16 November →