Oninit® Informix Analyser — Security & Privacy
The Informix Analyser handles operational data — configuration files, log tails, performance counters, AF dumps — that is typically considered confidential by the customers who run the underlying database. The summary below describes how we treat that data. Detailed operational and compliance documentation is available on request through your engagement contact.
What we receive
A submission consists of an ifxcollect tarball or an
af.<hex> assertion-failure file. These are
captured by the customer on the customer-controlled host and
uploaded through the portal. The analyser does not run on the
customer database, does not connect to the database remotely, and
does not collect anything not present in the submitted artefact.
Confidentiality
Submissions and the reports generated from them are treated as confidential information of the submitting customer. Each submission is scoped to its own ULID-addressed storage area; cross-customer access is structurally prevented (cross-tenant reads return HTTP 404 rather than 403, so a stranger cannot even verify a submission ID exists). Reports are not shared with third parties.
Authentication & access
Portal access is gated by a magic-link sign-in. Magic links expire in fifteen minutes; sessions are short-lived and stored in HMAC-signed cookies that the server can revoke. Paid-tier features (named snapshots, customer-facing DrWatson Q&A, the per-rule reference pages) sit behind an additional authorisation check.
Transport & storage
The portal expects to run behind TLS for any production customer deployment; uploads, downloads, and session cookies travel only over the encrypted channel. At-rest data lives on operator-managed storage with normal Unix permissions; encryption-at-rest options follow the deployment host's standard practice.
Pre-upload obfuscation
Customers who want a tighter trust boundary can scrub identifiers out of captures before upload. See Obfuscation for what DrWatson reads by default, what's safe to redact (hostnames, table and database names, SQL literals, OS user IDs), and the account-level toggles available on request.
DrWatson Q&A grounding
The optional question-and-answer panel on a delivered report is grounded strictly on that report's own findings. DrWatson is not shown the underlying fact base, other customers' data, or historical reports; it has no tool surface for fetching anything beyond the question and the report it was asked about. Customers who do not want any third-party model involvement can request the feature be disabled for their tenant.
Retention
Customer submissions and the rendered reports are retained on analyser storage for the period agreed in your engagement. The analyser ships a daily sweeper that purges submissions past their retention window. Deletion-on-request is supported — contact your engagement representative.
Audit trail
Every render produces an immutable record of which rules fired, the facts they consumed, and the recommendations attached. The record is available to the customer alongside the PDF report and is retained on the same schedule.
Reporting a security concern
For security questions, vulnerability reports, or compliance documentation requests, contact support.info@oninit.com or your usual engagement representative. Detailed operational posture (specific cryptographic primitives, key-management practice, data-flow diagrams, retention timers) is available under NDA.