SlideShare une entreprise Scribd logo
1  sur  4
Live Coverage
Waiting for NIST’s view on “password-dependent biometrics”
I posted an article “NIST Conundrum Unraveled” on 27/Oct, in which I referred to my
latest suggestion submitted to NIST that was labeled as "Public Draft".
The change I suggested was [5.2.3 should contain such a sentence as "Biometrics shall
not be operated together with a fallback password by OR/Disjunction (we need only to
go through either of the two) WHERE people want the level of security higher than a
password-only authentication. It could be operated, however, WHERE people want
better convenience rather than better security.”]
In the comment/rationale I added [In view of the observation that most of the biometric
products and solutions on the market and in commercial use are operated with a
fallback password by OR/Disjunction, this outcome might appear too inconvenient for
too many people. But the pains could be overcome soon if tackled right now. Should the
current worrying situation be left as it is, however, the damages that the people
concerned and the public at large have to suffer in the future would certainly be far
more devastating.]
The public draft had been scheduled to be released on 13/Oct. It was already past due
15 days on 28/Oct and it is now overdue by over a month and 10 days past the election.
We could see it released anytime soon.
< Whole text of the suggestion submitted on 15/Sep (#374) >
Reference (Include section and paragraph number): 4.2 and 5.2.3
Comment (Include rationale for comment): 4.2 Authenticator Assurance Level 2
apparently reads that both two factors are required (= we need to go through both of the
two = AND/Conjunction hereafter), whereas 5.2.3 explicitly reads “The biometric system
SHALL allow no more than 10 consecutive failed authentication attempts. Once that
limit has been reached, the claimant SHALL be required to use a different
authenticator or to activate their authenticator with a different factor such as a
memorized secret ( = we need only to go through either of the two = OR/Disjunction
hereafter).
It seems that there are two critical problems here. Firstly, the AND/Conjunction
requirement of 4.2 is just contradictory to the OR/Disjunction requirement of 5.2.3.
Here NIST is far away from having a clearly-defined and consistent criterion.
Secondly, judging from the views that NIST expressed in the thread of my earlier
now-closed suggestion #334, the OR/Disjunction requirement is justified by the issue of
vulnerable account recovery/reset. The vulnerable account recovery/reset is indeed a
major problem in itself but it is wrong to exploit it as a pretext to justify weakening the
user authentication.
Intriguingly, the talk by NIST of vulnerable account recovery/reset destroys the view of
NIST that OR/Disjunction should be encouraged, as specifically analyzed below.
The talk of vulnerable account recovery/reset would appear valid when applied to the
cases of two factors (biometrics and passwords) used by AND/Conjunction, since
biometrics, one of the factors to be invariably passed, is known for frequent rejections
when run at a near-zero false acceptance rates. This results in the necessity of notably
frequent account recovery/reset, which are there for criminals to exploit as NIST
correctly points out. Ironically the conclusion of this discussion is that NIST is wrong in
4.2 which require two factors used by AND/Conjunction.
The above does not mean, however, that the same talk of account recovery/reset would
be valid in the cases of two factors (biometrics and fallback passwords) used by
OR/Disjunction, since logic tells that it is impossible to demonstrate that the
authentication of “either of a password or a rejection-prone biometrics” brings notably
fewer chances of account recovery/reset than a password-only authentication.
As such the talk of vulnerable account recovery/reset does not give any positive effect on
the issue of “the larger attack surfaces” brought about by “being able to use either of two
authenticators is less secure than only having one”.
The remaining fact is that the security of biometrics used with a fallback password by
OR/Disjunction is clearly lower than that of a password-only authentication. It should
be viewed as “below-one” factor authentication.
A shortage of security is not so serious a problem when people are aware of it as it is.
But the false sense of security (we wrongly feel safer when we are actually less safe) is
different. What I wish to see the least is NIST not only failing to prevent it but working
as a major source of it.
In view of the observation that most of the biometric products and solutions on the
market and in commercial use are operated with a fallback password by OR/Disjunction,
this outcome might appear too inconvenient for too many people. But the pains could be
overcome soon if tackled right now. Should the current worrying situation be left as it is,
however, the damages that the people concerned and the public at large have to suffer in
the future would certainly be far more devastating.
Being aware of this now, NIST is expected to act most quickly”.
Suggested Change: 5.2.3 should contain such a sentence as "Biometrics shall not be
operated together with a fallback password by OR/Disjunction (we need only to go
through either of the two) WHERE people want the level of security higher than a
password-only authentication. It could be operated, however, WHERE people want
better convenience rather than better security.”
< References >
NIST Conundrum Unraveled
http://www.slideshare.net/HitoshiKokumai/nist-conundrum-unraveled
DRAFT NIST Special Publication 800-63B Digital Authentication Guideline
https://pages.nist.gov/800-63-3/sp800-63b.html
Suggestion #374: Factors for Authentication Assurance Level 2 need to be clearly
defined
https://github.com/usnistgov/800-63-3/issues/374#event-804359364
Public Draft
https://github.com/usnistgov/800-63-3/milestone/5

Contenu connexe

Plus de Hitoshi Kokumai

Intriguing Evlolution from One to Two and Back to One
Intriguing Evlolution from One to Two and Back to OneIntriguing Evlolution from One to Two and Back to One
Intriguing Evlolution from One to Two and Back to OneHitoshi Kokumai
 
Cyber Predicament by Text-Only Password Systems
Cyber Predicament by Text-Only Password SystemsCyber Predicament by Text-Only Password Systems
Cyber Predicament by Text-Only Password SystemsHitoshi Kokumai
 
Updated: Presentation with Scripts at CIW2018
Updated:  Presentation with Scripts at CIW2018Updated:  Presentation with Scripts at CIW2018
Updated: Presentation with Scripts at CIW2018Hitoshi Kokumai
 
Presentation with Scripts at CIWEU2018
Presentation with Scripts at CIWEU2018Presentation with Scripts at CIWEU2018
Presentation with Scripts at CIWEU2018Hitoshi Kokumai
 
Updated: Identity Assurance by Our Own Volition and Memory
Updated: Identity Assurance by Our Own Volition and MemoryUpdated: Identity Assurance by Our Own Volition and Memory
Updated: Identity Assurance by Our Own Volition and MemoryHitoshi Kokumai
 
Deployment of Biometrics & Password - NIST63B
Deployment of Biometrics & Password - NIST63BDeployment of Biometrics & Password - NIST63B
Deployment of Biometrics & Password - NIST63BHitoshi Kokumai
 
Clues to Unravelling Conundrums - Biometrics deployed 'in parallel' as again...
Clues to Unravelling  Conundrums - Biometrics deployed 'in parallel' as again...Clues to Unravelling  Conundrums - Biometrics deployed 'in parallel' as again...
Clues to Unravelling Conundrums - Biometrics deployed 'in parallel' as again...Hitoshi Kokumai
 
Business Dimension of Expanded Password System
Business Dimension of Expanded Password SystemBusiness Dimension of Expanded Password System
Business Dimension of Expanded Password SystemHitoshi Kokumai
 
Expanded password system - Reliable Identity Assurance
Expanded password system - Reliable Identity AssuranceExpanded password system - Reliable Identity Assurance
Expanded password system - Reliable Identity AssuranceHitoshi Kokumai
 

Plus de Hitoshi Kokumai (9)

Intriguing Evlolution from One to Two and Back to One
Intriguing Evlolution from One to Two and Back to OneIntriguing Evlolution from One to Two and Back to One
Intriguing Evlolution from One to Two and Back to One
 
Cyber Predicament by Text-Only Password Systems
Cyber Predicament by Text-Only Password SystemsCyber Predicament by Text-Only Password Systems
Cyber Predicament by Text-Only Password Systems
 
Updated: Presentation with Scripts at CIW2018
Updated:  Presentation with Scripts at CIW2018Updated:  Presentation with Scripts at CIW2018
Updated: Presentation with Scripts at CIW2018
 
Presentation with Scripts at CIWEU2018
Presentation with Scripts at CIWEU2018Presentation with Scripts at CIWEU2018
Presentation with Scripts at CIWEU2018
 
Updated: Identity Assurance by Our Own Volition and Memory
Updated: Identity Assurance by Our Own Volition and MemoryUpdated: Identity Assurance by Our Own Volition and Memory
Updated: Identity Assurance by Our Own Volition and Memory
 
Deployment of Biometrics & Password - NIST63B
Deployment of Biometrics & Password - NIST63BDeployment of Biometrics & Password - NIST63B
Deployment of Biometrics & Password - NIST63B
 
Clues to Unravelling Conundrums - Biometrics deployed 'in parallel' as again...
Clues to Unravelling  Conundrums - Biometrics deployed 'in parallel' as again...Clues to Unravelling  Conundrums - Biometrics deployed 'in parallel' as again...
Clues to Unravelling Conundrums - Biometrics deployed 'in parallel' as again...
 
Business Dimension of Expanded Password System
Business Dimension of Expanded Password SystemBusiness Dimension of Expanded Password System
Business Dimension of Expanded Password System
 
Expanded password system - Reliable Identity Assurance
Expanded password system - Reliable Identity AssuranceExpanded password system - Reliable Identity Assurance
Expanded password system - Reliable Identity Assurance
 

Dernier

Data Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt RobisonData Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt RobisonAnna Loughnan Colquhoun
 
Understanding the Laravel MVC Architecture
Understanding the Laravel MVC ArchitectureUnderstanding the Laravel MVC Architecture
Understanding the Laravel MVC ArchitecturePixlogix Infotech
 
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerHow to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerThousandEyes
 
A Call to Action for Generative AI in 2024
A Call to Action for Generative AI in 2024A Call to Action for Generative AI in 2024
A Call to Action for Generative AI in 2024Results
 
Salesforce Community Group Quito, Salesforce 101
Salesforce Community Group Quito, Salesforce 101Salesforce Community Group Quito, Salesforce 101
Salesforce Community Group Quito, Salesforce 101Paola De la Torre
 
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdfThe Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdfEnterprise Knowledge
 
Transcript: #StandardsGoals for 2024: What’s new for BISAC - Tech Forum 2024
Transcript: #StandardsGoals for 2024: What’s new for BISAC - Tech Forum 2024Transcript: #StandardsGoals for 2024: What’s new for BISAC - Tech Forum 2024
Transcript: #StandardsGoals for 2024: What’s new for BISAC - Tech Forum 2024BookNet Canada
 
The 7 Things I Know About Cyber Security After 25 Years | April 2024
The 7 Things I Know About Cyber Security After 25 Years | April 2024The 7 Things I Know About Cyber Security After 25 Years | April 2024
The 7 Things I Know About Cyber Security After 25 Years | April 2024Rafal Los
 
Maximizing Board Effectiveness 2024 Webinar.pptx
Maximizing Board Effectiveness 2024 Webinar.pptxMaximizing Board Effectiveness 2024 Webinar.pptx
Maximizing Board Effectiveness 2024 Webinar.pptxOnBoard
 
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...Miguel Araújo
 
08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
08448380779 Call Girls In Diplomatic Enclave Women Seeking Men08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
08448380779 Call Girls In Diplomatic Enclave Women Seeking MenDelhi Call girls
 
Breaking the Kubernetes Kill Chain: Host Path Mount
Breaking the Kubernetes Kill Chain: Host Path MountBreaking the Kubernetes Kill Chain: Host Path Mount
Breaking the Kubernetes Kill Chain: Host Path MountPuma Security, LLC
 
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...shyamraj55
 
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure service
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure serviceWhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure service
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure servicePooja Nehwal
 
Neo4j - How KGs are shaping the future of Generative AI at AWS Summit London ...
Neo4j - How KGs are shaping the future of Generative AI at AWS Summit London ...Neo4j - How KGs are shaping the future of Generative AI at AWS Summit London ...
Neo4j - How KGs are shaping the future of Generative AI at AWS Summit London ...Neo4j
 
08448380779 Call Girls In Civil Lines Women Seeking Men
08448380779 Call Girls In Civil Lines Women Seeking Men08448380779 Call Girls In Civil Lines Women Seeking Men
08448380779 Call Girls In Civil Lines Women Seeking MenDelhi Call girls
 
Slack Application Development 101 Slides
Slack Application Development 101 SlidesSlack Application Development 101 Slides
Slack Application Development 101 Slidespraypatel2
 
Histor y of HAM Radio presentation slide
Histor y of HAM Radio presentation slideHistor y of HAM Radio presentation slide
Histor y of HAM Radio presentation slidevu2urc
 
Google AI Hackathon: LLM based Evaluator for RAG
Google AI Hackathon: LLM based Evaluator for RAGGoogle AI Hackathon: LLM based Evaluator for RAG
Google AI Hackathon: LLM based Evaluator for RAGSujit Pal
 
08448380779 Call Girls In Friends Colony Women Seeking Men
08448380779 Call Girls In Friends Colony Women Seeking Men08448380779 Call Girls In Friends Colony Women Seeking Men
08448380779 Call Girls In Friends Colony Women Seeking MenDelhi Call girls
 

Dernier (20)

Data Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt RobisonData Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt Robison
 
Understanding the Laravel MVC Architecture
Understanding the Laravel MVC ArchitectureUnderstanding the Laravel MVC Architecture
Understanding the Laravel MVC Architecture
 
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerHow to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
 
A Call to Action for Generative AI in 2024
A Call to Action for Generative AI in 2024A Call to Action for Generative AI in 2024
A Call to Action for Generative AI in 2024
 
Salesforce Community Group Quito, Salesforce 101
Salesforce Community Group Quito, Salesforce 101Salesforce Community Group Quito, Salesforce 101
Salesforce Community Group Quito, Salesforce 101
 
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdfThe Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
 
Transcript: #StandardsGoals for 2024: What’s new for BISAC - Tech Forum 2024
Transcript: #StandardsGoals for 2024: What’s new for BISAC - Tech Forum 2024Transcript: #StandardsGoals for 2024: What’s new for BISAC - Tech Forum 2024
Transcript: #StandardsGoals for 2024: What’s new for BISAC - Tech Forum 2024
 
The 7 Things I Know About Cyber Security After 25 Years | April 2024
The 7 Things I Know About Cyber Security After 25 Years | April 2024The 7 Things I Know About Cyber Security After 25 Years | April 2024
The 7 Things I Know About Cyber Security After 25 Years | April 2024
 
Maximizing Board Effectiveness 2024 Webinar.pptx
Maximizing Board Effectiveness 2024 Webinar.pptxMaximizing Board Effectiveness 2024 Webinar.pptx
Maximizing Board Effectiveness 2024 Webinar.pptx
 
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
 
08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
08448380779 Call Girls In Diplomatic Enclave Women Seeking Men08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
 
Breaking the Kubernetes Kill Chain: Host Path Mount
Breaking the Kubernetes Kill Chain: Host Path MountBreaking the Kubernetes Kill Chain: Host Path Mount
Breaking the Kubernetes Kill Chain: Host Path Mount
 
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
 
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure service
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure serviceWhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure service
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure service
 
Neo4j - How KGs are shaping the future of Generative AI at AWS Summit London ...
Neo4j - How KGs are shaping the future of Generative AI at AWS Summit London ...Neo4j - How KGs are shaping the future of Generative AI at AWS Summit London ...
Neo4j - How KGs are shaping the future of Generative AI at AWS Summit London ...
 
08448380779 Call Girls In Civil Lines Women Seeking Men
08448380779 Call Girls In Civil Lines Women Seeking Men08448380779 Call Girls In Civil Lines Women Seeking Men
08448380779 Call Girls In Civil Lines Women Seeking Men
 
Slack Application Development 101 Slides
Slack Application Development 101 SlidesSlack Application Development 101 Slides
Slack Application Development 101 Slides
 
Histor y of HAM Radio presentation slide
Histor y of HAM Radio presentation slideHistor y of HAM Radio presentation slide
Histor y of HAM Radio presentation slide
 
Google AI Hackathon: LLM based Evaluator for RAG
Google AI Hackathon: LLM based Evaluator for RAGGoogle AI Hackathon: LLM based Evaluator for RAG
Google AI Hackathon: LLM based Evaluator for RAG
 
08448380779 Call Girls In Friends Colony Women Seeking Men
08448380779 Call Girls In Friends Colony Women Seeking Men08448380779 Call Girls In Friends Colony Women Seeking Men
08448380779 Call Girls In Friends Colony Women Seeking Men
 

Waiting for NIST's view on "password-dependent biometrics"

  • 1. Live Coverage Waiting for NIST’s view on “password-dependent biometrics” I posted an article “NIST Conundrum Unraveled” on 27/Oct, in which I referred to my latest suggestion submitted to NIST that was labeled as "Public Draft". The change I suggested was [5.2.3 should contain such a sentence as "Biometrics shall not be operated together with a fallback password by OR/Disjunction (we need only to go through either of the two) WHERE people want the level of security higher than a password-only authentication. It could be operated, however, WHERE people want better convenience rather than better security.”] In the comment/rationale I added [In view of the observation that most of the biometric products and solutions on the market and in commercial use are operated with a fallback password by OR/Disjunction, this outcome might appear too inconvenient for too many people. But the pains could be overcome soon if tackled right now. Should the current worrying situation be left as it is, however, the damages that the people concerned and the public at large have to suffer in the future would certainly be far more devastating.] The public draft had been scheduled to be released on 13/Oct. It was already past due 15 days on 28/Oct and it is now overdue by over a month and 10 days past the election. We could see it released anytime soon.
  • 2. < Whole text of the suggestion submitted on 15/Sep (#374) > Reference (Include section and paragraph number): 4.2 and 5.2.3 Comment (Include rationale for comment): 4.2 Authenticator Assurance Level 2 apparently reads that both two factors are required (= we need to go through both of the two = AND/Conjunction hereafter), whereas 5.2.3 explicitly reads “The biometric system SHALL allow no more than 10 consecutive failed authentication attempts. Once that limit has been reached, the claimant SHALL be required to use a different authenticator or to activate their authenticator with a different factor such as a memorized secret ( = we need only to go through either of the two = OR/Disjunction hereafter). It seems that there are two critical problems here. Firstly, the AND/Conjunction requirement of 4.2 is just contradictory to the OR/Disjunction requirement of 5.2.3. Here NIST is far away from having a clearly-defined and consistent criterion. Secondly, judging from the views that NIST expressed in the thread of my earlier now-closed suggestion #334, the OR/Disjunction requirement is justified by the issue of vulnerable account recovery/reset. The vulnerable account recovery/reset is indeed a major problem in itself but it is wrong to exploit it as a pretext to justify weakening the user authentication. Intriguingly, the talk by NIST of vulnerable account recovery/reset destroys the view of NIST that OR/Disjunction should be encouraged, as specifically analyzed below. The talk of vulnerable account recovery/reset would appear valid when applied to the cases of two factors (biometrics and passwords) used by AND/Conjunction, since biometrics, one of the factors to be invariably passed, is known for frequent rejections when run at a near-zero false acceptance rates. This results in the necessity of notably frequent account recovery/reset, which are there for criminals to exploit as NIST correctly points out. Ironically the conclusion of this discussion is that NIST is wrong in 4.2 which require two factors used by AND/Conjunction.
  • 3. The above does not mean, however, that the same talk of account recovery/reset would be valid in the cases of two factors (biometrics and fallback passwords) used by OR/Disjunction, since logic tells that it is impossible to demonstrate that the authentication of “either of a password or a rejection-prone biometrics” brings notably fewer chances of account recovery/reset than a password-only authentication. As such the talk of vulnerable account recovery/reset does not give any positive effect on the issue of “the larger attack surfaces” brought about by “being able to use either of two authenticators is less secure than only having one”. The remaining fact is that the security of biometrics used with a fallback password by OR/Disjunction is clearly lower than that of a password-only authentication. It should be viewed as “below-one” factor authentication. A shortage of security is not so serious a problem when people are aware of it as it is. But the false sense of security (we wrongly feel safer when we are actually less safe) is different. What I wish to see the least is NIST not only failing to prevent it but working as a major source of it. In view of the observation that most of the biometric products and solutions on the market and in commercial use are operated with a fallback password by OR/Disjunction, this outcome might appear too inconvenient for too many people. But the pains could be overcome soon if tackled right now. Should the current worrying situation be left as it is, however, the damages that the people concerned and the public at large have to suffer in the future would certainly be far more devastating. Being aware of this now, NIST is expected to act most quickly”. Suggested Change: 5.2.3 should contain such a sentence as "Biometrics shall not be operated together with a fallback password by OR/Disjunction (we need only to go through either of the two) WHERE people want the level of security higher than a password-only authentication. It could be operated, however, WHERE people want better convenience rather than better security.”
  • 4. < References > NIST Conundrum Unraveled http://www.slideshare.net/HitoshiKokumai/nist-conundrum-unraveled DRAFT NIST Special Publication 800-63B Digital Authentication Guideline https://pages.nist.gov/800-63-3/sp800-63b.html Suggestion #374: Factors for Authentication Assurance Level 2 need to be clearly defined https://github.com/usnistgov/800-63-3/issues/374#event-804359364 Public Draft https://github.com/usnistgov/800-63-3/milestone/5