During a tense political situation, a group calling itself a “cyber army” calls for attacks on utilities in a messenger channel. A few hours later the customer portal of a municipal utility is unreachable, flooded with requests. At the same time someone tries default passwords on the remote maintenance access of a pumping station. Neither is technically demanding. The group still publishes screenshots and claims to control the city’s water supply. For terrorist groups, effect is what counts: outages, fear and headlines matter more to them than technical finesse.
ISO/IEC 27005 names terrorists and cyber militias in Annex A as an example of risk sources. Their hallmark is the determination with which they act and their goal of disrupting operations and shaking trust in institutions. For most organizations, though, the risk is indirect: they rarely become the target themselves, yet they feel the consequences of an attack on power, networks or service providers in their surroundings.
What is behind it?
This covers groups that pursue political, religious or ideological goals through violence or the threat of it. In the IT space they appear as cyber terrorists or as loosely organized militias that mobilize volunteers through social networks. The line to state-directed groups is sometimes blurred, for example when a militia acts in the interest of a state without officially belonging to it.
Resources and approach
- Flooding. Attacks that knock out websites, portals or emergency services with requests are cheap to obtain and quickly produce visible effects.
- Known gaps. Many groups fall back on published vulnerabilities, default passwords and poorly protected controllers on the internet.
- Defacement. Hijacked websites display propaganda and are meant to prove that the opponent is vulnerable.
- Physical attacks. Arson on cable ducts, substations or radio masts hits supply networks and with them many organizations at once.
- Threats. A bomb threat alone can have a building evacuated for hours without anything actually happening.
Impact
Availability comes first: supply, communication and access to buildings fail. In industrial plants and utilities, a manipulated setpoint can turn into a danger to life and limb. On top of this comes the loss of trust, since the public effect is often greater than the technical damage. Restoring physical infrastructure usually takes much longer than rebooting servers.
Practical examples
Evacuating the data centre. A data centre operator receives an anonymous bomb threat. The police clear the building for six hours; the equipment keeps running, yet nobody may enter. A customer whose firewall fails during exactly this window can do nothing, because it has no second site.
Attack on the power supply. Unknown persons set cables on fire at a substation during the night. A business park is without power for two days. A manufacturer with a standby generator keeps working, while its neighbour without backup power loses production and also a database that was damaged when the power went out.
Controller on the internet. A group searches specifically for plant controllers that are connected to the internet without protection. At a small water association it changes a setpoint using a default password. An employee in the control room notices the change in time, and the group still circulates a video of the intrusion.
Typical threats
This risk source typically uses or triggers these BSI elementary threats:
- G 0.34 Attack: bomb and arson attacks on buildings and infrastructure.
- G 0.41 Sabotage: interference with controllers and supply installations.
- G 0.40 Denial of Service: flooding websites, portals and communication services.
- G 0.8 Failure or Disruption of the Power Supply, G 0.9 Failure or Disruption of Communication Networks and G 0.10 Failure or Disruption of Supply Networks: the most common way attacks reach organizations indirectly.
- G 0.11 Failure or Disruption of Service Providers: when a data centre, provider or logistics partner is affected.
- G 0.6 Disasters in the Surroundings and G 0.7 Major Events in the Surroundings: cordons and evacuations after an attack or during large events nearby.
- G 0.44 Unauthorised Entry into Premises: as preparation for physical attacks.
Effective controls
Prevention:
- A.7.5 Protecting Against Physical and Environmental Threats: structural measures and site selection for critical equipment.
- A.7.11 Supporting Utilities: uninterruptible power supply, standby generator and redundant cooling.
- A.8.20 Networks Security: protection against flooding attacks and no unprotected controllers on the internet.
Detection:
- A.5.7 Threat Intelligence: following situation reports from the authorities and warnings about campaigns against your sector.
- A.7.4 Physical Security Monitoring: surveillance of premises and technical rooms.
Response:
- A.5.29 Information Security During Disruption: maintaining security in emergency operation as well.
- A.5.30 ICT Readiness for Business Continuity: planned and practised recovery, alternative sites and redundancy.
Risk sources in ISO 27005
ISO/IEC 27005 broadly distinguishes two directions in the objectives of risk sources: either the attacker uses the resources of its target for its own benefit, or it wants to stop the target from using its resources. The standard names terrorism explicitly under the second direction, together with sabotage and destabilization. The fitting target objectives are “Influence” and “Obstacle to functioning” from Table A.9, which reappear as motivation in the product. For the likelihood of deliberate risk sources, the standard lists among other factors the influence of terrorist organizations. The asset-based approach helps with treatment: a threat such as a failure of the power supply can be rated against the affected assets, whether an attack or a technical defect lies behind it (→ ISO/IEC 27005 Information Security Risk Management).
Sources
- ISO/IEC 27005:2022, clauses 7.2 and 7.3.3 and Annex A.2.3: risk sources and target objectives
- BSI IT-Grundschutz Compendium: elementary threats G 0.6 to G 0.44
- ISO/IEC 27002:2022, clauses 5.7, 5.29, 5.30, 7.4, 7.5, 7.11 and 8.20