Security is in the foundation.
Every system we deliver is set up to current cybersecurity and privacy standards. Not as an optional extra, but as standard. After all, a house with a beautiful facade and a weak lock is not a good house.
Security by design
Before development starts, we map out for each system what data it holds, who may access it and what could go wrong.
- Standard
- A threat analysis and a security plan in the design phase.
- Per project
- How deep the analysis goes depends on the sensitivity of the data.
- Check
- You receive the security plan and we go through it together before development.
GDPR & privacy by design
We only process the data that is needed, for a defined purpose and with a retention period.
- Standard
- Data minimisation, purpose limitation and retention periods in the design; a data processing agreement when we process personal data on your behalf.
- Per project
- Support with a DPIA when the processing calls for one.
- Check
- The data flows and retention periods are included in the delivery documentation.
Encrypted, in transit and at rest
Connections and stored data are encrypted. Passwords and API keys are never in the source code.
- Standard
- TLS (HTTPS) on all connections and secrets in a managed key store.
- Per project
- Encryption of database and backups through the chosen hosting platform.
- Check
- We check the TLS settings and the storage of secrets at delivery.
Least privilege & MFA
Every user and every integration only gets the permissions it needs.
- Standard
- Role-based access and multi-factor authentication on admin accounts.
- Per project
- MFA or single sign-on for all users, connected to your own identity provider.
- Check
- You receive an overview of roles and permissions at delivery.
Tested against OWASP
We build and test against known vulnerabilities from the OWASP Top 10.
- Standard
- Code and dependencies checked for known vulnerabilities, and an OWASP Top 10 checklist before go-live.
- Per project
- Assessment at an ASVS level and an independent penetration test by an external party.
- Check
- We share the outcome of the checks at delivery.
AI within clear boundaries
AI only gets access to what it needs, and what it does can be traced.
- Standard
- Business AI services where your data is contractually not used for training, and logging of AI actions.
- Per project
- Human approval for sensitive actions and extra measures against prompt injection.
- Check
- The logs show which action the AI performed and at whose request.
European hosting where possible
Data is preferably stored in the EU. Where a service does not offer that, we tell you in advance.
- Standard
- Separate test and production environments, and backups.
- Per project
- The hosting location, which depends on the chosen services and your requirements.
- Check
- All services used and their locations are listed in the delivery documentation, in your name.
Logging & incident response
If something goes wrong, we want to see it quickly and everyone knows what to do.
- Standard
- Error monitoring, audit logs and a documented incident process.
- Per project
- Response and notification times, which we set out in the agreement.
- Check
- After an incident you receive a report of the cause, impact and measures taken.
Staying secure, not just becoming secure
Software ages. That is why security is not a one-off action.
- Standard
- Updates and security patches under a maintenance agreement.
- Per project
- Periodic re-checks or penetration tests for sensitive systems.
- Check
- Completed updates can be traced in the version history of your own repository.
These are standards and guidelines we use as a reference, not certifications held by CareScript. Which ones apply depends on your sector and the type of data. We decide that together in the design phase and record it in the security plan. If your organisation needs a certification or audit, we align the system and the documentation with it.
How this website is secured.
What we promise, we also apply to our own site. You can check these measures yourself in the browser or with a header scanner.
- Encrypted access only: HTTPS with HSTS, so browsers never fall back to an unencrypted connection.
- Strict script policy: a Content Security Policy only allows scripts, fonts and images from our own domain.
- Protection against misuse in frames: X-Frame-Options and frame-ancestors prevent clickjacking; X-Content-Type-Options and a restrictive Permissions Policy are enabled.
- No connections to third parties: fonts and images are on our own server. Visitor statistics run through our own domain, without cookies and without personal data.
- Contact form: required fields are checked in the browser, a hidden field catches spam bots and submissions also pass through Netlify's spam filter on the server. Submissions only reach CareScript, on accounts with multi-factor authentication, and are kept according to the periods in the privacy statement.
Secure software, custom built?
We are happy to discuss which requirements apply to your sector and your data.