Zum Inhalt springen
Grundlagen
16 Min. Lesezeit

ISO 27001 Work Breakdown Structure: A Practical WBS

support@ismscalculator.com|

Hierarchical WBS plan pinned in a project room

An ISO 27001 work breakdown structure (WBS) splits the whole project, from scoping to the certification audits, into phases, deliverables and small work packages that each have an owner, an effort estimate and a finish line. The most reliable way to build one is to follow the standard’s own cycle (plan, do, check, act), keep every work package small enough to estimate with confidence, and attach the mandatory documented information to the task that produces it. This guide shows the structure, a worked example, the estimating rules and the mistakes that stall projects.

Ismscalculator
Estimate Your ISO 27001 Plan
Compare a tailored ISO 27001 implementation estimate with model reference comparisons, using your company size, industry, and security maturity.
Visit the ISO 27001 calculator

TL;DR

  • A WBS is a deliverable-oriented tree of the work, not a task list. Name each branch after an outcome (“Risk register approved”), not an activity (“work on risks”).
  • Use five to six top-level phases: scoping and gap analysis, risk assessment and treatment, documentation, control implementation, internal audit and management review, and certification audits.
  • Break work down until you can estimate it. A common rule of thumb caps a work package at 8 to 80 hours.
  • Give every work package one owner, one predecessor and one piece of evidence, so the plan doubles as your audit trail.
  • Budget realistically: published ranges for full implementation run from a few months to a year, and the biggest swing factor is your starting maturity.

Table of Contents

What an ISO 27001 WBS is and why it helps

The Project Management Body of Knowledge defines a WBS as a deliverable-oriented hierarchical decomposition of the work the team will carry out. In plain terms: you start with the end result (a certified information security management system, or ISMS) and keep splitting it until each piece is small enough to assign, schedule and check off.

For information security projects, the usual teaching version is more specific. A university lecture on implementing information security describes the WBS as the backbone of a project plan, where each major task lists the work to be done, who is assigned, start and end dates, effort, estimated capital and noncapital expenses, and dependencies between tasks. Each major task is then divided into smaller tasks or specific action steps.

That description fits ISO 27001 well, because the standard asks for evidence at every step. A good WBS gives you four things:

  1. Scope control. If a task is not in the tree, it is not in the project. That stops scope creep and the quiet addition of “nice to have” controls.
  2. Accountability. Each work package has one named owner, which is where most ISMS projects either gain speed or lose it.
  3. A basis for estimating. You can price and schedule 60 small packages far more accurately than one block called “implement controls”.
  4. Audit readiness. Auditors ask for records. If each package lists its output, the evidence trail builds itself.

A WBS is not a schedule. It says what must be delivered. The schedule (your Gantt chart) adds sequence and dates on top of it. Build the WBS first, then plan the timeline from it.

The shape of the tree: follow plan, do, check, act

ISO 27001 is built on a continual-improvement cycle, so the cleanest top level mirrors it. A Spanish professional body’s implementation report shows exactly this: four top-level branches (create, implement, monitor, improve), each split into tasks tied to specific clauses, such as defining the scope and carrying out internal audits. That report was written against the 2005 edition of the standard, so use it for its structure, not its clause numbers. The current edition is ISO/IEC 27001:2022, with a 2024 amendment that added climate change to the context-of-the-organization review.

In practice most teams want a little more resolution than four branches, because “Plan” alone can eat half the project. Here is a six-branch version that works for a first certification.

WBS level 1 Plan-do-check-act step Main deliverable
1. Initiation, scope and gap analysis Plan Approved scope, project charter, gap report
2. Risk assessment and treatment Plan Risk methodology, risk register, treatment plan, Statement of Applicability
3. Policies and documentation Do Policy set, procedures, records templates
4. Control implementation Do Controls operating, with evidence
5. Monitoring, internal audit and management review Check Internal audit report, management review minutes
6. Corrective action and certification audits Act Closed nonconformities, Stage 1 and Stage 2 results

Number everything (1.1, 1.2, 2.1.1). Numbering lets you reference a package in risk logs, meeting notes and the audit file without ambiguity.

A worked example, level by level

The example below stops at level 3 for each branch. Your own tree will be deeper where the work is risky or expensive and shallower elsewhere.

1. Initiation, scope and gap analysis

  • 1.1 Secure management commitment: sponsor named, budget approved, project charter signed
  • 1.2 Define ISMS scope: list of locations, systems, data and business units in and out of scope, plus rationale for exclusions
  • 1.3 Understand context and interested parties: internal and external issues, customer and regulatory requirements, climate change considered as a relevant issue
  • 1.4 Run the gap analysis: current-state assessment against the standard’s clauses and Annex A controls, producing a prioritized gap report (our step-by-step gap analysis guide walks through the method)
  • 1.5 Build the project plan: this WBS, owners, effort estimates and timeline

2. Risk assessment and treatment

  • 2.1 Define the risk methodology: scales, acceptance criteria, how assets and owners are identified
  • 2.2 Build the asset inventory and assign owners
  • 2.3 Assess risks and record them in the risk register
  • 2.4 Choose treatments and write the risk treatment plan
  • 2.5 Produce the Statement of Applicability: every Annex A control reviewed, with inclusion or exclusion justified
  • 2.6 Obtain risk owner approval of residual risk

3. Policies and documentation

  • 3.1 Information security policy and objectives
  • 3.2 Core procedures: document control, internal audit, corrective action, incident management
  • 3.3 Topic-specific policies: access control, supplier security, acceptable use, backup, and so on
  • 3.4 Records and templates: logs, registers and forms that will hold future evidence

4. Control implementation

  • 4.1 Organizational controls: roles, supplier agreements, onboarding and offboarding steps
  • 4.2 People controls: security awareness training, screening, disciplinary process
  • 4.3 Physical controls: office access, equipment handling, clear desk rules
  • 4.4 Technological controls: access management, logging and monitoring, backup and restore tests, vulnerability management, encryption

This is the branch that needs the deepest decomposition, and we cover how to split it below.

5. Monitoring, internal audit and management review

  • 5.1 Define metrics and monitoring: what you measure, how often, who reviews it
  • 5.2 Plan and run the internal audit, with an auditor who is independent of the area audited
  • 5.3 Record findings and agree corrective actions
  • 5.4 Hold the management review with the required inputs and recorded decisions

6. Corrective action and certification audits

  • 6.1 Close internal audit nonconformities and verify the fix
  • 6.2 Select the certification body and book the audit dates
  • 6.3 Stage 1 audit: documentation review, readiness conclusions
  • 6.4 Fix Stage 1 findings
  • 6.5 Stage 2 audit: evidence that the controls operate
  • 6.6 Respond to any Stage 2 nonconformities and receive the certificate

A note on who does what at the end: the certificate comes from an accredited certification body after the Stage 1 and Stage 2 audits. A consultant can help build the ISMS and run the internal audit, but cannot certify you. Plan your branch 6 around the certification body’s availability, because audit slots often book weeks ahead.

Which deliverables are mandatory

A frequent planning error is producing too many documents, or missing the few that are required. Missing mandatory documented information is a nonconformity, while documents the standard does not ask for are yours to keep lean.

The standard’s own clauses require documented information for, among other things:

  • the ISMS scope (clause 4.3)
  • the information security policy (clause 5.2)
  • the risk assessment and treatment process (clauses 6.1.2 and 6.1.3)
  • the Statement of Applicability (clause 6.1.3)
  • information security objectives (clause 6.2)
  • evidence of competence (clause 7.2)
  • results of risk assessment and treatment (clauses 8.2 and 8.3)
  • monitoring and measurement results (clause 9.1)
  • the internal audit programme and results (clause 9.2)
  • management review results (clause 9.3)
  • nonconformities and corrective actions (clause 10.2)

The Annex A controls then add records depending on which ones your Statement of Applicability includes. Tag each work package in your WBS as “mandatory”, “control-driven” or “optional”. It keeps the team from gold-plating, and it shows the reviewer at a glance where the real obligations sit.

If you want a full task-by-task list to cross-check your tree against, our 80-step certification checklist covers it.

How small should a work package be?

Decomposition has a stopping rule. A project planning guide on visual WBS describes the 8/80 rule of thumb: keep each work package between 8 and 80 hours of effort, and stop splitting once you can confidently estimate duration and cost. The same guide notes that every project is unique, and the complexity of the project decides how many levels you need.

Apply that to ISO 27001 like this:

  • Too big: “Implement access control” (weeks, several owners, no clear finish line).
  • About right: “Define role-based access matrix for the in-scope systems” (about 20 to 30 hours, one owner, output is the matrix).
  • Too small: “Email IT about the matrix” (a step inside a package, not a package).

Other sound habits:

  • Three to five levels is usual for smaller organizations. Go deeper only for high-cost or high-risk deliverables, such as a monitoring tool rollout or a data center control.
  • Name outcomes. “Backup restore test completed and logged” tells the owner when they are done. “Improve backups” does not.
  • One owner per package. A team can contribute, but one person answers for it.
  • Record the predecessor. The risk assessment cannot finish before the asset inventory does. Statement of Applicability sign-off cannot happen before the treatment plan is approved.
  • Include the project’s own overhead. Reserve packages for status meetings, evidence collection and document reviews. Teams forget these and then run late.

Estimating effort and duration

Once the packages are small, estimating becomes arithmetic plus judgment. Three inputs matter most.

Starting point. A published gap assessment methodology reports first-time gap rates of 30 to 40 percent in organizations with informal security programs, with most gaps in documentation rather than technical controls, according to DecryptionDigest’s 2026 methodology article. The same article suggests sorting gaps into documentation, process and technical types, which maps directly onto your WBS: documentation gaps become short packages you can finish early, while technical gaps become longer, budgeted ones. Treat the figures as one practitioner’s observation, not a universal rate.

Size and capacity. A German IT services firm’s guide for mid-sized businesses says 6 to 12 months of preparation is realistic and depends on starting point, company size, who is available (an internal ISMS officer, a consultancy or a dedicated team) and IT maturity. It puts internal effort at roughly 0.3 to 1.0 full-time equivalents in the busy phase, then 0.1 to 0.3 for ongoing operation. Use that as a sanity check for the person-hours you assign across the tree.

Money. A US audit firm’s 2026 cost table projects readiness assessment at $5,000 to $10,000, implementation at $10,000 to $50,000, audit fees at $7,500 to $40,000 and annual surveillance at $6,000 to $20,000, for a three-year total of $43,000 to $150,000. Those are ranges for planning, and your own scope will move you within or outside them. Add a cost field to each branch of your WBS and compare the total against the range. For a fuller breakdown, see how much ISO 27001 certification costs and what the audit fees actually cover.

Projected ISO 27001 cost ranges by phase

For effort in person-days and how to turn it into dates, our guide to mapping ISO 27001 person days into a dated project plan is the natural next step, and the certification timeline guide shows how long each phase typically runs.

A simple estimating routine

  1. List every work package at the lowest level of your tree.
  2. Ask each owner for an effort figure in hours, with a low and a high case.
  3. Add the sum of the high cases for high-risk packages (new tooling, third-party dependencies) and the average for routine ones.
  4. Add 10 to 20 percent contingency at branch level, not on each package, so the buffer is visible.
  5. Compare totals against the ranges above and against the capacity of your people.

If the plan needs more hours than your team has, that is the finding. Fix it with scope, outside help or a longer schedule before you start, not in month five.

Dependencies, owners and audit steps

The last branches of the tree are where plans quietly fail, so give them as much care as the technical work.

Internal audit. Schedule it after the controls have operated long enough to produce records. Add a package for the auditor’s independence: the person who wrote the access control procedure should not audit it.

Management review. It needs inputs (audit results, risk status, objective performance, nonconformities), so list those as predecessors. Block the executives’ calendars at project start, since a postponed review can push the certification audit.

Corrective actions. Create a recurring package, not a one-off. Each nonconformity gets a root cause, a fix, a verification and a closing date.

Stage 1 and Stage 2. Stage 1 is a documentation and readiness review, and Stage 2 tests whether controls actually operate. Keep a buffer between them for fixes. Leave the exact audit duration to your certification body’s quote, since it depends on scope and headcount.

Surveillance. The project does not end at the certificate. Add a placeholder branch for annual surveillance audits and recertification so next year’s work is already budgeted. Our implementation timeline article lays out what to expect through that cycle.

Tailoring the WBS to your organization

The six-branch tree is a template. Adjust it to where you start.

Startups with no security program. Expect most of your effort in branches 3 and 4, because you are creating policies and processes from scratch. Keep scope tight (one product, one environment) and let cloud provider certifications cover the physical controls you do not run. Put customer-driven deadlines, such as a security questionnaire from a large prospect, on the timeline early, because they set your audit date.

Finance firms. Overlapping regulation changes the tree. Add packages that map your existing control frameworks and regulatory obligations to Annex A, so one piece of evidence serves several audits. Third-party risk usually deserves its own sub-branch under 4.1, with packages for vendor inventory, due diligence and contract clauses.

Organizations with a mature program. If you already run a risk process and a documented control set, branch 3 shrinks to updates and gap-filling, while branches 5 and 6 stay the same. Your gap analysis will show which packages you can mark “largely done, needs evidence”.

Tailoring the WBS to your organization

Multi-site or larger companies. Add a level between branch and package for each site or business unit, and a central coordination package for consistency. Audit scope and duration grow with headcount and site count, so plan certification body engagement early.

Common WBS mistakes

  • Listing activities instead of deliverables. “Meet with HR” cannot be verified. “Onboarding and offboarding checklist approved by HR” can.
  • Skipping the Statement of Applicability dependencies. It needs the risk treatment plan first, and it feeds control implementation.
  • Underestimating evidence collection. Controls that work but leave no record fail audits. Give each control package an evidence output.
  • Putting everything in one owner’s name. The ISMS manager becomes the bottleneck. Spread ownership to the people who run the systems.
  • Freezing the WBS. Review it after the gap analysis and again after the risk assessment, when you know what controls you actually need. Version it so you can show what changed and why.

Our perspective

Most teams ask us for a cost number first and a plan second, and then discover the two are the same exercise. A WBS is what turns a vague budget into a list of packages you can price, assign and defend.

What we see is that estimates go wrong at three points: scope drawn too wide, gap findings treated as one lump, and audit preparation left as a single line. That is why we built our calculator around company size, industry and security maturity, and why the assumptions behind each figure are editable and traceable. You can see how the numbers are built, change them and compare scenarios, rather than take a black-box total.

Our advice: build the tree first, estimate the small packages, then use benchmarks to check yourself against organizations like yours. If a branch looks far above or below the sector range, ask why before you commit the budget.

Martin

Turn your WBS into a costed, dated plan

If you have a draft tree and want to test it, our ISO 27001 cost calculator gives a real-time estimate of cost and effort based on your size, industry and maturity, with no signup needed for the first calculation. You can save several scenarios, compare them, and plan implementation phases on a customizable timeline.

Ismscalculator

Not sure where your biggest gaps are? The free 2-minute check gives you an instant readiness read, and the full readiness assessment goes domain by domain, which helps you decide which branches of your WBS need the deepest breakdown.

FAQ

How many levels should an ISO 27001 WBS have?

Most first-time projects work well with three to five levels. Go deeper only where the work is expensive or risky, such as tooling rollouts. Stop splitting when you can estimate a package with confidence, which in practice often means 8 to 80 hours of effort.

Should I organize the WBS by phase or by Annex A control?

Organize the top levels by phase (scoping, risk, documentation, implementation, audit, certification), because that is how work flows and how dependencies run. Use the Annex A control themes as a sub-structure inside the implementation branch, so each control has a package and an evidence output.

Who should own the work packages?

The person who runs the underlying process or system. Your ISMS manager coordinates and tracks, but IT, HR, facilities and legal owners should each answer for their own packages. One named owner per package is the rule, even when several people contribute.

How long will the project take?

Published ranges vary. One IT services guide calls 6 to 12 months of preparation realistic for mid-sized businesses, depending on starting point, size, capacity and IT maturity. Your WBS effort totals and your team’s availability give the real answer for your case.

Does the WBS count as ISO 27001 documentation?

The standard does not require a WBS, so it is a planning tool rather than a mandatory document. It still helps, because it links each package to the records and documented information that auditors do ask for.

Sources

Bereit, Ihre ISO 27001-Kosten zu schätzen?

Nutzen Sie unseren kostenlosen Rechner für eine maßgeschneiderte Kosten-, Aufwands- und Zeitplanschätzung basierend auf Ihrem Unternehmensprofil.

Schätzung berechnen — kostenlos
Zurück zu allen Artikeln