Good practice for working developers
Developers spend a lot of time keeping up with new tools. Underneath them sits a smaller set of public standards that change slowly. This page gathers the ones worth knowing well, so your everyday habits rest on something solid.
Making security part of everyday work
The National Cyber Security Centre publishes eight principles for secure development and deployment. They include protecting your code repository, securing the build and deployment pipeline, and continually testing your security. Another is simply to keep your security knowledge sharp.
The NCSC points out that tools developers already use help here. Version control, peer review and automated testing can all make your work more secure when they are used well.
Knowing what customers can expect of software
The UK Software Security Code of Practice was published in May 2025. It is voluntary. It sets out 14 principles in four themes, for organisations that make or sell software to businesses.
Several of its principles touch a developer's daily work. They include following a recognised secure development framework, understanding the third-party components in your software, and testing software and updates before release. Vendors are also asked to give customers at least a year's notice before support for a product ends.
The Code also expects a clear way for people to report security flaws. The NCSC's vulnerability disclosure toolkit shows how to set one up, including a security.txt file.
Keeping up with common web risks
The OWASP Top 10 is a widely used awareness document on the most critical security risks to web applications. The latest version is the 2025 edition. Reading it alongside your own code is a good way to spot familiar weak points.
Building things everyone can use
In the UK, 1 in 5 people have a long-term impairment that affects everyday activities. The Web Content Accessibility Guidelines, known as WCAG, help make web content work for them.
WCAG 2.2 has 13 guidelines under four principles. Its testable success criteria come in three levels, A, AA and AAA. UK government services must meet level AA of WCAG 2.2 as a minimum.
Sharing code in the open
Open source means more than access to the source code. The Open Source Definition sets ten criteria, such as free redistribution and allowing modified versions. Licences approved by the Open Source Initiative meet that definition.
The GOV.UK Service Manual notes that it is much easier to code in the open from the start of a project. Opening a repository later means a costly check at the end that nothing sensitive is inside.
Mapping your own skills
The Skills Framework for the Information Age, known as SFIA, describes professional skills across seven levels of responsibility. It is free for most non-commercial use, so you can use it to plan your own next step.
If security is where you want to grow, the UK Cyber Security Council sets professional standards for that field. It is recognised by Royal Charter.
Useful links
- NCSC: secure development and deployment guidance
- GOV.UK: Software Security Code of Practice
- NCSC: vulnerability disclosure toolkit
- OWASP Top 10
- W3C: WCAG 2 overview
- GOV.UK Service Manual: making your service accessible
- Open Source Initiative: the Open Source Definition
- GOV.UK Service Manual: making source code open and reusable
- SFIA Foundation: about SFIA
- UK Cyber Security Council