Home / Commons / Talks / Slides

Talks kit · Slides

Security basics: the slides.

The field guide as a 19-slide deck, with speaker notes. Present it from this page, or print it to PDF with one slide per page.

While presenting: → or Space next, ← back, Home and End, S speaker notes, F full screen, Esc to stop.

Moraph for Good · Commons

Security basics for small organizations.

The measures that matter most, in the order they matter, and what to do in the first hour of an incident.

A free field guide from Moraph for Good · moraph.org/commons/security-basics · Last reviewed October 2026

Moraph for Good · Security basics1 / 19

Speaker notes

Introduce yourself and your role at Moraph. Say that Moraph for Good is Moraph’s social impact program, that the guide is free to print and adapt, and that this session is not a sales pitch. Say early that it is general information, not advice about anyone’s own systems.

Why this matters

The same stakes, a fraction of the staff.

Finance

A community credit union answers to the same anti-money-laundering rules as a national bank, without a compliance department to answer them.

Health

A free clinic owes its patients the same privacy as a hospital system, and is a softer target for the same attackers.

Government

Ransomware does not check the size of a town before encrypting its records.

Moraph for Good · Security basics2 / 19

Speaker notes

Set the scene without statistics you cannot source. The point: small organizations hold the same sensitive records as large ones, with far fewer people. Ask what kinds of records the people in the room hold.

The field guide

Eleven measures, in the order they matter.

  1. 01Turn on multi-factor authentication for email first
  2. 02Keep administrator accounts separate
  3. 03Keep a backup ransomware can’t reach
  4. 04Know what you have
  5. 05Let updates install themselves
  6. 06Remove access the day someone leaves
  7. 07Make payment changes a two-person, two-channel rule
  8. 08Use the protections you already have
  9. 09Ask your vendors the hard questions
  10. 10Read your cyber insurance before you need it
  11. 11Write down the first hour

Moraph for Good · Security basics3 / 19

Speaker notes

These are in roughly the order to do them. There is not time to give every one the same weight: spend most of it on the first four and on payments.

Measure 1 of 11

Turn on multi-factor authentication for email first

Email is the master key: almost every other account’s password can be reset through it.

  • Switch on multi-factor authentication (a second step after the password) for every email account, starting with whoever handles money and whoever administers your systems.
  • Prefer an authenticator app or a physical security key over text messages, which can be intercepted or redirected.
  • Then do the same for banking, payroll, donor or client databases, and your domain registrar.

Moraph for Good · Security basics4 / 19

Speaker notes

Ask who has a second step when they sign in to work email. Explain why email comes first: password resets for almost everything else go through it. Text-message codes are better than nothing; authenticator apps and security keys are harder to phish or redirect. A practical first step: switch it on this week for whoever handles money and whoever administers systems.

Measure 2 of 11

Keep administrator accounts separate

An attacker who tricks an administrator gets everything the administrator can touch.

  • People who manage systems should have an everyday account for email and browsing, and a separate account used only for administration.
  • Keep the number of administrators as small as you can, and write down who they are.

Moraph for Good · Security basics5 / 19

Speaker notes

Many small organizations give everyone administrator rights because it is easier. Explain the risk in one sentence: whoever tricks an administrator gets everything the administrator can reach. Suggest a short written list of who the administrators are.

Measure 3 of 11

Keep a backup ransomware can’t reach

Ransomware looks for backups first. A backup on a drive that is always connected is not a backup.

  • Keep at least one copy of important data offline, or in a service that prevents deletion for a set period.
  • Restore something from it regularly. A backup you have never restored is a hope, not a plan.
  • Make sure the backup includes the things you would actually need to reopen: files, finance records, and the configuration of key systems.

Moraph for Good · Security basics6 / 19

Speaker notes

Ask when people last restored something from a backup. Explain offline or deletion-protected copies, and why a drive that is always plugged in is not enough. The backup log in the Commons templates is a simple place to start.

Measure 4 of 11

Know what you have

You cannot protect, update or recover what you have forgotten exists.

  • Keep a one-page list of devices, online accounts and services, who has administrator access to each, and where sensitive records live.
  • Include the services volunteers or former staff signed up for on the organization’s behalf.

Moraph for Good · Security basics7 / 19

Speaker notes

Suggest a single page: devices, online accounts and services, who administers each, and where sensitive records live. Mention the accounts volunteers or former staff created. The inventory template in Commons is a starting point.

Measure 5 of 11

Let updates install themselves

Most attacks on small organizations use weaknesses that were fixed months or years earlier.

  • Turn on automatic updates for operating systems, browsers and office software.
  • Replace devices and software that no longer receive security updates, even if they still work.

Moraph for Good · Security basics8 / 19

Speaker notes

Keep this short: automatic updates on, and replace devices and software that no longer get security updates. If asked how to tell, suggest the vendor’s support or end-of-life page.

Measure 6 of 11

Remove access the day someone leaves

Old accounts are a door nobody is watching.

  • When staff or volunteers leave, close or hand over their accounts the same day, and change any shared passwords they knew.
  • Review who has access to what a few times a year. It is always more people than you expect.

Moraph for Good · Security basics9 / 19

Speaker notes

Ask how long it takes to close an account when someone leaves. The same day is the goal, and shared passwords they knew should change. The joiners and leavers checklist in Commons helps.

Measure 7 of 11

Make payment changes a two-person, two-channel rule

Fake “we’ve changed our bank details” emails cost organizations more than most ransomware.

  • Never change a supplier’s or employee’s bank details on the strength of an email alone.
  • Call back on a number you already had, not one in the message, and have a second person approve the change.

Moraph for Good · Security basics10 / 19

Speaker notes

Often the costliest risk in the room. Explain the callback rule: never change bank details on the strength of an email; call back on a number you already had, and have a second person approve. Point to the payment fraud toolkit and its printable poster.

Measure 8 of 11

Use the protections you already have

Many productivity and email platforms include security features that are switched off by default.

  • Check that the platform’s recommended security settings are on, including protection against malicious attachments and links, and alerts for suspicious sign-ins.
  • Many technology vendors run nonprofit programs. Ask yours what is included before you buy anything extra.

Moraph for Good · Security basics11 / 19

Speaker notes

Encourage people to check the security settings of the platforms they already pay for before buying anything new. Many vendors run nonprofit programs; the Commons directory lists them. Don’t recommend specific products.

Measure 9 of 11

Ask your vendors the hard questions

Your data is only as safe as the weakest company holding it.

  • Before signing, ask where your data is stored, who at the vendor can see it, how quickly they will tell you about a breach, and how you get your data back if you leave.
  • Get the answers in writing. A reputable vendor will not mind.

Moraph for Good · Security basics12 / 19

Speaker notes

Four questions for any vendor: where is our data, who at the vendor can see it, how quickly will you tell us about a breach, and how do we get our data back if we leave. The Before you sign guide has the full list and a comparison table.

Measure 10 of 11

Read your cyber insurance before you need it

Some policies require you to call the insurer before you hire anyone to help.

  • If you have cyber insurance, find out now what it covers, what you must do first, and the number to call. Put that number in your first-hour plan.

Moraph for Good · Security basics13 / 19

Speaker notes

Anyone with cyber insurance should find the claims number and any “call us first” condition now, and put it in their first-hour plan. Don’t give opinions on particular policies or insurers.

Measure 11 of 11

Write down the first hour

In an incident, the systems that hold your plan may be the ones that are down.

  • Write a one-page plan: who decides, who to call, what to disconnect, where the backups are, and how you will reach staff without email.
  • Print it. Keep a copy somewhere other than your office network.

Moraph for Good · Security basics14 / 19

Speaker notes

Lead into the exercise: a one-page plan, printed, kept off the network. The incident plan builder makes one in a few minutes, and nothing typed into it leaves the browser.

If it happens

The first hour of an incident.

  1. Disconnect, don’t switch off. Unplug affected devices from the network or turn off Wi-Fi. Leave them powered on: switching off can destroy evidence of what happened.
  2. Move to a safe channel. Assume email and chat may be compromised. Use phone calls or personal devices to coordinate.
  3. Call your insurer, then your national agency. If you have cyber insurance, call them first: many policies require it. Then report to your national cyber security agency.
  4. Write everything down. Keep a timeline: what you noticed, when, and what you did. Responders, insurers and regulators will all ask for it.
  5. Don’t pay, delete or negotiate alone. Paying a ransom does not guarantee recovery, and may be illegal in some cases. Take advice first.
  6. Think about who you must tell. If personal, health or financial records may be involved, you may have legal duties to notify the people affected or a regulator, often within a set time. Get advice early.

Moraph for Good · Security basics15 / 19

Speaker notes

Walk through the steps, and stress the first: disconnect, but don’t switch off. If someone in the room is dealing with an incident now, stop and help them contact their national agency first.

Who to call

National agencies that take reports.

  • United StatesCISAwww.cisa.gov/report
  • CanadaCanadian Centre for Cyber Securitywww.cyber.gc.ca
  • United KingdomNational Cyber Security Centrewww.ncsc.gov.uk
  • AustraliaAustralian Cyber Security Centrewww.cyber.gov.au
  • New ZealandNational Cyber Security Centrewww.ncsc.govt.nz
  • IndiaCERT-Inwww.cert-in.org.in

Elsewhere: your national computer emergency response team (CERT) or the police. Call your insurer first if you have cyber insurance.

Moraph for Good · Security basics16 / 19

Speaker notes

Read out the agency for the country you are in. Remind people that Moraph for Good’s Shield program is not an emergency service.

Take it home

Free tools, no account needed.

  • Incident plan builderA one-page plan for the first hour, printed from your browser.moraph.org/commons/incident-plan
  • Security self-assessmentYes-or-no questions that become a to-do list.moraph.org/commons/self-assessment
  • TemplatesAcceptable use, joiners and leavers, backup log, contact sheet, inventory.moraph.org/commons/templates
  • Payment fraud toolkitThe callback rule, a poster and a staff briefing.moraph.org/commons/payment-fraud

Moraph for Good · Security basics17 / 19

Speaker notes

Show where each tool lives. Everything is free, needs no account, and the tools run in the browser: nothing typed into them is sent to Moraph.

When a guide isn’t enough

Moraph for Good can help.

Shield

A security review in plain words from Moraph’s security operations people, and help making the fixes.

Access

Moraph software, donated or discounted, run to the same standard as for paying clients.

Pro Bono

Moraph people on your hardest project, with a written scope, a named lead and an end date.

One short form for every program: moraph.org/apply. A person reads every application.

Moraph for Good · Security basics18 / 19

Speaker notes

Explain the programs briefly. Don’t promise support: the team decides against the published criteria. Don’t collect applications or contact details yourself; point people to moraph.org/apply.

Thank you

Questions?

Moraph for Good · Security basics19 / 19

Speaker notes

If a question is about one organization’s own systems, offer general principles and suggest applying for Shield rather than diagnosing in public. Afterwards, tell the Moraph for Good team at hello@moraph.org which questions came up, so Commons can answer them.