Problem
When security is added late, it is added badly: controls that users work around, gaps between systems, and fixes that delay launch. Designs often miss the threats that matter because nobody asked how the system could be misused.
Outcomes
- Threats identified and designed against before build starts.
- Security controls built into the architecture from the start.
- Personal data collected and kept only where needed.
- Secure patterns reused across projects.
- Fewer security findings late in delivery.
Scope
In scope
- Threat modelling.
- Security architecture design: network, application, data and identity.
- Secure design patterns and reference architectures.
- Encryption, key and secrets management design.
- Security requirements for delivery teams.
- Design reviews.
Not included
- Performing regulated security testing. We coordinate specialist testers.
Privacy engineering
Privacy is easier to build in than to retrofit. We design systems to collect only the personal data they need, protect it, keep it only as long as needed and make it easy to handle people's rights requests.
- Data protection impact assessment support.
- Data minimisation and retention design.
- Consent and preference handling.
- Rights request handling built into systems.
Approach
Discovery
We ask how the system could be attacked or misused, and build a threat model for it before anything is built.
Delivery Planning
We design proportionate controls for each threat, and turn the design into security requirements that delivery teams can build and test.
Build and Test
We review designs and builds against the requirements. Security requirements are tested, and secrets are never stored in code.
Operational Readiness, Hypercare and Closure
We hand over the threat models, designs, requirements and design review reports, together with secure patterns your teams can reuse. We close the work with your sign-off.
Deliverables
Technologies
Controls
Frequently Asked Questions
What is threat modelling?
It is a structured way of asking how a system could be attacked or misused, so the design can defend against it before it is built.
Can you review a design another team produced?
Yes. Independent design reviews are part of this service.
Does privacy engineering replace our data protection officer?
No. It supports your data protection officer by building their requirements into the system.
When should we involve you?
As early as possible, ideally during design. It is cheaper to design security in than to fix it later.
Designing a new system?
A Technical Audit reviews your security architecture and design in 10 to 15 working days and gives you a prioritised remediation plan. It does not include penetration testing unless separately contracted.