Security projects fail in familiar ways: the scope grows from “deploy MFA” to “redesign identity”, the business owner never signs off risk acceptance, a dependency on the network team is discovered in week ten, and nobody can show the auditor when a decision was made. Project documents exist to prevent exactly those failures. The test for each one below is simple: who updates it, who reads it, and what decision does it support? A document with no answer is overhead.
1 · The Documents, Phase by Phase
| Phase | Document | Must contain | Read by |
|---|---|---|---|
| Initiate | Business case | The risk or obligation driving the project, options considered, cost, expected risk reduction | Sponsor, finance |
| Project charter | Objective, scope and exclusions, sponsor, project manager, success criteria, budget, key dates | Steering committee | |
| Plan | Scope & work breakdown | Deliverables broken into work packages | Project team |
| Schedule (Gantt or milestone plan) | Milestones, dependencies, critical path | Team, steering committee | |
| RACI matrix | Who is Responsible, Accountable, Consulted and Informed for each deliverable | Everyone involved | |
| Communication plan | Who hears what, how often, through which channel | Stakeholders | |
| Execute | Task tracker | Owner, due date, status for each task | Project team |
| Test and acceptance records | What was tested, results, who accepted it | Auditors, operations | |
| Monitor & control | RAID log | Risks, Assumptions, Issues and Dependencies, each with an owner and a date | Project manager, steering committee |
| Change log | Requested changes to scope, time or cost; impact; decision and approver | Steering committee, auditors | |
| Status report | Progress against milestones, red/amber/green, decisions needed | Sponsor, steering committee | |
| Close | Closure report | Objectives met or not, open items handed to operations, residual risks accepted, lessons learned | Sponsor, auditors, operations |
▸ For security projects the change log and the closure report matter more than usual: auditors use them to see when a control went live, what was descoped, and who accepted the remaining risk.
2 · A RACI That Avoids the Usual Fights
Exactly one A per row. Example for an MFA rollout:
| Deliverable | CISO | IAM lead | IT service desk | HR | Business owners |
|---|---|---|---|---|---|
| MFA policy | A | R | C | C | I |
| Technical configuration | I | A/R | C | — | — |
| User enrolment and support | I | C | A/R | I | I |
| Exceptions approval | A | C | I | — | R |
| Communications to staff | C | C | R | A | I |
3 · Worked Example: an ISO 27001 Rollout
| Document | What it says on this project |
|---|---|
| Business case | Two large customers require certification at renewal; losing them outweighs the programme cost |
| Charter | Scope: product platform and supporting functions; certification audit in month 10; sponsor: COO |
| Schedule | Gap assessment → risk assessment → Statement of Applicability → controls → internal audit → management review → stage 1 and stage 2 audits |
| RAID log | Risk: HR cannot deliver background-check records in time. Dependency: logging platform upgrade by month 6. Assumption: current cloud provider’s attestation covers physical controls |
| Change log | Month 4: a newly acquired subsidiary added to scope; audit moved to month 11; approved by steering committee |
| Closure report | Certified; two minor nonconformities handed to the ISMS owner with dates; project lessons recorded |
The documents the ISMS itself must keep after the project ends are a separate set: see ISMS Document Set.
4 · The Minimal Set for a Small Project
- One-page charter — objective, scope, owner, dates, success criteria.
- Milestone plan — ten lines, not a 400-row Gantt chart.
- RACI — one A per deliverable.
- RAID log — reviewed weekly.
- Change log — every scope, time or cost change with its approver.
- Closure note — what was delivered, what was handed over, which risks were accepted, by whom.
Bottom line
- About twelve documents, not forty — each with an owner, a reader and a decision it supports.
- The RAID log does most of the work during delivery.
- One A per RACI row avoids the classic security-project stand-off.
- Change log and closure report are what auditors read later.
- Project documents end; ISMS records continue — hand them over explicitly.
Sources & method. Phase structure follows common project-management practice (initiation, planning, execution, monitoring and control, closure). Document lists reflect typical PMO template sets; the selection, RACI and worked example are the author’s analysis. Original analysis; no third-party graphics or text reproduced.
← Back to Cyber security