This weakness occurs when security features are so cumbersome or confusing that well-intentioned users feel forced to turn them off or find workarounds, defeating their purpose entirely.
At its core, this is a design failure that prioritizes theoretical security over real-world usability. When features like complex password rules, frequent re-authentication prompts, or convoluted privacy settings create significant friction, users will naturally seek the path of least resistance. This often means disabling the protection altogether, using weak passwords to meet requirements, or sharing credentials to avoid login hassles—actions that introduce far greater risk than the feature was meant to prevent. To avoid this, security must be baked into the user experience, not bolted on as an obstacle. Developers should design controls that are intuitive, context-aware, and minimally invasive. For example, offering biometric authentication alongside passwords, using risk-based authentication to reduce unnecessary prompts, or providing clear, immediate value for security actions. The goal is to make the secure choice the easiest and most obvious one, aligning security objectives with natural user behavior rather than fighting against it.
Impact: Bypass Protection Mechanism
By bypassing the security mechanism, a user might leave the system in a less secure state than intended by the administrator, making it more susceptible to compromise.