Your staff is your best defense against cybersecurity threats. And your biggest vulnerability. Most breaches start with a phishing email: someone clicks a malicious link and suddenly hackers have access to your systems.

You can't prevent this with technology alone. You need staff training. This lecture gives you a one-hour training program you can run yourself.

Why This Training Works

Most cybersecurity training is boring, theoretical, and forgotten in weeks. This approach is: practical (real scenarios), short (one hour), and reinforced (quarterly reminders).

The 1-Hour Training Program

Section 1: The Threat (10 minutes)

Show real examples:

  • "A nonprofit like ours was hit with ransomware. Files were encrypted. They couldn't access anything for three days. Cost $50K to recover." (Real story)
  • "A staff member got a phishing email that looked like it was from our CEO, asking for wire transfer. They sent $10K before realizing it was fake." (Real story)
  • "A volunteer's login was hacked. Someone accessed our donor database using their credentials." (Real story)

Make it real. Make it relevant to your organization. This makes people care.

Section 2: How Attacks Happen (15 minutes)

Cover three attack types:

Phishing: Emails that look like they're from someone you trust but are actually from hackers. They're asking you to click a link or download an attachment.

Example: "You receive an email that looks like it's from our Salesforce account, saying your password expired and asking you to reset it. You click the link. It looks like Salesforce login. You enter your credentials. You're now compromised."

What to do: hover over sender email to see true email address. Check for spelling errors. If something seems off, call the company directly (use a phone number from their website, not from email). Don't click links in emails—go directly to the website.

Password reuse: You use the same password across multiple sites. A website gets hacked. Hackers try your password on other sites (your email, banking, CRM). It works.

What to do: use a unique password for every account. Use a password manager. If you're having trouble remembering passwords, that's exactly why password managers exist.

Unpatched systems: Your computer has security holes. Microsoft releases a patch to fix it. You ignore it. Hackers exploit the hole.

What to do: turn on automatic updates. When you see "update and restart," don't delay it. Updates are security. Do it immediately or schedule it for tonight.

Section 3: What You Should Do (20 minutes)

Recognize phishing: Show screenshots of real phishing emails. Practice identifying them. Ask: is the sender email legitimate? Are there spelling errors? Does it create urgency ("act now!")? Does it ask you to do something unusual (provide password, download attachment, click link)?

Create strong passwords: Walk through password manager setup (Lastpass or 1Password). Show how to generate a strong password, store it, and use it. Everyone gets set up during training if they don't have one.

Enable multi-factor authentication: Show how to turn it on for email and critical accounts. Everyone sets it up during training. Takes 10 minutes per person, prevents 99% of breaches.

Report suspicious activity: What do you do if you click a phishing link? You panic and don't tell anyone. Don't. Tell IT immediately. We're not mad, we appreciate you reporting so we can protect the organization. Establish a process: "If you think you've been compromised, email IT or call this number."

Section 4: What You Shouldn't Do (10 minutes)

  • Don't share passwords. Ever. Not even with colleagues "temporarily"
  • Don't use public wifi for work without VPN
  • Don't plug unknown USB drives into your work computer
  • Don't share donor data via email or text (use secure transfer)
  • Don't leave your computer unlocked when you step away
  • Don't write passwords on post-it notes
  • Don't ignore security warnings from your computer

Section 5: Q&A and Commitment (5 minutes)

Open questions. Then: "We need everyone's commitment. Cybersecurity isn't IT's job. It's everyone's job. Agree?" Everyone agrees. Now they're bought in.

Phishing Simulations (Quarterly)

Send fake phishing emails to staff. Track who clicks malicious links. Don't name and shame. But send those people extra training.

Services like PhishLabs or KnowBe4 do this automatically ($10-30/person/year). Or you can manually send fake phishing and track clicks.

Results: after first simulation, 30-40% click the malicious link. After three simulations, it drops to 10-15%. After annual training, stays low.

Annual Refresher

Do the full training annually (new staff need it). Do quarterly 15-minute refreshers on a specific topic (passwords, phishing, incident response).

Make It Stick

Learning requires reinforcement. After training:

  • Send an email recap of key points
  • Post a "security tip of the month" newsletter
  • When someone gets phished, use it as teaching moment (not punishment)
  • Celebrate: "We went 6 months without a successful phishing attack!" Make security a team win

Cost

Doing it yourself (what I've described): zero. Your time (one hour preparation + one hour delivery).

Using a platform (KnowBe4, PhishLabs): $10-30/person/year for training + phishing simulations.

For most nonprofits, DIY is fine. You know your organization and can tailor examples.

Key Takeaway

Your staff is your strongest defense if trained. Spend one hour teaching them the real risks, how to recognize attacks, and what to do. Then reinforce quarterly. Most breaches become impossible once staff knows what they're looking for.

Frequently Asked Questions

What if someone falls for a phishing simulation?

Send them a follow-up email with specific training: "You clicked a malicious link. Here's why this was dangerous. Here's how to recognize phishing in the future." Don't shame. Educate. If the same person falls for it repeatedly, that's a conversation with their manager (maybe they're not ready for systems with sensitive data).

How do we handle staff who ignore security advice?

Make it a policy. "All staff must use password manager and enable MFA for work accounts." Then enforce it. Anyone without it doesn't get access to critical systems. Make security a requirement, not optional.

Should we train volunteers and board members?

Yes, if they access your systems. A volunteer with access to donor data should get the same training as staff. Board members should at minimum understand the organization's security posture (you cover that in board briefings).