Human Factors in Cybersecurity
Explain which human tendencies (trust, urgency, fear, deference to authority) an attack exploits and design a habit or process that blunts it.
The attack that targets a person, not a computer
It is 6:40 in the evening at Tulsi Health's Kothrud store. Farida Shaikh has four customers waiting when the counter phone rings. A calm voice says he is from head office IT, that an auditor needs her MedLedger login within a few minutes, and that the store will fail tonight's audit if she delays. No firewall, antivirus or password rule is involved in what happens next. Whether Tulsi Health is safe depends entirely on what Farida does with the phone in her hand.
Attackers often find it easier to persuade a person than to break a machine. The study of how people's habits, feelings and limits affect security is called human factors. It explains why careful, intelligent staff still give away passwords, click bad links and approve fake payments. It also points to the fix, which is rarely "be more careful" and almost always a better habit or process.
One short call presses four buttons at once: a claim of authority, a deadline, a threat and a friendly reminder. The queue of customers adds pressure the caller did not even have to create.
Four buttons an attacker presses
Each line in that call was chosen to switch off careful thinking. Social engineers, people who manipulate others into breaking security, rely on a small set of human tendencies again and again. Once you can name them, you start hearing them.
The first is trust exploitation. Most people want to be helpful and assume that others are honest, and a workplace could not run without that. An attacker borrows trust by sounding familiar: using a colleague's name, mentioning last month's audit, or speaking the office's own jargon. It works the way a stranger gets through a housing society gate by calling the watchman "bhaiya" and naming a flat number; familiarity feels like permission.
The second is urgency. A deadline of "ten minutes" leaves no time to check, and checking is exactly what the attacker fears. The third is fear: a threat of a fine, a blocked account, a failed audit or trouble with the boss. Fear narrows attention to escaping the threat, so the question "is this real?" never gets asked. Urgency and fear usually travel together, because a scary deadline is the fastest way to rush someone.
The fourth is authority impersonation: pretending to be someone whose instructions people normally follow, such as the owner, the IT team, a bank officer or the police. In India this is the engine behind many fraud calls, from fake "courier customs officers" to callers claiming to be from the electricity board. People are trained from school onwards not to argue with authority, and attackers rent that habit for free.
Each tactic switches off a different part of careful thinking, and each has a matching habit that switches it back on.
Why careful people still get fooled
It is tempting to think only careless people fall for these tricks. In practice the opposite is often true: the people who are fooled are busy, conscientious and eager to do their job well. The human brain has a fast mode for routine decisions and a slow mode for careful ones. Pressure, noise and a queue of customers push everyone into the fast mode, where a confident voice and a familiar name are enough to act on.
Attackers choose their moments to match. They call at closing time, during festival rush, on the last day of the month when accounts are busy, or just after a real announcement that makes the story believable. A request that would look odd on a quiet Tuesday morning sounds perfectly normal at 6:40 pm with four customers waiting. That is why "train people to spot scams" is never enough on its own; the setting has to make the safe action easy even for a tired person.
Mistakes with no attacker at all
Not every human-factor incident involves a villain. Human error means an honest mistake that weakens security: an email sent to the wrong person because the address autocompleted, a password written on a sticky note under the keyboard, a laptop left unlocked during a tea break, or a shared folder set to "anyone with the link". Studies of real breaches regularly find a human mistake somewhere in the chain.
The useful response to an error is to ask what made it easy. Sameer Joshi in accounts once nearly sent the month's supplier payment sheet to a personal address with a similar name, because the mail app suggested it first. Scolding Sameer would not stop the next person making the same slip. Turning on a warning for emails leaving the company, and removing personal addresses from the shared contact list, does.
Blame makes people hide mistakes, so the weakness stays. Changing the process removes the trap for everyone who comes after.
Play the evening at the counter
The situations below are the kind Farida and her colleagues meet in a normal month. For each one, choose what you would actually do with a queue in front of you. When you pick an unsafe option it counts as an incident, and the feedback names the tactic that pushed you there.
Designing a habit that works on a bad day
A good defence against human-factor attacks does not ask people to be heroes. It gives them a simple rule they can follow even when tired, rushed and slightly scared. The most powerful one is a call-back rule: any request for a password, a payment or access that arrives by phone, message or email is confirmed by contacting the person through a number or address you already had, never one the request gave you. Security teams call this out-of-band verification, which simply means checking on a different channel from the one the request came on.
Indian banks use a version of this with lockers: opening one needs two keys held by two different people, so one person's mistake cannot open the box. Tulsi Health applies the same thinking to money. Any new supplier account, or any payment over ₹25,000, needs Sameer to enter it and Vikram to approve it on the banking portal, so a single persuaded person cannot move the money alone.
The rule works because the attacker controls the first channel but not the second. A genuine request survives the two-minute delay.
The last ingredient is security awareness: people knowing the common tricks, knowing the rules, and feeling safe to use them. Awareness works best as short, frequent practice rather than a yearly lecture, such as a five-minute example at the Monday store meeting or a harmless practice phishing email followed by a friendly explanation. Equally important is the message that reporting a mistake is welcome. A pharmacist who says "I think I clicked something bad" within five minutes gives Neha a chance to contain it; one who stays quiet out of embarrassment gives the attacker the whole night.
Put the call-back rule in order for the WhatsApp payment request from "Vikram sir". Arrange the steps the way Sameer should follow them when a message like that arrives at 5 pm on a Friday.