security-and-hardening

Preventing XSS and CSRF vulnerabilities involves treating every external input as hostile and enforcing secure defaults. This Skill provides guidance for input validation, secure session management, and applying security headers to harden data transmission.

Securing authentication and authorization in API services requires treating every authorization check as mandatory. This Skill enforces least privilege in API interactions and implements guidance for secure session management and sensitive data handling.

Input validation for secure coding works by systematically treating all external inputs as hostile. This Skill identifies and enforces security best practices across input handling to prevent common vulnerabilities in web and API services.

Yes, this security guidance is applicable to development workflows and code reviews. It bakes security-first practices into your development lifecycle to enforce secure defaults and reduce risk across user data and external integrations.

You need to implement security headers and secure session management whenever code touches user data, authentication, or external systems. This Skill treats security as a continuous constraint, applying best practices from the start of development.

Treating every external input as hostile is a security-first constraint rather than a limitation. It ensures secure defaults across input handling, authentication, and data transmission, reducing risk without specifying particular framework dependencies.