Security & trust
Utah implements technical safeguards for security research. We do not currently claim SOC 2 attestation, ISO/IEC 27001 certification, or a HIPAA-authorized service. Do not submit protected health information.
Access and isolation
New web workspaces use verified Google sign-in. Session cookies use Secure, HttpOnly, and SameSite protections; cookie-authenticated writes require the correct origin. Existing API keys remain supported. Bearer credentials in the web client are kept in session storage, and sign-out clears the local workspace. Native Windows credentials are protected with Windows DPAPI.
Research boundaries
Hosted testing requires account-bound proof of target ownership using DNS or HTTPS. The server validates the target and restricts private network destinations. Research output distinguishes observed evidence from hypotheses; an observed signal is not proof of exploitation.
Billing integrity
Checkout uses Stripe-hosted payment pages. Utah does not receive card numbers. The server binds a checkout reference to the selected plan and account. Fulfillment verifies the webhook signature, payment status, currency, amount, and Payment Link. Atomic ledger operations protect against duplicate credits and concurrent usage. Usage is reserved before inference; failed model requests release the reservation.
Application safeguards
The website uses a nonce-based Content Security Policy, HTTPS, HSTS, frame restrictions, request-size limits, and server-side rate limits. API responses are not cached. Model responses are restricted to the documented response fields; private reasoning fields are not forwarded.
Customer integrations and audit evidence
Provider and app credentials are encrypted with AES-GCM in account-scoped storage. App requests are restricted to the saved public HTTPS origin and base path, allowed methods, bounded payloads and no followed redirects. KV and R2 reads require membership in the connected Cloudflare account. Protected storage operations have an account audit trail. The AI offers SOC 2, HIPAA and ISO 27001 skills for reviewing supplied evidence and proposing remediations. Hash-linked audit history can detect changes within its stored chain; it is not an externally anchored immutable log. Recorded evidence does not constitute independent assurance. Separate KMS custody, organizational reviews and independent audits remain open requirements.
Assurance status
| Framework | Current status | Required organizational work |
|---|---|---|
| SOC 2 | Technical readiness work in progress | Independent auditor, defined system scope, control ownership, and an evidence period |
| ISO/IEC 27001 | Not certified | Operating ISMS, risk treatment, internal audit, management review, and certification audit |
| HIPAA | PHI not accepted | Applicable covered-entity assessment, signed BAAs with all relevant providers, risk analysis, and operational safeguards before any PHI |
Report a security issue
Contact michael@blacklabelbots.com. Include the affected URL, minimal reproduction, expected behavior, and a safe evidence sample. Avoid personal data, credentials, destructive testing, and access to other customers’ data. Our machine-readable contact is in security.txt.
Framework references: AICPA Trust Services Criteria, ISO/IEC 27001, and HHS cloud guidance.