Mission 28
AI Security, Deepfakes and Emerging Cyber Threats
AI tools can now copy a familiar voice, face or writing style in minutes. A HUMANWALL Champion treats any convincing message as a request, not as proof of identity, and helps the business use AI safely without leaking confidential data.
In this mission you will
- Explain why a familiar voice, video or writing style is no longer proof of who is asking.
- Apply independent verification and agreed code words to urgent requests involving money, access or confidential data.
- Identify which business information must never be pasted into public AI tools.
- Draft a short, practical AI-use policy that a small team can actually follow.
What has changed
For years, the advice was simple: if you are unsure, call the person or listen to their voice. AI has weakened that check. Freely available tools can now produce a voice note that sounds like your managing director, a short video call with a familiar face, or an email written exactly in your supplier’s style. Criminals need only a few public clips, such as a speech on social media or a conference video. The trick itself is old: urgency, authority and secrecy. What is new is how real it looks and sounds.
Warning signs in AI-assisted fraud
- Unusual urgency: “Do it in the next 20 minutes, I’m about to board a flight.”
- Secrecy: “Don’t tell accounts yet, this is a confidential deal.”
- A new channel: a leader who never sends voice notes suddenly sends one from an unknown number.
- Bypassing process: a request to skip the normal approver, purchase order or call-back.
- Short or poor-quality calls: the video freezes, the person avoids questions or ends the call quickly.
- Pressure on emotions: flattery, fear of letting the boss down, or a family emergency story.
The independent verification habit
- 1Pause. A genuine leader will accept a five-minute delay to protect the business.
- 2Do not reply on the same channel. End the call or leave the chat where the request arrived.
- 3Contact the person through a channel you already trust: the number saved in your records, the office landline or an in-person check.
- 4Ask for the agreed code word, or a question only the real person would know and that is not on social media.
- 5Follow the normal approval process anyway. Verification confirms identity; it does not replace the second approver.
- 6Report the attempt to your security contact, even if you were not fooled. Others may be targeted next.
Using AI tools safely at work
AI can save real time for drafting emails, summarising notes or translating product descriptions. The risk is what people paste in. Public AI tools may store prompts, and depending on settings, the provider may use them to improve its models. Treat anything you paste into a public tool as information that has left the business. Never paste customer lists, personal data of employees or customers, passwords, API keys, source code, pricing strategy, contracts, financial statements or anything covered by a confidentiality agreement. Also remember that AI output can be wrong, made up or out of date. A person must check it before it is sent to a customer, used in a contract or relied on for a decision.
A one-page AI-use policy for a small business
- Approved tools: list which AI tools staff may use for work, and which account type (personal or business).
- Never paste: personal data, customer data, credentials, financial details, code or confidential documents.
- Human review: a named person checks AI output before it goes outside the business or informs a decision.
- Labelling: be honest with customers when content is substantially AI-generated, where that matters.
- Reporting: tell the security contact if confidential data was pasted by mistake, without fear of blame.
- Review: look at the policy every six months, as tools and settings change quickly.
Practical business example
Kaveri Spices and the managing director’s voice note
Kaveri Spices, a fictional 30-person exporter in Kochi, had a habit: the managing director, Thomas, often sent WhatsApp voice notes to the team. One Friday evening, the accounts executive Divya received a voice note from an unknown number. It sounded exactly like Thomas. He said his phone had died at an airport, a buyer needed an urgent advance to a new account, and she should not disturb the finance manager. Divya felt the pressure. But three months earlier, after a Cyber Quest session, the team had agreed two rules: no payment on a voice note alone, and urgent requests need the code word agreed in person. Divya called Thomas’s saved number. He answered from home, puzzled. There was no buyer and no new account. Divya reported it, and the owner thanked her in the Monday team meeting.
The lesson: The voice was convincing, but it did not matter. A simple rule, a saved number and a code word made the fake request fail without anyone needing to spot the deepfake.
Key takeaways
- A familiar voice, face or writing style is a request, not proof of identity.
- For money, access or confidential data, verify through a known channel and follow the normal approval process, even under pressure.
- Agree code words in person for urgent requests from leaders, and report every attempt, even failed ones.
- Never paste personal data, customer data, credentials, code or confidential documents into public AI tools.
- A short AI-use policy with approved tools, a “never paste” list and human review is enough to start.
Scenario lab · +25 XP
The CEO on the video call
You are the finance lead at Sagar Logistics, a fictional 60-person freight company in Visakhapatnam. At 5:40 pm, you are pulled into a short video call. The face and voice look like your CEO, Arvind. He says a confidential acquisition needs a transfer to a new account before the bank closes, and that he will explain on Monday. The video is slightly blurry and he cuts the call after two minutes. A follow-up message on a messaging app repeats the bank details.
Fictional scenario. Never enter real passwords, OTPs or customer details anywhere in this course.
Decision 1 of 3
What do you do first?
Knowledge check · +20 XP on mastery
Check your understanding
Practical action · +40 XP (self-reported)
Write your three-step urgent-request rule and AI-use basics
Create a short rule for urgent leader requests and a one-page AI-use note for your team. Describe the process only. Do not write down the code word itself, passwords or any account details.
- 1.Write a three-step rule for urgent requests involving payments, access or confidential data: pause, verify through a saved number, then follow normal approval.
- 2.List who needs a code word (for example leaders, accounts and IT) and plan to agree it in person, not in writing.
- 3.List the AI tools staff may use for work and the account type they should use.
- 4.Write a “never paste” list covering personal data, customer data, credentials, financial details, code and confidential documents.
- 5.Name who reviews AI output before it goes to customers or informs decisions.
- 6.Share both notes at your next team meeting and set a date to review them in six months.
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