Ga naar de inhoud
Basisprincipes
13 min leestijd

ISO 27001 Board Presentation: Slides and Decisions to Ask For

support@ismscalculator.com|

Directors reviewing an ISO 27001 decision presentation

A good ISO 27001 board presentation is short, framed around decisions, and honest about cost and timing. It shows where your security program stands today, what certification will take, and exactly what you need the board to approve. Aim for about ten slides, one clear recommendation, and at least two costed options. This guide gives you the outline, the content for each slide, and a sample ask you can adapt.

Ismscalculator
Build a Defensible ISO 27001 Estimate
Estimate implementation cost and effort with a real-time calculator tailored to your company size, industry, and security maturity.
Estimate your ISO 27001 costs

TL;DR

  • Open with your current security posture, then progress, then a forward look with time for discussion. This is the three-part format ISACA recommends for board presentations on information risk.
  • Ask for decisions the board owns: budget, risk appetite, and risk acceptance. Leave product and supplier choices to management.
  • Present at least two options with costs and a recommendation, and say what happens if the board defers.
  • Use the 2022 edition of the standard (93 Annex A controls in four themes) as your baseline. Do not present the 2013 structure.
  • Show scope, gaps, phases, effort and cost assumptions as ranges you can defend, with the assumptions visible.

Table of Contents

What the board actually needs from you

Directors are not there to approve your control list. They want to know three things: are we exposed, what will it cost to fix and certify, and what do you need from us today.

ISACA notes that boards want the information risk and security program aligned with organizational strategy and requirements, and defensible if customers, compliance bodies, legal reviewers or enforcement authorities ever scrutinize it. ISO 27001 certification is one way to demonstrate that. Your presentation should therefore connect the project to business outcomes the directors already care about: winning enterprise deals, passing customer security questionnaires, reducing incident exposure, and meeting contractual obligations.

That framing changes the opening. Do not start with “ISO 27001 is an international standard for information security management systems.” Start with the business reason: “Three of our largest prospects now require certification, and our current controls are about 60% documented.” Use your own real numbers, of course.

A ten-slide outline that works

The ISACA three-part format gives you the skeleton: a short status review, project updates including staff and budget, and a forward-looking section that leaves time for discussion and board guidance. Here is how an ISO 27001 project maps onto it.

Part Slide What it contains
Posture 1. The ask in one line The decision you need and the date it is needed by
Posture 2. Why now Business drivers: customers, contracts, risk events, audits
Posture 3. Scope What the ISMS covers and what it excludes
Posture 4. Current gaps and top risks Maturity view, top five to seven risks, in plain language
Progress 5. What ISO 27001 changes The 2022 edition, in two or three lines
Progress 6. Plan and phases Timeline with milestones and owners
Progress 7. Effort and cost Internal hours, external spend, assumptions
Forward 8. Options Two or three paths with cost, timeline and trade-offs
Forward 9. Recommendation and decisions Specific approvals requested
Forward 10. If we wait What stays true if the board defers

Keep an appendix for the control-level detail. If a director asks, you can open it. If nobody does, you saved ten minutes of discussion for the decision.

Slide 1 and 2: lead with the ask and the business reason

Put the request on the first slide. A budget request works best when it is written as a decision the board can take, with real options, costs and a recommendation. Something like:

We are asking the board to approve a certification budget and to confirm the risk appetite that will guide the ISMS, so we can start the project in the next quarter.

Then give two or three business drivers, each with evidence you hold: a named customer requirement, a lost or delayed deal, an audit finding, a cyber insurance question. Directors respond to specifics. “Customers are asking” is weak. “Four security questionnaires in the last two quarters asked for an ISO 27001 certificate” is strong, provided it is true for you.

Slide 3: scope, in one picture

Scope is the most underestimated slide. The board should see what is inside the ISMS boundary: business units, locations, systems, data types, and key third parties. Just as important, show what is outside and why.

A simple diagram works better than a paragraph. Draw the product or service being certified, the supporting systems, the offices and cloud environments, and shade anything excluded. A narrow scope lowers initial cost and effort, but a customer may expect a scope that covers the service they buy. Say which customers or contracts your proposed scope satisfies.

Printed plan showing included and excluded ISMS areas

If you need to prepare the underlying inventory, our guides on IT asset inventory tips for audit readiness and asset classification for IT teams show how to build one the auditor will accept.

Slide 4: gaps and top risks, without jargon

This is where you show the current state. Two views help:

  1. A maturity view. ISACA suggests using capability maturity models with five defined tiers to review program functions against a recognized framework such as ISO/IEC 27001:2022. One chart, with current and target levels by domain, tells the story quickly.
  2. A short risk list. Five to seven risks, each in business language: what could happen, how likely, what it would cost, and what reduces it. Skip control IDs on this slide.

A gap assessment should compare your documented and operating controls against each clause and Annex A control, then rank the findings by risk and by effort. The result is a prioritized plan: quick wins first, then the structural work (risk assessment, policies, supplier management, logging, access reviews), then evidence collection and internal audit. Our ISO 27001 readiness assessment is built around that flow, and our risk assessment methodology guide explains how to score and rank what you find.

Before the meeting, align on risk appetite. The board owns it, and your risk scores mean little without it. Our guide to defining, measuring and applying risk appetite gives you language to propose.

Slide 5: explaining ISO 27001:2022 in two minutes

Some directors will have heard of the old version. Give them a short, accurate orientation.

  • ISO/IEC 27001:2022 was published on 25 October 2022 and sets requirements for an information security management system in organizations of any size and sector.
  • It cut Annex A from 114 controls to 93 and regrouped them from 14 control objectives into four themes: Organizational, People, Physical and Technological, according to the NQA USA transition plan.
  • The transition period ended on 31 October 2025, and certificates to the 2013 edition are no longer valid, per the same NQA document.

The practical message: any new project is a 2022 project. If you are replacing an older program, state that the project is built on the current control set, not the 2013 structure. For a plain-language tour of the four themes, point directors to our Annex A controls explained guide as pre-reading.

Slide 6: phases, owners and milestones

Show the plan as a simple Gantt-style timeline with five phases:

  1. Scoping and gap assessment. Define the boundary, assess current state, and agree risk appetite.
  2. Risk assessment and treatment. Identify risks, select controls, and produce the statement of applicability.
  3. Implementation. Write and roll out policies, close control gaps, train staff, and onboard key suppliers into the process.
  4. Internal audit and management review. Test the system before an external auditor does.
  5. Certification audit. Work with an accredited certification body on the staged audit and fix any findings.

One owner per phase, and one executive sponsor for the whole project. The board will read an unowned milestone as a risk.

For what evidence an auditor will expect, TÜV Rheinland’s US ISO 27001 page lists the typical building blocks: a tailored ISMS, a security policy aligned to strategic objectives, identified critical information assets with a risk assessment, an action plan, defined responsibilities with management involvement, employee awareness and training, and regular audits with ongoing improvement. Use that as a checklist for slide 6 and your appendix.

Slide 7: effort and cost, shown as ranges with assumptions

This is the slide that draws the most questions, so make the assumptions visible. Break cost into categories the finance lead recognizes:

  • Internal effort: hours from security, IT, HR, legal and engineering, plus the project lead’s time.
  • External advisory: gap assessment, implementation support, internal audit, if you choose to use them.
  • Tooling: policy management, evidence collection, monitoring, training platforms.
  • Certification: the certification body’s audit fees and any surveillance audits afterward.
  • Remediation: the technical fixes that the gap assessment turns up.

Company size, industry, and starting maturity drive these numbers more than anything else. A 40-person startup with cloud-only infrastructure and a 600-person financial firm with several offices are different projects. Present a low, expected and high case, and state what moves you between them (scope breadth, number of sites, how much documentation already exists).

Our guides on ISO 27001 cost drivers for SMBs, budget categories and security budget percentage bands help you test your numbers against what comparable organizations spend. Get quotes from certification bodies directly for the audit line, since fees depend on scope and size.

Slides 8 to 10: options, recommendation and the cost of waiting

This is the section that earns the meeting. Directors can approve budget above management’s authority and set risk appetite or accept risk beyond tolerance, but choosing a product, supplier or project plan is management’s decision. So frame the options by outcome, not by vendor.

A sample option table:

Option A: Scoped certification Option B: Full-company certification Option C: Defer
Coverage Core product and supporting systems All business units and sites None
Timeline Shorter Longer Not applicable
Cost Lower, with range Higher, with range Existing spend only
Customer coverage Customers who buy the core product All customers Unchanged
Residual risk Unscoped areas remain outside the ISMS Lowest Current gaps stay open

Fill every cell with your own figures. Then give a clear recommendation and the exact decisions you need:

  1. Approve the budget range for the recommended option.
  2. Confirm the risk appetite statement that will guide risk treatment.
  3. Name the executive sponsor.
  4. Set the next reporting date.

Finally, slide 10: say what stays true if the board waits. The gaps remain, the deals that require certification stay at risk, and the cost of starting later depends on scope and timing. State it plainly and without alarm.

Presenting to a U.S. finance firm or startup board

Finance firms. Boards at financial institutions already think in terms of regulatory exposure, third-party risk and audit. Position ISO 27001 as the management system that organizes controls you already need to evidence, not as a replacement for regulatory obligations. Ask counsel or your compliance head which regulators and contractual requirements apply to you, and show on one slide how the ISMS scope and controls support them. Do not claim that certification satisfies any specific regulation unless your counsel confirms it.

Startups. Early-stage boards care about cash runway and sales velocity. Lead with the revenue case (deals that need the certificate), keep scope narrow, and show a phased budget so spend follows traction. If nobody on the team has run a certification before, say so and show how you will cover the gap, whether through a hired lead or independent consultants.

In both cases, give the board a trigger for revisiting the plan: a new customer requirement, an acquisition, a change in hosting, or an incident.

How to run the meeting itself

  • Send a pre-read of three pages at most: the ask, the options table, and the timeline.
  • Present for 10 to 15 minutes, then stop. Reserve the remaining time for questions and the vote, in line with the forward-looking, discussion-focused third part of the ISACA format.
  • Use plain words. Say “we cannot show that access is reviewed” instead of “control 5.18 is partially implemented.”
  • Prepare for three questions: why this scope, why this budget, and what happens if we fail the audit. Have a one-sentence answer ready for each.
  • Record the outcome. Write down which decisions were taken and by whom, and send them within a day.

Perspective

We built ISMS Calculator because most ISO 27001 board conversations stall on one thing: nobody can show where the numbers came from. A slide that says “$X and Y months” invites a debate about trust. A slide that says “here are the assumptions, here is what changes them, and here is the range” invites a decision.

That is why our calculator produces real-time estimates from your company size, industry and security maturity, with editable assumptions, model reference comparisons to sanity-check them, and a methodology that is traceable and versioned. You can save several scenarios and compare them side by side, which is exactly what an options slide needs.

Our view is simple: prepare the board pack from your own inputs, not from a generic template. A template gives you slides. A scenario comparison gives you a recommendation you can defend.

Martin

Build your board numbers in minutes

If the cost and timeline slides are the blockers, start with the ISO 27001 cost calculator. Enter your company size, industry and current maturity, adjust the assumptions, and save multiple scenarios to compare for your options slide. You can export a PDF report, share a link with your CFO, and see how your estimate sits against model reference comparisons, with no signup needed for the first calculation.

Ismscalculator

Not sure where you stand? The free 2-minute readiness check gives you a quick starting point, and the full readiness assessment covers maturity across the four Annex A control themes our toolkit uses. Both feed directly into the posture and gap slides above.

FAQ

How long should an ISO 27001 board presentation be?

About ten slides and 10 to 15 minutes, with control-level detail in an appendix. Reserve the rest of the slot for discussion and a decision, which is the part of the meeting that matters.

What decisions should I ask the board to make?

Ask for budget approval above management’s authority, confirmation of risk appetite, and any risk acceptance beyond tolerance. Product, supplier and project-plan choices belong to management, so present them as part of your recommendation rather than as board votes.

Do I need to mention the 2013 version?

Only briefly. The 2022 edition replaced it, certificates to the 2013 edition stopped being valid after 31 October 2025, and a new project is built on the 93-control, four-theme structure. A single line on slide 5 is enough.

How do I estimate cost without a vendor quote?

Build ranges from your size, industry and starting maturity, and list the assumptions on the slide. A calculator with editable assumptions helps here, and you can refine the audit-fee line with quotes from accredited certification bodies once the board approves the scope.

Sources

Klaar om uw ISO 27001-kosten te schatten?

Gebruik onze gratis calculator voor een op maat gemaakte schatting van kosten, inspanning en planning op basis van uw bedrijfsprofiel.

Bereken uw raming — gratis
Terug naar alle artikelen