← Resources
Guide

How to choose NERC CIP compliance software: 12 questions to ask any vendor

What to ask before buying NERC CIP compliance software: how evidence is collected, whether it can touch OT devices, and what an auditor will see.

The short answer

The right NERC CIP compliance software depends on the gap you are closing: program tools hold policies, plans and records, while evidence tools collect configurations, logs and account lists from devices. For solar, wind and battery storage sites, look for read-only collection from OT devices (inverters, RTACs, relays) without an agent everywhere, coverage of CIP-003-9 low impact, evidence that can be shown to be unaltered, and on-premises installation that works without internet access.

Two kinds of tool, and most programs need both

Tools sold for NERC CIP do one of two jobs. Program tools hold what people write and decide: the CIP-002 impact categorization, CIP-003 policies and plans, training and access records, RSAW narratives. Evidence tools collect what systems produce: configurations, logs, installed software, open ports, account lists.

A program tool without evidence still leaves someone exporting firewall configurations and taking screenshots before every audit. An evidence tool without a program leaves the plans in folders. Know which gap you are closing before you compare products.

Questions about how evidence is collected

  • Does it only read from devices, or can it write? Ask which protocol functions it uses, for example Modbus and DNP3 read requests only. A compliance tool should never be able to change a relay or an inverter.
  • Which of your devices can it actually reach? Ask for the device list by vendor and model, and which ones are fully supported versus partly. Inverters, RTACs, relays and meters vary far more than Windows hosts.
  • Does it need an agent on every host? Many OT devices cannot run one. Agentless collection over SSH, WinRM, SNMP and vendor APIs covers most of a site; an agent is useful where file-integrity detail is needed.
  • How often does it collect, and can it also receive syslog and SNMP traps as they happen? CIP-007 R4 and CIP-010 R2 are easier to evidence continuously than in a quarterly sweep.

Questions about the evidence itself

  • Can it prove a record was not changed after it was collected? Ask how: hashing, hash chains, signatures, and whether you can verify that yourself.
  • Does each record say where it came from and when? An auditor will ask whether a configuration was exported from the device or typed up afterwards.
  • Can you get your evidence out in an open format (CSV, PDF) without the vendor? You will need it for audits years from now.
  • How does it compare a configuration with the baseline (CIP-010 R1), and who approves a change into the baseline?

Questions about where it runs

  • Can it be installed on-premises, and does it work without an internet connection? Many entities will not send BES Cyber System Information to a cloud service (CIP-011).
  • How is the tool itself secured: authentication between its parts, multi-factor sign-in, roles, signed updates? It will hold network diagrams and configurations, which are BCSI.
  • How are updates delivered on a network with no internet? Ask for the offline update process and how packages are verified.

Questions about the audit

  • Does it map evidence to standards and requirements, and fill the RSAW, or only store files?
  • Does it cover low impact (CIP-003-9 Attachment 1) as well as medium and high? Most solar, wind and battery sites start at low impact.
  • Can a reviewer see why a requirement shows as met, down to the records behind it? A score with no trail does not help in an audit.

Spreadsheets are a legitimate starting point

A small low impact program can run on documents and spreadsheets. The cost appears as sites are added: evidence gathered by hand at audit time, versions that disagree, and no way to show when something changed. The point to move to a tool is usually when evidence collection, not writing the plans, becomes the work.

Run a pilot on one real site

Ask to connect the tool to one site's real devices, read-only, for a few weeks. Check what it found against your own asset list, look at the evidence it produced for one CIP-007 and one CIP-010 requirement, and ask your compliance lead whether they would hand it to an auditor.

Common questions

What is the best NERC CIP compliance software for solar and battery storage sites?

There is no single best tool; it depends on whether you need program management, evidence collection or both. For solar and battery storage, the deciding questions are whether the tool only reads from OT devices, which inverters, RTACs and relays it supports, whether it covers CIP-003-9 low impact, whether it can prove evidence was not changed, and whether it runs on-premises without internet. Run a read-only pilot on one real site before buying.

What is a NERC CIP evidence collection tool?

Software that collects the records auditors ask for directly from systems: device configurations, logs, installed software, open ports, accounts and security patches. It supports requirements such as CIP-007 R4 (logging) and CIP-010 R1 and R2 (baselines and change monitoring), and should record where and when each record was collected.

Should NERC CIP compliance software run in the cloud?

Many entities will not send BES Cyber System Information to a cloud service under CIP-011, so on-premises installation that works without an internet connection, with a verifiable offline update process, is a common requirement.

Can a small low impact program use spreadsheets instead?

Yes. A small CIP-003-9 low impact program can run on documents and spreadsheets. A tool usually starts to pay off when collecting evidence across many sites, not writing the plans, becomes the work.

What does GridShield do?

GridShield, from GridSafe Technology, collects NERC CIP evidence read-only over SSH, WinRM, SNMP, vendor REST APIs, Modbus TCP and DNP3 read requests, keeps every record SHA-256 hash-chained in an Evidence Vault, installs on-premises from a bootable ISO with signed offline updates, and fills RSAW worksheets from collected evidence for your team to review.

General guidance, not legal or compliance advice. Your obligations depend on your registration and assets — confirm them with your compliance team and Regional Entity.

More from Resources