security-review

Security checks for a new API endpoint should cover secrets handling, input validation, access controls, and data exposure. This skill identifies gaps in these areas and specifies concrete mitigations and secure-by-default patterns.

You can audit code for leaked secrets by integrating this skill into CI pipelines to review new code for secret leakage and insecure patterns. It checks authentication, input handling, and API endpoints for vulnerabilities.

Yes, this security review covers authentication and authorization flows. It applies to implementing authentication/authorization and identifies security gaps in access controls across web and mobile projects.

Yes, you can use this for securing third-party integrations. It ensures safe integration with third-party services by checking secrets management, input validation, and data exposure.

The best way to enforce OWASP best practices in a CI pipeline is integrating a security checklist that covers secrets management, input validation, CSRF, and rate limiting to audit new code for insecure patterns.

To check for input validation and CSRF vulnerabilities, apply a comprehensive security checklist covering input handling, authorization, and data exposure to specify concrete mitigations and secure-by-default patterns.