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.

Artifact GuideGLOBALFIPS 140-3

FIPS 140-3 Module boundaries FAQ

A concise explanation of what the FIPS 140-3 boundary means for cryptographic module scope, interfaces, components, and validation evidence.

Based on FIPS 140-3 and Cryptographic Module Validation Program (CMVP) implementation guidance. Use it to frame product and validation discussions, not to claim CMVP approval.

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

Under FIPS 140-3, the is the line around the hardware, software, firmware, or hybrid components that make up the cryptographic module. Boundary decisions drive which components, interfaces, services, operational environments, and sensitive security parameter paths must be described and tested.

Search this module

Find a question or answer quickly

3 of 3 questions
Question 1

What is the module boundary under FIPS 140-3?

FIPS 140-3 applies to cryptographic modules and covers security requirement areas such as module specification, module interfaces, roles and services, software and firmware security, operating environment, physical security, sensitive security parameter management, self-tests, and lifecycle assurance.

For a boundary question, start with the module embodiment: hardware, software, firmware, or hybrid. Then identify the executable code, firmware, circuitry, physical enclosure or perimeter, interfaces, and services that form the module. Keep the cryptographic boundary distinct from the tested operational environment: a software module can execute inside a platform's physical perimeter while the operating system, processor, and other applications remain outside its cryptographic boundary.

  • For software modules, CMVP guidance describes the software cryptographic module as the executable code that includes security-relevant algorithms, security functions, processes, and module components.
  • The operating system, computing platform, and other general-purpose applications can be in the tested operational environment while remaining outside the software module's cryptographic boundary.
  • When a component is outside the boundary, do not describe its behavior as validated module behavior unless the applicable CMVP documentation supports that claim.
Question 2

How do bound and embedded modules affect the boundary?

CMVP implementation guidance treats binding and embedding from the perspective of the module under validation, called the Implementation Under Test (). An embedded existing validated module () is wholly contained within the IUT boundary and provides services only to the IUT.

A bound arrangement has two separate, disjoint cryptographic boundaries: the depends on an , and application services can be available from either module. Sensitive security parameters that move or are established between those boundaries are subject to the applicable entry, output, and establishment requirements; calling the modules bound does not merge their validated scopes.

  • For software, firmware, and hybrid binding cases, the and the existing validated module must each operate on tested operational environments that are the same or one is within the other.
  • If the relies on the existing validated module to meet a FIPS 140-3 requirement, the test report must show how the relied-upon requirement is met without violating other FIPS 140-3 requirements.
  • A FIPS 140-3 cannot embed or bind to a FIPS 140-2 existing validated module under the cited CMVP guidance.
Question 3

What should be documented before making a boundary claim?

Boundary documentation should be specific enough for a customer, assessor, or procurement reviewer to understand the module being claimed without confusing product packaging with the validated cryptographic module.

In public wording, name the module, certificate context if one exists, module type, tested operational environment where relevant, interfaces, services, and any bound or embedded existing validated module. Avoid implying that an entire product, cloud service, platform, or dependency is FIPS 140-3 validated when only a defined module is in scope.

  • Keep a boundary diagram or written boundary description that separates in-boundary components from the operating system, hardware platform, applications, and services outside the cryptographic boundary.
  • List the module interfaces, approved services, algorithms, self-tests, sensitive security parameter handling, and software or firmware integrity expectations that depend on the boundary.
  • For a bound or embedded existing validated module, identify the module by name, CMVP certificate number, version, and the subset of functionality used by the .
Recommended next step

Prepare FIPS 140-3 module boundary evidence

This FIPS 140-3 boundary guidance helps align module diagrams, security-policy wording, certificate references, and evidence requests.

Assessment workflow
Map boundary evidence

Connect module scope, interfaces, services, and certificate references to reviewable evidence.

Explore next step
Research workflow
Check a boundary question

Use cited research support when a module, platform, or dependency boundary is unclear.

Explore next step
Talk to Sorena
Talk through the module scope

Review the boundary, evidence, and public wording before making FIPS 140-3 claims.

Explore next step
Primary sources

References and citations

CMVP Implementation Guidance for FIPS 140-3
csrc.nist.gov4 citations
Referenced sections
  • CMVP guidance for interpreting boundaries in software modules and for bound or embedded existing validated modules.
  • Explains how software module boundaries relate to the tested operational environment, general-purpose computing platform, and applications outside the cryptographic boundary.
  • Defines embedded and binding modules, including separate or contained boundaries, operational environment expectations, and FIPS 140-2 restrictions for FIPS 140-3 IUTs.
Show 1 more
  • States documentation expectations for IUT submissions that use an existing validated module, including clear separation of IUT and EVM information.
"defined cryptographic boundary"
More quoted passages
"external to the cryptographic boundary"
"separate, disjoint cryptographic boundary"
"precisely identify the EVM"
NIST FIPS 140-3 security requirements for cryptographic modules
doi.org3 citations
Referenced sections
  • Primary standard for the security requirement areas applied to cryptographic modules.
  • Identifies the FIPS 140-3 security requirement areas that apply to cryptographic module design, implementation, and operation.
  • Supports keeping boundary discussions tied to the FIPS 140-3 module requirement areas rather than broad product-level claims.
"security requirements for cryptographic modules"
More quoted passages
"cryptographic module specification"
"secure design and implementation"

Related guides

FIPS 140-3 Algorithm Certificates FAQ

How CAVP algorithm certificates support, but do not replace, FIPS 140-3 cryptographic module validation evidence.

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 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.