Route each exposed AI key to the person who pushed it
Amplifier ingests secret detection findings from GitLab and attributes each one to the committer
The developer gets one question in Slack or Teams that states what revocation affects: this key was flagged in a repository you pushed; revoke it?
Security decides which findings go to the developer and which go straight to the security team
At a glance
Release Status
Beta
Categories
AI Security
Reaches employees in
Slack and Microsoft Teams
Retire agent credentials nobody is using
Amplifier joins GitLab token data with identity and endpoint signals into a lifecycle record for each AI agent
When an agent stops running but its token stays live, the owner can retire it in one answer
Amplifier orchestrates the revocation through the provider's admin interface and verifies the credential is inactive before closing the finding
Close each finding with the evidence attached
Every finding records who approved, what was revoked, and when
Amplifier ingests findings from GitLab and doesn't scan repositories on its own
Report closed findings and retired credentials to auditors and the board from your own environment
