You are the incoming CISO for a global B2B SaaS provider. To secure a lucrative multi-year contract with a European government agency, your organization must achieve ISO/IEC 27001 certification within the next nine months. The Board of Directors has approved the initiative and is eager to see immediate operational momentum.
During the ISMS kickoff meeting, the CEO asks: "We have everyone in the room. Should we start by mapping out our vulnerabilities, setting the total budget for the project, or deciding exactly how we are going to treat our current cyber risks?"
As the executive authority on security governance, you must redirect the Board to the mandatory starting point of the ISO 27001 lifecycle.
According to ISO 27001, of the steps for establishing an Information Security Governance program listed below, which comes first?
The executive team is demonstrating a common operational bias: rushing to execute (budgeting, assessing, mitigating) before defining the foundational intent and scope of the program. Without formal executive direction, subsequent efforts will lack alignment with business objectives and risk wasting resources.
From a technical standpoint, finding vulnerabilities feels like progress. From a governance standpoint, assessing vulnerabilities without a Board-approved mandate means you don't actually know what assets matter most to the business or what criteria should govern the assessment. Governance dictates that strategy must precede execution.
B. Define Information Security Policy is the correct and necessary first step. Under ISO 27001 (Clause 5: Leadership), top management must establish the Information Security Policy. This document translates business intent into security direction, establishes management's commitment, defines the scope of the ISMS, and sets the criteria against which all future risks and budgets will be evaluated.
A. Decide how to manage risk: Risk treatment methodologies (accept, avoid, transfer, mitigate) can only be decided after the overarching policy establishes the organization's risk appetite.
C. Identify threats, risks, impacts and vulnerabilities: You cannot effectively identify and evaluate risks without the context and scope established by the Information Security Policy. The policy defines what is important to protect.
D. Define the budget of the Information Security Management System: Defining a budget before establishing the policy and scope is a critical business error. The policy dictates the scope, the scope dictates the risk assessment, and the risk assessment justifies the budget.
ISO 27001 relies heavily on top-down governance. The hierarchy of establishment is:
Refine your executive leadership skills with our CCISO strategic simulations.
Explore more CCISO simulations