bastion

Data Classification and Secure Handling

Build this skill

Assign information to Public, Internal, Confidential or Restricted levels and apply the matching storage, sharing, access and disposal rules.

Not every file deserves the same lock

On a busy Friday, Sameer Joshi in accounts is asked for three things within an hour: the new price list for the Nashik stores, next week's shift roster, and the salary sheet for the bank. He sends all three the same way, as attachments in the staff WhatsApp group, because that is quickest. The price list was meant for customers anyway, so no harm there. The roster was fine for staff. The salary sheet, now on forty phones, was not. The mistake was not carelessness about one file; it was having no simple way to tell which files needed which kind of care.

Data classification is that simple way. It means sorting an organisation's information into a small number of levels according to how much harm it would cause if it were seen, changed or lost by the wrong people, and attaching clear handling rules to each level. Once a file has a level, nobody has to think hard about it. The level tells you where it may be stored, who may open it, how it may be sent and how it must be destroyed.

Four levels, from the notice board to the safe

Your college already classifies information, even if nobody calls it that. The fest dates and the fee notice go on the notice board by the gate, where anyone can read them. The class timetable and the staff duty list go on the staff-room board, for people inside the college. The marks register sits in a locked cabinet in the office, opened only by the office staff and the teachers concerned. The question papers for the end-semester exam sit in the principal's safe, and only two or three people know the combination.

Public College notice board fest dates, fee notice At Tulsi Health Price list, store hours Anyone may read it Harm if leaked: none Internal Staff only Staff-room board timetable, duty list At Tulsi Health Shift roster, staff circulars All staff may read it Harm if leaked: small Confidential Locked office cabinet marks register At Tulsi Health Supplier contracts, salaries, sales figures Named teams only Harm if leaked: serious Restricted Principal's safe exam question papers At Tulsi Health Prescriptions, payment and ID details A few named people ! Harm if leaked: severe

Four places in a college, four levels of care. The level comes from the harm a leak would do, not from how important the document feels.

Most organisations use four levels much like these. The names vary from company to company, and some use three or five, but the idea is always the same: the more harm a leak would cause, the fewer people see the data and the stronger the protections around it.

Public data is information meant for anyone. Tulsi Health's price list, store addresses and opening hours, and the privacy notice in the app are public. Nobody needs to protect their confidentiality, though their integrity still matters: a price list altered by an outsider to show wrong prices would cause real trouble.

Internal data is for people inside the organisation but would cause little harm if it slipped out. The shift roster, staff circulars about the Diwali timings and the IT team's guide to connecting a new printer are internal. A leak would be awkward rather than damaging, so the rule is simply "keep it inside Tulsi Health".

Confidential data would cause serious harm to the business or to individuals if it leaked, so only named teams may see it. Supplier contracts with their negotiated discounts, monthly sales figures, staff salaries and the customer contact list are confidential at Tulsi Health. A competitor seeing the discounts could undercut the business; staff seeing each other's salaries could cause real distress.

Restricted data is the most sensitive level, where a leak could cause severe harm to people or bring legal penalties. At Tulsi Health this means prescriptions and the medicines each customer takes, payment details, and copies of staff ID documents such as Aadhaar cards. Only the few people whose job requires it may open restricted data, every access should be recorded, and it should never leave the systems built to hold it.

Restrictedprescriptions, payment, IDsa few named peopleConfidentialcontracts, salaries, salesnamed teamsInternalroster, circulars, guidesall staffPublicprice list, store hoursanyone

Each step up the stack means fewer people and stronger protection. Most of an organisation's files sit in the bottom two levels; the effort goes into the top two.

Sort the items below into their levels. When an item seems to sit between two levels, ask what the worst realistic leak would do and to whom. If one file mixes levels, such as a delivery sheet that lists customers' names alongside their medicines, it takes the level of its most sensitive item.

Handling rules that follow the label

A label only helps if it changes what people do. Secure data handling means following the rules for a file's level at every step: when you store it, share it, print or carry it, and destroy it. Writing the rules as one short table, and putting it on the wall of every store, turns classification from a policy document into a habit.

Level Where it may be stored How it may be shared When finished
Public Anywhere, including the website Freely Normal deletion
Internal Tulsi Health systems and staff accounts With staff, not outsiders Normal deletion
Confidential Named folders with access limited to a team Company email to named people only; never chat groups Delete, and shred any printouts
Restricted Only MedLedger and the app database Not sent at all; people log in to view it Secure deletion, shred paper, log it

Two details make these rules work. First, labelling: confidential and restricted files carry their level in the file name or at the top of the page ("CONFIDENTIAL: salary sheet, Nov"), so the person receiving one knows immediately how to treat it. Second, access control matches the label: the folder holding salary sheets lets only accounts and the owner in, so a wrong click cannot send it to forty phones.

Labelmark the levelStoreright folderthenSharenamed peoplethenPrint/carrynever left outif neededDisposedelete or shredfinally

The level is decided once, at the first step. Every later step just reads the label and follows the rule for that level.

Who may see each level

Classification decides how sensitive data is; access decides who may reach it. The principle that joins them is least privilege: each person gets exactly the access their job needs, and no more. A pharmacist must read and update prescriptions to do their work; an intern does not, however trustworthy they are. Access granted "just in case" is exactly what turns one stolen password into a large exposure.

Set the access below for four Tulsi Health roles. Each cell can be None, View or Edit. Think about the daily work of each person: Farida dispenses medicines, Arjun runs the Nashik Road store, Sameer handles payments and payroll, and Riya is a computer science intern helping the IT team. Check your answer to see where you gave too much (a risk) or too little (the job breaks).

Notice that nobody in the lab can edit the price list. Public data still needs its integrity protected, so only the head office team that sets prices may change it, even though everyone may read it. Classification and access work together: the label says how careful to be, and the access list makes that care automatic.

Follow your curiosity.

โ†‘ โ†“ to explore ยท Enter to open ยท Escape to close