How QUBIQ handles access and disclosure
What the platform enforces, what this website does, and how to report something you have found.
In the platform
Role-based access control. Permissions are defined per resource and per API surface rather than as a single administrator flag, so an operator, an integrator and a plant manager can hold genuinely different capabilities.
Audit trail. Configuration changes and operator writes are recorded with the actor, the action, the timestamp and the originating client address. The audit trail can also be written to an external journal so it does not live only inside the system it is auditing.
Outbound request guarding. The REST gateway refuses to fetch internal addresses on request. A gateway that will fetch any URL it is told to is a liability on an OT network, so that behaviour is tested rather than assumed.
Scoped inbound routes. REST endpoints exposed by a pipeline carry explicit scopes; they are not open by virtue of existing.
Script isolation. Python runs in separate worker processes rather than inside the runtime, so a runaway script cannot take the gateway down with it.
Not in this release
We would rather list these than let you assume them:
- Single sign-on (SAML or OIDC). Authentication today is username and password with role-based authorisation on top.
- Multi-factor authentication.
- Hot-standby redundancy.
All three are on the roadmap. If one of them gates a deployment for you, tell us — that is exactly the kind of input that sets our build order.
On this website
The site stores content and form submissions in Postgres with row-level security enabled on every table. The public site reads through an anonymous role that can only see published rows and cannot write anything at all. Administrative writes are authorised by database policy rather than by application code, so a bug in the front end cannot grant access the database has not granted.
Reporting a vulnerability
If you have found something, we want to know, and we will not be difficult about it.
Email security@goqubiq.com with enough detail to reproduce the issue. We will acknowledge within two business days and keep you informed while we work on it. Please give us a reasonable window to fix the problem before disclosing it publicly.
We do not currently run a paid bounty programme. We do credit reporters who want to be credited.