Use of Single-factor Authentication |
Weakness ID: 308 (Weakness Base) | Status: Draft |
Description Summary
Extended Description
While the use of multiple authentication schemes is simply piling on more complexity on top of authentication, it is inestimably valuable to have such measures of redundancy. The use of weak, reused, and common passwords is rampant on the internet. Without the added protection of multiple authentication schemes, a single mistake can result in the compromise of an account. For this reason, if multiple schemes are possible and also easy to use, they should be implemented and required.
Scope | Effect |
---|---|
Authentication | If the secret in a single-factor authentication scheme gets compromised, full authentication is possible. |
Example 1
Phase: Architecture and Design Use multiple independent authentication schemes, which ensures that -- if one of the methods is compromised -- the system itself is still likely safe from compromise. |
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 287 | Improper Authentication | Development Concepts (primary)699 Research Concepts (primary)1000 |
ChildOf | ![]() | 654 | Reliance on a Single Factor in a Security Decision | Research Concepts1000 |
PeerOf | ![]() | 309 | Use of Password System for Primary Authentication | Research Concepts1000 |
Mapped Taxonomy Name | Node ID | Fit | Mapped Node Name |
---|---|---|---|
CLASP | Using single-factor authentication |
Submissions | ||||
---|---|---|---|---|
Submission Date | Submitter | Organization | Source | |
CLASP | Externally Mined | |||
Modifications | ||||
Modification Date | Modifier | Organization | Source | |
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Common Consequences, Relationships, Other Notes, Taxonomy Mappings | ||||
Previous Entry Names | ||||
Change Date | Previous Entry Name | |||
2008-04-11 | Using Single-factor Authentication | |||