Tenant isolation
A person signed into one factory cannot read another factory's devices, readings or users.
Security
What is in place, and what is not finished.
This page stays with what the product enforces. Roadmap items are labelled as roadmap.
Per-device tokens
Ingest tokens are stored hashed. A sensor posts only its own reading.
MFA
Every factory user can enroll an authenticator. Ops sign-in uses its own second factor. A factory can require MFA for the whole team.
Audit log
Security-sensitive changes are written to an append-only audit trail.
Ops allow-list
In production the fleet console refuses remote access when the IP allow-list is empty. Loopback remains available for local administration.
Health token
The public health check returns only a status. Component detail requires a separate token.
Headers and process user
Responses send a content security policy and the usual browser hardening headers. The app and the background worker are built to run as a non-root user.
Roadmap
- MQTT from the factory over TLS, with a per-gateway identity. Until that ingress exists, the broker is not published.
- Keep the ops allow-list to named networks. An entry of 0.0.0.0/0 matches every IPv4 address, so it is not a restriction.
- Data residency is agreed in the customer contract. This page does not claim a hosting region.
Report a vulnerability privately to the FactoraERP maintainers. Do not include customer telemetry or live credentials.