Secure Coding & Release Discipline ยท Lesson 1 of 4
Production change control
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
Changes to live systems go through the agreed process: reviewed, tested and with a way to roll back. That's how problems are caught, and undone fast.
In your work
Before a sale, a client asks you to 'just tweak' a price rule directly in their live database. You make the change through the normal release instead, with a reviewed script and a tested way back.
What the UK rules say
- The NCSC's secure development principles include securing the build and deployment pipeline.
- UK GDPR expects organisations to be able to restore personal data in a timely way after a technical incident, which is what backups and rollbacks are for.
What to do
- Use the agreed release route, even for one-line changes.
- Get the change reviewed, with tests that cover it.
- Know how you'll roll back before you deploy.
- Release at agreed times, and tell the people affected.
Watch out for
- Editing live data by hand because it's 'only one line'.
- Releasing late on a Friday with nobody around to help.
In your organisation
What's your organisation's change process for live systems, and what counts as an emergency?
Your employer's own policies come first.
Sources
- NCSC, Secure development principles: secure the build and deployment pipeline (opens in a new tab), checked 6 October 2026.
- ICO, A guide to data security (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
