Abhilekh · Security

Security is the architecture.

Abhilekh monitors regulated pharma environments, so the platform is built so records cannot be silently altered — from the sensor’s firmware to the auditor’s report.

Defence in depth

Every layer, verifiable

Isolation, integrity, and identity controls are enforced at each hop — not just at the application.

Records & data integrity

Every reading and user action enters a SHA-256 checksum chain on the server — a tamper-evident, immutable audit trail retained for 5+ years. E-signatures capture identity, timestamp, and meaning-of-signature, authenticated with password + TOTP.

Tenant isolation

PostgreSQL Row-Level Security isolates every tenant's data at the database layer — isolation is enforced by the database itself, not only by application code.

Access control

Role-based access control spans system roles (super_admin, support, billing) and tenant roles (admin, manager, operator, viewer), with multi-factor authentication mandatory for administrative access.

Device identity & transport

Every logger connects over TLS 1.2+ with per-device credentials — one broker identity per device, confined to its own topic space. X.509 device certificates are issued at provisioning, and mutual-TLS verification is on the security roadmap.

Signed firmware updates

Firmware ships as signed dual-bank A/B images (RSA-2048). A failed or interrupted update rolls back to the previous bank — a fleet device is never left bricked or running unverified code.

On-device immutable log

Each ABH logger maintains an immutable local audit log — 4 MB on 16 MB-flash loggers, 2 MB on coin-cell units — checksum-chained on the device itself, so records survive connectivity loss and reconcile after USB harvest.

Secrets & key management

Secrets, PKI, and e-signature transit run through HashiCorp Vault — credentials are never hard-coded into services or devices.

Cloud-native operations

The platform runs as a managed cloud SaaS on Kubernetes — MQTT/Kafka/Flink/ClickHouse streaming pipeline with per-tenant data paths, operated centrally by Neodrics.

Data path

Protected at every hop

A reading travels from a logger to a QA officer's report without ever leaving authenticated, encrypted, checksum-chained custody.

Device
per-device TLS credentials · immutable local log
MQTT broker
TLS 1.2+ · authenticated connections
Kafka
telemetry backbone · append-only
Flink CEP
stateful alert detection
ClickHouse
time-series store · analytics
Apps
RBAC + MFA · signed actions
On the roadmap

Data-residency options

For regulated markets that require in-country data residency, deployment options are on the product roadmap. This page documents what is built today — anything not listed here should be treated as not yet shipped.

Responsible disclosure

Found a security issue?

If you believe you have found a security vulnerability in a Neodrics product or this website, please report it to info@neodrics.com with details and reproduction steps. We ask for reasonable time to respond before public disclosure.

Vendor assessment

Need this for your quality system?

Running Abhilekh through security or vendor review? We'll walk your team through the architecture, controls, and validation documentation.