Skip to content

GitHub secret scanning - extended metadata is generally available [GA] #1263

Description

@glider-bot

Value Prop

To help you understand ownership and impact of a leaked secret, GitHub secret scanning now surfaces additional metadata for supported secret types. Metadata varies by type and includes owner-email, owner-id, owner-name, secret-id, secret name, secret-issued-date, secret-expiration-date, organization-name, organization-id, and last-used-date.

Expected Outcome

When a secret is leaked, knowing what was exposed is only half the battle. Teams also need to know who owns it, when it was created, and what systems it can access. This enriched metadata helps teams dramatically reduce the time it takes security and development teams to triage and remediate leaked secrets.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions