What a Nonprofit Actually Holds
Four categories are worth separating, because they trigger different obligations. Donor data includes names, contact information, giving history, and in many cases payment card or bank account details for recurring gifts. Even where a payment processor holds the card data, the organization usually holds enough to matter. Client or beneficiary data is often the most sensitive, particularly for organizations providing health, housing, immigration, youth, counseling, or domestic violence services. A breach there carries consequences for individuals that go well beyond financial harm, and in some cases disclosure can put people at physical risk. Employee and volunteer data includes identification and banking information, and for volunteers often background check results. Grant and contract data may include information covered by confidentiality obligations to a funder. Each category can trigger state breach notification obligations, and organizations operating across state lines face multiple notification regimes at once.
- Donor records including payment and bank details for recurring gifts
- Client and beneficiary records, often highly sensitive by nature
- Employee and volunteer records including screening results
- Funder data subject to contractual confidentiality obligations
How Nonprofit Incidents Typically Happen
The patterns are consistent. Business email compromise leads, often targeting the finance function with a request to change a vendor's payment details or to wire funds for an urgent program need. Nonprofits are particularly exposed because approval chains are short and the culture is responsive. Donation page compromise is second. A giving page running outdated software or a third party script can be manipulated to capture payment data, and the organization discovers it when donors report fraudulent charges. Third is credential theft through phishing, often reaching a shared mailbox or an account without multifactor authentication. Fourth is ransomware, which for a small organization frequently means losing access to the donor database during a campaign, and the operational damage can exceed any ransom demand. Fifth, and the most preventable, is simple misdirection: a spreadsheet of donors or clients emailed to the wrong recipient, or a mail merge that exposes one recipient's information to others.
- Business email compromise aimed at the finance function
- Compromise of online giving or event registration pages
- Phishing and credential theft, especially on accounts without multifactor authentication
- Ransomware during a campaign period, and simple misdirected disclosures
What Cyber Coverage Pays For
A cyber policy has two halves. First party coverage funds the organization's own response: forensic investigation, legal counsel to determine what notification law requires, notification itself, credit monitoring where appropriate, public relations and donor communications, data restoration, and business interruption for the period systems are unavailable. Cyber extortion coverage addresses ransomware, generally with its own sublimit and conditions. Third party coverage responds to claims against the organization, including privacy liability, network security liability, and regulatory defense, along with payment card related liabilities where applicable. Two points matter more for nonprofits than for commercial buyers. The response cost side is usually the real exposure, because an organization with a modest budget cannot absorb forensic and notification costs out of operating funds. And the reputational communication piece is not a luxury, because an organization that handles donor notification poorly loses recurring revenue that no insurance policy replaces.
- First party coverage funds forensics, notification, restoration, and lost income
- Third party coverage responds to privacy and network security claims
- Response costs are usually the dominant exposure for a small organization
- Donor communication support protects the revenue that matters most
Where Cyber Meets the Rest of the Program
Boards should understand three adjacencies. Funds transfer losses from a fraudulent payment instruction often sit under a crime policy rather than a cyber policy, frequently with a social engineering sublimit and a condition requiring documented callback verification. An organization without that endorsement may have no coverage for the single most likely loss. Directors and officers coverage can be implicated where a board is alleged to have failed to oversee data protection. That is a governance claim, not a breach response claim, and it responds under the management liability policy rather than the cyber policy. Fidelity and employee dishonesty exposure overlaps as well, since internal misuse of donor payment data is a crime policy question. Mapping these three against each other is a short exercise and it prevents the discovery, during an incident, that the available coverage sits in a different policy with a different deductible and a different carrier.
- Fraudulent payment instruction losses usually sit in the crime policy
- Social engineering coverage often requires documented callback verification
- Board oversight allegations respond under directors and officers coverage
- Internal misuse of donor data is a crime policy question
Controls a Small Organization Can Actually Implement
Four things carry most of the value and none of them require a large budget. Enable multifactor authentication on email, the donor database, and any financial system, with no exceptions for shared mailboxes or long tenured staff. Require documented verbal verification by callback to a known number for every change to payment instructions or banking details, and make it a written policy so nobody has to decide in the moment. Limit access by role so that volunteers and program staff cannot export the full donor or client database. And set a retention schedule, deleting what is no longer needed, because data you do not hold cannot be breached. Then address vendors. The donor platform, payment processor, email tool, and any contractor with administrative access should be inventoried, with their security documentation on file. For the board, ask for an annual report covering those four controls and the vendor list. That is a reasonable oversight cadence and it is also what a directors and officers underwriter wants to hear.
- Enable multifactor authentication on email, donor, and financial systems
- Require documented callback verification for payment and banking changes
- Restrict database export rights by role
- Inventory vendors and report the control status to the board annually
Frequently Asked Questions
Related Resources
This article is for general information and is not a substitute for policy language or professional advice.
