After two days of continuous rain, a small stream bursts its banks and floods a business park overnight. At a wholesaler, the server room in the basement stands half a metre under water. Fortunately, the backup sits in a data centre in another city. Even so, it takes two weeks until replacement hardware has been procured, set up and loaded with the backed-up data. Environmental influences have neither intent nor target: site, construction and preparation decide whether they become a risk.
In its definition, ISO/IEC 27005 distinguishes three types of risk sources, and the environmental one is among them. In its list of typical threats, the standard uses this type to mark every event that does not stem from human action. In the product, events in the surroundings also belong here, such as an accident next door, because from the organization’s point of view they are just as impossible to influence.
What is behind it?
This covers weather and climate (heat, storms, heavy rain, lightning, hail, snow load), floods, earthquakes and other natural events, fires, dust and corrosion, and events in the surroundings that happen to the organization without it having any say. This risk source comes with every site, and it can be planned for well. That is exactly why it pays to take a sober look at its effect on your own sites.
How environmental influences act
- Direct damage. Water in the basement, lightning striking the building services, fire in the neighbouring building, storm damage to the roof above the server room.
- Climatic strain. Heat overwhelms the cooling, high humidity and temperature swings wear down electronics.
- Gradual wear. Dust from construction sites, exhaust fumes, salty air or soot shorten the lifespan of fans, power supplies and contacts.
- Indirect effect. A storm takes down power, networks or supply chains even when your own site stays intact.
- Blocked access. Evacuations, closed roads or major events keep employees and technicians away from the site.
Impact
Availability comes first: buildings and equipment fail, and replacement takes time. Integrity suffers when storage media are damaged by heat, water or voltage spikes. The damage becomes especially severe when production systems and backups stand in the same place, since the same event then hits both.
Practical examples
Heatwave in the server room. During a heatwave, the only air conditioning unit in a planning office’s server room fails. The temperature climbs steadily over the weekend. The servers throttle their performance, two hard disks fail, and on Monday the file server is unreachable.
Accident in the neighbourhood. A hall burns at a chemical plant three streets away. The authorities close off the area for a day and ask residents to keep their windows shut. The employees of a neighbouring service provider cannot reach their workplaces, and without prepared remote access the business comes to a standstill.
Dust from the construction site. Next to a mail order company’s warehouse, construction goes on for months. Fine dust gets through the ventilation into a network cabinet. The fans clog, the switches overheat and fail at irregular intervals.
Typical threats
These BSI elementary threats stem from this risk source:
- G 0.3 Water: floods, heavy rain, backflow from the sewers.
- G 0.2 Unfavourable Climatic Conditions: heat, cold, humidity.
- G 0.5 Natural Disasters: storms, earthquakes, widespread flooding.
- G 0.1 Fire: lightning strikes, forest and wildland fires, fires in the neighbourhood.
- G 0.4 Contamination, Dust, Corrosion: construction sites, exhaust fumes, aggressive air.
- G 0.6 Disasters in the Surroundings: accidents at neighbouring plants or on transport routes.
- G 0.7 Major Events in the Surroundings: events and closures that make access difficult.
Effective controls
Prevention:
- A.7.5 Protecting Against Physical and Environmental Threats: site selection, construction, water and fire protection, sensors for temperature and humidity.
- A.7.8 Equipment Siting and Protection: placing equipment above basement level and away from water pipes and dusty areas.
- A.7.11 Supporting Utilities: cooling with reserve capacity, backup power, surge protection.
Detection:
- A.5.7 Threat Intelligence: feeding severe weather warnings and flood forecasts into alerting.
Response:
- A.8.13 Information Backup: backups in a place the same event does not reach.
- A.8.14 Redundancy of Information Processing Facilities: critical systems at a second site or in separate zones.
- A.5.30 ICT Readiness for Business Continuity: practised recovery and fallback options.
Risk sources in ISO 27005
In its definition, ISO/IEC 27005 names human, environmental and technical risk sources. In Table A.10, the marker “E” goes to every threat that occurs without human action. The group of natural threats there includes floods, earthquakes and pandemics among others, while fire and water can additionally be caused by accident or on purpose. For the likelihood of accidental risk sources, among which the standard counts natural events at this point, it refers to geographical factors such as proximity to dangerous facilities and to the possibility of natural events such as extreme weather or flooding. It also makes clear that risk identification includes sources the organization cannot control (→ ISO/IEC 27005 Information Security Risk Management).
Sources
- ISO/IEC 27005:2022, definition 3.1.6, clauses 7.2.1 and 7.3.3, Annex A.2.5.1: risk sources, likelihood and typical threats
- ISO/IEC 27001:2022/Amd 1:2024: amendment on climate change in clauses 4.1 and 4.2
- BSI IT-Grundschutz Compendium: elementary threats G 0.1 to G 0.7
- ISO/IEC 27002:2022, clauses 5.7, 5.30, 7.5, 7.8, 7.11, 8.13 and 8.14