Source
Source-code handling, security & compliance — found from sitemap — Semgrep
Checked for Semgrep on 6 Nov 2026
- Page
- https://docs.semgrep.dev/compliance/soc2
- Checked
- 6 Nov 2026, 17:03 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:f0ace3025bec94102d09495ad42f5b24b275510c35d18e5f87e2fd56dbdd97a3
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
SOC 2 type2 certified Report an error
“Semgrep Inc. is SOC 2 Type II certified.”
-
SOC 2 managed scans infrastructure Report an error
“For Semgrep Managed Scans, scans run on Semgrep’s SOC 2 Type II-certified AWS infrastructure.”
-
SOC 2 cli customer infrastructure Report an error
“For CLI deployments, scans run on customer infrastructure (which may or may not be SOC 2 certified, depending on customer controls).”
-
SOC 2 cloud cicd certified Report an error
“Cloud CI/CD providers (GitHub, GitLab, Azure DevOps, Bitbucket) are SOC 2 certified.”
-
SOC 2 audit logs Report an error
“When Semgrep scans your code, it generates audit logs that document every scan execution, security finding, remediation action, and status change with timestamps and user attribution.”
-
SOC 2 policy enforcement block merges Report an error
“When properly configured with CI/CD systems, Semgrep policy enforcement allows security teams to define custom security rules that can block code from merging when violations are detected.”
-
SOC 2 policy override allowed Report an error
“Note that developers with appropriate permissions can override policy blocks when necessary.”
-
SOC 2 jira integration Report an error
“Jira integration documents your remediation workflow with timestamps and assignments”
-
SOC 2 sbom generation Report an error
“SBOM generation provides supply chain visibility for vendor risk management controls (CC9.1).”
-
SOC 2 no guarantee Report an error
“Semgrep provides security tooling that can support compliance efforts, but does not guarantee compliance.”
-
Page last updated Report an error
“Last updated: November 2025”
-
SOC 2 type2 duration note Report an error
“Organizations pursuing SOC 2 Type II certification need to demonstrate that security controls are operational and effective over time (typically 6-12 months), not just implemented at a point in time.”
Scores citing this record
- The Application Security Engineer Developer workflow, quality gates & fixes
- The Application Security Engineer Platforms, deployment & administration
- The Application Security Engineer Source-code handling, security & compliance
- The Engineering Manager Developer workflow, quality gates & fixes
- The Engineering Manager Platforms, deployment & administration
- The Engineering Manager Source-code handling, security & compliance
- The Lead Developer Developer workflow, quality gates & fixes
- The Lead Developer Source-code handling, security & compliance
- The Platform Engineer Developer workflow, quality gates & fixes
- The Platform Engineer Platforms, deployment & administration
- The Platform Engineer Source-code handling, security & compliance
- The Product Security Officer Developer workflow, quality gates & fixes
- The Product Security Officer Platforms, deployment & administration
- The Product Security Officer Source-code handling, security & compliance
- The Product Security Officer European sovereignty
- The Skeptic Developer workflow, quality gates & fixes
- The Skeptic Source-code handling, security & compliance
- The Skeptic European sovereignty