security-scanning

CI security scanning: secrets, deps, SAST, triage, expiring exceptions

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 29, 2025

When & Why to Use This Skill

This Claude skill automates essential security scanning within CI/CD pipelines, integrating secret detection, dependency analysis, and Static Application Security Testing (SAST). It streamlines the DevSecOps workflow by providing automated vulnerability triage and managing expiring security exceptions to ensure continuous compliance without hindering development velocity.

Use Cases

  • Automated Secret Detection: Prevent the accidental exposure of sensitive credentials like API keys and tokens by scanning code during every CI build.
  • Software Supply Chain Security: Identify and gate critical vulnerabilities in third-party dependencies to protect the application from supply chain attacks.
  • Static Application Security Testing (SAST): Conduct deep code analysis to detect security flaws such as SQL injection or XSS early in the software development lifecycle (SDLC).
  • Vulnerability Triage and Exception Management: Facilitate a structured process for reviewing security findings and managing time-bound exceptions with clear ownership and reasoning.
namesecurity-scanning
description"CI security scanning: secrets, deps, SAST, triage, expiring exceptions"
version1.1.0
categoryuniversal
authorClaude MPM Team
licenseMIT
summary"Baseline CI scans (secrets, deps, SAST) with triage and expiring exceptions"
tags[security, scanning]

Security Scanning

Quick Start

  • Secrets: fail fast; rotate on exposure.
  • Dependencies: gate critical/high; automate updates.
  • SAST: start high-signal; ratchet over time.
  • Exceptions: require reason, owner, and expiry.

Load Next (References)

  • references/tooling-matrix.md
  • references/ci-workflows.md
  • references/triage-and-remediation.md
  • references/common-findings-and-fixes.md
  • references/supply-chain-and-sbom.md