Trust & security
Security at ERP Preflight
Artifacts from SAP systems can contain configuration, code and personal data. These are the controls implemented in the platform.
Tenant isolation in the database
Every tenant table is protected by PostgreSQL row-level security. Tenant queries run as a dedicated non-privileged role, so isolation is enforced by the database even if application code is wrong.
Safe file ingestion
Uploads are checked by file signature rather than extension, scanned for malware and unpacked with limits on size, expansion ratio, nesting and paths. XML is parsed with external entities disabled.
Secret redaction
Credentials and secrets are redacted before code snippets are stored as evidence.
Tenant-scoped storage
Customer artifacts are stored under a tenant- and project-specific path; download links are short-lived.
Deterministic analysis and AI boundaries
Findings are produced by deterministic rules. Optional AI assistance cannot raise confidence above INFERRED, and customer artifacts are not used to train AI models.
Account security
Passwords are hashed with Argon2id, sign-in endpoints are rate limited and sessions can be revoked by signing out.
More details
To report a vulnerability, contact the operator via the address in the imprint. Imprint
Find out what will break — before go-live
Create a workspace, upload your first export and review evidence-backed findings.