Security
Security is part of how the software is built and run, not a feature added at the end. This page describes our practices. Specific commitments for a project are written into its scope.
Application security
We validate input on the server, use established frameworks rather than hand-rolled security code, and keep dependencies up to date with automated update checks.
Authentication
Sign-in is handled by an established identity provider or framework, not custom password code. Where a project needs it, we add single sign-on or multi-factor authentication.
Authorisation
Access is based on roles, and checked on the server for every request, so people only see and change what their role allows.
Secrets management
Passwords, keys and tokens are never committed to source code. They are generated per environment and stored only where the running system needs them.
Encryption
Traffic to public applications is served over HTTPS, and administrative access goes through an encrypted VPN. Encryption of stored data is agreed per project based on the hosting choice.
Infrastructure isolation
Production and testing run in separate environments. Where we run the infrastructure, networks are segmented so public, private and administrative traffic are kept apart.
VPN access
Servers we manage are administered over a private VPN with key-only logins. Administrative interfaces are not exposed to the public internet.
Backups
What is backed up, how often, where it is kept and how a restore is tested are agreed per project and written into the plan.
Logging
Application and access logging is set up per project, with retention agreed with you, so issues can be investigated without collecting more than needed.
Monitoring
Services are checked automatically, and the responsible people are alerted when something stops responding.
Deployment controls
Releases are built automatically from reviewed code. Nobody edits a production server by hand, and production runs a build that was first deployed to testing.
Data ownership
Who owns the data and the code, and where data is hosted, is set out in writing for each project before work starts.
Certifications and frameworks
If your organisation needs a project to meet a specific security framework or certification, tell us at the start so we can discuss what is required before you commit.
Have security requirements to discuss?
Tell us what your organisation needs and we will explain how we would meet it.
Talk to an engineer