Usable security designs security mechanisms and interfaces so people can handle cryptography correctly with minimal opportunity for misuse. It treats user error as a design problem rather than a reason to blame users. section 16.5 section 16.8
Practical strategies include:
- Make security features transparent and reduce the number of decisions users must get right. section 16.5
- Replace fragile expectations, such as strong unique passwords, with mechanisms such as second-factor authentication. section 16.5
- Use conservative, tried-and-tested designs that are difficult to implement or configure badly. section 16.8
Warnings users click through
Browsers moved from simple invalid SSL/TLS certificate warnings toward making risky acceptance harder. Warning fatigue still matters: Google Chrome users clicked through common SSL errors at rates as high as 70.2%. section 16.5
