Administrative resilience means an organization’s ability, for example, to maintain its operations when the operating environment is disrupted. In today’s global operating environment, the risk of such disruptions is constantly increasing, making organizational preparedness essential. Organizational resilience is built at multiple levels.
The first part of our blog series examined management responsibility and strategic cybersecurity choices. In this second part, we look at how these choices are translated into governance models and processes so that the right issue reaches the right person for resolution early enough
During a disruption, the crucial question is whether the organization knows who makes the decisions and how information is quickly delivered to the right parties. The impact of a disruption is difficult to predict and manage if a service has no owner, roles are unclear, practices vary, and instructions are outdated.
Even good technical controls cannot compensate for these shortcomings, and an approved information security policy protects no one if it hasn’t been put into practice. Operations are strengthened by a culture in which personnel receive role-based training, rehearse disruption scenarios, and feel able to report shortcomings they identify.
At the same time, cloud services, identity solutions, and AI agents are expanding organizations’ attack surfaces. An attacker may need only one exploitable vulnerability in a critical system. AI accelerates the discovery and exploitation of vulnerabilities, leaving organizations with even less time to respond to shortcomings (CISA Vulnerability Review FY 2024/2025; CERT-EU / Threat Landscape Report 2025: A Year in Review, pdf).
Even good technical controls can't compensate for shortcomings in ownership, roles, practices and instructions. An approved information security policy protects no one if it hasn’t been put into practice. Operations are strengthened by a culture in which personnel receive role-based training, rehearse disruption scenarios, and feel able to report shortcomings they identify.
Legislation, regulatory requirements, and service agreements may require an up-to-date risk management operating model and proportionate controls. Management is responsible for identifying requirements, leading and overseeing risk management, and ensuring the necessary resources are available. Designated service and process owners are responsible for implementation within their areas of responsibility. In addition to policies and instructions, effective arrangements are therefore needed.
In preparing for cyber threats, the administrative level connects management’s strategic decisions with operational work. Administrative resilience is built on four interconnected elements:
roles and authority
treatment of identified risks
accountability and continuous improvement
flow of information
Read more about these below, or skip directly to the CISO checklist at the end.
The business owns its operations and the associated risks. Information security, data protection, legal, and technical experts contribute their assessments to decision-making. Roles and decision-making authority are defined in the governance model.
At a minimum, document:
who approves new services and features, access to critical information, required controls and deviations from them, and who acts as the designated deputy for each role
supplier contacts and the parties’ practical responsibilities under the agreements
which matters require review and approval by multiple parties
what is reported about risks, deviations, and corrective actions, to whom, and how often
how disruption situations are managed: who compiles the situational picture, decides on restricting operations, assesses notification obligations, and handles the necessary communications
The responsible person needs information, time, and sufficient authority to perform the role. In a small organization, one person may hold several roles. A larger organization requires a more coordinated division of responsibilities and clear ways of working together. The need for additional resources should be escalated to management early enough for a decision.
Risk management begins by examining critical core operations and their dependencies: What could prevent the service from being delivered? What would happen if information were incorrect, a supplier were unavailable, or extensive access rights fell into the wrong hands?
The risk management procedure defines how risks are identified, classified, assessed, and treated. When the business and specialists assess impact and likelihood together using the same criteria, risks can be compared and measures targeted appropriately. An annual risk workshop is not enough because risks emerge through everyday changes: a new service is acquired, a supplier is changed, or new features are added to a tool.
Risk management is moved from paper into practice in three steps:
For each risk, record the business impact, owner, selected measures, and residual risk.
Prioritize measures according to which shortcomings can actually be exploited. At the same time, assess the time, expertise, and budget they require.
Monitor whether the measures are implemented and whether they reduce the risk.
Resilience is also strengthened by the ability to identify new risks and address them quickly.
Evidence that measures have been implemented should be collected as part of the work, not only for an audit or disruption investigation. The basic documentation should identify critical services, dependencies, key risks, owners, approved solutions and their rationale, and the date of the next review.
Documentation helps translate identified requirements into practice and monitor their implementation. At the same time, completed measures provide evidence of how obligations have been met. Documentation can feel like burdensome bureaucracy if the same information is recorded in several places or if its purpose and benefits remain unclear.
Good documentation answers practical questions:
Which services are critical, and in what situations will a service be shut down to prevent the damage from spreading?
In what order and how quickly will operations be restored if a system or supplier fails?
What information will be recorded during a disruption for notifications and subsequent investigation?
Where can up-to-date instructions be found even when the usual systems are unavailable?
Who corrects shortcomings identified in exercises and audits, by when, and what is reported to management?
A lightweight task tracker and annual planning calendar are often sufficient for monitoring. They should provide a high-level view of the matters to be reviewed, the responsible persons, schedules, and where the evidence can be found.
Roles and decisions have a practical impact only when information about them reaches the right people. Information must therefore flow in all directions across the organization.
Management decisions must be translated into clear communications, instructions, and training that enable people to act accordingly. Information flows should be tested in advance, and backup communication channels and people should also be agreed.
Information flows from personnel to management through observations made in everyday work, such as a flaw in a way of working or an error in instructions. An observation is useful only if it is reported immediately and reaches the right person. This requires effective reporting channels and a culture in which the person reporting an issue is not blamed.
What matters more than the volume of messages and instructions is that they clearly state what is expected of each person. Training should therefore also be linked to roles and practical situations. Training and communications should address at least:
what organization-related information people need to know in their role and where up-to-date information can be found
how and to whom a suspected shortcoming or disruption should be reported
how the adequacy of competence and operating practices is verified and measured
Information security management can be structured and verified using, for example, the ISO/IEC 27001 standard, which also supports organizational management and risk management. However, using the standard or obtaining certification does not in itself demonstrate that statutory obligations have been met.
An entity within the scope of Finland’s national Cybersecurity Act must register in the list of entities (Section 41) and submit incident notifications within the specified deadlines (Sections 11–14). The GDPR, in turn, requires a separate personal data breach notification procedure (Articles 33–34), the fulfilment of data subject rights (Articles 12–22), and, where necessary, a data protection impact assessment (Article 35).
Assess whether the current governance model covers all operations to which legal requirements apply, or whether there are services or functions that the current model does not address. For example, an operation or service may fall outside the scope of ISO certification but still be subject to legal requirements. A supplier’s ISO certificate can provide useful information about its level of information security, but it does not replace the organization’s own risk management.
A separate responsibility and reporting chain is not needed for every regulation. Information security, data protection, AI, and continuity management can be connected to shared decision points and monitoring, provided that the specific requirements of each regulation and the corresponding evidence remain identifiable.
The management of critical operations can be described using the following model.
Do and check: Which services and business functions are critical? What data, systems, suppliers and people do they need?
Documented output: Information inventories, description of critical services and dependencies, and owners
Do and check: Which legal and contractual requirements apply to this operation?
Documented output: Identified requirements, their targets and responsibilities
Do and check: What could jeopardize the operation or data? How is the risk treated, and who approves the remaining risk?
Documented output: Risk classification and assessment, selected measures, rationale and approvals
Do and check: Who implements the measures, with what authority and resources, and within what timeframe?
Documented output: Assigned implementation plan and up-to-date instructions
Do and check: What evidence shows that the agreed measures work and the identified requirements are met?
Documented output: Results of checks, exercises and assessments (with their impacts) and identified gaps
Do and check: Have the operation, dependencies, risks or requirements changed? What will be corrected and what is escalated to management?
Documented output: Updated assessments, follow-up of corrections and management reporting
At a minimum, document matters so that each decision and measure is easy to understand, implement, and verify, including during a disruption.
In upcoming the final part of the blog series, we will move to the operational level: how responsibilities and controls are reflected in access rights, information handling, incident management, and recovery.
See also:
The first part of our administrative resilience blog series examined management responsibility and strategic cybersecurity choices.
Our previously published guide: The EU NIS2 Cybersecurity Directive and Finland’s national Cybersecurity Act, a concise introduction to Finnish legislation covering who the Act applies to, what obligations it imposes on different organizations, and where to find reliable guidance from the authorities.