Understand AI
What it can do, where it fails and how it enables deception.
AI & CYBER THREATS / EXECUTIVE PROTECTION
The voice
is familiar.
Verify the order.
Recognise impersonation. Check before acting.
Two-day training for personal security and executive protection teams.
2 days · 09:00–17:45 each day · No coding required
DEMONSTRATIONS. DECISIONS. TEAM PRACTICE.
YOUR INSTRUCTORMishal AbdullahEngineer. 3× founder. Always a builder.↗
TWO DAYSpractise.PAUSE · VERIFY · REPORT
INSTRUCTOR AT A PREVIOUS TECHNOLOGY WORKSHOP.LEARN / REHEARSE
Built in the real world.
Brought into the room.
3×Founder & builder
30+C-level leaders coached in tech
17Accepted public contributions
FOUNDING ENGINEER ATKernel42.ai ↗01 / EXPERIENCE MEETS A NEW THREAT
The discipline stays.
The deception
has changed.
AI can copy a voice, fabricate a video or impersonate a trusted contact.
Practise independent checks and reporting under pressure. The course supports your organisation’s procedures; it does not replace them.
View the programme ↘Course content
Recognise the threat.
Know the next step.
Short demonstrations. Team decisions. Practical checks.
Recognise impersonation
Compare cloned voices, fake video and convincing messages.
Verify instructions
Known-number callbacks, agreed challenges and two-person approvals.
Reduce exposure
Check your public footprint and make a practical privacy improvement.
Use AI safely
Approved tools, breach-check limits and protecting sensitive details.
Practise the response
Timed team scenarios, incident reporting and a final verification test.
Less than 20 minutes of talk before an activity or demonstration.
View the exercises ↗Two-day programme
Understand the threat.
Practise the response.
09:00–17:45 each day, including breaks.
DAY ONE
Understanding the threat.
- 15 MIN
The stakes
- 30 MIN
Pause. Verify. Report.
- 35 MIN
AI in plain language
- Break · 15 minutes
- 90 MIN
AI-powered reconnaissance & OSINT
- Lunch · 60 minutes
- 75 MIN
Voice cloning
- 75 MIN
Deepfakes
- Break · 15 minutes
- 90 MIN
The full AI threat map
- 15 MIN
Day 1 quiz & wrap-up
DAY TWO
Defence, protocols & practice.
- 15 MIN
The callback
- 90 MIN
AI for defence
- Break · 15 minutes
- 30 MIN
Dark web exposure: access, checks & response
- 45 MIN
Footprint reduction & removal requests
- Lunch · 60 minutes
- 90 MIN
Verification protocols deep-dive
- Break · 15 minutes
- 120 MIN
Tabletop exercises
- 45 MIN
Reporting, final test & close
Pause. Verify. Report.
Pause
Stop when urgency or secrecy pushes you to bypass a rule.
Verify
Call a known number—not one supplied in the request. Apply the agreed checks.
Report
Tell the supervisor. Record what happened. Escalate through the agreed channels.
Two-person approval for sensitive route, schedule and access changes, aligned with your organisation’s procedures.
Four situations
to rehearse.
Two hours of team practice. Fictional identities and schedules.
An urgent route change
Verify an unscheduled pickup request.
A video call from “the office”
Independently check a request to admit a stranger.
A vendor at the door
Check credentials and obtain approval.
A schedule becomes public
Report the leak and review affected plans.
WHAT PARTICIPANTS TAKE BACK TO DUTY
Clear checks.
A shared response.
Practical references and rehearsed habits.
Not just a notebook full of technical terms.
- ↗A one-page verification card
The team’s callback, challenge and approval routine. - ↗A practical take-home checklist
A reference for unusual instructions and incidents. - ↗At least one privacy improvement
A change made during the personal footprint audit. - ↗A shared reporting routine
Who to tell, what to document and when to escalate.
OBSERVABLE LEARNING. CONTROLLED PRACTICE.
Practise seriously.
Keep the exercise controlled.
How learning is checked
- End-of-day quizzes
- Observed team decisions
- A final verification test
- Participant feedback
How practice stays controlled
- Synthetic or consented samples
- Fictional identities and schedules
- Approved tools and offline backups
- No probing without authorisation
Do not bring live principal details, routes, duty rosters, access codes or confidential incident records into demonstrations or public AI tools. Any training setup must follow the organisation’s approvals.
Teaching through practice↗
Your instructor
Mishal Abdullah
Software engineer · Three-time founder
Founding Engineer at Kernel42.ai. Previously at Docket AI, working on AI integrations and call-data analysis.
Founder of Volls, Kryate and OpenReview. Coached 30+ C-level leaders in tech.
I explain AI through demonstrations, connecting its capabilities and limits to your team’s security procedures.
More about my work ↗Before the training
Is technical experience needed?+
No coding or AI experience needed. Learn through demonstrations and team practice.
Will we use sensitive information?+
No. Fictional schedules and consented or synthetic samples only. No live routes, principal details or unauthorised probing.
What happens in the dark web session?+
A controlled 30-minute demonstration of a legitimate .onion site, breach checks and reporting. No access to stolen data. No result does not prove safety; removal may leave copies elsewhere.
What arrangements are needed?+
Agree dates, venue, fees, equipment, approved tools and offline backups with the training coordinator. Device use follows organisational policy.
How is learning assessed?+
Quizzes, observed team decisions, a final verification test and participant feedback.
FOR SECURITY LEADS & TRAINING COORDINATORS
Prepare the team.
Practise the checks.
Discuss group size, dates and training arrangements.
Share only non-sensitive requirements on LinkedIn.
Operational details belong in your approved channels.