Password Aging with Long Expiration |
Weakness ID: 263 (Weakness Base) | Status: Draft |
Password Aging with Long Expiration |
Weakness ID: 263 (Weakness Base) | Status: Draft |
Description Summary
Scope | Effect |
---|---|
Authentication | As passwords age, the probability that they are compromised grows. |
Example 1
A common example is not having a system to terminate old employee accounts.
Example 2
Not having a system for enforcing the changing of passwords every certain period.
Phase: Architecture and Design Ensure that password aging is limited so that there is a defined maximum age for passwords and so that the user is notified several times leading up to the password expiration. |
Just as neglecting to include functionality for the management of password aging is dangerous, so is allowing password aging to continue unchecked. Passwords must be given a maximum life span, after which a user is required to update with a new and different password. |
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 255 | Credentials Management | Development Concepts (primary)699 |
ChildOf | ![]() | 404 | Improper Resource Shutdown or Release | Research Concepts (primary)1000 |
PeerOf | ![]() | 262 | Not Using Password Aging | Research Concepts1000 |
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 | Allowing Unchecked Password Aging | |||
Security-Database help your corporation foresee and avoid any security risks that may impact your IT infrastructure and business applications.