Personal GitHub Repositories Can Expose Secrets Beyond Enterprise Scanning

· Original article ↗

Summary

Wiz says 56% of company-impacting secrets it found were in employees’ personal repositories. The post explains how linking developer identities to public repos, validating credentials, and mapping access paths can help teams prioritize and remediate exposures.

Key points

  • Wiz Research found verified secret leaks in 65% of the Forbes AI 50; 56% of company-impacting secrets were in employees’ personal repositories.
  • Bots can collect secrets from public GitHub commits within minutes or seconds, and leaked credentials may provide infrastructure access.
  • The article says four of the five most frequently leaked validated secrets in its cited report were for AI services.
  • Enterprise secret scanners may miss personal repositories because they are outside organizational inventories; a detected string alone does not establish that a credential is active or what it can access.
  • Wiz describes correlating developer identities with personal public repositories, then mapping exposed credentials to accessible resources to assess potential impact.
  • The described Red Agent tests whether detected credentials are active and what they can reach; teams can then trigger credential rotation or revocation and track remediation.

Article Details

Topic
Managing exposed credentials in developers’ personal public repositories through identity correlation, exploitability validation, and remediation.

Vendors

Products

Industries

Related Articles