Provider access should match the workflow
GitLab projects and branches are selected through the connected OAuth identity.
Provider-specific workflow
Validate GitLab repositories without moving the team to a different source-control workflow.
Use the authorized GitLab identity to choose a public or private project and branch, run supported code validation, and bring the evidence into SecOpsium's shared fix queue and history.
Why This Matters
Scheduled work requires refreshable access
OAuth access and refresh credentials are held in Vault for authorized scans that run later.
Provider limits must stay visible
GitLab code validation is supported; the current repository configuration audit remains GitHub-specific.
What SecOpsium Scans
- Supported secret and code findings in the selected GitLab project and branch.
- Public or private projects accessible to the authorized identity.
- Manual and scheduled code-validation results.
- Current and historical validation evidence in the shared workflow.
Validation workflow
- 1Start the GitLab OAuth connection from the intended SecOpsium workspace.
- 2Authorize the requested GitLab scope.
- 3Choose an accessible project and branch.
- 4Run a manual validation or supported schedule.
- 5Remediate, revalidate, and disconnect when access is no longer needed.
Frequently Asked Questions
Are private GitLab projects supported?
Yes, when the connected identity and OAuth scope permit access.
Can GitLab validations be scheduled?
Yes, for supported code-validation workflows.