Norway's Total Defence Year 2026: Preparedness is no longer just the state's job
Norway's Minister of Justice and Public Security is asking businesses, including small ones, to write continuity plans that actually get used, and to rehearse them. We've distilled the advice from E24's podcast episode on the Total Defence Year into five concrete steps, plus the issue the podcast only touches on: digital dependency.
2026 is Norway's Total Defence Year. The label may sound like something that concerns the Armed Forces, the civil protection authority and municipal crisis plans, in other words, someone else. But when Minister of Justice and Public Security Astrid Aas-Hansen recently appeared on E24's podcast, the message was strikingly little about the state and strikingly much about anyone running a business: total defence is the sum of everything that keeps society running, and businesses are part of it. Including the small plumbing firm.
It's easy to dismiss as ceremonial rhetoric. You shouldn't. Behind the phrase "total defence" lies a sober observation about what modern crises actually look like, and advice concrete enough to act on before summer is over.
The threat picture is composite, and that's the point
The episode revolves around the concept of hybrid threats: war in Europe, extreme weather and cyberattacks, not as three separate scenarios, but as pressures that can occur simultaneously and amplify each other. A storm that knocks out the power is one thing. A storm that knocks out the power while a cyberattack hits the payment systems is something else.
For a business, this means the old dividing lines, where security belongs to the IT department and preparedness belongs to the state, no longer describe reality. The vulnerabilities the minister points to in the episode are mundane: What happens at your company when the power goes? When internet and mobile networks are down? When the supplier at the other end of the chain doesn't deliver? And the uncomfortable question underneath: do you actually know what assets you manage, and where you are vulnerable?
One of the most thought-provoking points in the conversation concerns dependency: large parts of Norwegian business rest on a small number of large foreign technology providers. That is efficient in peacetime. It is also a vulnerability, not because the providers are unreliable, but because the dependency is one-sided, invisible in daily operations, and rarely mapped. If the service disappears for technical, commercial or geopolitical reasons, many businesses have no plan B.
A plan nobody uses helps nobody
The most practical part of the episode is its critique of the preparedness document. Many businesses have a contingency plan. Fewer have one that gets used. The minister describes the problem precisely: the plans are too theoretical and too complex, written to satisfy an audit, archived as a PDF, never opened again. In an actual crisis such a plan is worthless, because nobody remembers what it says, and what it says tends to assume systems that have just failed.
The episode's call is to move from theory to practice: write simple, manageable continuity plans, and rehearse them regularly. A two-page plan everyone knows beats a sixty-page binder nobody has read. The logic is the same as in first-aid training: the value lies not in the documentation but in the actions being automatic when it matters.
Five steps, distilled
The episode's advice boils down to five points. None of them require consultants or a budget resolution to get started.
- Map your assets, risks and vulnerabilities. Not as a 40-page risk analysis, but as honest answers to three questions: What is the most important thing we manage? What could stop us? Where are we most exposed? Write it down. This is the foundation everything else rests on, and the step most companies skip.
- Write a continuity plan people can actually use. Short, concrete, with a paper copy available. Who calls whom when the mobile network is down? How do you deliver your core service without power for two days? Who can make decisions when the CEO is unreachable?
- Rehearse: regularly, not once. A one-hour tabletop exercise every six months ("the power went out at nine this morning. What do we do now?") reveals more than months of plan-writing. The exercise is also the only real test of whether step two produced something usable.
- Anchor it in the board and management. Preparedness is not an operational detail. It is a strategic responsibility. The episode is clear that this belongs on the board agenda. The ability to deliver during a crisis is also a reputation issue: customers remember who kept the wheels turning.
- Do an honest cyber check, including the dependencies. Not just "do we have two-factor and backups?", but: Which cloud services would halt the business if they vanished? Do our data also exist somewhere we control? Have we tested that the backup actually restores? A dependency you have mapped and accepted is a decision. A dependency you have no overview of is a vulnerability.
What the episode only touches on: digital resilience is also an architecture choice
The podcast stops roughly there, a sensible place for a minister to stop. But for anyone turning the advice into practice, the last thread is worth pulling a little further.
Point five is really an architecture question. A business where all data, all communication and all working tools live with providers outside its own control can do everything right in points one through four and still stand helpless the day those services are unavailable. Conversely, every system that can run locally, or at least has a local fallback mode and local copies of critical data, adds a degree of freedom when something fails. This is not about leaving the cloud. It is about knowing exactly what you will do the day it doesn't answer, and about owning enough of your own digital foundation that the answer isn't "nothing".
The Total Defence Year is a good occasion to ask that question, not because the crisis is necessarily coming, but because the answer says a great deal about how robust the business really is, including in the entirely undramatic everyday where a provider changes terms, prices or availability.
Conclusion
The episode's message is instructive precisely because it is so undramatic: nobody is asking small businesses to build bunkers. They are being asked to know what they manage, keep a simple plan for keeping the wheels turning, rehearse it, and understand their own digital dependencies. That is achievable for almost everyone: a day's work to get started, a few hours every six months to maintain.
Preparedness, like most things that matter, is a working habit rather than a document. And as with all habits, the only real mistake is postponing the start.
Based on E24's podcast episode with Minister of Justice and Public Security Astrid Aas-Hansen on the Total Defence Year 2026 (June 2026). The account is paraphrased. Listen to the episode for the minister's own words.