How it works
Amnify Agent runs scans, reads useful context from existing tools, and builds a knowledge graph across cloud, code, Kubernetes, containers, pentests, docs, tickets, and chat. It asks for missing context when needed and acts only within the limits you set.
Agent intelligence
Amnify does not treat findings as isolated alerts. It builds a connected graph across scan results, cloud, code, owners, policies, open work, chat context, and remediation history.
Cloud accounts, code repositories, SAST, DAST, Kubernetes, containers, pentests, tickets, docs, chat, runbooks, and deployment history become shared context.
When ownership, intent, exception rationale, or business impact is unclear, the Agent can ask the right person instead of guessing.
Approvals, disputes, fixes, and ignored recommendations become feedback that helps the Agent act more precisely over time.
Amnify Agent
One connected model for reasoning across risk, ownership, and remediation.
Repos, dependencies, secrets, and infrastructure-as-code.
Containers, pods, services, and live operational signals.
Accounts, identities, networks, data stores, and configuration.
Docs, tickets, chats, policies, ownership, and runbooks.
Cloud connections
Amnify uses provider credentials and least-privilege read access for scanning. You choose which subscriptions, accounts, and projects are enabled.
Service principal
Create an Azure app registration, grant the service principal Reader access to the subscriptions you want scanned, then add the tenant, application, and client secret in Amnify.
IAM user or assume role
Connect AWS with static credentials or an assume-role setup. The docs use read-only scanning permissions such as SecurityAudit and validate the role before accounts are enabled.
Service account
Create a dedicated service account with Viewer access, provide its JSON credentials, and choose the projects Amnify should scan.
Deploy workflows
Deploy turns approved cloud patterns into repeatable requests. Built-in checks cover common controls, while custom checks let operators enforce the rules that matter to your environment.
Enable ready-made checks for the cloud and infrastructure patterns your team already reviews.
Add your own policy gates for ownership, regions, tags, exposure, approval rules, and business-specific requirements.
Template-based deployments come from a GitHub-backed library, with variables rendered in the Amnify UI for repeatable requests.
Plans are reviewed and approved before infrastructure changes are applied, with run history preserved for follow-up.