Tenant isolation
Every record belongs to exactly one organization, and every read and write is filtered by it. The organization comes from a verified session or token, never from anything a request supplies, so a caller cannot ask for another organization’s data by naming it. Sessions are bound to one organization at a time.Credentials
Keyless where possible
Azure and GitHub involve no long lived secret from you. Access is a grant on your side, using short lived tokens issued at the time of use.
Always encrypted
Everything is encrypted at rest and in transit.
Yours to revoke
Every credential belongs to an account you created and control. Revoke it at your provider and Amnify’s access ends immediately.
Leaked secrets are never stored
Amnify does not store any leaked secret, anywhere. When a scan finds a credential, key or token exposed in a repository, the finding keeps only where it was found (the repository, commit, file and line range) and a redacted form of the secret: at most its first four characters, enough to recognise which credential it is, never its value. Before saving a finding or a pull request review comment, Amnify also checks it for a secret left in and redacts that the same way.
What Amnify reads, and what it does not
- Cloud access is read only and configuration only. Amnify reads how a resource is configured. It has no access to what is inside it.
- GitHub and GitLab access covers the repositories you select, and nothing else.
- Repository write is bounded to a new branch and a pull request, or a merge request on GitLab. Never your default branch, and never a merge.