UTAH Open workspace ↗

PENTESTING AI · RED TEAM · BLUE TEAM · AUTHORIZED TESTING

Pentesting AI for red teams,blue teams & builders.

Model real adversary paths with Attack, validate security posture, and immediately switch to Defense or Spartan to ship the remediation diff and regression suite.

OFFENSIVE & DEFENSIVE LOOPAttack + Defense + Spartan
MULTI-AGENT COORDINATIONShared Cloud Agent Rooms
BROWSER & LINUX EXECUTIONIsolated Chrome & REA Lanes

01 / PURPLE-TEAM ARCHITECTURE

Offensive hypothesis and defensive remediation in the same room.

Traditional penetration tests end in a static PDF weeks after code ships. Generic AI assistants refuse to reason past surface checklists. Utah lets authorized engineers test hypotheses, record verifiable evidence, and close the vulnerability in one continuous session.

RED TEAM · ATTACK AGENT

Adversarial path & boundary modeling

Map authentication state machines, multi-tenant IDOR/BOLA vectors, OAuth redirect flows, GraphQL batching abuse, webhook signature bypasses, and privilege-escalation chains across your architecture.

BLUE TEAM · DEFENSE AGENT

Posture verification & detection engineering

Verify TLS/HSTS, CSP frame-ancestors and script nonces, cookie flags, CORS origin reflection, rate-limit ceilings, and WAF/Sigma detections with clear separation between observed signals and hypotheses.

REMEDIATION · SPARTAN AGENT

Production-ready patches without placeholders

Turn every confirmed finding into a complete code patch, strict input schema, and deterministic unit/integration test ready for pull-request review.

02 / OWASP & API COVERAGE

Structured coverage across modern web, API, and cloud stacks.

Authorized security review domains in Project Utah
Assessment SurfaceWhat Utah Inspects & ModelsVerification Output
Authentication & SessionsOAuth2/OIDC state/PKCE, JWT alg/aud/iss confusion, password reset race conditions, cookie scopeState-transition audit + hardened middleware patch
Multi-Tenant AuthorizationObject-level IDOR/BOLA, role-claim spoofing, service-grant fencing, cross-tenant cache keysTenant-isolation matrix + negative test cases
Server-Side Request & ParsingSSRF URL parsers, redirect hops, XXE/YAML/JSON prototype pollution, webhook replay windowsAllowlist/egress guard + deterministic parser tests
Client & Edge HeadersCSP script/style nonces, object-src, frame-ancestors, HSTS preload, COOP/CORP, security.txtLive header posture receipt + exact Worker/Nginx config

03 / CLI & HARNESS COMMANDS

Drive red-team and blue-team reviews from your terminal or IDE.

Run coordinated Chrome & repository checks from the Utah CLI

Switch seamlessly between local code inspection and isolated Defense/Attack browser lanes.

utah --browser-agent defense --task "/chrome Inspect https://example.com response headers and summarize CSP/HSTS gaps"
utah --mode deep --task "Review src/auth/ for token replay, timing leaks, and missing origin checks"

Attach Utah 15-tool MCP to Cursor, Claude Code, or Codex

Write a 0600-permission MCP config with zero hardcoded secrets on disk.

utah --task "/ide cursor --write"
utah --task "/ide claude --write"

FAQ / DIRECT ANSWERS

Common technical questions.

Can I use Utah for penetration testing and red-team / blue-team exercises?

Yes. Utah provides dedicated Attack (authorized offensive research and threat modeling), Defense (posture hardening and detection), and Spartan (code remediation) workspaces, plus shared Agent Rooms where multiple AI sessions collaborate on an engagement.

Does Utah distinguish between confirmed vulnerabilities and hypotheses?

Yes. Utah’s response protocol explicitly separates observed primary evidence (HTTP status, headers, code lines, SHA-256 receipts, test exit codes) from unverified hypotheses so reports never inflate an unconfirmed signal into a false claim of exploitation.