Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Build security into every project from the start – not only IT projects – with a security check at key milestones.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Projects change how information is collected, shared and operated, even when the deliverable is not an IT system. Security review conducted only before launch may discover architectural or contractual weaknesses after the team has lost practical options. Integrating security into project decisions helps owners identify requirements early and retain a clear record of which risks were addressed, accepted or transferred into ongoing operations.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Only software development projects receive security checks, while office moves, business outsourcing and new service launches proceed without equivalent risk consideration.
A project passes its delivery gate although unresolved security requirements have no accountable owner or approved plan for post-launch treatment.
Security approval is recorded as a single checkbox, with no evidence of the scope reviewed, assumptions made or changes since the review.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Add security questions to project initiation covering information sensitivity, new suppliers, access changes and relevant obligations. Use the answers to determine the depth of review and specialist involvement, rather than applying the same heavyweight checklist to every project.
Translate identified risks into explicit project requirements and acceptance criteria. Allocate responsibility between the sponsor, project manager, security reviewer and delivery teams. Include security dependencies in procurement and schedule planning so necessary assessments occur before irreversible purchasing or design decisions.
Review security at meaningful decision points such as design approval, supplier selection and service acceptance. Record changes that invalidate earlier assumptions, and maintain a risk or issue log with treatment owners. Make unresolved exceptions visible to the person authorised to accept them.
Complete a structured handover to operations. Transfer the required procedures, asset records, monitoring arrangements and residual risks, and confirm the receiving team accepts ownership. After launch, review whether the controls operate as intended rather than treating project closure as proof of security effectiveness.
What an auditor will ask to see
Project initiation and design records showing the security risks, applicable requirements and proportional review approach agreed before major delivery commitments.
Gate review records and exception decisions identifying the evidence examined, unresolved issues, accountable approvers and conditions attached to any permission to proceed.
Operational handover records linking delivered controls, residual risks and supporting documentation to named service owners and subsequent verification or improvement actions.
Baseline documents in the kit
These free kit documents help you document or evidence A.5.8. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.