Security & trust
If you record vulnerabilities and security incidents in Nebrino, you entrust us with sensitive information. This page explains where that data is stored and how we protect it – only measures that are actually in operation.
- Servers in Germany
- ISO/IEC 27001 data centres
- No AI services
- Two-factor and single sign-on
- Security contact per RFC 9116
- Daily encrypted backups
Where your data is stored
- The application, database (Supabase, self-hosted) and file storage run on our own servers at Hetzner Online GmbH in the Falkenstein data centre; encrypted backup copies are kept on a second Hetzner server in Nuremberg.
- Products, SBOMs, findings, reporting cases and evidence do not leave these servers. We use no database or storage services from US providers.
- Nebrino uses no AI services. Your information is not sent to language models.
- For vulnerability matching, only package names and versions are sent to public databases (OSV.dev, NVD), no information about you. Emails are sent via Brevo (servers in France, Germany and Belgium), payments are handled by Stripe – details on the subprocessors page.
Access and tenant isolation
- Each organisation only sees its own data: the database itself enforces isolation (row level security), and automated tests check it for every table on every change.
- Two-factor authentication (TOTP) for every account; once set up, the database also requires the second factor. Single sign-on (SAML) with enforcement per domain.
- Roles per organisation (owner, admin, member). Passwords are stored only as hashes; API keys, invitation and supplier links only as SHA-256 hashes.
- Encrypted connections throughout (HTTPS with HSTS), content security policy, rate limiting of sign-in attempts.
Traceability
- Reporting cases keep an audit log that only the server writes and nobody can change or delete. Submitted notifications are frozen, corrections require a reason.
- A change log records who changed products, assessments, documentation and evidence, and when.
- Released document versions are archived as PDF with a checksum, which is verified on every download.
Availability and your data
- Daily encrypted backup of database and files; the copy is fetched by a second server that can only read the backups on the main server.
- Monitoring from a second location, public status page. Deadlines run regardless of Nebrino – which is why every reporting case has an emergency sheet and a calendar file.
- You can export all data of your organisation at any time and delete the organisation. Server log data is deleted after 14 days at the latest.
Reviews and reports
- Code review based on OWASP criteria (27 Sep 2026) and a subject-matter review including security findings (October 2026). An external penetration test is still pending; we do not hold a certification of our own (such as ISO 27001).
- Found a vulnerability in Nebrino? Report it to the address in our security.txt – we reply in writing.