CUT THROUGH THE CVE NOISE — Explore the platform
TRUST CENTER

How we keep your data safe, and what we do not claim.

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.

Last reviewed 2026-11-19 · Nederlands

At a glance

In place

Separation enforced in the database

Rows of other organisations are refused by the database itself (Row-Level Security), checked on production.

In place

Two-step verification

Available to everyone, mandatory for our operators, enforceable per organisation.

In place

Tamper-evident decision records

Every decision about a finding is chained with a hash, with an exportable evidence pack.

In place

EU hosting, no tracking

Server in the European Union. No analytics, advertising or third-party scripts.

In place

Back-ups outside the server

Back-ups are encrypted and a copy is stored outside the server every night.

Not available

No own certification yet

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.

Security controls

Access and identity

  • Password storageIn place

    Salted scrypt hashes, minimum length 12; constant-work check for unknown accounts.

  • Two-step verificationIn place

    Authenticator app with recovery codes, secrets encrypted; mandatory for our operators; an administrator can require it for the whole organisation (password-based accounts).

  • Single sign-onIn place

    Microsoft Entra ID via OIDC (PKCE, state, nonce, signature checks). Verified against a test identity provider; not yet against a customer's own tenant.

  • Sessions and API tokensIn place

    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.

  • RolesIn place

    Viewer, analyst and administrator, enforced per action.

  • Work e-mail onlyIn place

    Sign-up is limited to work e-mail addresses.

Separation and data protection

  • Tenant separationIn place

    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.

  • Customer filesIn place

    Stored outside any web root under random names, downloaded only through authenticated, organisation-scoped, audited requests; SHA-256 rechecked before serving; never executed.

  • Encryption in transitIn place

    TLS for all public traffic with HSTS and automatically renewed certificates; database and Redis on an internal network without published ports.

  • Export and deletionIn place

    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.

  • Encryption of credentials and back-upsIn place

    Passwords and tokens are stored hashed; two-step secrets and back-ups are encrypted.

Traceability

  • Audit trailIn place

    Sign-ins, failed sign-ins and changes to inventory, SBOMs, findings, rules, settings, users and sources, with the IP address.

  • Decision records and evidence packIn place

    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.

Application and supply chain

  • Application hardeningIn place

    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.

  • Dependencies and imagesIn place

    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.

  • Automated testsIn place

    A full automated suite runs on every change, including cross-tenant, injection, upload and sign-in tests, also against PostgreSQL with Row-Level Security.

Operations and resilience

  • Local back-upsIn place

    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-upsIn place

    Off-site back-ups are made every night.

  • Server hardeningIn progress

    Automatic security updates, firewall limited to SSH/HTTP/HTTPS and key-only SSH; a read-only check script exists.

  • Uptime monitoringIn place

    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.

  • Incident responseIn progress

    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.

  • Independent penetration testNot available

    Not yet performed.

Privacy and compliance

  • No trackingIn place

    No analytics, advertising or third-party scripts; fonts and icons from our own domain; only strictly necessary cookies.

  • GDPR documentsIn place

    Privacy statement, data processing agreement, subprocessor list and cookie notice; the contractual documents are drafts pending legal review.

  • Cyber Resilience ActIn progress

    Applicability for the hosted service and any downloadable edition is being assessed with legal advice; we make no compliance claim yet.

  • Hosting provider certificationsIn place

    Our hosting provider is ISO 27001 and SOC 2 certified; these cover its infrastructure, not our application.

  • Own certificationNot available

    SeQurance itself is not certified (ISO 27001, SOC 2, NEN 7510).

Documents

Report a vulnerability

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 policy

Talk to us

Need 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