Most serious outages don’t start with attackers.
They start with uncontrolled software changes in live environments.
Annex A 8.19 exists to ensure organisations control how software is installed, updated, and changed on operational systems, reducing the risk of disruption, compromise, and unintended security weaknesses.
This control is about discipline in production, not slowing delivery.

Annex A 8.19 of ISO 27001:2022 focuses on controlled installation of software on operational systems.
At a practical level, this means:
The control does not prohibit updates. It expects organisations to treat production systems as sensitive environments requiring control and oversight.
Operational systems are systems used to:
Changes in these environments carry higher risk because:
Common causes of incidents include:
Annex A 8.19 ensures organisations do not confuse speed with safety when changing operational systems.
This control replaces ISO 27001:2013 Annex A 12.5.1 and 12.6.2, consolidating and strengthening expectations.
A pragmatic approach to Annex A 8.19 typically includes the following elements.
Organisations should clearly identify systems considered operational, including:
Clear definition prevents accidental bypass of controls.
Installation and update rights should be:
Unrestricted installation rights are a predictable failure point.
Software installation should require:
This applies to:
Authorisation creates accountability.
Annex A 8.19 expects software to be:
Testing should confirm:
Production is not a test environment.
Software installation is a form of change.
Annex A 8.19 aligns closely with:
Emergency changes should still be:
Urgent does not mean uncontrolled.
Organisations should maintain a trusted library of:
This helps ensure:
Unknown software sources increase supply chain risk.
Organisations should maintain records showing:
Records support:
Unrecorded changes are invisible changes.
Annex A 8.19 explicitly supports rollback planning.
Before installation, organisations should consider:
Rollback capability reduces risk of prolonged outage.
Where vendors or suppliers install or update software:
Third-party installation does not remove organisational accountability.
Users should only be able to install software:
This supports:
Operational systems should never be “self-service”.
Unused or legacy software should be:
Unused software increases:
Annex A 8.19 does not require:
It does require organisations to:
Most production incidents are self-inflicted.
Operational stability depends on change discipline.
Annex A 8.19 is about keeping control when systems matter most.
When software installation on operational systems is managed effectively:
Development is where change is expected.
Operations are where control is essential.
Annex A 8.19 ensures organisations never lose sight of that difference.
We can help you understand your actual security needs and even if we cant help we can point you in the right direction
Talk to a security expert today