domains / families / security / security-scanning-security-sast

security-scanning-security-sast

combined

Static Application Security Testing (SAST) for code vulnerability 'Static Application Security Testing (SAST) for code vulnerability

When to use

• Use for code review security analysis, injection vulnerabilities, hardcoded secrets, framework-specific patterns, custom security policy enforcement, pre-deployment validation, legacy code assessment, and compliance (OWASP, PCI-DSS, SOC2).…

When not to use

• You only need runtime testing or penetration testing
• You cannot access the source code or build outputs
• The environment forbids third-party scanning tools
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The first copy is the operational procedure: it contains the actual tool selection, installation commands, configuration files, custom Semgrep rules, and vulnerability pattern examples. The second copy is a wrapper that strips out the procedure and instead mandates reading an external 'detailed guide' and adds generic limitations. Neither copy is a faithful reproduction of the other; the first has the steps the second lacks, and the second has the external-reference constraint and limitations the first lacks. Crowning the first would hide the second's explicit requirement to consult the detailed guide, while crowning the second would hide the actual scanning steps.