What happens during a SecOpsium scan?
SecOpsium checks an authorized repository or target for supported security signals, normalizes the results, and presents findings with severity and remediation guidance.
Docs
Scanning Model
SecOpsium is designed around a simple loop: authorize access, scan the selected repository, normalize supported findings, and help the team decide what to fix next.
Scan flow
A scan starts when a user selects a repository or supported target they are authorized to assess.
The scanner checks supported content and configuration signals, then returns findings with severity, category, evidence context, and remediation guidance.
The SaaS stores the resulting findings and metadata so the team can review progress, generate reports, and maintain a security cadence.
- Repository access is scoped to the authorized workflow.
- Findings are normalized before they appear in the dashboard.
- Reports and grades summarize supported findings, not every possible security risk.
What a finding represents
A finding is a supported security signal backed by available evidence. It may be a hardcoded secret-like value, a repository posture issue, or another supported exposure signal.
Findings are meant to guide remediation. They are not a claim that SecOpsium has fully audited the system or proven the absence of other issues.
How the SaaS differs from the CLI
The open-source SecOpsium CLI provides a way to run and inspect local repository checks.
The SaaS adds hosted execution, team workflows, dashboards, reports, scan history, and prioritization around the findings.
Frequently Asked Questions
Does a scan prove that a repository is secure?
No. A scan shows what supported checks found at that time. It does not prove that every issue has been found or that the repository is completely secure.
Why keep scan history?
Scan history helps teams compare posture over time, confirm remediation, and avoid treating each security check as a one-off event.