Security & trust, documented for review.

AssetStack is an enterprise asset-management platform engineered for organisations with strict security obligations — government agencies, utilities and critical-infrastructure operators. The platform combines independently audited infrastructure with a single-tenant deployment model so that each customer's asset, facility and financial data is fully isolated, encrypted and auditable.

The underlying infrastructure is certified and audited by independent third parties. Reports are available to enterprise prospects under NDA.

In transit

• TLS encryption on all API calls and data transfers, enforced at the gateway.
• Modern cipher suites protect against interception and downgrade attacks.

At rest

• All data tables are encrypted with AES-256 or equivalent.
• Encryption keys are managed by a dedicated key-management service.
• Uploaded files are served through signed, time-limited URLs.

Standards-based authentication

• OAuth 2.0 — the same protocol trusted by Google, Microsoft and Apple.
• Signed, time-limited tokens validated server-side; logout revokes the session immediately.

Multi-factor authentication (MFA)

• Authenticator-app (TOTP) or SMS second factor available for all accounts.
• Protects against credential theft and phishing.

Enterprise single sign-on (SSO)

• OIDC integration with corporate identity providers — Okta, Azure AD, GitHub and any OIDC-compliant IdP.
• Centralised identity, group-based access and automated de-provisioning.

Every customer runs on a dedicated application instance with its own isolated database and unique application identifier. There is no shared multi-tenant database, and therefore no class of cross-tenant data-leakage vulnerabilities.

• Each instance is provisioned from a master template; no customer data is ever copied during provisioning.
• One instance physically cannot read or write another instance's data.
• Isolation is guaranteed by infrastructure, not only by application logic.

Row-level security (RLS)

Controls which records each user can read, create, update or delete based on identity and role.

Field-level security (FLS)

Controls which fields within a record a user can read or write — e.g. internal cost projections and assessment notes can be restricted to administrators.

An automated security scanner continuously detects permission gaps, exposed credentials and misconfigurations.

Sensitive operations run server-side and enforce security in code, not just in the UI:

• Authentication checks — every privileged endpoint verifies the caller and rejects unauthenticated requests with a 401.
• Role gates — administrative operations (model retraining, system audits, financial approvals) verify the caller's role and return 403 otherwise.
• Least-privilege elevation — elevated service-role access is requested explicitly per operation, never granted by default.
• Parameterised queries — the data layer prevents injection attacks by construction.

Secrets management

• API keys and credentials live in an encrypted secrets vault, never in source code.
• Secrets are injected at runtime and never exposed to the browser.
• Rotating a secret automatically redeploys dependent functions with zero downtime.

Every sensitive action is recorded to an append-only audit log, available to administrators for forensic investigation and compliance reporting.

Logs are append-only (users cannot edit or delete them), restricted to administrators, and — on enterprise tiers — streamable into external SIEM tooling such as Splunk or Datadog.

Access is governed by configurable roles, with every sensitive operation checking the caller's role before proceeding.

Roles are fully customisable per deployment and managed by administrators.

• Default: United States data centres.
• Enterprise tiers: EU or UK clusters for data-localisation requirements.
• Suitable for organisations subject to GDPR, UK GDPR and regional data-sovereignty mandates.