Essential Cybersecurity Terminology
Separate an asset, a threat, a vulnerability, a risk and an incident in a described situation, and reason about it from both the attacker's and the defender's side.
Five words for one sticky note
At the Nashik Road branch, Arjun Pawar, the store manager, has stuck the billing laptop's password on a yellow note on the screen so the evening staff can log in. Customers stand a metre away. Security people can describe this small scene with five different words, and each word points at a different part of the problem: the asset being protected, the threat that could harm it, the vulnerability that makes the harm possible, the risk that it happens, and the incident if it does. Getting these words straight is not vocabulary for its own sake. Each one tells you something different to look at, and something different to fix.
One scene, five words. The asset, the threat and the vulnerability are things you can point at; the risk is a possibility, and the incident is what happens if the possibility comes true.
Assets: what is worth protecting
An asset is anything of value to a person or an organisation: something that would cost money, time, safety or trust to lose. A digital asset is one that exists in, or is reached through, computers. For Tulsi Health that means the customer database, the MedLedger software and its sales data, staff email accounts, the Tulsi Health app itself, and even the domain name tulsihealth.in that customers type to find it. Devices are assets too, such as the 14 billing laptops and the store Wi-Fi routers.
Some assets are less visible but matter just as much, like the trust of 2.4 lakh customers who hand over their prescriptions. Think of what a family protects at home: the gold in the steel cupboard, the property papers in a file, and the family's good name in the neighbourhood. Some of these can be replaced with money and some cannot, and a sensible family guards them differently. The first question in any security discussion is therefore "what do we have that is worth protecting?"
Threats: what could cause harm
A threat is anything that could harm an asset. Often it is a person: a criminal sending fake emails, a thief at a crowded counter, a former employee who still knows a password. A person or group that could cause harm on purpose is called a threat actor. But a threat does not have to be a villain. A staff member deleting the wrong folder, a burst water pipe above the server cupboard, a long power cut and a failing hard disk are all threats too.
Only some threats are people with bad intentions. A plan that guards against attackers but ignores mistakes and failures leaves half the threats untouched.
A threat on its own does nothing to you. Burglars exist in every city, yet most houses are not burgled tonight, because a threat needs a way in.
Vulnerabilities: the weak spot a threat can use
A vulnerability is a weakness that lets a threat succeed. In a house it is the unlocked window, not the burglar. In the Nashik Road scene it is the password written where anyone can read it. Other common vulnerabilities are software that has not been updated after a known flaw was found, one Wi-Fi password shared by staff and guests, a laptop with no screen lock, and staff who have never been shown what a fake email looks like.
Vulnerabilities are the part an organisation controls most directly. Tulsi Health cannot stop scammers from existing or the monsoon from arriving, but it can give each employee their own login, install MedLedger updates from Rathi Softech, and keep the guest Wi-Fi separate. That is why so much everyday security work is finding weak spots and closing them before anyone uses them.
Risk and incident: before and after
A risk is the possibility that a threat will use a vulnerability to harm an asset, together with how bad that harm would be. It is a statement about the future: "a stranger may read the note and later log in to MedLedger, which could expose the day's sales and let prices be changed". A risk exists only where all three pieces meet. Remove the vulnerability (no sticky note, a separate login for each employee) and the same stranger standing at the same counter creates almost no risk.
A security incident is what happens when the possibility comes true: an event that actually harms, or seriously threatens, the confidentiality, integrity or availability of an asset. The stranger does log in that night and changes prices; that is an incident. The monsoon gives a familiar comparison. A forecast of heavy rain in Pune tomorrow is like a risk, a statement of likelihood and possible damage, while a flooded underpass with a bus stuck in it is the incident.
Break any link in the chain and the incident cannot happen. Defenders usually break it at the vulnerability, because that is the link they control.
Sort the cards below into the five words. A quick test helps: an asset is something you have, a threat is something that could act, a vulnerability is a weakness, a risk is a possibility in the future, and an incident is something that has already happened.
The attacker's view and the defender's view
An attacker and a defender look at the same scene with different questions. The attacker asks "where is the easiest way in, and what is it worth to me?" and needs to find only one weak spot. The defender asks "what matters most here, what could reach it, and would we notice?" and has to think about every door. Cricket captures the imbalance: a batter needs only one loose ball to hit a boundary, while the fielding captain must place nine fielders to cover every gap, over after over.
Good defenders borrow the attacker's questions to find gaps, then answer them with the defender's priorities and budget.
The attacker mindset is useful to defenders. Walking through your own systems as an outsider would ("if I wanted the customer list, what would I try first?") reveals weak spots that a checklist misses, like the sticky note that everyone at Nashik Road had stopped seeing. The defender mindset adds what attackers ignore: priorities, a limited budget, the people who still need to do their jobs, and the question of how quickly a problem would be noticed.
Practise switching between the two views below. You play Neha Kulkarni, the IT and security lead, for one week. Each situation shows what an attacker would notice; choose the defender's best first move.