Section
Develop
It’s not possible to provide a recipe on how to write secure code in a few simple and concise articles. However, it doesn’t mean it’s an insurmountable task reserved only for security experts! Everyone developing software at Bouvet should be familiar with OWASP Top 10, which is a good starting point to understand the challenges faced by developers.
The articles you find under the topic Develop on this page will focus on what happens on a developer’s workstation, apart from actual code. They won’t delve into specific attack methods or how to defend against them. You will also find advice on how a team should work to prevent, identify, and fix vulnerable code.
In this section
- Software Supply Chain Everyone who develops software uses third-party packages. All third-party packages represent code written by others and pose a risk to the delivery if we do not have control over what we use and an overview of weaknesses and risks associated with them.
- Version Control Version control is an essential tool in all development projects, but how do you use it effectively and what should you consider?
- Data Validation Data validation reduces both security risk and quality issues. Never trust data blindly, whether it comes from users, integrations, or AI pipelines.
- Security Practices There is much to consider when building a secure solution, and an important starting point is the OWASP Top 10.
- Development Environment, Tools, and Build Environment The environments and tools we work with are essential for the project. The team should standardize tool usage, document configuration, and reduce risk in the development and build chain.
- Documentation Good documentation is essential for continuity, traceability, and security. This applies to the choices made, the threats assessed, and the system’s actual behavior — including in AI systems.
- Secrets, Keys, and Certificates Every development project needs secrets, keys, and certificates: values that grant access, that lock data, or that prove who a service is. They have to be stored safely, replaced at regular intervals, and renewed before they expire — and the three do not tolerate the same mistakes.
- Security Testing In line with other elements associated with the topic of quality, we depend on testing to verify that we have achieved the goal. Security testing is an important part of this, as it allows us to demonstrate that the delivery is not vulnerable to certain attack methods.
- Code Review Code review means someone other than the author looks over a change before it is let into the solution. It is one of the cheapest security controls we have, and unlike most tools it can also ask the important questions about what the change means in a wider context.