The National Institute of Standards and Technology (NIST) requests comments on Draft Federal Information Processing Standard (FIPS) 201-3, Personal Identity Verification (PIV) of Federal Employees and Contractors (Standard). This Standard defines common credentials and authentication mechanisms offering varying degrees of security for both logical and physical access applications. The draft revision proposes changes to FIPS 201-2, Standard for Personal Identity Verification of Federal Employees and Contractors to include: expanding specification on the use of additional PIV credentials known as derived PIV credentials, procedures for supervised remote identity proofing, the use of federation as a means for a relying system to interoperate with PIV credentials issued by other agencies, alignment with the current practice/policy of the Federal Government and specific changes requested by Federal agencies and implementers.
The draft of FIPS 201-3 is available for review and comment on the NIST Pages website at https://pages.nist.gov/FIPS201/. A printable PDF is available on the NIST Computer Security Resource Center at https://csrc.nist.gov/publications/detail/fips/201/3/draft.
Comments on FIPS 201-3 must be received on or before February 1, 2021. Comments should be submitted on the project repository at https://github.com/usnistgov/FIPS201/issues. Comments may alternatively be sent to piv_comments@nist.gov preferably using the comment template available at https://csrc.nist.gov/publications/detail/fips/201/3/draft.
All submissions, including attachments and other supporting materials, will become part of the public record and subject to public disclosure. NIST reserves the right to publish relevant comments, unedited and in their entirety. Relevant comments received by the deadline will be published electronically at https://github.com/usnistgov/FIPS201 without change or redaction, so commenters should not include information they do not wish to be posted. Personal information, such as account numbers or Social Security numbers, or names of other individuals, should not be included. Do not submit confidential business information or otherwise sensitive or protected information. Comments that contain profanity, vulgarity, threats, or other inappropriate language or content will not be posted or considered.
If you wish to generate the document directly from its source, see the build instructions.