bastion

Fundamental Security Principles

Build this skill

Classify a security failure as a loss of confidentiality, integrity or availability, and weigh a control's protection against its cost to usability.

Three ways a prescription record can go wrong

Pick any record in the Tulsi Health database: say, the prescription that Farida Shaikh, the senior pharmacist at Kothrud, filled for Mrs. Lata Gokhale last month. Three quite different things could go wrong with it. A stranger could read it. Someone could change it. Or it could refuse to open just when Farida needs it at the counter. Security professionals name these three properties confidentiality, integrity and availability, and call them together the CIA triad (the letters have nothing to do with any spy agency).

The triad is useful because almost every security failure you will ever read about is the loss of one or more of these three. When something goes wrong, asking "which of the three did we lose?" tells you what kind of problem you have and what to do first. The same three questions also work in advance, when you are deciding how to protect something new.

C Confidentiality Prescriptions Only the right people can see it. Bank locker: key holders only I Integrity Rx: Mrs. L. Gokhale Amlodipine 5 mg 50 mg ? ! changed by whom? Nobody changes it without being noticed. Railway chart: names stay true A Availability ! App down Sun, 9:00 pm It works when it is needed. ATM: no use if it is off

The same prescription can fail in three ways: seen by the wrong person, quietly changed, or out of reach when it is needed.

Confidentiality: only the right eyes

Confidentiality means information is seen only by the people who are meant to see it. A bank locker is the everyday picture: the bank keeps it in its vault, but only the account holder with the right key can open it. Mrs. Gokhale's prescription should be visible to her and to the pharmacist filling it, and not to other customers, not to every Tulsi Health employee, and certainly not to someone on the internet.

Confidentiality is lost when a database is accidentally left open to the internet, when an email with a customer list goes to the wrong address, or when a pharmacist reads out a patient's medicines across a crowded counter. The controls that protect it decide who may see what: passwords, access rights ("only pharmacists can open prescriptions"), and encryption, which scrambles data so that only someone holding the right key can turn it back into readable text.

Integrity: correct and untouched

Integrity means information is accurate and has not been changed by anyone who should not change it, whether on purpose or by mistake. Think of the reservation chart pasted outside a railway coach. If someone could quietly alter the names or berth numbers, the chart would still be readable, but nobody could trust it. In a pharmacy, integrity can be a matter of health: if a record that says "amlodipine 5 mg" becomes "50 mg", the data is still private and still available, yet it is now dangerous.

Integrity is also lost when medicine prices in MedLedger are altered, when a fake supplier invoice is slipped into the shared drive, or when a half-finished software update leaves a file corrupted. The controls that protect it allow only certain people to edit, keep a log of who changed what and when, and compare data against a known good copy so that a change cannot go unnoticed.

Availability: there when it is needed

Availability means systems and data can be used at the moment they are needed. An ATM that shows "temporarily out of service" at midnight has not leaked anyone's balance or lost anyone's money, yet it has failed the person standing in front of it. For Tulsi Health, availability is lost when the app is down on a Sunday evening, when the store Wi-Fi stops and orders cannot reach the counter, or when ransomware (harmful software that locks files until a payment is made) freezes the billing laptops so no bill can be printed.

The controls that protect availability are about having another way: backups that can be restored, spare equipment, enough computing capacity for busy days, and a plan for working on paper for a few hours. Of the three properties, availability is the one customers notice first, because a leak can stay hidden for months while a dead app is obvious within minutes.

ConfidentialityAsks: who can see it?Lost: customer list leakedGuard: access rights, encryptionIntegrityAsks: is it still correct?Lost: 5 mg changed to 50 mgGuard: edit rights, change logsAvailabilityAsks: can we use it now?Lost: app down on Sunday nightGuard: backups, spare capacity

Each property asks its own question. A control that answers one question well may do nothing for the other two.

Reading the triad in real incidents

Real incidents do not arrive labelled with a letter, so the skill is to ask the three questions in turn. Some incidents hit more than one property. Ransomware that locks the shared drive is first an availability loss, but if the criminals also copy the files before locking them and threaten to publish them, confidentiality is lost too. Name the main loss first, because it decides the first response: a leak needs the exposure closed and the affected people told, a tampered record needs the correct value restored and the change traced, and an outage needs the service brought back.

Try that habit on the incidents below. For each one, ask which property is broken first, and choose that bucket even if a second property is also involved.

Stronger security can make work harder

Every security control adds a step for somebody. Neha Kulkarni, Tulsi Health's IT and security lead, wants staff passwords that are hard to guess. Suppose she insists on 16-character passwords changed every month and locks an account after three wrong attempts. On paper that looks strong. In practice, staff write their passwords on sticky notes beside the billing laptop, use predictable patterns such as Tulsi@Jan and Tulsi@Feb, and keep her team of two busy with reset calls all day.

This tension is called security versus usability: the more effort a control demands, the more people try to get around it, and a control that people get around protects nothing. A housing society shows the same pattern. If the gate makes every delivery person wait twenty minutes for a resident's approval, residents soon start leaving the side gate open. The aim is not the strictest possible rule but the strongest protection that people will actually follow.

Strong, then bypassedMonthly 16-character passwords end up onsticky notesThe targetSensible password plus two-step loginWorst of bothAnnoying rules that stop nothingEasy, exposedOne shared counter password for everyoneEasier to use →Real protection →

The best controls sit top right: hard for an attacker, light for the people doing the work. Strict rules that push people to work around them drift down.

A control that sits in the top right is two-step login: after the password, the system asks for a second proof, such as a code on the employee's phone. It costs a few seconds, yet it stops a person who has stolen only the password, which in turn lets the password rules be gentler.

Use the model below to set Tulsi Health's staff login policy. Watch how much protection survives once human behaviour is counted, and how many reset calls land on Neha's team each month.

Follow your curiosity.

↑ ↓ to explore · Enter to open · Escape to close