Enterprise Security & Trust Whitepaper

How TrackIt protects your SAP data.

This page describes what is actually built and verified in production today, and is explicit about what is not yet in place. We state the verified technical reality plainly rather than hiding behind marketing assertions.

Database RLSFORCE Enabled
In-SAP Code0 ABAP Lines
Ledger IntegritySHA-256 Chained
EncryptionAES-256-GCM
DATABASE LEVEL ISOLATIONImplemented

Tenant isolation, enforced by the database

Every tenant-scoped table carries a Postgres row-level security policy keyed on the requesting organization, applied per-request via SET LOCAL — not just an application-layer check that a forgotten filter could bypass. Policies are FORCE-enabled, so even the table owner is subject to them. Verified: a session scoped to one organization returns zero rows for another; an unscoped session returns zero rows rather than everything.

PROJECT BOUNDARY ENFORCEMENTImplemented

Project isolation within an organization

Every route enforces that a user has both an active organization membership and an active project membership before returning project content. For transport request data specifically, this is additionally backed by a database-level restriction: a session scoped to one project cannot read or write another project's transport requests, even via a raw query, regardless of application-layer bugs.

TAMPER-EVIDENT RECORDImplemented

Tamper-evident audit ledger

Governance actions are recorded in a hash-chained ledger — each entry’s signature incorporates the previous entry’s, so altering or deleting a past record breaks the chain in a way that is independently verifiable, not just logged. A separate HMAC-signed activity log covers general application events.

ENCRYPTION AT RESTImplemented

Encryption

Sensitive fields (SSO client secrets, SAP connection credentials) are encrypted at rest with AES-256-GCM. All traffic is served over TLS. Database role credentials are rotatable via a provided operator script, and the platform enforces least-privilege database roles for the application, background workers, and migrations separately.

FEDERATED IDENTITY & SCIMImplemented

Sign-in, single sign-on and directory sync

Email and password with TOTP two-factor, magic links, and Microsoft Entra or Google sign-in. Your organization’s admin can connect your own identity provider over SAML 2.0 or OpenID Connect: the email domain must be proven with a DNS record, and only existing, active members of your organization can sign in that way. SCIM 2.0 directory sync provisions users and groups, limited to your verified domain. Requiring SSO cannot be switched on until it has worked once, so a wrong setting cannot lock you out.

OPERATOR PRIVACY BOUNDARYImplemented

The platform operator cannot read your records

Platform operators (TrackIt staff) see counts and manage billing and lifecycle state. They cannot read your transports, approvals, evidence, audit trail or member list, and the API enforces this rather than the console hiding it. Every operator change is written to an append-only operator log. If you want hands-on help, your organization admin invites a support engineer with the role the task needs and removes them afterwards; the invitation and removal are in your own audit trail.

POINT-IN-TIME DISASTER RECOVERYImplemented

Backup and recovery

Nightly logical backups (checksummed) plus continuous write-ahead-log archiving for point-in-time recovery. Restore verification runs on a schedule, and a restore that only produces a partial database fails loudly rather than reporting false success. A recent drill restored a 187 MB dump in about 41 seconds. Copying backups off the server is a deployment setting; ask us to confirm it is on for your deployment.

Compliance Roadmap — Honest Current Status

What is built vs. what is on the roadmap

We are not yet SOC 2 or ISO 27001 certified, and the platform has not yet had an independent third-party penetration test. Both are on our roadmap. If either is a requirement for your procurement process, tell us — we plan around real customer timelines rather than a fixed date, and can share our internal security review findings under NDA in the meantime.

Also not yet in place: the SAP connection has been tested against a simulator and automated test suites, not yet against a customer’s live production landscape; single sign-on and directory sync have not yet been run against a live customer Entra or Okta tenant; and TrackIt runs on a single server with no automatic failover, so there is no uptime commitment until one is agreed in your contract.

The claims above were checked against a running system, by an internal security review and by automated tests, not asserted from documentation. That review is not a substitute for independent, third-party certification, and we say so plainly rather than implying otherwise.

Questions about a specific control, or need documentation for your security architecture review?