If your nonprofit keeps getting phishing emails, three changes do most of the work: staff report the messages instead of answering them, every account requires multifactor authentication, and your domain publishes SPF, DKIM and DMARC so criminals cannot send mail in your name. The emails will not stop. The aim is that a click no longer turns into a stolen account or a wired payment.
This guide covers what to do with the email in front of you, what to do if someone already clicked, which controls matter most, the free help available to nonprofits, and when to bring in a managed IT provider in Washington, DC. Sources were checked on November 18, 2026.
What should staff do with a phishing email?
Do not click links, open attachments or reply. Report the message with the phishing report option in Outlook or Gmail, then delete it. The Federal Trade Commission also asks people to forward phishing emails to reportphishing@apwg.org, forward phishing texts to SPAM (7726), and report the attempt at ReportFraud.ftc.gov.
Then tell whoever handles IT. One reported message often means the same message reached several colleagues, and a quick warning to all staff is worth more than any filter rule.
What if someone already clicked or entered a password?
Treat the account as compromised and act the same day. Changing the password is not enough on its own, because attackers leave ways back in.
- In Microsoft 365, Microsoft's guidance is to disable the account or reset its password, revoke active sign-in sessions, remove any sign-in methods and app permissions the user does not recognize, and delete suspicious forwarding and inbox rules. Do not send the new password by email, since the attacker may still be reading the mailbox.
- In Google Workspace, Google's guidance is to suspend the user, which resets sign-in cookies and app tokens, then reset the password and check for forwarding rules before restoring access.
- If the click may have installed software, the FTC advises updating the computer's security software and running a scan.
- If money was sent, call the bank immediately and ask for a recall, then file a complaint at ic3.gov. The FBI's Internet Crime Complaint Center says to contact the bank as soon as the fraud is recognized.
The fuller sequence, including who has to be notified under DC law, is in what to do when a nonprofit is hacked.
Why do nonprofits get so much phishing?
Nonprofits publish staff names, titles and email addresses, move money on request, and often run without anyone assigned to security. That is an easy profile to target. Business email compromise aimed at finance staff, ransomware on shared files, and account takeover through a reused password are the three incidents ETTE is called into most often.
Which controls reduce phishing the most?
Five controls, in the order we would put them in place:
- Multifactor authentication on every account. Microsoft's documentation says MFA can block more than 99.2 percent of identity-based attacks. In Microsoft 365, security defaults turn it on at no extra cost on any plan. Conditional Access, which lets you set the rules yourself, needs Microsoft Entra ID P1, and Microsoft 365 Business Premium includes it.
- Phishing-resistant sign-in for administrators and finance staff. Microsoft recommends passkeys, FIDO2 security keys or Windows Hello for Business, because codes from a text message or an app can still be phished.
- SPF, DKIM and DMARC on your domain, so a criminal cannot send email that appears to come from your organization. ETTE's free Email Security Scorecard checks all three for any domain.
- A callback rule for payments. Any request to change bank details or send a payment is confirmed by phone on a number you already had. The FBI recommends verifying such requests through a second channel.
- Short, regular staff training. People who have seen a realistic example report the next one faster.
What free help is available to nonprofits?
CISA, the federal cybersecurity agency, keeps a list of no-cost resources for nonprofits and civil society groups. The ones most relevant to phishing:
- Microsoft AccountGuard, which adds protections and nation-state threat notifications to Microsoft 365 accounts at no cost for eligible nonprofits.
- Google's Advanced Protection Program, which hardens Gmail accounts against phishing.
- The Global Cyber Alliance Cybersecurity Toolkit for Mission-Based Organizations, which walks an organization through choosing free tools.
- The Access Now Digital Security Helpline, which gives no-cost emergency response and advice to civil society groups.
- NGO-ISAC, an information sharing center for nonprofits.
These are worth using. They do not configure your tenant, enforce MFA for the person who keeps putting it off, or watch the alerts at night. Someone still has to own that.
Who can help a nonprofit in Washington, DC with phishing?
If nobody at your organization owns email security, a managed IT provider is the usual answer. Ask any provider you consider these questions:
- Do you enforce MFA for every account, and can you show the report that proves it?
- Who watches for a compromised account outside business hours?
- How quickly do you respond when a staff member reports a suspicious sign-in?
- Will you take our domain to an enforced DMARC policy, and how long does that take?
- What do we pay per user, and what is not included?
ETTE is a managed IT provider in Washington, DC that has served nonprofits and associations since 2002, with CISSP and CISA certified engineers. For managed clients we enforce MFA and Conditional Access, run Microsoft Defender for Office 365 email protection with SPF, DKIM and DMARC, and provide around-the-clock managed detection. Security incidents carry a 20-minute urgent response objective. Managed plans start at $125 per user per month remote-only and $150 fully managed, with nonprofit pricing available.
Start with the free Email Security Scorecard, read how we handle email security and nonprofit data security, or talk with an advisor at 202-345-1965. For background on the controls, see email security for nonprofits.
Vendor and agency guidance in this article was checked against Microsoft, Google, FTC, FBI and CISA pages on November 18, 2026. Confirm current steps on those pages before acting on them.