Many security weaknesses are introduced during change, not day-to-day operations.
Annex A 5.8 exists to ensure that information security is considered as part of project management, rather than treated as a separate or downstream activity once decisions have already been made.
This control recognises that projects often introduce new systems, processes, suppliers, and ways of working — all of which can materially affect information security risk.

Annex A 5.8 of ISO 27001:2022 focuses on integrating information security into project management.
At a practical level, this means:
The control does not prescribe a specific project management methodology or require formal security gates for every project. Instead, it expects a consistent, proportionate approach to ensuring security is considered whenever projects introduce change.
The intent is prevention — catching security issues early, when they are cheaper and easier to address.
Projects are a common source of information security risk because they often involve:
When security is only considered after a solution has been selected or built, organisations are left with limited and costly options.
Annex A 5.8 ensures that information security is embedded into project decision-making, rather than treated as an afterthought.
From a security perspective, this reduces the likelihood of:
From a business perspective, it supports smoother delivery and fewer late-stage blockers.
A pragmatic approach to Annex A 5.8 typically includes the following elements.
Not all projects carry the same level of security risk.
Projects that commonly trigger security consideration include those involving:
Clarity here avoids unnecessary overhead while ensuring relevant projects are covered.
Security is most effective when considered before key decisions are locked in.
This may include:
Early consideration supports better design choices and avoids rework.
Where security requirements are identified, they should be agreed and documented at an appropriate level.
These requirements may relate to:
The level of detail should be proportionate to the project’s risk and complexity.
Security risk does not remain static during delivery.
Projects often evolve, introducing:
Periodic review helps ensure that security considerations remain aligned with reality, not just the original plan.
For higher-risk projects, organisations may choose to:
This reinforces accountability without imposing unnecessary formality.
Most issues arise when security is disconnected from project governance.
Annex A 5.8 is about building security into change, not slowing projects down.
When information security is integrated into project management:
Projects shape the future state of the organisation. Treating security as part of that future — rather than an afterthought — is the outcome Annex A 5.8 is designed to achieve.
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