Two operators at a control-room desk with a row of monitors, a laptop and keyboards

OT/ICS security

NERC CIP-011: information protection for BES cyber systems, explained

Last updated:

NERC CIP-011-3, "Cyber Security — Information Protection," is the mandatory, FERC-approved Reliability Standard that governs how utilities and grid operators identify and protect BES Cyber System Information (BCSI), and how they sanitize Cyber Assets before reuse or disposal. Per its own Purpose clause it exists "to prevent unauthorized access to BES Cyber System Information (BCSI) by specifying information protection requirements in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the Bulk Electric System (BES)." CIP-011-3 was adopted by the NERC Board of Trustees on 12 August 2021 and approved by FERC on 7 December 2021 under Docket No. RD21-6-000; it became effective and enforceable on 1 January 2024, the same day as CIP-004-7, per NERC's own 2023 CMEP and ORCP Annual Report. It remains the enforceable version today, even though a virtualization-focused successor, CIP-011-4.1, is already FERC-approved for a 2028 compliance date (see below).

Key takeaways

  • Both requirements in the standard are built around a single defined term: BES Cyber System Information (BCSI).
  • Part 1.1's scope and Part 1.2's scope both cover High and Medium Impact BES Cyber Systems and their associated EACMS and PACS.
  • Part 2.2 (Disposal) — "Prior to the disposal of applicable Cyber Assets that contain BCSI," the entity must either prevent unauthorized retrieval of BCSI or destroy the data storage media outright.
  • Device makers handle BCSI more often than they think: support cases, commissioning files and returned hardware.

Who must comply, and what does BCSI actually mean?

CIP-011 applies to High and Medium Impact BES Cyber Systems, categorized under the separate CIP-002 process, and — depending on the requirement — their associated Electronic Access Control or Monitoring Systems (EACMS), Physical Access Control Systems (PACS), and Protected Cyber Assets (PCA).

Both requirements in the standard are built around a single defined term: BES Cyber System Information (BCSI). Per NERC's own Glossary, BCSI is "information about the BES Cyber System that could be used to gain unauthorized access or pose a security threat to the BES Cyber System." The definition is deliberately narrower than "anything related to a BES Cyber System" — it excludes "individual pieces of information that by themselves do not pose a threat or could not be used to allow unauthorized access to BES Cyber Systems, such as, but not limited to, device names, individual IP addresses without context, ESP names, or policy statements." What the definition does include: "security procedures or security information about BES Cyber Systems, Physical Access Control Systems, and Electronic Access Control or Monitoring Systems that is not publicly available and could be used to allow unauthorized access or unauthorized distribution; collections of network addresses; and network topology of the BES Cyber System." Getting this scoping right matters in practice — a CIP-011 program that over-classifies BCSI (treating every IP address or device name as protected) creates unnecessary handling overhead, while under-classifying it (missing network topology diagrams or access procedures) leaves genuine gaps.

What does R1's information protection program require?

Requirement R1 (Medium VRF, Operations Planning time horizon) requires "one or more documented information protection program(s)" covering two parts:

Part Requirement Example measures
1.1 "Method(s) to identify BCSI" Documented identification methods; labels or classification markings; training materials enabling personnel to recognize BCSI; designated BCSI storage locations
1.2 "Method(s) to protect and securely handle BCSI to mitigate risks of compromising confidentiality" Documented procedures for storage, transit and use (on-premise); encryption, hashing, tokenization or electronic key management (off-premise electronic BCSI); physical lock/badge management or biometrics (off-premise physical BCSI); vendor risk assessments or business agreements (administrative methods)

Part 1.1's scope and Part 1.2's scope both cover High and Medium Impact BES Cyber Systems and their associated EACMS and PACS. Notably, CIP-011-3 does not mandate a single specific protection technology — the standard's own Measures language lists encryption, hashing, tokenization, physical controls and administrative controls as equally acceptable examples, leaving the entity to select methods appropriate to how and where it stores BCSI.

Can BCSI be stored in the cloud, and who must control the keys?

Yes. CIP-011-3 and CIP-004-7 were revised so that off-premise storage, including cloud services, has a defined compliance path, and NERC's ERO Enterprise-endorsed Implementation Guidance on cloud solutions for BCSI (21 June 2023) says both standards "were modified to clarify and provide a secure path towards utilization of modern third-party off-premises electronic data storage and analysis systems (e.g., cloud services)." The guidance orders the work as identify BCSI (Part 1.1), protect its confidentiality (Part 1.2), then manage provisioned access under CIP-004-7 R6. It is also clear that the shared-responsibility split does not "suggest or imply transference of compliance responsibilities from the Responsible Entity to a third-party."

The pivot is CIP-004-7 R6's definition: "to be considered access to BCSI in the context of this requirement, an individual has both the ability to obtain and use BCSI." A cloud administrator who can obtain encrypted files but cannot decrypt them does not have both. That is why key custody drives the evidence. The guidance lists four key models with the evidence each needs:

Key model (Implementation Guidance, Part 1.2) Evidence the guidance suggests
Vendor-owned and managed keys Detection or notification controls so keys are not used without the entity's authorization
Customer-owned keys in the cloud vault Detection or notification controls on access to the key vault
Customer-owned keys on premises or in a separate cloud Service contract and diagram showing the keys are not stored with the BCSI
Customer-owned keys in a cloud HSM Service contract and the provider's key-management procedure

Administrative evidence can sit alongside: vendor service agreements, risk assessments, and third-party reports "such as FedRAMP Audit reports, SOC 2 Type 2 reports or similar." The guidance also asks entities to account for paths such as eDiscovery tools, cloud administrator roles and break-glass accounts. NERC's Primer for Cloud and BCSI Protection (RSTC, 10 December 2025) adds that with entity-managed keys "a CSP would not have access to the keys and therefore could not decrypt or read the information", and that, at end of life, "simply encrypting the BCSI and destroying the keys, also known as cryptoshredding, is not seen as a best practice"; it points to deletion evidence "such as that described in NIST 800-88".

Once access is provisioned, CIP-004-7 R6 sets three clocks for High Impact systems and Medium Impact systems with External Routable Connectivity: authorize "based on need" before provisioning (Part 6.1), verify at least once every 15 calendar months that each person still has an authorization record and a need (Part 6.2), and on termination remove the ability to use provisioned access "by the end of the next calendar day" (Part 6.3).

What does R2 require for Cyber Asset reuse and disposal?

Requirement R2 (Lower VRF, Operations Planning time horizon) requires documented processes for two distinct triggers, and additionally scopes in Protected Cyber Assets (PCA) alongside BES Cyber Systems, EACMS and PACS:

  • Part 2.1 (Reuse) — "Prior to the release for reuse of applicable Cyber Assets that contain BCSI" (except reuse within other in-scope systems), the entity must "take action to prevent the unauthorized retrieval of BCSI from the Cyber Asset data storage media." Acceptable evidence includes records of sanitization actions (clearing, purging, destroying) or records of alternative controls such as encryption or retention within a Physical Security Perimeter.
  • Part 2.2 (Disposal) — "Prior to the disposal of applicable Cyber Assets that contain BCSI," the entity must either prevent unauthorized retrieval of BCSI or destroy the data storage media outright.

Neither Part specifies a numeric sanitization timeline (no "within X days" window) — the requirement is purely sequential: the protective action must happen before reuse or disposal, with the specific method left to the entity's documented process. Entities building a decommissioning checklist should not invent a compliance deadline here; the standard's own text only requires the ordering, not a countdown.

Which device and firmware files are BCSI?

Device makers handle BCSI more often than they think: support cases, commissioning files and returned hardware. The standard does not list file types, so the test is the Glossary definition quoted above. Reading it against common vendor-side files:

File a vendor may receive or hold How the definition reads on it
A single device name or an IP address in a support ticket Excluded: "individual pieces of information" such as "device names, individual IP addresses without context"
Configuration export with interface addresses, firewall rules and accounts Likely BCSI: "collections of network addresses" and security information "not publicly available"
Network diagram or a site's packet capture Likely BCSI: "network topology" and collections of addresses
Published firmware image and release notes Generally not BCSI: public product information, not information about the entity's system
A returned relay or RTU with site settings in flash Contains BCSI until sanitized; the utility's R2 process applies before it leaves

The classification is the utility's call under Part 1.1, but a vendor that receives these files becomes part of the utility's Part 1.2 evidence, usually through the "business agreements" and "vendor service risk assessments" the measures name. Contract terms of that kind also sit in CIP-013 supply chain risk management.

What does a relay RMA look like under CIP-011? (worked example)

Synthetic example, for illustration only: the utility, vendor and device are invented. A transmission utility returns a failed protective relay from a Medium Impact substation to the manufacturer:

  1. Identify:the asset record shows the relay holds its settings file and an event log with network addresses, so it contains BCSI under the entity's Part 1.1 method.
  2. Decide reuse or disposal:the relay leaves the Applicable Systems for repair, so R2 applies before release.
  3. Prevent retrieval:the technician runs the vendor's documented settings-erase procedure, or removes and keeps the storage card, following the utility's media method (see NIST SP 800-88 media sanitization).
  4. Record:the work order logs the asset ID, method, date and technician; that record is the R2 evidence and is kept for three calendar years.
  5. Ship:only then does the relay go to the vendor.

For the vendor, the useful product feature is a documented, verifiable erase of all site data, including logs, so step 3 does not depend on removing hardware.

How long must CIP-011 evidence be kept?

Per CIP-011-3's Compliance section, "the applicable entity shall retain evidence of each requirement in this standard for three calendar years" — the same retention period used across the CIP suite (see CIP-004 and CIP-013). Where non-compliance is found, evidence related to it must be kept "until mitigation is complete and approved or for the time specified above, whichever is longer."

What changes in CIP-011-4.1, and when?

CIP-011-3 is the standard enforced today, but a successor is already locked in. On 19 March 2026 the Federal Energy Regulatory Commission issued Order No. 919 (Docket No. RM24-8-000), approving 11 modified CIP Reliability Standards together as part of NERC's Project 2016-02 virtualization package — published in the Federal Register on 24 March 2026 at 91 FR 13957, naming "CIP-011-4.1 (Cyber Security—Information Protection)" alongside CIP-002-7, CIP-003-10, CIP-004-8, CIP-005-8, CIP-006-7.1, CIP-007-7.1, CIP-008-7.1, CIP-009-7.1, CIP-010-5 and CIP-013-3. The order itself states "this final action is effective May 26, 2026." One naming note worth flagging: NERC's May 2025 supplemental petition referred to an interim errata draft as "CIP-011-4," but the version FERC actually approved — and the one to cite going forward — is CIP-011-4.1.

Per NERC's implementation plan, the revised standards take effect on the later of 1 April 2026 or "the first day of the first calendar quarter that is 24 months after" the order's effective date. NERC's own July 2026 Standards, Compliance, and Enforcement Bulletin confirms the resulting literal date, listing "CIP-011-4.1 – Cyber Security — Information Protection" among standards for which "the revised standards will become effective July 1, 2028." The package's substantive driver is the same across all 11 standards: four new NERC Glossary terms (Cyber System, Management Interface, Shared Cyber Infrastructure, Virtual Cyber Asset) and revisions to 18 existing defined terms, needed so the CIP suite applies cleanly to virtualized infrastructure. For CIP-011 specifically, NERC's proposed definition change extends BCSI to also cover information about "Shared Cyber Infrastructure". The CIP-011-4.1 text makes two further changes. "SCI supporting an Applicable System" is added to the Applicable Systems of Parts 1.1, 1.2 and 2.1. And R2 becomes a single Part 2.1: "Methods to prevent the unauthorized retrieval of BCSI from Applicable Systems containing BCSI, prior to their disposal or reuse", with destruction listed among the evidence examples rather than as a separate disposal part. The R1 requirement text and its measures are otherwise unchanged.

What are the common pitfalls?

  • Treating the cloud provider's certification as the whole answer. SOC 2 or FedRAMP reports are administrative evidence; the entity still documents key custody and access paths.
  • Forgetting break-glass and eDiscovery access, which the Implementation Guidance names as ways personnel can obtain BCSI.
  • Relying on cryptoshredding for cloud deletion, which NERC's 2025 primer says is not seen as a best practice.
  • Shipping RMA hardware before the R2 record exists. The action has to precede release.
  • Sending full configuration exports to vendor support when a single log line would do.

What is a workable starting point?

  1. Scope BCSI precisely before building a protection programThe Glossary definition explicitly excludes isolated data points (a bare IP address, a device name) — over-classifying everything as BCSI creates unnecessary handling burden, while missing network topology diagrams or access procedures leaves a genuine R1 gap.
  2. Treat R1's two parts as identify-then-protect, in that orderPart 1.1 (identification methods) has to exist before Part 1.2 (protection methods) can be meaningfully applied — a protection procedure is only as good as the identification step that tells personnel what it covers.
  3. Don't invent a sanitization deadline for R2The standard requires action prior to reuse or disposal, not within a specific number of days — document the sequencing, not a countdown that CIP-011-3's text doesn't require.
  4. Document PCA scope separately for R2R2 pulls in Protected Cyber Assets, which R1 does not — a reuse/disposal process built only around BES Cyber Systems, EACMS and PACS will miss PCA-hosted BCSI.
  5. Start tracking CIP-011-4.1's Shared Cyber Infrastructure scoping nowWith a FERC-approved 1 July 2028 compliance date already set, entities planning virtualized storage or access infrastructure for BCSI should evaluate the Shared Cyber Infrastructure definition change ahead of the mandatory date rather than retrofitting afterward.

SoftWSP does not classify, store or sanitize BCSI for an entity. OT Snapshot reads a Zeek analysis of a wired capture, and device firmware security extracts an SBOM from an uploaded firmware image as CycloneDX 1.6 JSON and matches it against NVD, CISA KEV, FIRST EPSS and CISA's CSAF ICS advisories, with an engineer reviewing each AI-drafted, cited report. A capture or configuration export from a High or Medium Impact site can itself be BCSI, so it goes through the entity's own Part 1.1 and 1.2 methods, and CIP-004 R6 access decisions, before it is shared with any outside analysis service. The change records for that firmware sit under CIP-010.

This guide quotes NERC's own published text of CIP-011-3 and the Federal Register text of FERC Order No. 919; it is not a substitute for the full standard, NERC's Implementation Plan, or compliance/legal advice. CIP-011-3 remains the enforceable standard as of this guide's publication — CIP-011-4.1 is approved and becomes mandatory at a later effective date.

Put this guide to work

Frequently asked questions

What is NERC CIP-011-3, and who must comply?

CIP-011, "Cyber Security — Information Protection," is the mandatory, FERC-approved NERC Reliability Standard governing how utilities and grid operators identify and protect BES Cyber System Information (BCSI) and sanitize Cyber Assets before reuse or disposal. Per its own Purpose clause it exists "to prevent unauthorized access to BES Cyber System Information (BCSI) by specifying information protection requirements in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the Bulk Electric System (BES)." The currently enforceable version, CIP-011-3, was adopted by the NERC Board of Trustees on 12 August 2021 and approved by FERC on 7 December 2021 under Docket No. RD21-6-000; per NERC's own 2023 CMEP and ORCP Annual Report, "On January 1, 2024, CIP-004-7 and CIP-011-3 became effective and enforceable. These Reliability Standards were updated to clarify the CIP requirements related to both managing access and securing BES Cyber System Information." It applies to High and Medium Impact BES Cyber Systems, as categorized under the separate [CIP-002](/guides/nerc-cip-002-bes-cyber-system-categorization/) process, and their associated Electronic Access Control or Monitoring Systems (EACMS) and Physical Access Control Systems (PACS).

What counts as BES Cyber System Information (BCSI)?

Per NERC's own Glossary of Terms (as reflected in NERC's Project 2016-02 CIP definitions comparison document), BES Cyber System Information is "information about the BES Cyber System that could be used to gain unauthorized access or pose a security threat to the BES Cyber System." The definition explicitly excludes low-value fragments: "BES Cyber System Information does not include individual pieces of information that by themselves do not pose a threat or could not be used to allow unauthorized access to BES Cyber Systems, such as, but not limited to, device names, individual IP addresses without context, ESP names, or policy statements." Examples the definition does include: "security procedures or security information about BES Cyber Systems, Physical Access Control Systems, and Electronic Access Control or Monitoring Systems that is not publicly available and could be used to allow unauthorized access or unauthorized distribution; collections of network addresses; and network topology of the BES Cyber System." The scoping matters directly for CIP-011 compliance, since both of the standard's requirements are built entirely around identifying and protecting this one defined category of information.

What do Requirement R1 (Information Protection Program) and R2 (Cyber Asset Reuse and Disposal) actually require?

R1 (Medium VRF, Operations Planning time horizon) requires "one or more documented information protection program(s)" with two parts: Part 1.1 requires "method(s) to identify BCSI" — acceptable measures per the standard include documented identification methods, labeling/classification schemes, training materials, or designated storage locations; Part 1.2 requires "method(s) to protect and securely handle BCSI to mitigate risks of compromising confidentiality," covering storage, transit and use, with measures ranging from documented handling procedures to technical controls like encryption, hashing, tokenization or physical access controls for off-premise BCSI. R2 (Lower VRF, Operations Planning time horizon) requires documented processes for two triggers: Part 2.1 (reuse) requires that "prior to the release for reuse of applicable Cyber Assets that contain BCSI," the entity "take action to prevent the unauthorized retrieval of BCSI from the Cyber Asset data storage media"; Part 2.2 (disposal) requires the same prevention of unauthorized retrieval, or destruction of the data storage media, "prior to the disposal of applicable Cyber Assets that contain BCSI." Neither Part specifies a numeric sanitization timeline — the standard requires the action happen *before* reuse or disposal, and leaves the specific method (clearing, purging, destroying, or technical/physical controls that prevent retrieval) to the entity's own documented process. R2's scope additionally includes Protected Cyber Assets (PCA), which R1's scope does not.

Is CIP-011-3 already being replaced, and by when do entities need to comply?

Yes — a successor, CIP-011-4.1, is already FERC-approved, though CIP-011-3 remains the enforceable standard today. On 19 March 2026 the Federal Energy Regulatory Commission issued Order No. 919 (Docket No. RM24-8-000), published in the Federal Register on 24 March 2026 at 91 FR 13957 (FR document 2026-05716), approving 11 modified CIP Reliability Standards as part of NERC's Project 2016-02 virtualization package — explicitly naming "CIP-011-4.1 (Cyber Security—Information Protection)" alongside CIP-002-7, CIP-003-10, CIP-004-8, CIP-005-8, CIP-006-7.1, CIP-007-7.1, CIP-008-7.1, CIP-009-7.1, CIP-010-5 and CIP-013-3. The order's own text states "this final action is effective May 26, 2026," and NERC's implementation plan computes the compliance date as "the later of April 1, 2026, or the first day of the first calendar quarter that is 24 months after" that effective date. NERC's own July 2026 Standards, Compliance, and Enforcement Bulletin confirms the resulting literal date: "CIP-011-4.1 – Cyber Security — Information Protection" is listed among standards for which "the revised standards will become effective July 1, 2028." Note that an earlier errata-corrected draft was labeled "CIP-011-4" in NERC's May 2025 supplemental petition — the final FERC-approved version is CIP-011-4.1, and entities should cite that exact version number going forward.

Sources

  1. NERC: CIP-011-3 — Cyber Security – Information Protection (currently effective standard, full text: Purpose, Applicability, Requirements R1-R2 with Tables, Compliance, Evidence Retention, Violation Severity Levels)
  2. NERC: 2023 CMEP and ORCP Annual Report (14 Feb 2024) — confirms "On January 1, 2024, CIP-004-7 and CIP-011-3 became effective and enforceable"
  3. NERC: CIP Definitions — Project 2016-02 Modifications to CIP Standards (current vs. proposed Glossary terms, incl. BES Cyber System Information)
  4. Federal Register: Order No. 919; Virtualization Reliability Standards, 91 FR 13957 (FERC, Docket No. RM24-8-000, issued 2026-03-19, published 2026-03-24, effective 2026-05-26) — lists CIP-011-4.1 among the 11 approved standards, with NERC's implementation plan formula
  5. NERC: Standards, Compliance, and Enforcement Bulletin, 6-12 July 2026 — confirms CIP-011-4.1 becomes effective 1 July 2028
  6. NERC: CIP-011-4.1 — Cyber Security — Information Protection (FERC-approved 19 March 2026; Applicable Systems incl. Shared Cyber Infrastructure, merged R2 Part 2.1)
  7. NERC: CIP-004-7 — Cyber Security – Personnel & Training (R6, Access Management for BCSI)
  8. NERC RSTC Implementation Guidance: Usage of Cloud Solutions for BES Cyber System Information (BCSI), CIP-004-7 R6 and CIP-011-3 R1 (21 June 2023)
  9. NERC Security Guideline for Electric Sector: Primer for Cloud and BCSI Protection (approved by the RSTC 10 December 2025)
Was this guide helpful?

In this cluster

NERC CIP-011: information protection for BES cyber systems, explained