| Encryption | All connections over HTTPS with HSTS, and encrypted backups. | A.8.24 |
| Passwords and keys | Kept in a managed vault, with minimal permissions per key. We rotate a leaked key immediately and report it as an incident. | A.5.17, A.8.24 |
| Two-factor authentication | Mandatory for staff. | A.8.5 |
| Limited access | Staff only have access to what they need. Requests can only be reached by our server functions, not through the public database API. | A.5.15, A.8.3 |
| Network and firewalls | Vercel WAF with bot protection, firewall and brute-force protection on our servers, server management via a private network. | A.8.20, A.8.21 |
| Personal link | The code in your personal link sits after a hash sign (#), so it does not end up in server logs. The database only holds a hash of that code. | A.8.5 |
| Forms and attachments | The server checks all input again, Vercel BotID stops automated abuse and attachments are checked for file type, number and size. | A.8.26, A.8.28 |
| Security headers | CSP, HSTS, X-Content-Type-Options, Referrer-Policy and Permissions-Policy on the website. Other websites cannot embed our pages. | A.8.26 |
| Backups | Daily, stored encrypted at a separate location, plus weekly snapshots of the servers. | A.8.13 |
| Monitoring | Alerts when the website is down. | A.8.16 |
| Incidents | Every incident is recorded, investigated for its cause and followed up with improvements. | A.5.24 to A.5.27 |
| Vulnerabilities | Automatic alerts for vulnerable dependencies. | A.8.8 |
| Change management | Changes go through a pull request on a protected main branch. | A.8.25, A.8.32 |
| Suppliers | An overview of our subprocessors, with a link to their data processing terms. | A.5.19, A.5.20 |
| Source code | Kept in a private environment with mandatory two-factor authentication. | A.8.4 |
| Test and production | Changes are first tested in a separate preview environment. | A.8.31 |
| Configuration | Monitoring of deviating server settings and changes to the firewall. | A.8.9 |
| Recovery | A recovery plan aiming for at most 24 hours of data loss and recovery within about 2 hours. | A.5.30 |
| Security reports | Report a security issue confidentially via info+security@certificeerwijzer.nl. | A.6.8 |
| Overview of systems | A register of our company assets. | A.5.9 |