Bottom line NERC CIP-005 does not ask a regulated entity to buy a VPN. It asks that remote sessions go through an Intermediate System, that encryption ends there, and that multi-factor authentication is required. A VPN alone does not make an entity compliant. This is an enterprise matter: the small-team shortcut that works for a law office does not apply to a registered entity.
What this page is for
This page is for the IT or security lead at an energy company who needs to understand where a business VPN fits next to the NERC CIP remote-access rules. It sits under our best VPN for business guide, which explains how a business VPN differs from a personal one. For larger organisations see the enterprise VPN guide. Other regulated fields have different rules; see best VPN for healthcare and best VPN for law firms.
We do not run our own security tests, and we did not check any vendor against CIP-005. Every vendor-specific line below is what the vendor says on its own pages, with the date we read it. The standard and the commentary we used are linked under References. This is general information, not compliance advice.
Does NERC CIP require a VPN?
The standard names no VPN and no product. CIP-005-7 asks for an Intermediate System, encryption that terminates at it, and MFA for Interactive Remote Access. A VPN can be one piece of that path, but the standard is about the design: where the session ends, what it can reach, and how you show an auditor that nothing bypasses it. A VPN alone does not make an entity compliant.
Can a small team use a consumer VPN instead?
For a registered entity, no, and we would not suggest it. Part 2.1 is about an Intermediate System that sits in front of the protected systems, which is a network design, not something a consumer VPN app sets up for you. ReliabilityFirst, one of NERC’s regional entities, also recommends that a device remotely accessing the system over a VPN should not split-tunnel, meaning it should not send other traffic outside the VPN at the same time. That is a view, not a rule.
| Topic | What the sources say |
|---|---|
| Intermediate System | Part 2.1 requires one for all Interactive Remote Access to applicable systems |
| Where encryption ends | Part 2.2 says it terminates at the Intermediate System |
| MFA | Part 2.3 requires it for all Interactive Remote Access sessions |
| Split tunnelling | ReliabilityFirst recommends against it on the remote device; not part of the standard |
| Small teams | Not addressed by the standard. The entity’s size does not change Table R2 |
If you are a contractor or vendor who connects into a registered entity, ask the entity what its remote-access design requires before you buy anything.
Which business plans include the controls
The controls an entity can switch on are multi-factor sign-in (MFA, a second proof beyond a password), single sign-on (SSO, so access follows your staff accounts) and dedicated IP or allow-listing (so a system accepts connections only from a fixed address). Each vendor below says what its plans include, read on 8 October 2026.
| Provider | Dedicated IP or static IP | SSO | Price shown per user per month |
|---|---|---|---|
| NordLayer | Core and above | Listed | $11 (Core), yearly billing |
| Proton VPN for Business | Professional | Professional | From $9.99, appears to assume a multi-year term |
| Cloudflare Zero Trust | Enterprise add-on | Listed | Free under 50 users; $7 pay-as-you-go; Enterprise by quote |
| Tailscale | Not stated | With any identity provider | Standard $8, Premium $18 |
Cloudflare and Tailscale have no review page on VPN.com, so they are not linked internally. NordLayer has no review page either, so NordLayer links to its own site through our partner link. We earn a commission if you buy NordLayer through it; that does not change what its pages say. None of these rows says the product acts as an Intermediate System.
What to ask a vendor before it sits in a remote-access path
- Where does the session end, and can it be the Intermediate System or sit in front of it? This is an architecture question for your compliance team and auditor.
- Which security reports or certifications do you hold, and can I see them? Ask for the report, not just the badge, and check its date.
- Which controls come with my plan? Dedicated IP, SSO and MFA enforcement are gated by plan at the vendors above.
- What does the vendor log, and where is it stored? Your own duty to show evidence does not end with the vendor’s promise.
Final Verdict
| If this is your situation | Start with |
|---|---|
| You are a registered entity with High or Medium impact systems | Your compliance team and auditor first; then a plan that fits the design they approve |
| You want MFA, SSO and a fixed IP in front of corporate systems | NordLayer Core or Proton VPN Professional, as each vendor says. Compare the term you must commit to |
| You already use a zero-trust platform | Check what its Enterprise tier says about dedicated egress IPs and MFA |
| You are a small supplier connecting into an entity | The entity’s remote-access requirements |
The VPN is one control. Your architecture, your impact ratings and your auditor decide the rest.
References
- Nerc. n.d. NERC CIP-005-7: Cyber Security, Electronic Security Perimeter(s). https://www.nerc.com/pa/Stand/Reliability%20Standards/CIP-005-7.pdf.
- Rfirst. n.d. ReliabilityFirst: Remote Access, Advanced Topics (The Lighthouse). https://www.rfirst.org/wp-content/uploads/2023/09/35-2019-11-Remote-Access-Advanced-Topics.pdf.
- Europa. n.d. NIS2 Directive (EU) 2022/2555, Article 21 (EUR-Lex). https://eur-lex.europa.eu/eli/dir/2022/2555/oj.
- Nordlayer. n.d. NordLayer pricing. https://nordlayer.com/pricing/.
