sharp-edges

To identify insecure API design patterns and security footguns, analyze your software designs for error-prone patterns and insecure defaults that enable security mistakes. This process focuses on misuse resistance and secure-by-default principles to prevent developer errors.

Dangerous default settings in a configuration schema are insecure configuration options that lead to security vulnerabilities. Auditing these configurations flags dangerous defaults to ensure designs follow secure-by-default principles.

To review an authentication library for misuse resistance, analyze the API specification to detect footguns where the easy path leads to insecurity, such as accidentally disabling signature verification or choosing weak cryptographic modes.

Secure-by-default design in cryptographic ergonomics ensures developers cannot easily misuse APIs by accidentally choosing weak cryptographic modes. It assesses adherence to the pit of success design philosophy to prevent security mistakes.

Yes, you can evaluate threat modeling and common security anti-patterns using this approach. It requires understanding common security anti-patterns and threat modeling to analyze interfaces prone to developer misuse.

You should audit API designs for security footguns and insecure defaults when reviewing new authentication libraries or configuration schemas. This ensures your designs follow secure-by-default principles and prevents accidental security mistakes.