Secure Software Development
Software built with security considered from the start, not bolted on at the end.
The problem
Security problems are cheapest to fix when the software is being designed, and most expensive after it is live. Building security into the design means fewer nasty surprises at launch.
What's included
- Software built to an agreed scope, with security designed in from the beginning
- Threat thinking up front: what could go wrong, and what would it cost
- Sensible handling of logins, permissions, data and secrets
- A security review of the finished software before it goes live
- Clear documentation so your team can run and maintain it
How it works
- 1
Scope
We agree what is being built, who it is for, and what needs protecting.
- 2
Design
We plan the software with security considered from the start.
- 3
Build
The software is built and regularly checked against what we agreed.
- 4
Review and launch
A security review before go-live, then a handover so your team can run it.
FAQs
What kind of software do you build?
Scope is agreed per project. Tell us what you need, and we will say honestly whether it is a good fit before any work starts.
Who owns the software?
This is set out in the written agreement for each project.
Can you review software built by someone else?
Yes. See Application Defence Analysis for reviews of apps that are already built.