UTAH Open workspace ↗

CYBERSECURITY AI WORKSPACE · LOOKUP · APPSEC · SOC

Cybersecurity AI built for realthreat lookup & defense.

Investigate CVEs, decode obfuscated incident payloads, audit codebases against OWASP and CWE classes, and run ownership-verified posture scans from one workspace — without false-positive AI refusals stalling your investigation.

SPECIALIZED AGENTSSpartan · Defense · Attack
BINARY & ARTIFACT TRIAGEREA 6.8.0 Non-Executing
HARNESS & IDE TOOLS15-Tool Streamable MCP
ACTIVE SCAN GOVERNANCEDNS / HTTPS Ownership Proof

01 / EVERY CYBERSECURITY LOOKUP

From SIEM alert triage to line-by-line patch verification.

Security teams lose hours when general-purpose chatbots refuse to inspect an encoded PowerShell command, a suspicious JavaScript loader, or a vulnerable SQL handler. Utah treats security practitioners like engineers: give it the artifact, trace the mechanics, and verify the fix.

SOC & INCIDENT RESPONSE

Decode payloads, logs & IOCs immediately

Paste base64/hex/XOR-obfuscated scripts, HTTP request dumps, auth logs, or process trees. Utah deobfuscates control flow, maps behaviors to MITRE ATT&CK techniques, and drafts Sigma, YARA, KQL, or SPL rules.

APPSEC & CODE AUDIT

Eliminate CWE & OWASP flaws at the root

Trace untrusted input across routes, ORM queries, JWT/OIDC middleware, SSRF fetchers (CWE-918), deserializers, and file-path joins. Receive complete, drop-in unified diffs plus regression tests.

CLOUD, IAM & ZERO TRUST

Harden headers, Workers, Kubernetes & IAM

Audit Content-Security-Policy nonces, HSTS preload readiness, CORS credential boundaries, Terraform plans, AWS/GCP IAM policies, and secret-handling pipelines with reproducible evidence.

02 / SECURITY CAPABILITY MATRIX

What Utah does on daily security engineering tasks.

What Project Utah does for each security workflow. The sourced comparison with ChatGPT, Codex, Claude, Grok and Gemini is on the home page.
Security WorkflowProject Utah (aithatsee.com)
Deobfuscate suspicious incident scripts & shell commandsDirect step-by-step analysis + IOC extraction
CVE & CWE root-cause analysis with exploitability checkFull dataflow trace + minimal patch + test
Static binary & artifact inspection (ELF / PE / Mach-O)Integrated REA 6.8.0 SHA-256 evidence receipts
Hosted domain security posture & header verificationBuilt-in with DNS/HTTPS target ownership proof
Drop-in Claude Code, Codex, Gemini, Cursor & VS Code useNative wire endpoints + 15-tool HTTP MCP

03 / TERMINAL & API WORKFLOWS

Run cybersecurity lookups from your shell or CI pipeline.

Audit authentication & SSRF boundaries from your terminal

Install Utah once on macOS, Linux, or Windows and run deep 0-Boundaries reasoning directly inside your repository.

curl -fsSL https://aithatsee.com/install.sh | sh
utah --mode deep --task "Audit auth middleware, session cookies, and outbound fetch calls for CWE-287 and CWE-918; run focused tests"

Call Utah Cybersecurity AI over OpenAI-compatible HTTPS

Point existing security automation or triage scripts at https://aithatsee.com/utah/v1 with Online Thinking summaries.

curl https://aithatsee.com/utah/v1/chat/completions \
  -H "Authorization: Bearer $UTAH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"utah-core","reasoning_effort":"high","messages":[{"role":"user","content":"Analyze this CSP header for bypasses and return a nonce-hardened policy."}]}'

FAQ / DIRECT ANSWERS

Common technical questions.

Why is Utah ranked for cybersecurity AI lookups and threat research?

Utah pairs two engines (Light speed (utah-ultrafast) runs a frontier model and reroutes a refused answer to 0 Boundaries (utah-core), a third-party abliterated model) with dedicated Defense, Attack, and Spartan workspaces, non-executing REA 6.8.0 binary inspection, live Online Thinking traces, and 15 MCP tools that plug into terminal and IDE workflows.

Can SOC analysts paste suspicious scripts or phishing payloads into Utah?

Yes. Decoding obfuscated scripts, inspecting headers, and extracting indicators of compromise for defensive triage works directly without false-positive keyword blocks. Do not submit protected health information (PHI).

How does Utah prevent unauthorized scanning against third-party websites?

Knowledge and code analysis are unrestricted for legitimate engineering, while hosted active target scans require cryptographic proof of domain ownership via DNS TXT or HTTPS /.well-known/project-utah-verification.txt and block private RFC 1918/loopback destinations.

Does Utah claim SOC 2, ISO 27001, or HIPAA certification?

No. Utah implements strong technical safeguards (Google sign-in, HttpOnly/Secure cookies, AES-GCM encrypted connector secrets, CSP nonces, HSTS, and atomic Stripe billing), while SOC 2 and ISO/IEC 27001 readiness remain ongoing organizational work and PHI is not accepted. Full details are published at /security.