Support FIPS 140-2 requirements

FIPS 140-2 is a U.S./Canada standard that defines security requirements for cryptographic modules used to protect sensitive data. Modules are validated under the CMVP program at security levels 1–4 and are widely required by government and regulated industries. (Note: FIPS 140-3 is the successor standard and is now in effect.)

Download FIPS endpoint checklist (PDF)

Reference: NIST FIPS 140-2 and CMVP program documentation.

What FIPS 140-2 covers

FIPS 140-2 specifies requirements for cryptographic modules, with evaluation across areas like roles & services, key management, physical security, self-tests, and design assurance. Modules receive an overall level based on individual area ratings.

Key points:

  • CMVP validation: Modules must be validated by accredited labs under the Cryptographic Module Validation Program (CMVP).
  • Approved algorithms: Deploy cipher suites using approved algorithms as specified by FIPS and related annexes.
  • Transition to 140-3: 140-3 replaces 140-2; many agencies accept 140-2 during the overlap while moving to 140-3.

How Codeproof helps you align with FIPS

Note: FIPS compliance requires using validated crypto modules in the underlying OS/application stack. Codeproof supports deployment and governance controls that help you enforce these requirements across devices. Your organization is responsible for selecting FIPS-validated modules and maintaining overall compliance.

  • OS-level crypto posture: Enforce device encryption and policies that require OS features (e.g., FileVault/BitLocker/Wrapping keys) configured to use FIPS-approved crypto where available.
  • Certificate & key lifecycle: Push certificates, install trusted roots/intermediates, and rotate keys at scale; restrict weak protocols/ciphers via managed configs.
  • App allowlists: Allow only vetted apps/containers that leverage FIPS-validated crypto modules; block non-compliant apps.
  • Network protections: Configure Wi-Fi, VPN, and per-app VPN with approved cipher suites; require TLS with strong parameters.
  • Device integrity: Detect jailbreak/root, posture drift, and take automated remediation actions (quarantine, selective wipe).
  • Audit readiness: Export device inventory, configuration states, change history, and compliance reports for auditors.

Related: iOS MDM · macOS MDM · Windows MDM · Android MDM

FIPS FAQs

Is Codeproof itself FIPS validated?
Codeproof provides management and enforcement. FIPS validation applies to cryptographic modules (e.g., OS crypto libraries, HSMs). Ensure your platform components are FIPS-validated where required.
What’s the difference between 140-2 and 140-3?
FIPS 140-3 supersedes 140-2 and harmonizes with ISO/IEC 19790. Agencies are transitioning; verify your authority’s acceptance and timelines before deployment.
How do we prove use of approved algorithms?
Document OS/application module versions and their validation certificates, enforce policy baselines, and export Codeproof reports showing applied configurations.
Does device encryption alone satisfy FIPS?
No. You must also ensure the cryptographic module itself is validated and configured to use approved algorithms/parameters.

Maximize employee productivity through Codeproof