Standards

The UK Software Security Code of Practice, for teams that build with AI.

The Software Security Code of Practice, published by DSIT and the NCSC in May 2025, sets out 14 principles for organisations that develop or sell software to businesses. It is voluntary, with a self-assessment, and buyers are starting to ask suppliers about it.

Last reviewed .

The four themes

  • Secure design and development
  • Build environment security
  • Secure deployment and maintenance
  • Communication with customers

The 14 principles sit under these four themes. Read them in full on GOV.UK before you rely on this summary.

What changes when AI writes the code

The principles do not mention who or what wrote the code, so they apply to AI-assisted changes in the same way. What changes is the volume and speed of change, and the question a buyer will ask: how do you know what was changed, by what, and who approved it?

Evidence you can produce as you build

EmberNest records the scope and acceptance test agreed before work starts, the gate results on each change, and two approvals linked to the change and its tests. That is the kind of record a self-assessment draws on.

How to start

Begin with a free assurance report on one codebase to see your level and the findings that matter most.

Get your free assurance report

This page is not legal advice.

All standards

Talk through the standards that apply to you.

Book a conversation