Separation enforced in the database
Rows of other organisations are refused by the database itself (Row-Level Security), checked on production.
SeQurance helps organisations decide what to fix. That only works if you can trust us with your inventory. This page lists what we do, how it is evidenced, and where we are still working. We would rather tell you a gap than hide it.
Rows of other organisations are refused by the database itself (Row-Level Security), checked on production.
Available to everyone, mandatory for our operators, enforceable per organisation.
Every decision about a finding is chained with a hash, with an exportable evidence pack.
Server in the European Union. No analytics, advertising or third-party scripts.
Back-ups are encrypted and a copy is stored outside the server every night.
SeQurance itself does not hold ISO 27001, SOC 2 or NEN 7510 certification, and no independent penetration test has been done.
Statuses describe today. Each statement is backed by an automated test, the code or an observation of the running system. Contract documents marked draft are being reviewed by a lawyer.
Salted scrypt hashes, minimum length 12; constant-work check for unknown accounts.
Authenticator app with recovery codes, secrets encrypted; mandatory for our operators; an administrator can require it for the whole organisation (password-based accounts).
Microsoft Entra ID via OIDC (PKCE, state, nonce, signature checks). Verified against a test identity provider; not yet against a customer's own tenant.
Random 256-bit tokens, only a hash stored; sessions last 12 hours and end on sign-out, role change, deactivation and password change; API tokens are shown once, expire and can be revoked.
Viewer, analyst and administrator, enforced per action.
Sign-up is limited to work e-mail addresses.
Every query is scoped to the organisation and the database refuses other organisations' rows (Row-Level Security); automated cross-tenant tests; an isolation check runs against production.
Stored outside any web root under random names, downloaded only through authenticated, organisation-scoped, audited requests; SHA-256 rechecked before serving; never executed.
TLS for all public traffic with HSTS and automatically renewed certificates; database and Redis on an internal network without published ports.
Administrators export all organisation data and delete the organisation themselves; deletion is immediate in the live system and back-up copies expire within 35 days.
Passwords and tokens are stored hashed; two-step secrets and back-ups are encrypted.
Sign-ins, failed sign-ins and changes to inventory, SBOMs, findings, rules, settings, users and sources, with the IP address.
Append-only, hash-chained records of decisions, optional approval by a second person, evidence files, and an exportable pack that can be checked without us. It shows alteration; it is not a certificate.
CSRF protection, deny-all CSP for the API and nonce-based CSP for the interface, nosniff, frame denial, strict input validation, upload limits, safe XML parsing, SSRF protection, rate limits, neutralised CSV export.
Python dependencies locked with hashes; vulnerability scans on every change and weekly (pip-audit, npm audit, Trivy on both images); hardened containers: no root, read-only filesystem, no extra capabilities.
A full automated suite runs on every change, including cross-tenant, injection, upload and sign-in tests, also against PostgreSQL with Row-Level Security.
Database and uploaded files are backed up every night and before every update, encrypted, and kept for 14 days on the server.
Off-site back-ups are made every night.
Automatic security updates, firewall limited to SSH/HTTP/HTTPS and key-only SSH; a read-only check script exists.
External uptime checks with alerts by e-mail; the public status page is at https://stats.uptimerobot.com/npYLO4tcqh. There is no 24/7 operations centre.
A written procedure covers detection, triage, containment, notification (72 hours to the authority where we are controller; without undue delay to customers) and review. It has not been exercised yet.
Not yet performed.
No analytics, advertising or third-party scripts; fonts and icons from our own domain; only strictly necessary cookies.
Privacy statement, data processing agreement, subprocessor list and cookie notice; the contractual documents are drafts pending legal review.
Applicability for the hosted service and any downloadable edition is being assessed with legal advice; we make no compliance claim yet.
Our hosting provider is ISO 27001 and SOC 2 certified; these cover its infrastructure, not our application.
SeQurance itself is not certified (ISO 27001, SOC 2, NEN 7510).
Found a security problem? Tell us and we will respond within five working days. Our policy explains what is in scope and how we handle reports.
Read the policyNeed our data processing agreement, a security questionnaire answered, or a copy of the evidence behind a control? We answer on working days.
Write to us