Search CSRC

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

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

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

FIPS 140-3 Logo Usage and Application What are the official FIPS 140-3 validated product logos? or For validated products, the logo must be accompanied by the "FIPS 140-3 Validated" and the certificate number. If a product has a FIPS 140-3 module internal to the product, "FIPS 140-3 Inside" and the certificate number must also accompany the logo. The FIPS 140-3 logo is a Certification Mark of NIST, which does not imply product endorsement by NIST, the U.S. or Canadian Governments. What are the guidelines for the use of the FIPS 140-3 logo? Both phrases "FIPS 140-3 Validated" and...

2018 Notices [11-30-2018] CMVP Validation Policy The CMVP has a long history of performing validations that show conformance to the FIPS 140-2 standard on any cryptographic module from anywhere in the world regardless of country of origin and/or company. The US Government passed the National Defense Authorization Act (NDAA) for Fiscal Year 2019 on 13 Aug 2018, which contains language that restricts federal agencies from engaging in business with certain named companies. US government agencies will be held accountable to ensure that they are not doing business with the companies...

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

ARCHIVED PROJECT: This project is no longer being supported. The content is no longer being updated, and the information may be outdated. Many organizations are in the process of moving to role based access control. The process of developing an RBAC structure for an organization has become known as "role engineering.". Role engineering can be a complex undertaking, For example, in implementing RBAC for a large European bank with over 50,000 employees and 1400 branches serving more than 6 million customers, approximately 1300 roles were discovered. In view of the complexities, RBAC is...

The suite of NIST information security risk management standards and guidelines is not a "FISMA Compliance checklist." Federal agencies, contractors, and other sources that use or operate a federal information system use the suite of NIST Risk Management standards and guidelines to develop and implement a risk-based approach to manage information security risk. FISMA emphasizes the importance of risk management. Compliance with applicable laws, regulations, executive orders, directives, etc. is a byproduct of implementing a robust, risk-based information security program. The NIST Risk...

A Comprehensive, Flexible, Risk-Based Approach The Risk Management Framework (RMF) provides a process that integrates security, privacy, and cyber supply chain risk management activities into the system development life cycle. The risk-based approach to control selection and specification considers effectiveness, efficiency, and constraints due to applicable laws, directives, Executive Orders, policies, standards, or regulations. Managing organizational risk is paramount to effective information security and privacy programs; the RMF approach can be applied to new and legacy systems, any type...

The purpose of these courses is to provide those new to risk management with an introduction to key publications associated with the NIST Risk Management Framework (RMF) methodology for managing cybersecurity and privacy risk. The RMF Online Introductory Courses are developed by NIST and available on-demand, and free of charge. Please refer first to the FAQ below for questions about course logistics, topics and content, initial troubleshooting of issues, and certificate of completion and course credit before reaching out to the team with questions. Select a course below to learn...

The SCAP Release Cycle Changes to SCAP impact a large number of organizations that manage content and provide SCAP Validated Products and Modules and SCAP-related services. A change to SCAP often results in considerable efforts to migrate products, content, and other capabilities to the new SCAP revision. To mitigate risks relating to level-of-effort, timing, and specification changes, revisions to SCAP are managed according to a coordinated process. The following work flow process addresses these concerns. The SCAP release cycle defines a process for managing change relating to SCAP and the...

SCAP must evolve continuously to meet the changing needs of the community. As a result, multiple versions of SCAP may be available at any given time. The following list presents the versions that are currently available. The current effective version is SCAP 1.3. Protocol SCAP: Security Content Automation Protocol Version: 1.4 (IPD) Status: IPD (Initial Public Distribution) Specification: NIST SP 800-126 Rev. 4 Annex: NIST SP 800-126 Rev. 4 Annex SCAP: Security Content Automation Protocol Version: 1.3 Status: Final Specification: NIST SP 800-126 Rev. 3 Annex: NIST SP 800-126 Rev....

The SCAP community is a public/private partnership consisting of interested parties from industry, research and educational institutions, and government that are working to advance automation and standardization of technical security operations. Involvement in SCAP extends to email-based discussion lists, conferences, and various technical working groups sponsored by a variety of organizations. SCAP Email Discussion Lists SCAP Discussion List (View and Subscribe) The SCAP team at NIST maintains a moderated discussion list that users can post to, regarding the Security Content Automation...

2017.01.27 - Microsoft Virtual PC Windows 7 32-bit VHD (USGCB-Windows7-VPC-x86-1.1.x.0-20110124.zip) - End of Life (EOL). This VHD is no longer supported and is unavailable. 2015.04.20 - USGCB SCAP 1.2 Content Final Release for Microsoft Windows XP, Windows Vista, Windows 7, Windows XP Firewall, Windows Vista Firewall, Windows 7 Firewall, Internet Explorer 7, and Internet Explorer 8 posted. 2015.02.25 - USGCB SCAP 1.2 Content Release Candidate 1 for Microsoft Windows XP, Windows Vista, Windows 7, Windows XP Firewall, Windows Vista Firewall, Windows 7 Firewall, Internet Explorer 7, and...

The following is a list of algorithms with example values for each algorithm. This list may not always accurately reflect all Approved* algorithms. Please refer to the actual algorithm specification pages for the most accurate list of algorithms. Encryption - Block Ciphers Visit the Block Cipher Techniques Page FIPS 197 - Advanced Encryption Standard (AES) AES-AllSizes AES-128 AES-192 AES-256 SP 800-67 - Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher TDES FIPS 185 - Escrowed Encryption Standard containing the Skipjack algorithm Skipjack...

NIST S/MIME Activities NIST has developed a NIST SP 800-49, Federal S/MIME V3 Client Profile for security and interoperability based on IETF specifications. The profile includes all mandatory features of the (S/MIME V3) IETF RFCs (RFCs 2630 through 2634) with the EXCEPTION that implementation of RFC 2631 Diffie-Hellman Key Agreement cryptographic algorithm mandated in IETF RFC 2630 is NOT required. In addition, the profile mandates certain optional features required for interoperability and security in secure email products. The primary audience is federal agencies, but the profile may be...

The circuit files with the straight-line programs (SLPs) are stored in our GitHub page, here: https://github.com/usnistgov/Circuits/tree/master/data/slp AES implementations S-Box and Inverse S-Box: A<=27; G<=100; G<=110/GD<=14. MixColumns: G<=86; G<=93/GD3. Inverse MixColumns: G<=105/GD<=5. #AND = 28 Tuple Metric Link #AND (A) AND depth (AD) #Gates (G) Gate depth (GD) #XOR + #XNOR A/AD/G circ 28 4 131 32 103 A/AD/GD circ 28 4 177 14 149 A/G circ 28 5...

In March 2019, NIST received 57 submissions to be considered for standardization. The first round of the NIST lightweight cryptography standardization process began with the announcement of 56 Round 1 Candidates in April 2019 and ended in August 2019. The status report on the first round is available here. The following table lists the Round 1 Candidates: History of Updates Download all Zip Files (53 MB) does not include IP Statements Candidate Algorithm Information Submitters Comments ACE Zip File...

The second round of the NIST lightweight cryptography standardization process began when NIST announced the 32 Round 2 Candidates in August 2019. Round 2 concluded when the finalists were announced in March 2021. The status report on the second round is available here. The following table lists the Round 2 Candidates: History of Round 2 Updates Download all Round 2 Zip Files (96 MB) Candidate Algorithm Information Submitters Comments ACE Zip File (2MB) Specification Changelog Algorithm Update (Sep 2020) Website...

Workshops Date September 24-26, 2025 Sixth PQC Standardization Conference (In-Person / Virtual) Venue: NIST Gaithersburg, Maryland, USA Call for Papers April 10-12, 2024 Fifth PQC Standardization Conference (In-Person) Hilton Washington DC/Rockville Hotel Rockville, MD Call for Papers November 29- December 1, 2022 Fourth PQC Standardization Conference Virtual Call for Papers June 7-9, 2021 Third...

Zero-Knowledge Proof (ZKP) is an important Privacy-Enhancing Cryptography (PEC) technique. It enables proving the truthfulness of a mathematical statement, without revealing information that may have been useful in finding said truthfulness and is not apparent in the statement. Besides myriad privacy-preserving applications, ZKPs are also useful in establishing correct behavior in other cryptography protocols, such as in Secure Multi-Party Computation (MPC). The NIST PEC project is accompanying ZKP developments and initiatives toward future useful standards. For technical reasons, it is...