Cyber incident grab bag: Ensuring your incident response reflects reality

Use this module if your cyber incident involves unclear ownership, or complex organisational arrangements.


Managing a cyber incident during organisational change and complexity

Use this module if your incident involves unclear ownership, or complex organisational arrangements. This often arises when councils operate across shared services, partners or suppliers, or where roles, leadership or governance arrangements are changing and not fully established.

What to expect

In these situations, your incident response may not fail, but it will be harder to coordinate and control.

You should expect:

  • unclear or contested ownership of systems, services, or decisions
  • fragmented or uncertain decision-making, particularly where leadership or roles are changing
  • gaps in knowledge, where key information sits with individuals or suppliers
  • competing priorities across services, partners, political or organisational leadership
  • less ability to act quickly due to the need for more complex coordination.

Do not assume your existing plans reflect how your organisation actually operates. Historic arrangements and decisions may still shape how systems and services work, even if they are not well understood or where organisational memory is less strong.

Typical signs this is affecting your response

You may be experiencing this if:

  • it is unclear who owns a system, service, or decision
  • different teams, partners, or leaders are giving conflicting direction
  • decision-making authority or escalation routes are unclear or still evolving
  • you are dependent on specific individuals to understand systems or processes
  • plans or documentation assume structures that don’t reflect reality (for example, unclear boundaries, or reliance on manual workarounds)
  • you discover unknown or ‘off the radar’ systems, contracts or dependencies during the incident
  • multiple stakeholders are asserting legitimate but competing priorities during the response.

Recognising these patterns early can help you respond more effectively.

Your key strategic actions

Do not assume that long standing arrangements are well understood or documented. Historic decisions, informal workarounds, and legacy arrangements may still shape how your organisation operates – you will need to actively establish clarity as you respond.

Focus on the following critical actions throughout your response and recovery. (Note: these are a strategic guide, not an exhaustive list of every action you should take.)

  • Map ownership and dependencies. Identify which services, systems, and contracts are in scope, where they cut across teams, partners, and organisations, and who is responsible.
  • Clarify ownership and decision making early. Establish who has authority to make operational and risk decisions during the incident. Put in place strategic coordination arrangements, for example, joint teams to manage alignment of your communications.
  • Surface and test assumptions about responsibilities, data access and decision rights early, and check this directly with service owners, suppliers, and technical teams.
  • Do not delay action while seeking perfect clarity. Work on the best available information and update your understanding as the situation develops.
  • Empower rapid technical action where needed to protect your systems and data. Ensure technical and security teams have the authority to isolate systems or take defensive actions rapidly, including outside normal working hours.
  • Use clear interim assumptions where needed. Where ownership or responsibilities are unclear, define and share a working position, and update it as understanding improves. Where decisions must be made with incomplete information, proceed based on clear interim assumptions, and revisit these as your understanding improves.
  • Engage shared service partners, suppliers, and neighbouring authorities early where dependencies exist.
  • Document decisions, trade-offs, and uncertainties as part of the incident record
  • Pay early attention to culture, particularly in newly formed or changing organisations. Building trust, openness, and shared purpose will support a more effective response and recovery.

Learning from previous incidents

Other councils who have experienced serious cyber incidents have found that:

  • historic arrangements (for example, previous shared services or legacy integrations) can create links and connections between councils and partners that are not well understood or documented
  • explicit decisions are safer than assumed ones, not making timely decisions can make the challenges harder
  • transparency with partners, regulators and government builds confidence, especially when certainty is limited
  • aligning communications across affected councils can be challenging, especially where the impacts of the incident vary between the councils
  • prioritisation for response and recovery is challenging when working across organisational boundaries
  • major organisation changes can mean that key people have left the council and that culture is more sensitive to the pressures of a serious incident.

Guidance across the different time stages