Search CSRC

Call for Additional Digital Signature Schemes for the Post-Quantum Cryptography Standardization Process (PDF) Closed June 1, 2023 The Round 2 candidates were announced October 24, 2024. NIST IR 8528, Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process is now available. NIST announced that the PQC standardization process is continuing with a fourth round, with the following KEMs still under consideration: BIKE, Classic McEliece, HQC, and SIKE. However, there are no remaining digital signature candidates...

2023 [10-30-2023] Implementation Guidance for FIPS PUB 140-2 and the Cryptographic Module Validation Program has been updated. Updated Guidance G.8 Revalidation Requirements – Added requirements in Scenario 3B for a table indicating which certificate fields have been updated. G.17 Remote Testing for Modules – Updated to be consistent with the FIPS 140-3 remote testing guidance. D.4 Requirements for Vendor Affirmation of SP 800-56B- Removed reference to the December 31, 2023 transition. D.9 Key Transport Methods – Updated the language on the December 31, 2023...

The NIST Framework for Improving Critical Infrastructure Cybersecurity ("the Framework") released in February 2014 was published simultaneously with the companion Roadmap for Improving Critical Infrastructure Cybersecurity. The Roadmap identified Cyber Supply Chain Risk Management (Cyber SCRM) as an area for future focus. Since the release of the Framework and in support of the companion Roadmap, NIST has researched industry best practices in cyber supply chain risk management through engagement with industry leaders. In 2014 and 2015, NIST interviewed a diverse set of organizations and...

ARCHIVED PROJECT: This project is no longer being supported. The content is no longer being updated, and the information may be outdated. The following RBAC case studies and experience reports may be useful in planning for RBAC implementations. We will add to this collection as more reports become available. (Please note that the authors and organizations below are not affiliated with NIST or any other agency of the US Government, unless otherwise noted, and NIST cannot endorse or comment on these publications.) Submit comments or suggestions on this collection to the Project...

ATTENTION: The Project Lead is no longer at NIST. Inquiry responses may be delayed. ISO/IEC 29147 International Organization for Standardization/International Electrotechnical Commission (2018) ISO/IEC 29147:2018 – Information technology – Security techniques – Vulnerability disclosure (ISO, Geneva, Switzerland). Available at https://www.iso.org/standard/72311.html ISO/IEC 30111 International Organization for Standardization/International Electrotechnical Commission (2019) ISO/IEC 30111:2019 – Information technology – Security techniques – Vulnerability handling processes (ISO,...

At A Glance Purpose: Implement the controls in the security and privacy plans for the system and organization Outcomes: controls specified in security and privacy plans implemented security and privacy plans updated to reflect controls as implemented Resources for Implementers RMF Quick Start Guide (QSG): Implement Step FAQs Security Configuration Settings Multiple Supporting NIST Publications include templates Examples include: SP 800-88, Guidelines for Media Sanitization, SP 800-34 Revision 1, Contingency Planning Guide for Federal Information...

SP 800-38A: Five Confidentiality Modes In Special Publication 800-38A, five confidentiality modes are specified for use with any approved block cipher, such as the AES algorithm. The modes in SP 800-38A are updated versions of the ECB, CBC, CFB, and OFB modes that are specified in FIPS Pub. 81; in addition, SP 800-38A specifies the CTR mode. In the Addendum to SP 800-38A, NIST has specified three variants for extending the domain of the CBC mode using "ciphertext stealing." SP 800-38B: An Authentication Mode The CMAC authentication mode is specified in Special Publication...

Historical FAQs Frequently Asked Questions (FAQs) [updated 11/18/2024] Example Files API Notes (Sept 2017) API Notes (March 2017) API Notes (November 2016) API Notes (June 2016) Source Code Files for KATs (Dec 2021) KAT (Sept 2017) KAT (June 2016) Variable Label Test #2048 (June 2016) Variable Message #2048(June 2016) Intermediate Values (June 2016) Note - the intermediate values below were for the draft versions of ML-KEM and ML-DSA. Please use the correct test vectors for the final versions. The Cryptographic Algorithm Validation Program (CAVP) provides full test...

At the beginning of each fiscal year (FY), NIST CMVP prepares a budget justification for the NIST Cost Recovery fees for the following fiscal year. The NIST Budget office reviews the information and is the approver for the final NIST Cost Recovery fees for the following fiscal year. FY17: begins October 1, 2016; ends September 30, 2017. FY18: begins October 1, 2017; ends September 30, 2018. The NIST Cost Recovery fees for FY17 and FY18 are (see Implementation Guidance (IG) G.8 for an explanation of the different scenarios): FY17 FY18 CR...

Archived. This page is archived for informational purposes only. See End-of-Life Announcement: NIST SCAP Validation Program. The NIST SCAP Validation Program has concluded. NVLAP terminated SCAP Testing accreditation effective September 2, 2025, and SCAP test methods were removed from affected NVLAP scopes of accreditation as of that date. NVLAP accepted SCAP Validation Test Reports from accredited laboratories only until 12:00 AM (midnight) EDT on September 2, 2025. Previously accredited laboratories (historical reference only) The organizations below were listed as NVLAP-accredited...

At A Glance Purpose: Inform organizational risk management processes and tasks by determining the adverse impact with respect to the loss of confidentiality, integrity, and availability of systems and the information processed, stored, and transmitted by those systems Outcomes: system characteristics documented security categorization of the system and information completed categorization decision reviewed/approved by authorizing official Resources for Implementers RMF Quick Start Guide (QSG): Categorize Step FAQs Controlled Unclassified Information (CUI)...

NIST continues to accept public comments on modes of operation, including comments on: Properties of individual modes (security, performance, etc.) Comparisons of proposed modes Recommendations for standardization Other related issues, such as padding. Comments may be submitted to [email protected] Comments on the Draft Specification of FPE Modes On February 28, 2019, NIST announced a public comment period, ending April 15, 2019, on Draft Special Publication 800-38G Revision 1, Recommendation for Block Cipher Modes of Operation: Methods for Format-Preserving Encryption. In...

Asset identification plays an important role in an organization's ability to quickly correlate different sets of information about assets. This specification provides the necessary constructs to uniquely identify assets based on known identifiers and/or known information about the assets. This specification describes the purpose of asset identification, a data model for identifying assets, methods for identifying assets, and guidance on how to use asset identification. It also identifies a number of known use cases for asset identification. The Asset Specifications Development List is...

On July 19, 2022, NIST announced its intention to update the series of special publications dedicated to the Protection of Controlled Unclassified Information (CUI). Many changes are actively under consideration reflecting the current thinking of NIST after extensive review and analyses of the public comments. Based on the feedback received, inputs from workshops and conferences, and discussions with federal agencies, the changes under consideration include: Streamlining the Introduction and Fundamentals sections of the document Withdrawing requirements that are either outdated, no longer...

ARCHIVED PROJECT: This project is no longer being supported. The content is no longer being updated, and the information may be outdated. The following references provide historical background and important details about RBAC. RBAC Book Role-Based Access Control, 2nd edition (2007) by David Ferraiolo, Ramaswamy Chandramouli, and D. Richard Kuhn Select a heading to expand/collapse the view. Early Papers D.F. Ferraiolo and D.R. Kuhn (1992), Role-Based Access Controls, 15th National Computer Security Conference. The original RBAC paper; introduced...

The Asset Reporting Format (ARF) is a data model to express the transport format of information about assets, and the relationships between assets and reports. The standardized data model facilitates the reporting, correlating, and fusing of asset information throughout and between organizations. ARF is vendor and technology neutral, flexible, and suited for a wide variety of reporting applications. The Emerging Specifications Discussion List is available for developers interested in ARF and other emerging security automation standards. Please subscribe to this list through the SCAP...

The Applicability Language specification defines a standardized structure for forming complex logical expressions out of Well-formed Names (WFNs). These expressions, also known as applicability statements, are used to tag checklists, policies, guidance, and other documents with information about the product(s) to which the documents apply. For example, a security checklist for Mozilla Firefox 3.6 running on Microsoft Windows Vista could be tagged with a single applicability statement that ensures only systems with both Mozilla Firefox 3.6 and Microsoft Windows Vista will have the security...

The Dictionary specification defines the concept of a CPE dictionary, which is a repository of CPE names and metadata, with each name identifying a single class of IT product. The Dictionary specification defines processes for using the dictionary, such as how to search for a particular CPE name or look for dictionary entries that belong to a broader product class. Also, the Dictionary specification outlines all the rules that dictionary maintainers must follow when creating new dictionary entries and updating existing entries. CPE Dictionary Resources Release 2.3 CPE 2.3 Dictionary...

Blockmatrix functions have been integrated with Hyperledger Fabric, making it possible to use Hyperledger in a broader range of applications. Applications that currently use Hyperledger Fabric will be able to function without change, with blockmatrix components providing distributed ledger functions in a transparent manner. To support privacy requirements for deleting private user information, data blocks containing PII can be deleted offline, or functions can be added to the application with appropriate access control for administrators or users as determined by the organization. -...

Common Platform Enumeration (CPE) is a standardized method of describing and identifying classes of applications, operating systems, and hardware devices present among an enterprise's computing assets. CPE does not identify unique instantiations of products on systems, such as the installation of XYZ Visualizer Enterprise Suite 4.2.3 with serial number Q472B987P113. Rather, CPE identifies abstract classes of products, such as XYZ Visualizer Enterprise Suite 4.2.3, XYZ Visualizer Enterprise Suite (all versions), or XYZ Visualizer (all variations). IT management tools can collect information...

In 2012, we co-founded the International Workshop on Combinatorial Testing, focused on theory and application of CT. Papers from previous workshops are listed below. IWCT 2025 A Combinatorial Approach to Reduce Machine Learning Dataset Size Megan Olsen, M S Raunak, Rick Kuhn, Fenrir Badorf, Hans van Lierop, Francis Durso A Search-Based Benchmark Generator for Constrained Combinatorial Testing Models Paolo Arcaini, Andrea Bombarda, Angelo Gargantini Combinatorial Methods for Enhancing the Resilience of Production Facilities Klaus Kieseberg, Konstantin Gerner, Bernhard Garn,...

2026 Fees [Updated 01-05-2026] Cost recovery fees are collected for NIST CMVP report review of new module or entropy submissions, modified module or entropy submissions, and for report reviews that require additional time due to complexity or quality. These fees are referred to as Cost Recovery (CR) and Extended Cost Recovery (ECR). Modules and entropy sources are not validated unless all applicable fees have been collected by NIST Billing. Please see the CMVP FIPS 140-2 Management Manual or CMVP FIPS 140-3 Management Manual for further information. For FIPS 140-2 Currently the CR...

The NIST Security and Privacy Control Overlay Repository (SCOR) provides stakeholders a platform for voluntarily sharing control overlays created by subject matter experts to help reduce the duplication of effort and share best practices for the information security and privacy community. What is a Control Overlay? An overlay may provide a fully specified set of controls, control enhancements, and parameter values to address specific circumstances, situations, and/or conditions unique to specific communities of interest, industry sectors, or coalitions/partnerships. Learn More About...

Algorithm Specifications Algorithm information is available from the Cryptographic Toolkit page. Algorithm Validation Testing Requirements The algorithm validation testing requirements for FIPS 198-1 are specified in: The Keyed-Hash Message Authentication Code (HMAC) Validation System (HMACVS). Testing Notes Prerequisites for HMAC testing are listed in the CAVP Frequently Asked Questions (CAVP FAQ) General Question GEN.5. Test Vectors Use of these test vectors does not replace validation obtained through the CAVP. The test vectors linked below can be used to informally verify the...

As part of a holistic risk management strategy and applying the information security concept of defense-in-depth, organizations should employ appropriate configuration settings on commercial information technology products that compose their organizational systems. These products include, for example, mainframe computers, workstations, portable and mobile devices, and network components. Requirements to establish mandatory configuration settings derive from the Federal Information Security Management Act as implemented by FIPS 200 and NIST Special Publication 800-53 (Control CM-6,...