Practical Guide
Cybersecurity for nonprofits.
Nonprofits run on small teams, limited budgets, and donor trust. This guide covers the threats worth taking seriously, a prioritized checklist you can work through, and low-cost ways to get started.
The risks
Threats worth taking seriously.
Most incidents at nonprofits start with ordinary, preventable gaps rather than sophisticated attacks.
01
Phishing and business email compromise
Fake invoices, spoofed executives, and credential-harvesting links aimed at staff who handle money or donor data.
02
Ransomware
Encrypted files and stolen data can stop programs for days. Tested backups and MFA are the most effective defenses.
03
Donor and client data exposure
Donor records, payment details, and client case files are valuable to attackers and costly to lose in trust.
04
Vendor and cloud misconfiguration
Shared drives open to anyone with the link, forgotten test sites, and default settings in donation or CRM tools.
05
Volunteer and former-staff access
Accounts that outlive the role, shared passwords, and personal devices with access to organizational systems.
06
Wire and payment fraud
Last-minute changes to bank details for grants, payroll, or vendors. Verify any payment change by phone using a known number.
Where to begin
A prioritized checklist.
- 011. Inventory what you hold
- List the systems, accounts, and data you hold — donors, clients, staff, finance — and where each lives.
- 022. MFA everywhere
- Turn on multi-factor authentication for email, finance, donor CRM, and admin accounts first.
- 033. Backups you have tested
- Keep backups separate from your main systems and restore from them on a schedule to prove they work.
- 044. Email authentication
- Publish SPF, DKIM, and DMARC records so attackers can't easily send mail that looks like it came from you.
- 055. A patch and update cadence
- Apply operating system, browser, and plugin updates on a regular, owned schedule.
- 066. Review vendor access
- Know which vendors and tools can reach your data, and remove access that is no longer needed.
- 077. One owner for cyber
- Name one person accountable for cybersecurity, even if the work itself is shared or outsourced.
- 088. A board-readable status
- Report progress to your board in plain language: what's done, what's open, and what it needs.
How TitanDef fits
Start on a small budget.
- TitanDef Community Edition is free for qualified 501(c)(3)s with an operating budget under $2M.
- Pro bono pen testing: five slots per quarter for qualified 501(c)(3)s, by application. See pen testing, then ask us about applying.
- Grantees of our foundation partners get the Starter edition through Grantee Cyber Health.
- Need funding? Read our cybersecurity grants guide.
FAQ
Questions, answered.
- Who qualifies for TitanDef Community Edition?
- Community Edition is free for qualified 501(c)(3) organizations with an operating budget under $2M. It covers an external attack surface scan, an inherent exposure review, peer benchmarking, and executive reporting.
- Do we need to book a demo to get Community Edition?
- No, Community Edition is a sign-up, not a demo. Check your eligibility on the Community Edition page; book a demo only if you want to talk through paid tiers or need help.
- Does TitanDef offer pro bono penetration testing?
- Yes, TitanDef offers five pro bono pen testing slots per quarter for qualified 501(c)(3)s, by application. Book a demo or email info@titandef.com to ask about applying.
- Where should a small nonprofit start with cybersecurity?
- Start by turning on multi-factor authentication for email and finance systems. Then inventory the data you hold, test your backups, and name one person who owns cybersecurity.
- Can grants pay for nonprofit cybersecurity?
- Yes, several grant, donated-software, and insurance-credit programs can fund nonprofit cybersecurity. Our cybersecurity grants guide walks through the main ones and how to sequence them.
Next step

