CadreGPT Enterprise Trust, Governance & Zero-Trust Architecture

Enterprise Security, Governance & Zero-Trust Architecture

Built from the ground up with AES-256-GCM envelope encryption, strict multi-tenant isolation, and zero-training commercial AI model routing.

SOC 2 Type II Aligned ISO/IEC 27001 Controls GDPR & UK DPA Ready Zero Model Training Guarantee RFC 9116 Machine Readable
Request Security Packet & SOC 2 Bridge View Data Processing Addendum View Subprocessors Directory

SOC 2 Type I Compliance Readiness Package

Audited against AICPA Trust Services Criteria (Security, Availability, Confidentiality)
100% Ready (6/6 Controls Operational) Download Evidence (JSON)
CC6.1 Access Control: Least-privilege RBAC matrix with fail-closed default deny
CC6.6 Boundary Security: Strict public allowlist reverse proxy rejecting unsigned tokens
CC6.7 Data Protection: Per-workspace AES-256-GCM envelope encryption & dedicated HMAC secrets
CC7.2 Audit Trail: Immutable append-only AuditLog table with PII and credential scrubbing
CC8.1 Change Controls: Versioned immutable agent snapshots & Prisma migrations history
A1.2 Availability: Automated on-call paging alerts, circuit breakers & transient retry policies

Four Core Architectural Pillars of Enterprise Trust

Every layer of CadreGPT enforces deterministic safeguards rather than probabilistic hopes.

Zero Model Training Guarantee

All inference calls routed through the CadreGPT Central Model Gateway utilize strict commercial enterprise API agreements (Google Vertex/Gemini API, Anthropic Commercial API, OpenAI Enterprise API). Under these legally binding contracts, customer prompts, instructions, execution tokens, and generated outputs are NEVER used to train foundation models.

Zero Retention Policy: Prompts are strictly processed in ephemeral volatile memory and immediately purged upon token stream completion.

AES-256-GCM Envelope Vault

Third-party credentials (Google Search Console, Google Workspace, Microsoft 365, WordPress, Shopify, GitHub, Slack, HubSpot, Klaviyo, Plausible, Stripe, and custom webhook/REST endpoints) use unique per-workspace Initialization Vectors (IV), cryptographic authentication tags, and tenant-salted key derivation. Raw secrets are never stored in plaintext and never leaked into LLM prompt contexts.

Ephemeral In-Memory Decryption: Secrets are decrypted solely inside the worker process for the millisecond duration of tool execution.

Human-in-the-Loop (HITL) Gates

High-privilege actions (database writes, production code pushes, public WordPress publishing, payment triggers) automatically pause the BullMQ worker into an immutable AWAITING_APPROVAL state. No mutation occurs until an authorized human inspects parameter diffs and cryptographically signs authorization.

Fail-Safe Timeout: Tasks unapproved within 24 hours automatically expire and safely abort without executing external state mutations.

Two-Phase Financial Invariance

To eliminate runaway agent billing or infinite execution loops, CadreGPT enforces mathematical two-phase compute metering. Phase 1 holds an atomic reservation against your workspace balance before turn dispatch; Phase 2 settles exact token costs and releases the delta immediately.

Hard Spending Ceilings: Configurable monthly spend limits suppress auto-recharge transactions once breached, preventing budget overruns.
Technical Controls Matrix

End-to-End Enterprise Security Controls

Auditor-ready mapping of CadreGPT security layers to enterprise compliance standards.

Security LayerTechnical Control ImplementationEnterprise Standard
Data in Transit
Strict Transport Security (HSTS) with TLS 1.3 enforced across all web traffic, API endpoints, webhook callbacks, and upstream AI model router connections. Perfect Forward Secrecy (PFS) with 256-bit cipher suites.TLS 1.3 / NIST SP 800-52r2
Data at Rest
All third-party credentials and integration tokens are encrypted using AES-256-GCM envelope encryption with per-tenant salted keys and 96-bit unique nonces. Database storage volumes are encrypted via AWS KMS / LUKS.AES-256-GCM / FIPS 140-3
Tenant Isolation
Logical multi-tenant separation enforced at the database layer via strict workspace foreign key scoping and application-level authorization interceptors. Zero cross-workspace query leakage or token sharing.SOC 2 CC6.1 / ISO 27001 A.9.4
Worker Isolation
Agent execution runs in BullMQ workers that are separate processes from the web application. The model itself cannot open a socket, read a file, or reach the network: its only route outward is a declared, schema-validated tool, each call metered by the credit ledger and held for human approval when the action is sensitive.Declared-Tool Boundary
Secret Logging Defense
Automated telemetry redaction pipeline inspects all agent traces, stdout streams, and error dumps. High-entropy strings, Bearer tokens, GitHub keys, and password patterns are masked with [REDACTED] before persisting.GDPR Art. 32 / PCI-DSS Req 3
Access Control & RBAC
Granular role-based access control (Workspace Owner, Admin, Operator, Viewer). Cryptographically signed JWT session tokens with strict expiration and immediate revocation on password reset or role change.OAuth 2.0 / NIST RBAC Level 2
IMMUTABLE AUDIT TRAILS

Cryptographically Verifiable Execution Telemetry

Enterprise compliance requires forensic accountability. Whenever an autonomous agent takes an action, CadreGPT creates an immutable, timestamped telemetry event capturing:

1. Exact Prompt Hash
SHA-256 fingerprint of the prompt dispatched to the commercial AI gateway.
2. Model Routing Metadata
Selected provider (Vertex/Gemini, Anthropic, OpenAI), model version, latency, and token count.
3. Tool Argument Diffs
Exact JSON parameters before and after human authorization review.
4. Approver Signature
Authenticated user ID, IP address, and approval timestamp for HITL gates.
All audit trails are preserved with append-only integrity for 365 days.
Inspect RFC 9116 security.txt
Coordinated Vulnerability Disclosure

Responsible Disclosure & Security SLAs

CadreGPT welcomes responsible security researchers and partners. We maintain a strict security response SLA.

View security.txt Policy
24 Hours
Initial Triage SLA
Dedicated security engineer acknowledges and confirms vulnerability report.
72 Hours
Critical Patch SLA
Remediation or mitigation deployed for high and critical CVEs.
99.9%
Uptime SLA Target
High-availability multi-region redundancy with continuous health monitoring.
Report security inquiries directly to: [email protected]
Safe Harbor: We will not pursue legal action against researchers acting in good faith.

Enterprise Procurement & Security FAQs

Common questions from information security, risk, and compliance officers.

Does CadreGPT or upstream AI providers train models on our enterprise data?

Never. CadreGPT operates exclusively under enterprise tier terms with Google Cloud (Vertex/Gemini API), Anthropic, and OpenAI. These agreements legally certify that neither customer inputs, agent prompt expansions, nor execution outputs are retained or utilized for foundation model training or parameter adjustments.

How can our procurement team review CadreGPT's SOC 2 Type II report and DPA?

Enterprise customers can execute our standard Data Processing Addendum (DPA) directly online. To request our complete SOC 2 Type II audit report, ISO 27001 mapping, and penetration test executive summary under mutual NDA, please contact [email protected].

What happens to our encrypted credentials if we revoke an integration or terminate our account?

When you disconnect an integration, the associated ciphertext, initialization vectors, and authentication tags in our envelope vault are immediately purged from active storage. Upon account termination, all workspace data undergoes a 30-day soft-retention window before permanent cryptographic wipe, adhering to GDPR Article 17 requirements.

Can we enforce custom spend ceilings and Human-in-the-Loop rules?

Yes. Administrators configure hard monthly spending caps per workspace that prevent any automated execution turn from incurring overages. Additionally, tool approval policies allow organizations to designate exactly which tools (e.g. database updates, payment actions, public publishing) require mandatory human sign-off before execution.