Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

added faq on procured requirement #23

Merged
merged 2 commits into from
Jul 5, 2020
Merged

added faq on procured requirement #23

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a82898e
added faq on procured requirement
jricher Jul 2, 2020
060a257
Apply suggestions from code review
jricher Jul 2, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 6 additions & 0 deletions _63B/procured.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
---
question: B18
title: What process does "procured" refer to when talking about authenticators?
jricher marked this conversation as resolved.
Show resolved Hide resolved
---

[800-63B section 4.2.2](https://pages.nist.gov/800-63-3/sp800-63b.html#aal2req) states that "Authenticators _procured by_ government agencies SHALL be validated to meet the requirements of FIPS 140 Level 1." (emphasis added) The intent of the _procured by_ language is to exempt user-provided ("bring-your-own") authenticators from having to meet FIPS 140 requirements, particularly in the government-to-public use case. The FIPS 140 requirement applies only to authenticators directly purchased and/or issued by a government agency.
jricher marked this conversation as resolved.
Show resolved Hide resolved