We use privacy-by-default, cookieless analytics.

Optional analytics cookies are used only if you accept them.

Read our Terms of Use and Privacy Policy.

FAQGLOBALFIPS 140-3

FIPS 140-3 Algorithm certificates FAQ

Use algorithm certificates as scoped evidence for tested cryptographic algorithm implementations inside a FIPS 140-3 module claim.

This page explains what to check before reusing an in module evidence, customer responses, or procurement reviews.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
4 sections3 primary sources
Overview

Short answer: an is evidence that a particular cryptographic algorithm implementation was tested by for a stated implementation version and operational environment. It does not by itself prove that a product or module is validated to FIPS 140-3 under .

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

What does an algorithm certificate prove under FIPS 140-3?

A supports the algorithm part of a FIPS 140-3 evidence package. It shows that the named implementation was tested for the algorithm capabilities and operational environments recorded by CAVP. An accredited Cryptographic and Security Testing (CST) laboratory separately tests the cryptographic module that integrates and uses that implementation, and reviews and validates the submission.

That distinction matters in public claims. A product team should not describe a product as FIPS 140-3 validated merely because one embedded algorithm has a certificate. The module still needs its own validation record and Security Policy for the claimed module boundary.

  • Use the certificate to identify the tested algorithm implementation, implementation version, and operational environment.
  • Use the module certificate and Security Policy to support a FIPS 140-3 module-validation claim.
  • Keep customer and procurement wording separate: -tested algorithm implementation is not the same claim as -validated cryptographic module.
Recommended next step

Build a clean FIPS 140-3 certificate evidence map

Connect each CAVP certificate to the module boundary, Security Policy row, operational environment, and customer-facing claim it supports.

Assessment workflow
Map certificates to controls

Turn certificate checks into accountable evidence tasks and review triggers.

Explore next step
Research workflow
Check a scoped claim

Review whether a certificate supports the exact module, environment, and customer claim.

Explore next step
Talk to Sorena
Talk through implementation

Review the certificate evidence map, public wording, and next validation questions with Sorena.

Explore next step
Question 2

What should I check before reusing a certificate in module evidence?

Check the certificate number, algorithm capabilities and parameters, implementation version, and tested operational environment, then compare those details with the module configuration that will rely on the algorithm. IG 2.3.A requires the validated implementation to remain unmodified after integration and its environment to be identical to, or fully included in, the module's tested environment.

For software, firmware, and hybrid modules, the tested operational environment matters. If the algorithm was tested on a different operating system, processor, platform, or hypervisor arrangement, do not assume the certificate automatically covers the module under test.

  • Compare the certificate's implementation name and version with the implementation shipped in the module.
  • Compare the certificate's operating system, platform, processor, and hypervisor details with the module's tested operational environment.
  • Treat changed code, changed processor bit size, changed operating system, or changed hardware implementation as a reason to re-check testing coverage.
Question 3

What evidence should be kept with algorithm certificates?

Keep enough evidence to show why the certificate supports the current module claim. Connect the entry to the module boundary, the Security Policy table or service row where the algorithm is used, required self-tests, and the operational environment tested for the module. A certificate for an approved algorithm does not make every parameter, mode, protocol use, or service approved.

Do not use stale certificate screenshots as the only evidence. Keep the public URL, certificate number, algorithm and implementation identifiers, module certificate or submission reference, Security Policy excerpt, and the date the evidence was checked.

  • Record the certificate number, algorithm name, implementation name, implementation version, and tested operational environment.
  • Map each certificate to the module service or Security Policy row that relies on that algorithm implementation.
  • Re-check the evidence when the algorithm implementation, module version, operating environment, processor acceleration path, supplier component, or module status changes.
  • For processor algorithm acceleration (PAA) or processor algorithm implementation (PAI) use, verify whether the guidance requires testing in both software/firmware-only execution and accelerated execution.
Question 4

Questions and answers

Does a prove FIPS 140-3 module validation?

No. A certificate validates an algorithm implementation, while validates the cryptographic module. Use the as supporting evidence, but rely on the module certificate and Security Policy for the actual FIPS 140-3 claim.

What should I compare before reusing an in module evidence?

Compare the algorithm implementation name and version, the certificate number, and the tested operational environment against the module configuration that will rely on it. If the operating system, platform, processor, hypervisor, or code changed, re-check the claim instead of assuming reuse is valid.

What evidence should be kept with an ?

Keep the public URL, certificate number, algorithm and implementation identifiers, module certificate or submission reference, Security Policy excerpt, and the date the evidence was checked. That record should show why the certificate supports the current module claim.

Primary sources

References and citations

CMVP Implementation Guidance for FIPS 140-3
csrc.nist.gov4 citations
Referenced sections
  • Primary guidance for algorithm certificate reuse, operational environments, and module evidence.
  • Supports the distinction between CAVP testing for algorithm implementations and CMVP validation for cryptographic modules.
  • Grounds the reuse rule for binding cryptographic algorithm validation certificates to modules under test.
Show 1 more
  • Supports evidence fields for certificate binding, operating environment checks, and PAA/PAI testing considerations.
"the validation certificate serves as a benchmark"
More quoted passages
"Cryptographic algorithm implementations are tested and validated under the Cryptographic Algorithm Validation Program"
"has not been modified upon integration into the cryptographic module"
"the tested operational environment"
NIST CAVP validation search
csrc.nist.gov4 citations
Referenced sections
  • Public search page for checking CAVP algorithm validation records referenced in module evidence.
  • Public NIST search page for checking algorithm validation records used as supporting evidence.
  • Public lookup for confirming the certificate entry, algorithm name, implementation details, and listed operating environment.
Show 1 more
  • This source helps re-check the public certificate entry instead of relying only on copied text or screenshots.
"Cryptographic Algorithm Validation Program"
NIST FIPS 140-3 security requirements for cryptographic modules
doi.org3 citations
Referenced sections
  • Primary standard source support for keeping algorithm-certificate claims tied to cryptographic modules and their required security areas.
  • Explains that CMVP validates cryptographic modules and that validated modules are the procurement metric for agencies.
  • Supports retaining module-level CMVP validation evidence separately from algorithm-certificate evidence.
"security requirements for cryptographic modules"
More quoted passages
"A test report for modules demonstrating compliance will be submitted to the CMVP"

Related guides

FIPS 140-3 Certificate Maintenance FAQ

How to maintain FIPS 140-3 certificate evidence after validation by checking module status, version, caveats, Security Policy, and revalidation records.

FIPS 140-3 Entropy Evidence FAQ

How FIPS 140-3 entropy evidence should document entropy source location, GetEntropy access, SP 800-90B testing, Security Policy text, and certificate caveats.

FIPS 140-3 Module Boundaries FAQ

Understand how FIPS 140-3 module boundaries affect cryptographic module scope, interfaces, software and firmware components, and bound or embedded validated modules.

FIPS 140-3 operational environments FAQ

Learn what a FIPS 140-3 operational environment means for software, firmware, and hybrid cryptographic modules, and what evidence to check before relying on a validation claim.

FIPS 140-3 security levels: how to choose and evidence them

A practical FAQ on FIPS 140-3 security levels, module scope, CMVP evidence, bound or embedded modules, and common claim mistakes.

FIPS 140-3 Vendor Affirmation FAQ

When vendor affirmation can support a FIPS 140-3 module claim, what it does not supersede, and which Security Policy, CAVP, CSTL, and test-report evidence to keep.

Show all related guides (28)

How should teams handle approved mode under FIPS 140-3?

Answer the FIPS 140-3 approved-mode question with service-level indicators, Security Policy evidence, and limits on non-approved functions.

FIPS 140-3 algorithm certificate mapping: ACVTS certificates to module boundary

Map CAVP algorithm certificates to FIPS 140-3 module services, approved security functions, security policy tables, and validation evidence.

FIPS 140-3 Applicability Test

Check whether FIPS 140-3 applies to a cryptographic module claim by testing agency use, module boundary, security level, approved functions, CMVP status, and procurement evidence.

FIPS 140-3 Approved and Non-Approved Mode Workflow

Classify FIPS 140-3 module services by approved security service, allowed no-security-claimed use, and non-approved service evidence.

FIPS 140-3 approved-mode evidence workflow

Collect FIPS 140-3 approved-mode evidence for a specific module service: boundary, indicator, selected CAVP capabilities, Security Policy entry, and deployment configuration.

FIPS 140-3 Change Impact Review

Review FIPS 140-3 module changes against boundary, version, operational environment, embedded module, software loading, CVE, and certificate evidence.

FIPS 140-3 CMVP Lifecycle and Status Guide

Follow a FIPS 140-3 module from scoping and CST-laboratory testing through CMVP review, publication, Active status, revalidation, and procurement checks.

FIPS 140-3 compliance guide

A FIPS 140-3 compliance guide grounded in official sources for cryptographic module scope, security levels, CMVP validation evidence, and procurement review.

FIPS 140-3 Entropy and DRBG Evidence

FIPS 140-3 entropy and DRBG guidance for module boundary decisions, entropy caveats, Security Policy evidence, ESV references, and DRBG CSP handling.

FIPS 140-3 FAQ for Cryptographic Modules

Answers to common FIPS 140-3 questions about scope, CMVP validation, algorithm certificates, module boundaries, approved mode, and validation evidence.

FIPS 140-3 Module Boundary Selector Workflow

A FIPS 140-3 workflow for selecting a cryptographic module boundary, separating embedded and bound modules, and collecting CMVP validation evidence.

FIPS 140-3 Security Policy Template

Draft the vendor-authored parts of a FIPS 140-3 CMVP Security Policy and prepare the structured module information that CMVP merges into the final policy.

FIPS 140-3 Validation Checklist

Checklist for preparing a cryptographic module for FIPS 140-3 validation: boundary, levels, services, approved algorithms, entropy, tests, security policy, and change evidence.

FIPS 140-3 Validation Maintenance

Decide whether a changed FIPS 140-3 module still matches its validation or needs a CMVP revalidation scenario, evidence update, or paused claim.

FIPS 140-3 Validation Maintenance Change Workflow

Triage a changed FIPS 140-3 module against current CMVP revalidation scenarios, Security Policy evidence, CAVP testing, operational environments, and CVE handling.

FIPS 140-3 vs ISO/IEC 19790 and ISO/IEC 24759

Compare FIPS 140-3 with ISO/IEC 19790 and ISO/IEC 24759 for cryptographic module validation scope, evidence, testing, and procurement claims.

FIPS 140-3: FIPS 140-2 vs FIPS 140-3

Compare FIPS 140-2 legacy references with FIPS 140-3 requirements, ISO/IEC 19790 alignment, CMVP testing evidence, and guidance mappings.

FIPS 140-3: Module Boundary and Service Mapping

Map a FIPS 140-3 cryptographic module boundary to services, approved algorithms, operational environments, and CMVP validation evidence.

FIPS 140-3: Module Boundary Selector

Select and document a FIPS 140-3 cryptographic module boundary across hardware, software, firmware, operational environment, services, and validation evidence.

FIPS 140-3: Operational Environment

FIPS 140-3 operational environment guidance for software, firmware, hybrid, CAVP certificate, EVM, and PAA/PAI validation claims.

FIPS 140-3: Security Levels Explained

Compare FIPS 140-3 Security Levels 1 through 4 by requirement area and document a level claim without extending it beyond the validated module.

FIPS 140-3: step-by-step workflow for mapping algorithm certificates to CMVP modules

Map CAVP algorithm certificates to a FIPS 140-3 module by matching the tested implementation, operational environment, service use, and CMVP Security Policy record.