Built-in Agent Catalog: All 45 Cloud Security Agents

Cynative ships with 45 built-in agents embedded in the binary — no configuration required to run them. Each agent is a reviewed prompt for a specific security research question. They are grouped by cloud platform below. Use cynative agents list to see every agent with its source and status, and cynative agents show <name> to inspect the exact prompt before running it.

AWS (20)
Azure (11)
GCP (5)
GitHub (4)
Kubernetes (5)

Agent	What it answers
`aws-behavior-anomalies`	Find the CloudTrail escalation and enumeration sequences that depart from what the principal running them normally does, and explain what changed.
`aws-container-isolation`	Determine which running ECS tasks cross the boundary to the host that runs them, what the container instance behind each one reaches, and which EKS clusters carry no cluster security group.
`aws-credential-exposure`	Assess AWS root credentials, IAM user MFA state and long-lived access keys against what each one reaches.
`aws-data-encryption`	Determine which unencrypted AWS data can leave the service boundary, and where a KMS key policy is no narrower than the service permission behind it.
`aws-destruction-resilience`	Determine what in an AWS account could be destroyed with no recoverable copy, starting with the keys already scheduled for deletion.
`aws-detection-coverage`	Find the AWS regions and alarm paths where activity would generate no signal that reaches anyone.
`aws-domain-takeover`	Find AWS DNS records and resource references whose target no longer exists in the account, and registered domains without transfer lock.
`aws-hardcoded-secrets`	Find credentials sitting in AWS resource configuration and bound what each one reaches using the account’s own APIs.
`aws-inference-exposure`	Determine who can invoke Bedrock model endpoints in an AWS account, what a hijacked one reaches and whether abuse would appear in the call record.
`aws-metadata-theft`	Determine which EC2 instances expose their instance profile through the metadata service, and what each of those roles reaches.
`aws-network-exposure`	Determine which AWS network paths from the internet complete end to end, and what the identity attached to each exposed resource reaches.
`aws-perimeter-bypass`	Find AWS Network Firewall and WAF deployments that pass traffic without inspecting it, and the subnets whose routes bypass them.
`aws-policy-exposure`	Classify every non-storage AWS resource policy as anonymous, external-account or internal, and resolve the outside accounts each one names.
`aws-privilege-escalation`	Map the paths from each AWS IAM principal to administrative control, naming the calls that walk each one.
`aws-public-datastores`	Determine which AWS managed data services answer from public DNS and what authentication stands in front of each.
`aws-public-storage`	Resolve effective public and cross-account access to S3 buckets, Multi-Region Access Points, ECR repositories and Glacier vaults.
`aws-snapshot-exposure`	Determine which AWS snapshots, AMIs and SSM documents are shared outside the account, whether the share is usable and what the source held.
`aws-supply-chain`	Find the CodeBuild, CodeArtifact, Lambda layer and CDK paths that admit code or a build trigger from outside an AWS account, and resolve what each build role reaches.
`aws-transport-encryption`	Report AWS services carrying traffic without TLS against the CIDRs admitted to their ports, together with the certificates behind them.
`aws-unpatched-workloads`	Rank AWS workloads on unsupported versions by network reachability and by what the Inspector findings against them report.

cynative -p --agent aws-privilege-escalation

cynative -p --agent aws-public-datastores "AWS account 128149835728 only"

cynative --agent aws-network-exposure

Agent	What it answers
`azure-aks-exposure`	Determine who can reach each AKS API server and which Azure principals can retrieve its static cluster-admin credential.
`azure-appservice-exposure`	Determine how code and requests reach Azure App Service and Function apps, and what each app’s managed identity holds.
`azure-detection-coverage`	Find the Azure subscriptions, regions and alert paths where activity would produce no signal that reaches anyone.
`azure-inference-exposure`	Determine which Azure OpenAI accounts and AI Search services are reachable from outside the subscription and what a caller reaching one obtains.
`azure-keyvault-exposure`	Determine the shortest path to each Azure Key Vault’s contents, whether the read would be recorded and whether the vault can be purged.
`azure-network-exposure`	Resolve the effective inbound NSG rules per interface and report the ones reaching a running machine, with that machine’s managed identity.
`azure-privilege-escalation`	Map the Azure principals that can grant themselves further access, and report the scope each one holds it at.
`azure-public-datastores`	Determine which Azure SQL, MySQL, PostgreSQL, Cosmos DB and Databricks deployments admit outside connections and what authenticates them.
`azure-storage-exposure`	Resolve effective access to each Azure storage account across anonymous blob access, shared keys and the network rule set.
`azure-supply-chain`	Determine who can push to each Azure container registry, which workloads pull from it and what the running images carry.
`azure-vm-hardening`	Determine the paths to a session on each Azure virtual machine or to the contents of its disks, and what each path requires.

cynative -p --agent azure-keyvault-exposure

cynative -p --agent azure-privilege-escalation

cynative --agent azure-storage-exposure

Agent	What it answers
`gcp-audit-coverage`	Determine which activity in a GCP organization would go unrecorded, from the audit configuration each project carries, its load balancer logging and its asset inventory.
`gcp-inference-exposure`	Determine which Vertex AI endpoints grant prediction outside the organization and which API keys reach the Generative Language API unrestricted.
`gcp-network-exposure`	Expand GCP firewall rules to the instances they actually select, and report what each reachable instance’s service account holds.
`gcp-public-bindings`	Find GCP resources granting allUsers or allAuthenticatedUsers, and establish what each public binding permits.
`gcp-static-credentials`	Find GCP service accounts holding broad roles with exportable keys, the impersonation chains between them and API keys with no restriction.

cynative -p --agent gcp-public-bindings

cynative -p --agent gcp-static-credentials

cynative --agent gcp-network-exposure

Agent	What it answers
`github-branch-protection`	Determine which GitHub repositories permit a merge without effective review, and which of those deploy or publish.
`github-org-access`	Determine who holds write access across a GitHub organization and how an outside identity could obtain it.
`github-unpatched-dependencies`	Find dependencies with a known advisory still shipping from this organization’s repositories, and which of them a fix already exists for.
`github-workflow-trust`	Find GitHub Actions workflows that run untrusted code with credentials, and resolve what those credentials reach.

cynative -p --agent github-workflow-trust

cynative -p --agent github-unpatched-dependencies

cynative --agent github-org-access

Agent	What it answers
`k8s-pod-privilege`	Determine which pods reach their node, what that node holds and which pod specifications carry literal secret values.
`k8s-self-managed-apiserver-access`	Determine who can reach a self-managed Kubernetes cluster’s API server, as which identity and what its admission chain accepts.
`k8s-self-managed-cluster-secrets`	Determine what can read a self-managed Kubernetes cluster’s etcd directly, and whether an encryption provider is configured for the secrets in it.
`k8s-self-managed-controller-exposure`	Check a self-managed Kubernetes cluster’s controller manager and scheduler for exposed endpoints and for credentials shared across every controller.
`k8s-self-managed-kubelet-access`	Determine whether a kubelet in a self-managed Kubernetes cluster can be reached directly and what it requires before executing in a pod.

cynative -p --agent k8s-pod-privilege

cynative -p --agent k8s-self-managed-apiserver-access

cynative --agent k8s-self-managed-cluster-secrets

Running any agent

cynative agents list
cynative agents show <name>
cynative -p --agent <name>

agents list shows every agent from both sources — built-ins and any agents you have placed in ~/.cynative/agents/ — with its source and status. agents show prints the exact file that would run, writing the source path to stderr. Neither command requires credentials or configuration.

Use cynative agents show <name> to copy a built-in as the basis for a custom agent:

cynative agents show aws-public-datastores > ~/.cynative/agents/my-aws-public-datastores.md

Give your copy a distinct name to keep both the built-in and your version available side by side. See Writing Agents for the full agent file format.

Get Started

Using Cynative

Agents

Connectors

LLM Providers

Configuration

Project

Built-in Agent Catalog: All 45 Cloud Security Agents

Running any agent

​Running any agent

Running any agent