That's excellent news! The expansion of security campaigns to include secret scanning alerts is a significant enhancement for organizations using GitHub Advanced Security.

This integration addresses a key pain point in security management - coordinating the remediation of exposed secrets across multiple repositories. By providing organization-level overviews and centralized tracking, teams can now:

Systematically prioritize and address high-risk secret exposures

Reduce manual coordination efforts between different teams

Maintain clear accountability throughout the remediation process

Focus on the most critical security issues with proper context

The combination of code scanning and secret scanning campaigns creates a unified approach to security remediation, moving beyond mere detection to ensure actual resolution of vulnerabilities. This is particularly valuable for organizations managing large codebases where secret sprawl can be challenging to track manually.

For teams already using Secret Protection or Advanced Security, this should significantly streamline their security operations and help prevent credential leaks from falling through the cracks during remediation efforts.

When you launch secret scan campaign, it only shows DEFAULT category and not generic secret types. Why ?