Authentication July 11, 2026 We strengthened project-level access controls and account privacy protections across SecOpsium.
Strengthened project authorization checks across project operations. Improved privacy protections around registration and authentication responses. Prevented sensitive authentication responses from being cached. Improved application rate limiting for traffic received through protected proxy infrastructure. Why it matters
Teams get stronger tenant isolation and safer account workflows without adding steps to their day-to-day security work.
Reporting July 10, 2026 Project reports and remediation queues can now focus on an individual scan or the project's complete scan history.
Added report filtering for individual scans or the complete project history. Added scan-specific remediation queue views. Aligned scan-detail reporting with project report views. Improved navigation between scan results, reports, and prioritized fixes. Why it matters
Teams can isolate findings from a specific release, investigation, or remediation cycle without losing the broader project context.
July 7, 2026
We refreshed the SecOpsium dashboard to make projects, scans, reports, schedules, and workspace settings easier to navigate.
Added a more compact dashboard sidebar. Refreshed project, scan, report, schedule, and remediation surfaces. Improved visual consistency across profile, workspace, notification, and team settings. Refined repository selection and scan-launch workflows. Why it matters
Security work stays easier to follow as teams move from a project overview to scan results, reports, schedules, and fixes.
GitLab July 3, 2026 SecOpsium now supports GitLab repository scanning alongside GitHub, with stronger source-control handling across manual and scheduled workflows.
Added GitLab repository connections for private and public code scans. Expanded scheduled code scans so connected GitLab repositories can run automatically with the same protected scan flow. Improved scan consistency across providers by refining duplicate finding consolidation and branch-aware repository handling. Hardened source-control credential use so provider access stays scoped to the selected repository workflow. Why it matters
Teams using GitLab can validate repositories and schedule recurring scans without moving their source code or changing their existing development workflow.
GitHub June 27, 2026 GitHub-backed scan setup is smoother for teams moving between connected repositories, public targets, and branch-specific scans.
Improved branch discovery for connected GitHub repositories and public repository URLs. Refined repository-picker states when a GitHub App installation is missing, revoked, or out of date. Made code scanning, web exposure scanning, and configuration audits easier to launch from project workflows. Why it matters
Teams can move from repository selection to the right scan workflow with less setup friction and clearer connection guidance.
Reporting June 26, 2026 Reports now focus more clearly on the findings that create the most operational risk for a team.
Improved A-F security grade presentation for project and workspace reporting. Added clearer blast-radius context so teams can see what a leaked secret or exposed asset can affect. Refined report history views to make risk trends easier to compare over time. Why it matters
Teams spend less time sorting through findings and more time addressing the risks most likely to affect their systems.
May 2026
Configuration audits continue to expand beyond secret detection so teams can catch risky repository settings earlier.
Added checks for missing branch protection and risky repository administration patterns. Improved prioritization for findings with known, partial, or unknown operational impact. Updated digest and report language to be easier for engineering and business stakeholders to read. Why it matters
Teams can identify risky repository administration patterns before they turn into preventable exposure or access-control incidents.