How Below Threshold protects procurements
This page says plainly what is protected and what is not.
Signing in
- Every buyer, evaluator and administrator account needs a password and a code from an authenticator app (two-step sign-in).
- After 5 wrong passwords or codes, the account is locked for 15 minutes.
- Staff are signed out automatically after 30 minutes without activity, and after 10 hours in any case.
- Suppliers do not have passwords. They confirm their email address with a 6-digit code that works for 15 minutes, only in the browser that asked for it.
- Invitation links are unique to one supplier and only work for the email address they were sent to, with a code. A forwarded link on its own gives no access.
Sealed submissions
- Nobody at the buyer can open answers, prices or files before the deadline, and only after the procurement lead releases them. Releasing needs a confirmation and is logged.
- Each supplier's submission is encrypted with its own key. The service only unlocks that key for the buyer once the deadline has passed and the lead has released the submissions.
- Evaluators must declare any conflict of interest before they can see submissions. A declared conflict needs a recorded decision first.
- Every attempt to open submissions, and every file download and export, is recorded in the audit trail. Exporting a record with bid contents is limited to the procurement lead.
- The deadline is checked by the server on every submission, against one fixed time.
Data and files
- All connections use HTTPS. Plain http:// addresses are redirected, and browsers are told to use HTTPS only.
- Stored files and submission contents are encrypted (AES-256).
- Each organisation sees only its own procurements. The people who run the platform have no access to procurements through the application.
- A real virus scanner is not connected yet. We use ClamAV, an open-source virus scanner that runs inside our own hosting. Until it is connected, uploads from real organisations are refused (the fictional demo uses a test scanner). Files that fail the check are quarantined: kept encrypted, never downloadable by anyone, logged, and deleted after 30 days.
- The audit trail can only be added to: the database refuses changes and deletions, and each entry includes a fingerprint (hash) of the one before it, so any change would be detected.
- Encrypted backups are made every day and kept for 35 days. Restoring from a backup is tested.
- Hosting region: to be confirmed before any live procurement.
What this does not protect against
- The hosting itself. The service holds the keys it needs to run, so someone with full control of the hosting (the hosting company, or anyone who got into our hosting account) could in principle read stored data. Encryption protects copies of the database and backups, not a fully compromised server. Submissions are not sealed by a separate key holder.
- Email. Codes, invitations and outcome letters go by email, so they are only as safe as the recipient's inbox.
- Your own devices and accounts. Anyone with your password and your authenticator app can act as you.
- Independent testing. The service has not yet had an independent security test (penetration test).
Report a security problem
Email security@belowthreshold.co.uk. Please do not test against real procurements: use the demo. See also security.txt.