How to Connect Snyk to SecureSpect
Automate software composition analysis and vulnerability management evidence by connecting your Snyk organization to SecureSpect.
Ready to connect? Follow the steps in SecureSpect — the integration dialog walks you through the same process described here.
Open Integrations →Overview
The Snyk integration gives SecureSpect read access to your vulnerability findings, license compliance status, and fix rates. This data maps directly to SOC 2 CC6.8 (Malicious Software Prevention) and CC7.1 (Configuration Monitoring) controls, automating a significant portion of your evidence collection.
What Gets Monitored
- Open vulnerabilities — Critical and high severity counts, fix rate trends
- License compliance — License policy violations flagged by Snyk
- Fix coverage — Percentage of projects with active PR fixes
- Organization settings — Snyk Code enabled, container scanning configured
Step 1 — Generate a Snyk API Token
The token grants access to all organizations your account can see. For tighter scoping, create a service account at the organization level:
securespect, role: Viewer.Step 2 — Connect in SecureSpect
Step 3 — Understand the Findings
Vulnerability score — SecureSpect calculates a weighted score based on CVSS severity and fix availability. A score below 80 triggers a finding.
Fix rate — The percentage of high/critical vulnerabilities that have an available fix (Snyk PR) open or merged. SOC 2 auditors expect this to be above 70%.
Ignored vulnerabilities — Snyk vulnerabilities marked "Ignored" are surfaced separately in SecureSpect, since auditors often ask about acceptance decisions.
Remediation Workflow
# Install Snyk CLI and test locally
npm install -g snyk
snyk auth
snyk test --severity-threshold=high
# Open a fix PR
snyk fix
SecureSpect will pick up the remediation within the next 24-hour sync window, or click Sync now in the integration settings.