
us-nerc-cip
NERC CIP reference plugin with scope, evidence checklist, and SCF-backed gap assessment.
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install us-nerc-cip@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 1
NERC CIP Expert
Reference-depth expertise for NERC Critical Infrastructure Protection (CIP)
Reliability Standards, represented in SCF as usa-federal-nerc-cip-2024. This
plugin bundles the SCF crosswalk (122 SCF controls to 204 framework controls)
with NERC CIP-specific assessment context.
Framework Identity
- SCF framework ID:
usa-federal-nerc-cip-2024 - Region: Americas
- Country: US / North American bulk power system jurisdictions
- Regulators: North American Electric Reliability Corporation (NERC), Regional Entities, and Federal Energy Regulatory Commission (FERC) in the US
- Common shorthand: NERC CIP
- Current assessment baseline: NERC CIP Reliability Standards represented in the 2024 SCF crosswalk
Framework In Plain Language
NERC CIP is the cybersecurity and physical security standards family for Bulk Electric System (BES) reliability. It focuses on identifying BES Cyber Systems, categorizing impact, protecting electronic and physical perimeters, managing personnel risk, hardening systems, responding to incidents, recovering from events, protecting information, and managing supply chain risk. For GRC work, the assessor needs to see repeatable evidence tied to registered functions, assets, impact ratings, and Reliability Standard requirements.
Territorial Scope And Applicability
NERC Reliability Standards apply across interconnected North American bulk power system jurisdictions through NERC, Regional Entities, and applicable regulatory authorities. Scope analysis starts with registered entity functions such as BA, DP, GO, GOP, RC, TO, TOP, and TP, then maps Facilities, assets, BES Cyber Systems, Electronic Security Perimeters, Physical Security Perimeters, and associated cyber assets. Do not treat NERC CIP as a generic IT security framework; applicability depends on BES reliability functions and asset impact categorization.
Mandatory Artifacts
Evidence usually centers on CIP-002 BES Cyber System categorization records, asset inventories, impact rating rationale, security management controls, personnel training and risk assessment records, access authorization lists, electronic access control evidence, physical access control evidence, system hardening baselines, vulnerability assessments, patch management records, incident response plans and exercises, recovery plans and tests, protected information handling procedures, and supply chain risk management plans.
Cadence And Timelines
Cadence varies by CIP standard and requirement. Assessors should preserve the entity's compliance calendar, recurring evidence, dated approvals, test results, change records, and exception handling. Incident response, recovery testing, access reviews, vulnerability assessments, patch evaluation, configuration change management, and training records need dates and scope that align with the specific requirement being assessed.
Regulator And Enforcement
NERC develops and enforces Reliability Standards with Regional Entities; FERC approves and enforces standards in the United States. Non-compliance can lead to findings, mitigation plans, settlement activity, penalties, and enhanced oversight. Assessment output should separate control evidence and likely gaps from legal conclusions about violation risk or penalty exposure.
Interaction With Other Frameworks
NERC CIP overlaps with NIST CSF, NIST 800-53, ISO 27001, CIS Controls, and utility-specific operational technology security programs. Use the SCF crosswalk for control mechanics, but keep NERC CIP reporting focused on BES Cyber System categorization, registered functions, impact ratings, audit-ready evidence, and Reliability Standard requirement structure.
Common Misinterpretations
- "NERC CIP covers every utility IT system." It focuses on BES reliability assets and cyber systems; enterprise IT may be supporting evidence but is not automatically a BES Cyber System.
- "Low impact means low effort." Low impact assets still require defined programs, security management controls, access controls, incident response, and other requirement-specific evidence.
- "A security tool report is enough." CIP evidence needs requirement-level traceability, responsible entity context, dates, approvals, and scope.
- "Cloud and vendors are outside CIP." Supply chain and vendor access can be in scope when they affect BES Cyber Systems or associated protected information.
Command Routing
/us-nerc-cip:scope- determine applicability/us-nerc-cip:assess- run a gap assessment/us-nerc-cip:evidence-checklist- enumerate evidence requirements
All three delegate to /grc-engineer:gap-assessment with SCF framework ID
usa-federal-nerc-cip-2024 for the control-by-control mechanics, and wrap the
results in NERC CIP-specific terminology.
Levelling Up To Full
Full-depth plugins add framework-specific workflow commands tied to the audit ritual. Candidates for this framework:
/us-nerc-cip:bes-cyber-system-scope- build or review CIP-002 categorization and impact-rating evidence./us-nerc-cip:access-review-pack- assemble CIP access authorization, revocation, and review evidence./us-nerc-cip:vulnerability-and-patch-review- assess vulnerability assessment, patch evaluation, mitigation, and exception evidence./us-nerc-cip:incident-exercise-review- review incident response plan, testing, lessons learned, and reportability evidence.
References
Commands 3
NERC CIP Assessment
Runs a compliance gap assessment against NERC Critical Infrastructure Protection
(CIP) Reliability Standards by delegating to /grc-engineer:gap-assessment
with the framework's SCF identifier, then overlays NERC CIP-specific context and
evidence requirements.
Usage
/us-nerc-cip:assess [--scope=<scope>] [--sources=<connector-list>]
Arguments
--scope=<scope>(optional) - narrow the assessment to a NERC CIP workstream such asbes-cyber-system-categorization,electronic-security-perimeter,physical-security,personnel-training,system-security-management,incident-response,recovery-planning, orsupply-chain-risk.--sources=<connector-list>(optional) - comma-separated connector plugins.
What the assessment produces
- Compliance score - overall NERC CIP readiness percentage, weighted by mapped SCF controls.
- Applicable-requirements summary - which NERC CIP expectations apply to the entity and asset population.
- Control-by-control gap - all 204 mapped controls, with pass/fail/inconclusive status from connector findings.
- Evidence gaps - controls where no evidence source is configured.
- Remediation roadmap - prioritized by severity and effort.
Delegation
Under the hood:
/grc-engineer:gap-assessment "usa-federal-nerc-cip-2024" [--sources=<connector-list>]
The SCF crosswalk expands 122 SCF controls into the 204 NERC CIP mapped controls.
Framework-specific notes
- Start with
/us-nerc-cip:scopeto identify registered functions, Facilities, BES Cyber Systems, impact ratings, Electronic Security Perimeters, and Physical Security Perimeters. - Common assessment scopes are CIP-002 categorization, access authorization, electronic access controls, physical access controls, system hardening, vulnerability management, incident response, recovery planning, and supply chain risk.
- For NIST or ISO programs, verify that generic control evidence is traceable to NERC CIP requirement structure, responsible entity context, dated approvals, and asset scope.
- Treat vendor access and supply chain records as in scope when they affect BES Cyber Systems or associated protected information.
NERC CIP Evidence Checklist
Baseline evidence checklist for a NERC CIP assessment. The SCF crosswalk maps 122 SCF controls to the 204 NERC CIP controls; this command enumerates what evidence tends to be expected for each SCF family in scope.
Usage
/us-nerc-cip:evidence-checklist [--family=<SCF_family_code>]
Arguments
--family=<SCF_family_code>(optional) - restrict to a single SCF family such asIAC,CRY,AST, orBCD. Defaults to all families mapped for this framework.
Output
Markdown checklist grouped by SCF family with:
- SCF control ID to framework-native control ID(s) from the crosswalk.
- Evidence types typically expected.
- Which connector plugins can collect each type automatically.
- Which items require manual upload or narrative.
Framework-specific evidence
Collect NERC CIP evidence around the BES Cyber System lifecycle:
- BES Cyber System categorization: CIP-002 methodology, impact rating rationale, Facility lists, asset inventories, approvals, and review dates.
- Security management controls: policies, procedures, responsible owners, exception approvals, compliance calendar, and management review evidence.
- Personnel and training: role-based training, access authorization, personnel risk assessments, revocation records, and visitor controls.
- Electronic security perimeters: network diagrams, access point lists, firewall rules, remote access controls, MFA, interactive remote access logs, and change records.
- Physical security perimeters: site diagrams, access control lists, badge logs, visitor logs, alarm testing, and physical access review evidence.
- System security management: baselines, patch evaluations, vulnerability assessments, malicious code prevention, ports/services reviews, and change authorization.
- Incident response and recovery: response plans, exercises, incident logs, reportability analysis, lessons learned, recovery plans, backup evidence, and restoration test results.
- Information protection: protected cyber asset information handling, storage, transmission, disposal, and access evidence.
- Supply chain risk: procurement controls, vendor risk assessments, vendor remote access, software integrity, notification clauses, and tracking of supplier risk issues.
Prefer structured exports from identity, network, physical access, ticketing, asset management, vulnerability, backup, and GRC systems over screenshots. Where evidence is narrative, capture the responsible entity, registered function, asset scope, impact category, approval date, and linked requirement.
NERC CIP Scope
Determines whether and how NERC Critical Infrastructure Protection (CIP) Reliability Standards apply to the entity, Facilities, and cyber asset population. Reference-depth scope is a decision-tree prompt; Full-depth plugins extend this with registered-function and BES Cyber System categorization logic.
Usage
/us-nerc-cip:scope
What this produces
- Applicability verdict: in-scope, out-of-scope, or partially in-scope.
- In-scope entity types: registered functions such as BA, DP, GO, GOP, RC, TO, TOP, TP, or other NERC-defined responsible entity roles.
- In-scope assets: Facilities, BES Cyber Systems, Cyber Assets, Electronic Security Perimeters, Physical Security Perimeters, EACMS, PACS, and protected information.
- Jurisdiction reach: applicable North American bulk power system jurisdiction and Regional Entity oversight.
- Next steps: whether to proceed with
/us-nerc-cip:assessor/us-nerc-cip:evidence-checklist.
Framework-specific scope triggers
Ask the minimum questions needed to classify NERC CIP applicability:
- Which NERC registered functions does the entity perform?
- Which Facilities and assets support BES reliability obligations?
- Has the entity completed BES Cyber System categorization and impact rating?
- Which assets are high, medium, low, or out of scope?
- What Electronic Security Perimeters and Physical Security Perimeters exist?
- Which vendors, remote access paths, cloud services, or shared services support BES Cyber Systems or protected information?
- Which Regional Entity or jurisdiction governs the compliance program?
Return an applicability verdict, in-scope asset population, impact categories, responsible owners, and the follow-up command that should run next. Do not ask users to search NERC standards; translate their answers into practical NERC CIP scoping outcomes.
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/frameworks/us-nerc-cip
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- us-soxv0.1.0
- vault-kvv0.1.0
- wiz-inspectorv0.1.0
- academic-research-companionv0.1.0
- au-apra-cps-234v0.1.0
- aws-inspectorv0.1.0
- aws-secrets-inspectorv0.1.0
- azure-inspectorv0.1.0
- ch-fadpv0.1.0
- cis-controlsv0.1.0
- cmmcv0.1.0
- compliance-posture-dashboardv0.1.0
- crowdstrike-inspectorv0.1.0
- csa-ccmv0.1.0
- cyber-essentials-plusv0.1.0
- datadog-inspectorv0.1.0
- dorav0.1.0
- drata-inspectorv0.1.0
- essential8v0.1.0
- eu-nis2v0.1.0
- fedramp-20xv0.1.0
- fedramp-rev5v0.1.0
- fedramp-sspv0.1.0
- gcp-docsv0.1.0