Supported credential patterns
Gitleaks-backed rules and SecOpsium normalization identify supported secret-like values without claiming universal detection.
Code and secrets
Continuously validate that supported credentials are not exposed in repository content.
SecOpsium uses supported secret rules and repository context to surface credential-like values, explain practical next actions, and show whether a later validation still finds the same evidence.
Definition
What this capability validates
Secrets detection identifies supported API key, token, password, private-key, and credential patterns. It does not contact providers to prove that a value is live, valid, or exploitable.
Current capability
Evidence for review
Findings can include a rule identifier, repository path, short evidence snippet, severity, and remediation guidance.
Practical lifecycle
The product guides the team through detect, review, rotate or revoke, remove, and revalidate.
Local and hosted paths
The open-source CLI supports local checks while the hosted product adds authorized scans, history, grades, reports, and shared workflows.
Scope and Limits
- SecOpsium does not perform live provider validation of detected credentials.
- Pattern coverage cannot guarantee that every secret is found.
- A later scan confirms only that the supported evidence no longer appears in that validation scope.
Frequently Asked Questions
Does SecOpsium check whether a detected credential is active?
No. A finding is evidence that a supported credential pattern appears in repository content. The team should review, rotate, or revoke it through the provider.
What should happen after a secret is found?
Review the context, rotate or revoke the value if necessary, remove it from code, address the workflow that introduced it, and run a new validation.
Can every possible secret be detected?
No. SecOpsium detects supported patterns and keeps coverage limits explicit.