Secure Development Guidance
Practical security guidance for teams building their own software.
The problem
Internal teams are often asked to build useful software quickly, without anyone checking the security basics. A bit of guidance early helps them ship safely and avoid common, costly mistakes.
What's included
- Advice on secure design and common pitfalls for the software your team is building
- Guidance on logins, permissions, secrets and handling of sensitive data
- Advice on managing dependencies and third-party services
- Guidance on safe build and deployment practices
- Ongoing check-ins or reviews as the software evolves
- Plain-English guidance and checklists your team can keep using
How it works
- 1
Understand
We learn what your team is building and how you work.
- 2
Review
We look at the design and what has been built so far.
- 3
Advise
You get practical, prioritised guidance in plain English.
- 4
Follow up
Check-ins as the software grows, so good habits stick.
FAQs
We are not professional developers. Is this still useful?
Yes. Guidance is pitched at your team, whatever their experience, and focuses on what matters most for your situation.
Can you review what we have built so far?
Yes. A review of work in progress is a good way to start, and can be combined with ongoing guidance.
Is this a training course?
It is practical guidance and reviews tailored to your team and your software. Contact us if you would like to discuss training sessions.