Does SecOpsium store source code after scanning?
SecOpsium is designed not to retain full repository source code as a product artifact after scanning. It stores findings and metadata needed for remediation and reporting.
Docs
Code Retention
SecOpsium is built to keep scan results useful without turning the SaaS into a permanent store of customer source code.
What SecOpsium stores
SecOpsium stores the data needed to show scan results, remediation state, reports, and history.
That can include findings, severity, rule identifiers, file paths, evidence snippets, remediation guidance, project metadata, workspace metadata, and scan timestamps.
What SecOpsium avoids retaining
SecOpsium is designed not to retain full repository source code as a product artifact after scanning.
The product should store enough finding context for remediation, without keeping a complete copy of the repository in the dashboard.
- No full source-code archive as a product artifact.
- No GitHub personal access tokens stored for normal GitHub-backed scans.
- No claim that findings are a complete substitute for secure engineering review.
Why snippets exist
Short evidence snippets help teams understand where and why a finding was raised.
The goal is to preserve remediation context while minimizing unnecessary retention of code content.
Frequently Asked Questions
Why does SecOpsium store file paths or snippets?
File paths and short evidence snippets help users locate and understand findings without requiring full source-code retention in the product.
Is scan metadata still sensitive?
Yes. Findings, paths, snippets, and project metadata can be sensitive and should be protected as security data.