Security & Trust

Built for strict data boundaries.

Questor is designed around explicit controls over what a model can read, where source code is processed, and how every gate decision is signed and audited.

3D Code & Deployment Boundary
Stage 0 Redaction Your Boundary
Option 1 · Questor Cloud (Zero Infrastructure to Manage) Stage 0 strips secrets before analysis. Hard tenant isolation enforced server-side on every query.

Redacted Before Analysis (Stage 0)

Before any model reads source files, Questor's deterministic Rust sanitizer strips detected API keys, passwords, tokens, and private keys, logging every redaction into an Ed25519-signed manifest.

Bring Your Own Enterprise AI or Subscription

Run inference under your own enterprise terms by connecting Questor directly to your Azure OpenAI / AI Foundry deployment, Anthropic API, or Claude and Codex CLI subscriptions.

Stage-Gated Analysis & Air-Gapped On-Prem

Questor maps entry points, guards, and sinks deterministically first, running Stage 3 verification only on candidates that pass Stage 2.1 validation. For air-gapped environments, run completely offline via Ollama.

01 · Chain of custody

Signed gate decisions

Each gate decision (A–H) is Ed25519-signed with a per-tenant key over a canonical payload hash. A signed manifest binds the scan to the exact commit SHA and redacted source tree so exported audit packs can be verified offline.

gate · payload sha256 · signer · Ed25519

02 · Redaction first

Secrets stripped before prompts

Before analysis starts, Stage 0 clones and redacts the repository, stripping detected secrets and PII and recording each redaction (file, line, detector) in the signed manifest. Downstream stages operate strictly on the redacted snapshot.

clone → redact → sign → analyse

03 · Isolation

Server-enforced tenant scoping

Private & On-Prem editions run single-tenant inside your infrastructure. Questor Cloud enforces tenant isolation server-side on every query: tenant scope is derived from the authenticated session rather than client headers, and cross-tenant IDs return 404. Passwords use PBKDF2-HMAC-SHA256 and session cookies use HttpOnly · Secure · SameSite.

04 · Zero external egress

Air-gapped operation supported

The On-Prem edition requires no outbound internet access to run the pipeline. Inference can target an on-host model, an enterprise API endpoint under your own contract, or a host-side CLI agent where provider credentials stay outside scan containers.

05 · False-positive controls

Unverified claims are held or disproven

Candidates that fail negative controls are recorded as Disproven rather than promoted as warnings. Candidates requiring external runtime confirmation are held as Needs Evidence until answered, keeping engineering queues focused on confirmed issues.

06 · Reproducible audit logs

Append-only verification records

Exports are content-addressed and reproducible from stored evidence artifacts. Every case state change is recorded in an append-only audit log with actor, timestamp, and role metadata.

Vulnerability disclosure

Report a security issue.

We welcome coordinated vulnerability disclosure. Email security@mach41.com with technical details and reproduction steps. We acknowledge reports within two business days and provide status updates through remediation. Please do not test against workspaces you do not own.

coordinated disclosure · good-faith research credited

Inspect a signed case record.

Review how Stage 0 redaction and Gates A–H work together on a sample case, or schedule an architecture review for your environment.

© Copyright MACH41 (UK) Ltd. All rights reserved.