Bottom line No VPN makes a defense contractor CMMC compliant. CMMC Level 2 is 110 requirements; a VPN can help with three of them: encryption in transit, validated cryptography (only if its module is validated) and multi-factor sign-in (only if the plan enforces it). A VPN alone does not make a company compliant. Ask any vendor for its CMVP certificate number before CUI crosses its service.
What this page is for
This page is for an owner or IT lead at a small defense supplier choosing a business VPN. 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, best VPN for law firms and best VPN for law enforcement.
We do not run our own security tests. Every vendor-specific line below is what the vendor says on its own pages, with the date we read it. The regulations are linked under References. This is general information, not legal advice.
What does a VPN cover under CMMC?
CMMC Level 2 means the 110 requirements of NIST SP 800-171 Rev 2 across every system that handles CUI. A VPN is one technical control. Here is where it fits.
| Requirement | What it says | Does a VPN help? |
|---|---|---|
| 3.13.8 | Use cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission | Yes, for traffic that goes through the VPN |
| 3.13.11 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI | Only if the VPN’s module is validated, not just “FIPS compliant” |
| 3.5.3 | Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts | Only if the plan enforces MFA or connects to your SSO |
| The other requirements | Access control, audit, training, incident response, physical protection and more | No. These are policies, devices and people |
A VPN alone does not make a company compliant. The assessment looks at the whole system security plan.
If the vendor runs the service, the vendor is in scope
A VPN or zero-trust service run by a vendor is a cloud service. DFARS 252.204-7012[1] says an external cloud provider that stores, processes or transmits covered defense information must meet security requirements equivalent to the FedRAMP Moderate baseline, and 32 CFR 170.16[2] sets the same test for CMMC Level 2. Whether a service that only passes encrypted traffic counts as handling CUI is a scoping question for your assessor. Ask before you buy, not after.
What about a three-person shop?
A fair question: a company of three, five or ten may wonder whether a multi-device consumer plan is enough. CMMC sets no seat floor. A five-person shop answers the same list of requirements; size changes the cost and the paperwork, not the list. A multi-device plan can meet the transmission requirement only if its module is validated, which consumer plans rarely document. It also gives you no admin console to remove a leaver. If you have no CUI, only federal contract information, you are in Level 1, which is a short list and has no encryption-module rule.
What to ask a VPN company before CUI goes through it
- What is the CMVP certificate number of the module that encrypts our traffic, and is it Active? Check it on the NIST list yourself.
- Is the service itself FedRAMP authorized, and which services does that cover? Cloudflare lists “Cloudflare for Government” at High on the FedRAMP Marketplace but does not say on that listing which services are covered.
- Where do our connections terminate, and who can see the traffic? This matters for ITAR’s end-to-end test.
- Which controls come with my plan? Dedicated IP, SSO and MFA enforcement are gated by plan.
Controls you can buy, and which plan has them
The controls a team can switch on are dedicated IP or allow-listing (so a system accepts connections only from the team’s fixed address), single sign-on (SSO, so access follows your staff accounts) and multi-factor sign-in (MFA, a second proof beyond a password). 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 |
NordLayer has no review page on VPN.com, 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.
Final Verdict
| If this is your situation | Start with |
|---|---|
| Your contract involves CUI (Level 2) | A service that documents a validated module and its FedRAMP status; ask your assessor how it is scoped |
| You hold only federal contract information (Level 1) | A business plan with SSO and MFA is reasonable; the encryption-module rule is a Level 2 item |
| A vendor says only “FIPS compliant” | Ask for the certificate number. “Compliant” is not “validated” |
| Technical data under ITAR | Ask an export-control lawyer before you choose, including where the vendor stores or routes data |
The VPN is one control. Your system security plan, devices, training and assessor decide the rest.
References
- Acquisition. n.d. DFARS 252.204-7012. https://www.acquisition.gov/dfars/252.204-7012-safeguarding-covered-defense-information-and-cyber-incident-reporting..
- ECFR. n.d. 32 CFR 170.16. https://www.ecfr.gov/current/title-32/part-170/section-170.16.
- ECFR. n.d. 32 CFR 170.14: Level 1 and Level 2 requirements. https://www.ecfr.gov/current/title-32/part-170/section-170.14.
- ECFR. n.d. 32 CFR 170.15: Level 1 self-assessment. https://www.ecfr.gov/current/title-32/part-170/section-170.15.
- NIST. n.d. NIST SP 800-171 Rev 2. https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-171r2.pdf.
- Ndisac. n.d. NDISAC: SC.L2-3.13.11 CUI encryption. https://ndisac.org/dibscc/cyberassist/cybersecurity-maturity-model-certification/level-2/sc-l2-3-13-11/.
- NIST. n.d. NIST Cryptographic Module Validation Program. https://csrc.nist.gov/projects/cryptographic-module-validation-program.
- ECFR. n.d. 22 CFR 120.54: Activities that are not exports. https://www.ecfr.gov/current/title-22/part-120/section-120.54.
- Fedramp. n.d. FedRAMP Marketplace: Cloudflare for Government. https://www.fedramp.gov/marketplace/products/FR2000863987A/.
- Pilieromazza. n.d. PilieroMazza: CMMC levels and the information they cover. https://www.pilieromazza.com/cmmc-is-here-what-it-means-for-defense-contractors/.
- Nordlayer. n.d. NordLayer pricing. https://nordlayer.com/pricing/.
