KAI runs the pentest. Then proves it.
Recon, exploitation, attack-chain analysis, and a reproducible PoC for every finding — written by an agent trained on OSCP, OSCE3, and CRTO methodology.
Coverage across eight attack surfaces
Every technique mapped to OWASP, MITRE ATT&CK, CWE, and the compliance frameworks your auditors demand. KAI reasons about your target and picks the techniques most likely to succeed — not a fixed checklist.
Web Applications
24 TECHNIQUES- ›SQL injection (error / time / UNION-based)
- ›XSS, CSTI, SSTI, prototype pollution
- ›Authentication & 2FA bypass
- ›Session token weakness
- ›SSRF, file upload, deserialization
- ›Cloud-storage misconfig (S3, GCS, Azure Blob)
APIs
11 TECHNIQUES- ›REST + GraphQL introspection abuse
- ›OAuth 2.0 / OIDC / JWT cracking
- ›BOLA / IDOR / function-level auth
- ›Rate limiting & business-logic abuse
- ›Webhook + signature bypass
Active Directory & Identity
18 TECHNIQUES- ›Kerberoasting + AS-REP roast
- ›NTLM relay (SMB→LDAP, HTTP→ADCS)
- ›Coercion: PrinterBug / PetitPotam / DFSCoerce
- ›BloodHound-compatible enumeration
- ›RBCD, Shadow Credentials, S4U2Self
Cloud (AWS / Azure / GCP)
22 TECHNIQUES- ›IAM privilege escalation paths
- ›IMDSv1 / STS role-chaining abuse
- ›S3 / Blob / GCS bucket leakage
- ›Serverless function misconfig
- ›EKS / AKS / GKE cluster takeover
Network & Protocols
19 TECHNIQUES- ›SMB / SSH / RDP / LDAP / FTP
- ›TLS / DNS / DHCP weaknesses
- ›mitm6 (IPv6 DHCPv6 takeover)
- ›Database protocols: MSSQL, MySQL, PostgreSQL
- ›Out-of-band testing via Interactsh
Containers & Orchestration
14 TECHNIQUES- ›Docker socket exposure + escape
- ›Kubernetes RBAC abuse
- ›Pod-to-pod lateral movement
- ›Misconfigured ServiceAccount tokens
- ›Helm chart secret leakage
Source Code & Repositories
12 TECHNIQUES- ›SAST: injection, auth, crypto flaws
- ›Secret detection in code + git history
- ›IaC misconfig (Terraform, K8s, Docker)
- ›Dependency vulnerabilities + SBOM
- ›License compliance scanning
CMS & Application Stacks
7 TECHNIQUES- ›WordPress core + plugin CVEs
- ›Magento, Drupal, Joomla
- ›Outdated framework versions
- ›Plugin / theme vulnerability matching
- ›Admin path enumeration
See KAI in action
Six workspaces a security operator lives in — from triage to compliance reporting.
More than audits — KAI runs your security program
One agent, six different jobs — pick a workflow to see how it works.
Continuous Production Monitoring
KAI runs autonomous re-tests on a schedule (hourly, daily or weekly) against your live infrastructure. New vulns trigger alerts the moment they appear — no waiting for the next quarterly engagement.
- ›Heartbeat scans on configurable cadences
- ›Diff-aware: only re-tests what changed
- ›Slack / Teams / PagerDuty alerts on first detection
KAI vs everything else
Side by side with traditional pentests, legacy vulnerability scanners, and the new wave of AI security copilots.
Traditional Pentest: human-led engagement, billed per project. Legacy Scanners: Nessus / Qualys / Rapid7 / Tenable. AI Copilots: assistant-style tools that help operators run scans (not autonomous).
Plugs Into Your Security Stack
Source control, ticketing, alerting, cloud, and SIEM — KAI ships findings into the tools your engineering and SOC teams already use.
Source Code
Ticketing
Alerting
Cloud & Infrastructure
SIEM
Built for engineers
Every action in the UI is also one API call away. REST + GraphQL with HMAC-signed webhooks, official SDKs in Python / Go / TypeScript, native CI integrations, and a Terraform provider for infra-as-code scan policies.
- ›OpenAPI 3.1 spec — generate your own clients
- ›HMAC-signed webhooks with delivery retry log
- ›GitHub Actions, GitLab CI, Jenkins, Azure DevOps
- ›Terraform provider — version your scan policies
- ›JSON / SARIF / CSV / XLSX exports per scan
KAI Platform — FAQ
Common questions from security leaders evaluating KAI for their organization.