Cloud key in historical commit
Context, exposure and remediation priority were captured for review.
Case study
Discovering cloud keys buried in Git history
An engineering team removed a cloud access key from the current repository state, but the security team needed to verify whether the same credential existed elsewhere.
Example scenarioUse for SEO until real customer stories are available
Challenge
Hidden credentials outside controlled systems.
An engineering team removed a cloud access key from the current repository state, but the security team needed to verify whether the same credential existed elsewhere.
What Onyxaris scanned
- Repository history
- Branches
- Release archives
- Network share packages
- SharePoint handover folders
Findings
What the team discovered.
Same key in release archive
Context, exposure and remediation priority were captured for review.
Same key in network share deployment package
Context, exposure and remediation priority were captured for review.
Related configuration file in SharePoint
Context, exposure and remediation priority were captured for review.
Outcome
Prioritized remediation and repeatable review.
The team gained a structured cleanup list, rotated high-risk credentials, removed obsolete copies and created a repeatable process for future scans.
| Before | After |
|---|---|
| Unknown credential exposure | Risk-ranked findings by source |
| Manual folder review | Automated source scanning |
| No central evidence | Documented remediation trail |
| Repository-only view | Cross-source exposure visibility |
Start focused
Run a similar exposure assessment.
Use Onyxaris to start with one high-risk source and build a practical remediation plan.