Operating System Security Fundamentals
Decide which account type and which file permissions each person needs on a shared device, and list the secure settings a new laptop should start with.
The box that asked Riya for a password
Riya Menon, the computer science intern at Tulsi Health, wants to install a screen-recording tool on the Kothrud billing laptop so she can make training videos. A box appears asking for an administrator password, which she does not have, and the installation stops. That box is the operating system doing its security job. The operating system, or OS, is the main program that runs a device and every other program on it: Windows or Linux on a laptop, Android or iOS on a phone. Because it sits underneath everything, it decides who can log in, which programs may run, and who may read or change each file, so its settings shape the security of the whole device.
The program in charge of everything else
Every app on a laptop, from MedLedger to the web browser, needs the computer's memory, disk and screen. Apps do not touch these directly. They ask the operating system, much as residents of a society ask the secretary before using the community hall. Because every request passes through the OS, it is the natural place to enforce rules: this person may log in, this program may save files here but not there, nothing may change system settings without an administrator's approval.
Apps never reach the disk or memory directly. Every request goes through the OS, which is why its rules protect everything on the device.
Operating system security means the features the OS provides for this: login and accounts, permissions on files, a built-in firewall that blocks unwanted network connections, built-in malware protection, and updates that fix flaws in the OS itself. These features are already on every Tulsi Health laptop. Whether they protect anything depends on how they are set up, and the most important settings are about accounts.
One account for each person
A user account is the identity a person logs in with: a name, a password, and their own set of files and settings. When the Nashik Road staff all share one login called "counter", the laptop cannot tell Arjun from the evening assistant. If prices are changed or a file is deleted, the record says only "counter did it". If one employee leaves, the shared password has to be changed for everyone, which in practice means it never gets changed.
Giving each person their own account fixes all three problems. The OS records which account did what, so mistakes and misuse can be traced. A departing employee's account can be switched off without disturbing anyone else. And each account can be given exactly the access that person needs, which is where the difference between ordinary and powerful accounts comes in.
The warden's master key
Operating systems have two main kinds of account. A standard user account can run approved programs and work with its own files, but cannot install software, change system settings or read other people's files. An administrator account, or admin, has administrator privileges: it can do all of those things, including switching off the device's protection. A hostel shows the difference well. The warden carries a master key that opens every room, while each student carries a key that opens only their own.
A program runs with the keys of the person who started it. Opening a bad attachment as admin hands the attacker the master key ring.
The reason this matters is that a program runs with the rights of the person who started it. If Sameer opens a malicious attachment while logged in as admin, the malware also has admin rights: it can install itself permanently, switch off anti-malware and spread. If he opens it as a standard user, it is mostly trapped inside his own account. Giving the warden's key to every student would be convenient on the day someone is locked out, and disastrous the day one key is copied.
So the rule is to use a standard account for daily work and an admin account only for the moment a task truly needs it. On Windows, that moment is the box that asks for an admin password before a change; on Linux and macOS a similar prompt appears. The prompt is a pause to ask "should this really change the whole laptop?", and it works only if everyday staff do not know the admin password. At Tulsi Health, only Neha and one colleague hold admin accounts, and they do not use them for email or browsing.
Almost all daily work fits in a standard account. Admin is for a few short tasks, done by the people responsible for the device.
Practise the choice below. For each task at a Tulsi Health store, decide which kind of account should do it, and who should hold it.
A register of who may open which cupboard
Accounts say who you are; file permissions say what each account may do with each file or folder. Think of a register kept at a pharmacy's back office that lists, for every cupboard, who may open it and who may only look through the glass. Operating systems keep such a register for every file. The basic permissions are read (open and look), write (change or delete) and, for programs, execute (run). Permissions are usually set on a folder and apply to everything inside it.
Good permissions follow the principle of least privilege: give each person the least access their job needs, and nothing more. At Tulsi Health, the IT lead manages MedLedger's settings but has no reason to read prescriptions. An intern helping check the day's totals needs to view the bills, not change them. Extra access feels harmless until an account is misused, when every extra permission becomes extra damage.
Set the permissions below for a shared billing laptop at the Kothrud store. Every cell starts at "Edit", the careless default, so your job is mostly to take access away. Check your answer to see which cells give too much (a risk) and which give too little (the job breaks).
Salaries appear in no row of that table, because they are handled by Sameer at head office and should not be on a store laptop at all. Often the safest permission is to keep a file off a device entirely.
Secure settings from the first day
A fresh laptop is set up for convenience, not safety. Secure system configuration means changing those defaults before the device is handed to staff, and keeping them that way. The checklist is short: separate standard accounts for every person, a disabled guest account, a screen that locks itself after a few idle minutes, the built-in firewall and malware protection switched on, automatic updates on, and software nobody uses removed. Each step closes a door that would otherwise stay open on every laptop of the same model.
None of these needs extra software. They are settings the operating system already has, switched from convenient to safe.
Neha writes this checklist down and applies the same settings to all 14 billing laptops, so that a new laptop at a new store starts out as safe as the others. A written standard also makes drift visible: when someone switches the firewall off "just for today", the difference from the checklist shows up at the next monthly check, instead of quietly staying that way for a year.