Search CSRC

Each title heading is clickable - clicking each title will expand/collapse the list of standards & supporting documents. PIV Standards: FIPS 201-3 - Personal Identity Verification (PIV) of Federal Employees and Contractors (January 2022)     Federal Register Notice    2020 Draft comments and dispositions FIPS 201-2 has been withdrawn and is superseded by FIPS 201-3 PIV Card Specifications: SP 800-78-5 - Cryptographic Algorithms and Key Sizes for Personal Identity Verification  (July 2024)  SP 800-76-2 - Biometric Data Specification for Personal Identity...

Test Runner Software (updated February 13, 2020) SP 800-73-4 Test Runner for PIV Card Applications, Middleware and Data Model Please send an e-mail to [email protected] to request for a password to unzip the Test Runner file and/or for any questions you may have. DISCLAIMER: This software is released by NIST as a service and is expressly provided "AS IS." NIST MAKES NO WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR STATUTORY, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT AND DATA ACCURACY. NIST DOES NOT REPRESENT OR...

Test PKI Info  |  Sample Messages  |  Version 1 Test Cards  |  Email List In order to facilitate the development of applications and middleware that support the Personal Identity Verification (PIV) Card, the National Institute of Standards and Technology (NIST) has developed a set of test PIV Cards, which are available for purchase as a NIST Special Database. An overview of the test PIV Cards is provided in NIST 8347, NIST Test Personal Identity Verification (PIV) Cards Version 2.  NISTIR 8347 also contains technical details about the contents of each of the test cards in the set....

Draft FIPS 201-3 Virtual Public Workshop December 9, 2020 Presentations, Recording and Q&A chat transcript    Business Requirements Meeting of FIPS 201-3 (Government only)  March 19, 2019 Agenda with Presentations Workshop on Upcoming Special Publications Supporting FIPS 201-2 March 3-4, 2015 Agenda with Presentations Revised Draft FIPS 201-2 Workshop  August 26, 2012  Presentations Draft FIPS 201-2 Workshop April 18-19, 2011 Presentations: Overview (Goals of the workshop, purpose of the revision, overall revision process, summary of proposed changes) Hildegard Ferraiolo, NIST...

The Online Informative Reference Catalog contains all the Reference Data—Informative References and Derived Relationship Mappings (DRMs)—for the National Online Informative References (OLIR) Program. All Reference Data in the Informative Reference Catalog has been validated against the requirements of NIST Interagency Report (IR) 8278A Rev. 1 (Draft), National Online Informative References (OLIR) Program: Submission Guidance for OLIR Developers. If interested in participating in the OLIR program, please refer to the Informative Reference submission page. The OLIR Catalog provides an interface...

The Derived Relationship Mapping (DRMs) Analysis Tool provides Users the ability to generate DRMs for Reference Documents with a Focal Document of the Users’ choice. The DRMs are non-authoritative and represent a starting point when attempting to compare Reference Documents. Refer to Sections 3.3 – 3.6 of NISTIR 8278, National Online Informative References (OLIR) Program: Program Overview, Benefits and Uses  for additional guidance around understanding and utilizing the tool.  After creating a Display Report, Users can download the report in either a comma-separated value (CSV) file format or...

Primary Policy Machine References/Background: This paper provides a good overview of the Policy Machine's ability to express and enforce policies and policy combinations. However, unlike Policy Machine's most recent specification, this paper activates attributes prior to mediating an access request and does not recognize obligations or prohibitions. D. Ferraiolo, S. Gavrila, V. Hu, R. Kuhn, “Composing and combining policies under the policy machine, in: Proceedings of ACM Symposium on Access Control Models and Technologies”, 2005, pp. 11–20. These papers describe the benefits and...

For the most up to date macOS security recommendations, please visit the mSCP GitHub page listed below, which is supported by SP-800-219r1, Apple Security Guidance: macOS Security Compliance Project. https://github.com/usnistgov/macos_security  

Base EaaS Architecture Without A Decentralized Root Of Trust In this example, the client system is equipped with a Hardware Root of Trust (HRT) device. Examples of HRT devices are the Trusted Platform Module, Intel® Identity Protection Technology, and the ARM® TrustZone technology. The client system runs a dedicated software application capable of interfacing with the local HRT device on the one end and with the EaaS on the other end. The application communicates with the entropy server using standard plaintext protocols, such as HTTP. The dedicated application initiates the procedure for...

Florida Institute for Cybersecurity Research, University of Florida Intrinsic ID, Inc. 710 Lakeway Drive,  Suite 100,  Sunnyvale, CA 94085  Crypto4A, 1550A Laperriere Avenue, Ottawa, Ontario, Canada   2 Keys Corporation, 20 Eglinton Ave. W., Suite 1500,, Toronto, Ontario, Canada Real Random, LLC.     DISCLAIMER: Any mention of commercial products or organizations is for informational purposes only; it is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the products identified are necessarily...

Our work on EaaS will be (or has been) presented at the following events:   Upcoming Events   Past Events Live Demonstration at The 2015 Cybersecurity Innovation Form  (September 9-11, 2015)    Invited Talk at Workshop on Cryptography and Hardware Security for the Internet of Things IoT Security Workshop in College Park Maryland  October 8-9, 2015    Publication: Entropy as a Service: Unlocking Cryptoraphy's Full Potential,  IEEE Computer, 49(9): 98-102, September 2016   Invited Talk: Entropy as a Service: Unlocking Cryptoraphy's Full Potential,  2017 IEEE SOSE Workshop,...

The Automated Cryptographic Validation Testing System (ACVTS) comprises two main environments that support the Automated Cryptographic Validation Protocol (ACVP): the demonstration environment (ACVTS Demo aka “Demo”) and the production environment (ACVTS Prod aka “Prod”). Demo is a sandbox-style environment in which users may test their algorithm implementations and ACVP client applications. The Demo environment should be considered semi-volatile, meaning that any information stored in it is subject to loss at any time, though we do strive to keep the environment as stable and intact as...

AES Implementations have been validated as conforming to the Advanced Encryption Standard (AES) Algorithm, as specified in Federal Information Processing Standard Publication 197, Advanced Encryption Standard, using the tests found in the Advanced Encryption Standard Algorithm Validation Suite (AESAVS). CCM Implementations have been validated as conforming to the Counter with Cipher Block Chaining-Message Authentication Code (CCM), as specified in Special Publication 800-38C, using tests described in the CCM Validation System (CCMVS). Component...

Algorithm Specifications Algorithm specifications for current FIPS-approved and NIST-recommended block cipher algorithms are available from the Cryptographic Toolkit. Current testing includes the following algorithms: AES TDES Skipjack Algorithm Validation Testing Requirements Block Ciphers   Advanced Encryption Standard Algorithm (AES) The Advanced Encryption Standard Algorithm Validation System(AESAVS) specifies validation testing requirements for the ECB(Electronic Codebook), CBC (Cipher Block Chaining), OFB (Output Feedback), CFB (Cipher Feedback) and CTR (Counter) modes for...

Algorithm Specifications Algorithm specifications for current FIPS-approved and NIST-recommended block cipher modes are available from the Cryptographic Toolkit. Current testing includes the following block cipher modes: CMAC (SP 800-38B) XTS-AES (SP 800-38E) CCM (SP 800-38C) KW / KWP / TKW (SP 800-38F)(Key Wrap using AES and Triple-DES) GCM / GMAC / XPN (SP 800-38D and CMVP Annex A)     For testing...

Algorithm Specifications Algorithm specifications for current FIPS-approved and NIST-recommended digital signature algorithms are available from the Cryptographic Toolkit. Current testing includes the following algorithms: DSA | ECDSA | RSA (in FIPS 186-4) DSA | ECDSA | RSA (in FIPS 186-2) Algorithm Validation Testing Requirements FIPS 186-4 Digital Signature Algorithm (DSA) Digital Signature Algorithm Validation System (DSA2VS) specifies validation testing requirements for the DSA algorithm in FIPS 186-4. Testing Notes Prerequisites for DSA...

Algorithm Specifications Algorithm specifications for Key-Based KDFs (SP800-108) are available from the Cryptographic Toolkit. Algorithm Validation Testing Requirements The algorithm validation testing requirements for SP 800-108 are specified in: The SP800-108 Key Derivation Function Validation System (KBKDFVS). Testing Notes Prerequisites for KBKDF testing are listed in the CAVP Frequently Asked Questions (CAVP FAQ) General Question GEN.5. As of 1-1-2016, TDES KO2 encrypt is no longer compliant. (See SP800-131A Revision 1.) Test Vectors Use of these test vectors does not...

Algorithm Specifications Algorithm specifications for Key Agreement Schemes and Key Confirmation (SP800-56A) are available from the Cryptographic Toolkit. Algorithm Validation Testing Requirements The algorithm validation testing requirements for SP 800-56A are specified in: The KAS Validation System (KASVS) Testing Notes Prerequisites for KAS 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...

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

Algorithm Specifications Algorithm specifications for current FIPS-approved and NIST-recommended random number generators are available from the Cryptographic Toolkit. Current testing includes the following algorithm: DRBG (SP 800-90A) Algorithm Validation Testing Requirements Deterministic Random Bit Generators (DRBG) The DRBG Validation System (DRBGVS) specifies validation testing requirements for the DRBG algorithm in SP800-90A . Testing Notes Prerequisites for DRBG testing are listed in the CAVP Frequently Asked Questions (CAVP FAQ) General Question GEN.5. Test Vectors...

Algorithm Specifications Algorithm specifications for current FIPS-approved and NIST-recommended secure hashing algorithms are available from the Cryptographic Toolkit. Current testing includes the following algorithms: SHA-1 and SHA-2 Hash functions: SHA-1 SHA-224 SHA-256 SHA-384 SHA-512 SHA-512/224 SHA-512/256 (in FIPS 180-4) SHA-3 Hash functions: SHA3-224 SHA3-256 SHA3-384 SHA3-512 and XOFs: SHAKE128 SHAKE256 (in FIPS 202) Algorithm Validation Testing Requirements   FIPS 202, "SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions" Secure Hash Algorithm-3...

Algorithm Specifications Beginning in 2011, validation testing of individual algorithm components was made available. Many situations exist where the specifications of an algorithm standard are implemented in multiple cryptographic boundaries. For example, PIV Smartcard applications may implement one part of an algorithm on the smartcard and another part of the algorithm on the smartcard reader. Possible reasons for implementing an algorithm this way is processing limitations or size constraints. In this situation, the algorithm validation testing of the complete algorithm can't be utilized...

Retired Algorithms And Algorithm Components Current retired testing includes the following algorithms and references: DES Data (Message) Authentication Code (MAC) and Key Management Using ANSI X9.17 Message Authentication Code (MAC), FIPS 113 Key Management Using ANSI X9.17, FIPS 171 Algorithms and/or Algorithm Components as detailed in SP800-131A Revision 1 Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths RNG (FIPS 186-2 with Change Notice 1 dated October 5, 2001 (Appendix 3.1 and 3.2), ANSI X9.31 (Appendix A.2.4) and ANSI...