Lack of Administrator Control over Security |
Weakness ID: 671 (Weakness Class) | Status: Draft |
Description Summary
The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect the environment in which the product is being used. This introduces resultant weaknesses or prevents it from operating at a level of security that is desired by the administrator.
Extended Description
If the product's administrator does not have the ability to manage security-related decisions at all times, then protecting the product from outside threats - including the product's developer - can become impossible. For example, a hard-coded account name and password cannot be changed by the administrator, thus exposing that product to attacks that the administrator can not prevent.
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 657 | Violation of Secure Design Principles | Development Concepts (primary)699 Research Concepts (primary)1000 |
ParentOf | ![]() | 259 | Use of Hard-coded Password | Research Concepts1000 |
ParentOf | ![]() | 321 | Use of Hard-coded Cryptographic Key | Research Concepts1000 |
ParentOf | ![]() | 447 | Unimplemented or Unsupported Feature in UI | Research Concepts (primary)1000 |
ParentOf | ![]() | 798 | Use of Hard-coded Credentials | Research Concepts1000 |
Modifications | ||||
---|---|---|---|---|
Modification Date | Modifier | Organization | Source | |
2008-07-01 | Eric Dalci | Cigital | External | |
updated Time of Introduction | ||||
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Description, Relationships | ||||
2009-01-12 | CWE Content Team | MITRE | Internal | |
updated Description, Name | ||||
Previous Entry Names | ||||
Change Date | Previous Entry Name | |||
2009-01-12 | Design Principle Violation: Lack of Administrator Control over Security | |||