performing-sca-dependency-scanning-with-snyk

name	performing-sca-dependency-scanning-with-snyk
description	Use when this skill covers implementing Software Composition Analysis (SCA) using Snyk to detect vulnerable open-source dependencies in CI/CD pipelines. It addresses scanning package manifests and lockfiles, automated fix pull request generation, license compliance checking, continuous monitoring of deployed applications, and integration with GitHub, GitLab, and Jenkins pipelines.
domain	cybersecurity
tags	["devsecops","cicd","sca","snyk","dependency-scanning","secure-sdlc"]
subdomain	devsecops
version	1.0.0
author	oyi77
license	Apache-2.0
nist_csf	["PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04"]

Performing Sca Dependency Scanning With Snyk

Overview

Cybersecurity skill for performing sca dependency scanning with snyk. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "performing sca dependency scanning with snyk"

• "This skill covers implementing Software Composition Analysis (SCA) using Snyk to"

• When applications use open-source packages that may contain known vulnerabilities

• When compliance requires tracking and remediating vulnerable dependencies (PCI DSS, SOC 2)

• When needing automated fix PRs for vulnerable dependencies in CI/CD

• When license compliance requires visibility into open-source license obligations

• When continuous monitoring is needed for newly disclosed vulnerabilities in deployed dependencies

Do not use for scanning proprietary application code for logic vulnerabilities (use SAST), for runtime vulnerability detection (use DAST), or for container OS package scanning alone (use Trivy for a free alternative).

When NOT to Use

• When you lack proper authorization for testing
• For production systems without change management
• When the task requires legal or compliance expertise beyond technical scope

Prerequisites

• Snyk account (free tier covers up to 200 tests per month for open source)
• Snyk CLI installed or Snyk GitHub/GitLab integration configured
• SNYK_TOKEN environment variable set with API authentication token
• Project with supported package manifests: package.json, requirements.txt, pom.xml, go.mod, Gemfile, etc.

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> :
     {k: re.findall(v, text)  k, v  IOC_PATTERNS.items()}