When unidentified attackers seized control of Norway's Risevatnet dam this April, they did it with nothing more exotic than a weak password. For four full hours, the facility's valves sat exposed to remote manipulation. It is a stark reminder that connectivity creates vulnerability.
The Risevatnet Incident
In April 2025, attackers gained control of the Risevatnet dam's control systems in Norway. The attack vector was embarrassingly simple: a weak password on an internet-connected control interface. For four hours, the attackers had the theoretical ability to manipulate the dam's water flow controls.
Fortunately, no physical damage occurred. But the incident exposed a fundamental truth about connected infrastructure: the more critical the system, the more dangerous its connectivity becomes.
Why Critical Infrastructure Gets Connected
The push to connect critical infrastructure comes from understandable motivations:
- Remote monitoring: Operators can check system status without physical presence
- Efficiency: Automated systems can respond faster than human operators
- Cost savings: Fewer on-site personnel means lower operational costs
- Data collection: Connected systems generate valuable operational data
These benefits are real. But they come with a hidden cost: every connection is a potential attack vector.
The Password Problem
The Risevatnet attack used a weak password. This is depressingly common. Despite decades of security awareness training, organizations continue to protect critical systems with passwords like 'admin123' or 'password1'.
But here is the uncomfortable truth: even strong passwords are not enough. Given sufficient motivation and resources, attackers can eventually compromise any connected system. The question is not whether your password is strong enough. It is whether the system should be remotely accessible at all.
Lessons for Data Protection
The Risevatnet incident wasn't about data, but the principle applies directly. Consider your organization's most sensitive information:
- Strategic plans: Is your five-year strategy really needed online 24/7?
- Customer records: Do historical records need to be instantly accessible?
- Financial data: Should your complete financial history be one breach away from exposure?
- Legal documents: Does privileged information need to live on connected servers?
For each of these, ask: what's the actual cost of offline storage versus the risk of online exposure?
Beyond Temporary Isolation
Some organisations believe they have solved this problem with isolated systems, computers not connected to the internet. But true isolation is surprisingly rare. Systems get temporarily connected for updates. USB drives bridge the gap. Maintenance windows create exposure.
Firevault goes further with physical disconnection. Our vaults are designed to be offline by default, with connection only occurring when the owner physically initiates it. There is no maintenance window, no update cycle, no temporary connection that could be exploited.
The Real Question
The Risevatnet attack succeeded because a critical system was connected when it didn't need to be. The attackers didn't need sophisticated exploits—they needed a weak password and an internet connection.
Your organization's data faces the same calculus. Every piece of information stored online is one vulnerability away from exposure. For the data that matters most, the question is not how to protect it online. It is whether it should be online at all.
Conclusion
Norway's dam survived its four-hour compromise without physical damage. But the incident serves as a warning: connectivity creates vulnerability, and the most critical assets deserve the strongest protection.
For your most sensitive data, that protection is simple: take it offline. Firevault makes this practical, providing secure offline storage with controlled access when you need it. The best defence against remote attacks is having nothing to remotely attack.
