secure-code-guardian

Secure authentication and authorization requires enforcing password hashing with bcrypt or argon2, token-based authentication, and strict session management. This skill provides defensive coding patterns to implement these mechanisms and reduce OWASP risks across web and API services.

Preventing OWASP vulnerabilities involves applying structured threat modeling and secure design guidance early in development. This approach mitigates risks from insecure coding practices by enforcing parameterized queries, input validation, and secure configuration before deployment.

Securely hashing passwords and handling tokens requires using proven algorithms like bcrypt or argon2 for storage and applying safe token-based authentication practices. This skill provides production-ready templates to ensure secure session management.

Yes, secure coding guidance applies to both web applications and API services. It provides practical templates and references for implementing secure headers, parameterized queries, and comprehensive logging across languages and tech stacks.

Configuring secure headers and implementing comprehensive logging requires applying structured secure configuration practices. This skill enforces these requirements alongside input validation and encryption to identify and mitigate security risks in application code.

Threat modeling and secure design guidance are needed to identify and mitigate security risks stemming from insecure coding practices and misconfigurations. This skill provides structured guidance to prevent vulnerabilities during development and deployment.