Confidentiality, integrity and availability (CIA)

When people talk about information security, most of them think about hackers. The professional definition is broader, and it rests on three principles known together as the CIA triad:

  • Confidentiality: only those who are authorized see the information.
  • Integrity: the information is correct and complete, and has not been changed by mistake or on purpose.
  • Availability: the information and the systems are accessible when they are needed.

The ISO 27001 standard defines information security as preserving all three, and frameworks such as NIST CSF and the National Cyber Directorate guidance also deal with continuity and recovery. That is why a server that burned, a server room that flooded or an office left without power for days are information security incidents: the systems are not available, and sometimes the information itself is damaged or lost.

This distinction changes how things are handled in practice. When a physical incident is considered part of information security, preparing for it becomes part of the organization’s security plan, gets a budget and an owner, and is checked as seriously as preparation for ransomware.

What counts as a physical incident

A physical incident is any damage to the environment where the equipment and the information are located, regardless of any attacker:

  • Fire, including smoke and heat that damage equipment even when the flames did not reach it, and damage from the water used to put it out.
  • Flooding: a burst pipe, an air conditioner dripping over the network cabinet, a server room in the basement during a rainy winter.
  • Power outages and voltage drops, which cause servers to shut down improperly and sometimes damage disks.
  • Overheating: an air conditioner in the server room that stopped working over a weekend, without anyone knowing.
  • Theft or a physical break-in at the office, including theft of laptops and servers.
  • Damage to infrastructure outside the office: a communications cable cut during street works, or a security situation that prevents people from reaching the office.

What increases the risk

The most significant factor is concentration. When the servers, the backup, the documentation and the passwords are all in the same room, a single incident hits all of them together.

  • Backup in the same building: a backup device (NAS) standing next to the server, or an external disk in a drawer in the same office.
  • An unsuitable location: a server room in the basement, under water pipes, or in a room that is also used for storage.
  • An uninterruptible power supply (UPS) that was never tested: worn-out batteries, or a UPS that is not set up to shut the servers down properly (graceful shutdown) before it runs out.
  • A single source of cooling: one air conditioner, with no backup and no alert when it stops working.
  • Dependence on a single piece of infrastructure: one communications line and one power connection, with no alternative.
  • Computers without disk encryption: a stolen laptop or server also becomes a data exposure incident.
  • Knowledge that exists only in the office: passwords, licenses and supplier phone numbers stored on the systems that were damaged.

Early warning signs

Some incidents come without warning. Others give signs in advance, which are usually ignored because they do not seem urgent:

  • The UPS beeps or sends a low battery alert.
  • The temperature in the server room rises, or the air conditioner runs nonstop and cannot cool the room.
  • Damp stains on the ceiling or on the wall next to the network cabinet.
  • Short, recurring power drops, or flickering lights.
  • Disk errors and hardware warnings on the servers, especially after a power outage.
  • A burning smell or unusual noise from equipment.

Temperature and water sensors in the server room (environmental monitoring), together with monitoring of the UPS and of hardware health, turn these signs into alerts that reach someone who can deal with them, even when the office is empty.

The impact on the organization

The first impact is downtime. Without servers, without communications and without an office, work stops. After a physical incident, downtime tends to drag on, because equipment has to be replaced, deliveries have to arrive, the room has to be restored, and sometimes you have to wait for the insurance company’s assessor before touching anything.

When the backup was in the same place, the damage can be final: information that has no other copy is simply lost. Even without total loss, a sudden server shutdown can damage databases and files that were open at that moment. That is damage to the integrity of the information, and sometimes it is discovered only a few days later, when someone tries to open a file or produce a report.

There is also a confidentiality side that is easy to miss. Damaged disks sent to a recovery lab, equipment thrown away after a fire and computers stolen in the confusion all contain information. The data security regulations under the Privacy Protection Law include requirements for physical and environmental security of the systems where personal information is stored, and for backing it up and restoring it. Since Amendment 13 came into force, the Privacy Protection Authority has broader enforcement powers, and an organization that lost personal information because it had no copy outside the office will find that hard to explain.

How to reduce the risk

The principle is not to put all the eggs in the same building, and to plan in advance how the business works when the office is not available.

  • Critical systems in a data center or in the cloud: there you have backup power, redundant cooling, fire suppression systems and physical security that are hard to reproduce in an office server room.
  • A copy outside the office (off-site): at least one copy of the backup in another location, preferably a backup that cannot be changed or deleted (immutable backup).
  • A well-organized server room: a UPS with batteries that are tested and a proper shutdown, cooling with alerts, water and temperature sensors, and a fire suppression system suited to electrical equipment.
  • Disk encryption on laptops and servers, so that stolen equipment does not automatically become a data leak.
  • A second communications line from a different provider, and the ability to work remotely in a secure way.
  • Documentation that is accessible from anywhere: passwords in a secure password vault, a list of equipment and systems (asset management), contacts and recovery procedures that can be reached even when the office is closed.
  • Business continuity (BCP) and a disaster recovery plan (DRP): based on a business impact analysis (BIA), with a clear target for each system: how long you can be without it (RTO) and how much data you can afford to lose (RPO).

When it happens: the order of actions

  1. People first: employee safety comes before any equipment. Do not enter a flooded room and do not turn on wet equipment or equipment exposed to smoke.
  2. Declaring an incident: whoever was designated in the plan activates it, and tells employees where and how they work in the meantime.
  3. Damage assessment: which equipment was damaged, what still works, and what state the backups are in.
  4. Moving to an alternative environment: bringing up the critical systems in the cloud or at the alternative site (DR site), according to the priorities set in advance.
  5. Restoring and checking integrity: after the restore, check that the information is complete and correct, and do not settle for the system simply starting up.
  6. Control over damaged equipment: disks sent for recovery go through an authorized party with a record of who held them (chain of custody), and equipment that is thrown away goes through controlled wiping or destruction.
  7. Documentation: photos of the damage and a list of equipment for the insurance company, and a record of the decisions and times.
  8. Lessons: what worked, what did not, and what changes in the plan.

Even in a physical incident there is a place for a cyber incident response team. A break-in at the office in which computers were stolen, or equipment with personal information that left the organization’s control, requires finding out what information was on it, whether it was encrypted, and whether a report to the Privacy Protection Authority is required. Such a team also knows how to recognize when an incident that looks physical, such as a cut cable or cameras that stopped recording, is actually part of something else.

Where the IT company fits in

Preparing for a physical incident sounds like a building maintenance topic, but most of the decisions are IT decisions: where the systems run, where the backup is, how people work remotely and what the order of recovery is. An IT company that understands information security treats availability as part of protection, and builds the infrastructure so that an incident at the office does not become an incident for the whole business.

That includes the small details that only come to light on the day of the incident: whether the UPS really shuts down the servers, whether the air conditioner alert reaches anyone, and whether anyone knows where the password to the backup account is written down when the server it is stored on will not turn on.

Summary

  1. Availability is included in the business’s information security plan, alongside confidentiality and integrity.
  2. There is a backup copy outside the office, and it has been checked that you can restore from it.
  3. Critical systems run in a data center or in the cloud, or have a ready alternative environment.
  4. The UPS, cooling and sensors in the server room are tested and send alerts.
  5. The disks in laptops and servers are encrypted.
  6. There are written BCP and DRP documents, with an RTO and RPO for each system, and a documented recent exercise.