Zum Hauptinhalt springen
Risk source · ISO/IEC 27005

RS13 Environment

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27005ISO 27001BSI IT-Grundschutz

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:

Effective controls

Prevention:

Detection:

Response:

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

Frequently asked questions

How do I rate the likelihood of natural events?

Use public hazard maps for floods and heavy rain, data from the weather service, the history of your site and your insurer's rating. Also check which businesses handling hazardous substances are nearby. ISO 27005 names exactly such geographical factors as a basis for likelihood.

Do I have to consider climate change?

Since the 2024 amendment to ISO/IEC 27001, the organization has to determine, when looking at its context, whether climate change is a relevant issue. For many sites this means in practice more hot days that strain cooling, and more frequent heavy rain. Both belong in the risk assessment if they affect your sites.

Does the cloud solve the problem of environmental risks?

It shifts part of it. Cloud providers' data centres also stand in real places, so it is worth looking at regions and separate availability zones. Your offices, network connections and employees also remain where the weather hits them.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.