This system holds supplier due-diligence data.
234Supply holds supplier ownership information, due-diligence evidence and bank metadata. The controls below are product invariants — enforced in the domain layer and covered by automated tests, not left to operational discipline.
Tenant isolation at the data layer
Every tenant-owned row carries a tenant discriminator enforced by row-level security in Postgres as well as by the repository layer. A cross-tenant read fails at the database, not merely in a UI filter.
Least privilege on sensitive fields
Bank metadata, ownership information and internal evaluator notes are field-restricted. A supplier never receives another supplier’s data, and redaction happens where the data is fetched, so a restricted value never enters a response payload.
An audit trail tenant users cannot edit
Every controlled action — including releasing a month of deductions to payroll — writes an append-only event recording who acted, in which role, from where, the record it concerned, the reason given and a correlation ID. Audit events can be filtered and exported, never edited or deleted.
Corrections, not overwrites
No historical policy, consent, instruction, collection or financial event is ever silently changed. A correction creates a new linked event and a reversal preserves what it negates.
Careful authentication
Passwords of at least twelve characters, rate-limited sign-in that never reveals whether an account exists, and reset links that work once, expire within the hour and sign the account out everywhere.
One supplier identity, separate buyer relationships
A supplier maintains one company profile. Each organisation holds its own private supplier record, status and qualification history. Approval by one organisation is never visible to, or inherited by, another.
Uploads are checksummed and never executed
Every legacy workbook and document is checksummed and preserved byte-for-byte as source evidence. Formulas, macros, external links and data connections are never executed, and macro-enabled workbooks are refused. Uploaded files are recorded as unscanned until malware scanning is in place.
Portability by design
Your supplier register, employees, requests, repayments, deduction instructions and audit trail export on demand as files a spreadsheet opens. No billing dispute or plan change makes your own records unreachable.
Not yet in place
What a security review will ask about and we do not yet do. Each moves up the page when it ships and is tested.
Multi-factor authentication
A second factor for owners, payroll and approvers. Until then, use a password manager and a unique password.
Malware scanning of uploads
Uploads are stored and checksummed but not yet scanned, and are marked unscanned wherever they are shown. Nothing uploaded is ever executed.
Export of original uploaded files
The originals are kept as evidence; exporting them in bulk from the product is not yet available.
Independent certification
234Supply holds no ISO 27001 or SOC 2 report. We will not imply one.
Responsible disclosure: if you believe you have found a vulnerability, write to security@234supply.com. We will acknowledge within two working days.