Mission 01
The Human Wall — The First Line of Cybersecurity
Most cyber attacks on small businesses start with a person being asked to click, approve, pay or share. This mission shows how people, simple processes and basic tools work together to stop them.
In this mission you will
- Explain why people are an essential security control, not the weak link to be blamed.
- Describe how people, process and technology support one another in a small business.
- Respond safely to an unexpected login approval (MFA) prompt.
- Identify your organisation's approved channel for reporting something suspicious.
Why start with people?
No firewall can protect a business if its human wall is weak. Firewalls, antivirus and backups matter. But many attacks do not break in through technology at all. They ask someone to open a file, approve a login, change a bank account number or share a one-time password. When that person pauses and checks, the attack often stops right there. That pause is the human wall.
People are a control, not the problem
It is common to hear that "users are the weakest link". That idea does not help anyone. It makes people afraid to speak up, and attackers count on silence. A better view is this: people are a security control, just like a lock or a password. A control works well when it is supported. People make good security decisions when they have tools that are easy to use, clear steps to follow and a manager who thanks them for reporting, even when the report turns out to be a false alarm.
The three parts of a strong defence
- People: staff who know what normal looks like, notice when something is unusual, and feel safe to pause and ask.
- Process: simple agreed rules, such as "any change to supplier bank details is confirmed by phone on a known number" or "new laptops are set up by one named person".
- Technology: tools that reduce the chance of mistakes, such as multi-factor authentication (MFA), automatic updates, spam filtering and backups.
- Each part covers gaps in the others. Technology cannot judge a strange request. People get tired and busy. Process gives everyone a clear default when they are unsure.
Unexpected login approvals
Many email, accounting and banking services now send a prompt to your phone asking you to approve a login. This is multi-factor authentication, and it is a strong protection. But it only works if you approve prompts that you started yourself. If a prompt arrives when you are not logging in, someone else may already know your password and is trying to get past the second step. Some attackers send prompt after prompt, hoping you will tap "Approve" just to make them stop.
What to do with a prompt you did not expect
- 1Do not approve it. Tap "Deny" or "This wasn't me" if that option exists.
- 2Do not share any code shown on the screen with anyone who calls or messages you about it.
- 3Report it straight away through your approved channel, such as your manager, IT contact or the agreed WhatsApp group for security issues.
- 4Change the password for that account from a device you trust, using the official app or website, or ask your IT contact to help.
- 5Note the time and the service name. That helps whoever looks into it.
Reporting is a strength
Mistakes will happen. Someone will click a bad link one day. What matters most is how quickly it is reported. A report made in five minutes gives the business time to reset a password, call the bank or warn others. A report hidden for a week out of embarrassment can turn a small problem into a large one. Owners and managers build the human wall by thanking people for reporting and by never shaming them for an honest mistake.
Practical business example
The prompt that came at lunchtime
Meera runs a 12-person textile export firm in Surat. Her accounts executive, Rakesh, was eating lunch when his phone showed a login approval request for the company email. He was not at his desk and had not tried to log in. A minute later, a second request appeared, and then a third. Rakesh felt tempted to tap "Approve" to make them stop. Instead, he remembered what Meera had said in a short team meeting the month before: "If you get a prompt you did not start, deny it and tell me. You will never be in trouble for that." He denied the prompts and sent Meera a message in the team's security group. Meera called their IT support person, who reset Rakesh's password and signed out all other sessions. They later found that Rakesh had used the same password on a shopping site that had leaked customer logins. Nothing was lost. Meera thanked Rakesh in the next team meeting.
The lesson: The MFA tool gave a warning, but it was Rakesh's pause and Meera's clear, blame-free rule that turned that warning into a safe outcome. People, process and technology worked together.
Key takeaways
- People are an essential security control. Support them with clear rules and easy tools rather than blaming them.
- Urgency is a reason to pause and check, not to rush.
- Never approve a login prompt you did not start, and never share OTPs or on-screen codes with anyone.
- Every person should know the approved reporting channel without having to search for it.
- Thank people for reporting, even when it turns out to be nothing. That is how the human wall grows stronger.
Scenario lab · +25 XP
Three prompts, one decision
You work at a small pharmaceutical distributor in Indore. It is 8:40 pm and you are at home watching television. Your phone shows a request: "Approve sign-in to your work email?" You are not logging in to anything.
Fictional scenario. Never enter real passwords, OTPs or customer details anywhere in this course.
Decision 1 of 3
What do you do with the prompt?
Knowledge check · +20 XP on mastery
Check your understanding
Practical action · +40 XP (self-reported)
Build your first brick in the human wall
Take five minutes to set up the basics that make good decisions easier. Do not write down any passwords or codes while doing this.
- 1.Find out your organisation's approved channel for reporting something suspicious. If there is none, ask your manager or owner to name one person and one way to reach them.
- 2.Save that contact in your phone with a clear name, such as "Security – report here".
- 3.Write down one safe habit you will follow, for example: "I will never approve a login prompt I did not start."
- 4.Check whether your work email has MFA turned on. If you are not sure, ask your IT contact.
- 5.If you are an owner or manager, tell your team this week that reporting a mistake will never get them into trouble.
Do this in your own records. Don’t enter passwords, OTPs, customer data or incident details here.
Mission status: Not started
A mission is complete when you have read the lesson, answered the knowledge check and acknowledged the practical action. Mastery means scoring at least 3 of 4 on the knowledge check.
View my progress