security-scanning-suite

name	security-scanning-suite
description	Comprehensive security analysis including SAST, DAST, dependency scanning, secret detection, and vulnerability assessment. Use for security audits, CVE tracking, compliance checks, and preventing vulnerabilities from reaching production. Supports multiple languages and frameworks.
allowed-tools	["Read","Write","Edit","Bash","Glob","Grep","WebFetch"]

Security Scanning Suite

Purpose

"With no vulnerabilities, no security issues" (user's production requirement). This Skill provides comprehensive security scanning and analysis across multiple layers of your application stack.

Quick Start

Run a complete security scan on your project:

# Install essential scanners
pip install semgrep detect-secrets pip-audit
npm install -g snyk

# Quick security audit
semgrep --config=auto .                    # SAST scan
detect-secrets scan . > .secrets.baseline  # Secret detection
npm audit --audit-level=moderate          # Dependency scan (Node.js)
trivy fs .                                 # Filesystem vulnerability scan

For a production-ready security pipeline, see PATTERNS.md.

Core Scanning Types

1. SAST (Static Application Security Testing)

Code analysis to find security vulnerabilities without running the code.

Key Tools: Semgrep, Bandit (Python), ESLint-plugin-security (JS), gosec (Go)

Detects: SQL injection, XSS, hardcoded secrets, insecure deserialization

Quick Check:

# Run OWASP Top 10 checks
semgrep --config=p/owasp-top-ten .

See PATTERNS.md for custom rule creation.

2. Dependency Scanning (SCA)

Find known vulnerabilities in third-party libraries and dependencies.

Key Tools: npm audit, pip-audit, Snyk, Trivy, Dependabot

Detects: CVEs in dependencies, outdated packages, license issues

Quick Check:

# Node.js
npm audit --audit-level=moderate

# Python
pip-audit --requirement requirements.txt

# Multi-ecosystem
trivy fs --scanners vuln .

See PATTERNS.md for multi-language scanning.

3. Secret Detection

Prevent credentials and API keys from being committed to version control.

Key Tools: TruffleHog, detect-secrets, GitLeaks, git-secrets

Detects: API keys, passwords, tokens, private keys, connection strings

Quick Check:

# Scan current directory
gitleaks detect --source .

# Scan git history
trufflehog git file://. --json

See PATTERNS.md for pre-commit hooks.

4. Container Security

Scan Docker images and containers for vulnerabilities.

Key Tools: Trivy, Grype, Docker Scout, Snyk

Detects: Base image vulnerabilities, misconfigurations, malware

Quick Check:

# Scan Docker image
trivy image myapp:latest --severity HIGH,CRITICAL

# Scan Dockerfile
trivy config Dockerfile

See PATTERNS.md for comprehensive scanning.

5. Infrastructure as Code (IaC) Security

Analyze Terraform, CloudFormation, Kubernetes configs for security issues.

Key Tools: Checkov, tfsec, KICS, Terrascan

Detects: Misconfigurations, excessive permissions, insecure defaults

Quick Check:

# Scan Terraform
checkov -d infrastructure/ --framework terraform

# Scan Kubernetes
checkov -d k8s/ --framework kubernetes

See PATTERNS.md for IaC scanning workflows.

6. Dynamic Application Security Testing (DAST)

Runtime security testing of running applications.

Key Tools: OWASP ZAP, Nuclei, Burp Suite

Detects: Authentication issues, injection flaws, misconfigurations

Quick Check:

# Run ZAP against API
docker run -t owasp/zap2docker-stable zap-baseline.py -t http://localhost:8080

See PATTERNS.md for API security testing.

Implementation Workflow

graph LR
    A[Pre-Commit] --> B[Pull Request]
    B --> C[CI/CD Pipeline]
    C --> D[Pre-Deploy]
    D --> E[Production]

    A --> |Secret Detection| F[Block commits]
    B --> |SAST + Dependencies| G[Review findings]
    C --> |Full scan suite| H[Gate on severity]
    D --> |Container + IaC| I[Final checks]
    E --> |Continuous monitoring| J[Alert on new CVEs]

Common Security Gotchas

1. False Positives Overload

SAST tools generate many false positives that can overwhelm teams.

Solution: Start with high/critical only, use # nosec comments judiciously, create baseline files. See GOTCHAS.md for detailed strategies.

2. Secrets in Git History

Removing secrets from the current commit isn't enough - they remain in history.

Solution: Use git filter-repo to rewrite history, immediately rotate all exposed credentials. See GOTCHAS.md for cleanup procedures.

3. Transitive Dependencies

Your dependencies have dependencies, creating a deep vulnerability tree.

Solution: Use lock files, scan with --include-transitive flags, automate updates. See GOTCHAS.md for management strategies.

File Structure

• SKILL.md - This file, quick start and overview
• KNOWLEDGE.md - Security concepts, OWASP Top 10, tool comparisons
• PATTERNS.md - Implementation patterns for each scan type
• EXAMPLES.md - Complete working examples and scripts
• GOTCHAS.md - Troubleshooting and common issues
• REFERENCE.md - Tool APIs and configuration reference

Related Skills

• deployment-automation-toolkit - Integrate security into deployments
• code-review-framework - Security-focused code reviews
• architecture-evaluation-framework - Security architecture assessment
• gap-analysis-framework - Security gap identification

Quick Reference

Scan Type	Critical Tool	Command	When to Use
SAST	Semgrep	semgrep --config=auto .	Every commit
Secrets	Gitleaks	gitleaks detect --source .	Pre-commit
Dependencies	npm/pip audit	npm audit	Daily
Containers	Trivy	trivy image <name>	Pre-deploy
IaC	Checkov	checkov -d .	Infrastructure changes
DAST	OWASP ZAP	zap-baseline.py -t <url>	Staging/QA

For detailed implementation, see PATTERNS.md. For troubleshooting, see GOTCHAS.md.