A church is not a business. But to a cyber insurer, the paperwork looks almost the same.
When your church applies for cyber insurance, or renews it, the application asks the same security questions a small office gets. Do you use MFA? Are your backups offline? Has everyone had training? If your church runs on a part-time administrator and a few faithful volunteers, those questions can feel like they were written for someone else.
They weren't. This checklist walks through what insurers commonly ask, the traps that are special to churches, and how to make every honest answer a "yes."
One rule before we start. Always answer the application truthfully. A wrong answer can give the insurer a reason to deny a claim, right when you need it most. The goal is not to find a way to check "yes." The goal is to make "yes" true.
Want your own score first? Take the free self-check. It's 12 questions, takes about 5 minutes, and needs no credit card.
Why churches get asked the same questions as businesses
Insurers don't ask about your mission. They ask about your money and your data. And a church has plenty of both.
- Giving. Online giving platforms, text-to-give, and the bank account behind them.
- Payroll. Staff pay, direct deposit, and the payroll service login.
- Member data. Names, addresses, kids' check-in records, counseling notes, and giving history in your church management system.
- Wire and payment requests. Building projects, missions support, and vendor invoices.
To a criminal, that adds up to a small business with a trusting culture and a very busy inbox.
Email is where most of the trouble starts. In Coalition's 2026 Cyber Claims Report, which covers claims from 2025, business email compromise and funds transfer fraud together were 58% of the claims Coalition saw. And 52% of the funds transfer fraud claims began as a business email compromise. (Coalition's announcement has the same figures.)
Those numbers come from Coalition's policyholders as a whole, not from churches alone. But the pattern fits what we see in ministry: someone gets into an email account, or pretends to be someone they're not, and then asks for money.
The church-specific traps
Most church security gaps aren't about fancy technology. They come from good people sharing things to be helpful. Here are the five we see most.
Shared logins: the office@ mailbox
Many churches have a mailbox like office@ or pastor@ that several people use. The secretary checks it Monday, a volunteer covers Wednesday, and the pastor reads it on Sunday night.
Insurers ask whether all users need MFA to log in to email. A shared mailbox counts. If office@ can be opened with only a password, the honest answer is "partly," not "yes."
A shared password is like a church key that's been copied so many times nobody knows who has one. MFA adds a second lock that a copied key won't open.
The fix. Turn on MFA for the shared mailbox too. Better still, give each person their own account and grant them access to the shared mailbox. Microsoft 365 and Google Workspace both support this, and then nobody needs the shared password at all.
Volunteers who leave but keep access
Volunteers come and go. That's normal. The problem is that their access often stays.
The youth leader who moved away may still log in to the church management system. The volunteer who ran the church's social media three years ago may still be an admin on the Facebook page. A former treasurer may still have a login to the giving platform.
Each of those is a door nobody is watching.
The fix. Keep one list of who has access to what. When someone steps down, remove their access within a week, and change any password they knew. Review the list every quarter.
Pastor impersonation texts and emails
This is the most common church scam we know of, and it's simple. Someone sends a text or email that looks like it's from the pastor:
"Are you available? I'm in a meeting and need a favor. Can you pick up some gift cards for a family in need? I'll pay you back."
Or it asks the treasurer to wire money for an "urgent" mission need. The message is friendly, rushed, and asks you to keep it quiet. Those three things together are the warning sign.
Our very first weekly scam alert on X at @CDCScamWatch was about pastor gift card texts. Follow along for a short, plain-English alert each week you can share with your staff and volunteers.
The fix. Teach everyone one rule: the pastor will never ask for gift cards or a secret wire by text or email. If a message asks for money, stop and check with the pastor in person or on a phone number you already have.
Giving and payroll changes: the call-back rule
Here's a quieter version of the same scam. An email arrives that looks like it's from a staff member: "I changed banks. Please update my direct deposit." Or a vendor writes: "We have new bank details for the next invoice."
If someone is already inside a real email account, the message can come from the real address. That's why checking the email address is not enough.
The fix. Use a call-back rule. Any change to bank details, payroll, or giving deposits gets a phone call to a number you already have on file. Never use the number in the email or text that asked for the change. Write the rule down, and make sure the treasurer and the administrator both follow it every time.
Backups of your church management database
Your church management system holds the heart of your records: members, giving statements, kids' check-in, and contact lists. Losing it would hurt.
Insurers ask whether you keep backups offline or separate from your network, and whether you have tested a restore in the last 6 months. A backup sitting on the same network as the office computers is like keeping the spare key on the same key ring. If ransomware gets one, it can get both.
If your church management system is in the cloud, don't assume the vendor's backup covers you. Ask what they keep, how long they keep it, and how you'd get it back. Then export your own copy on a regular schedule and keep one copy offline.
The fix. Back up the database, keep one copy offline or immutable, and test a restore at least every 6 months. Write down the date and whether it worked.
The checklist: 12 yes or no questions
Answer each one honestly. Each question links to the full explanation in our guide, The 12 Cyber Insurance Application Questions, Explained.
- Does every email account have MFA, including office@ and any other shared mailbox? What a real yes looks like
- Does MFA protect every way in from outside the building, like remote desktop, the giving platform, the church management system, and online banking? What a real yes looks like
- Do all admin accounts use MFA, including your email admin, website, domain, and social media admin logins? What a real yes looks like
- Is your church management database backed up with one copy offline, and have you tested a restore in the last 6 months? What a real yes looks like
- Does every church computer have up-to-date endpoint protection, including the sound booth, the lobby kiosk, and the old office PC? What a real yes looks like
- Are updates installed within about 30 days on every computer, plus the router and firewall? What a real yes looks like
- Is email filtering turned on for spam, phishing, and bad attachments? What a real yes looks like
- Has everyone who uses church email or handles money, staff and volunteers alike, had scam training in the last year, including the call-back rule? What a real yes looks like
- Do staff and volunteers do everyday work on normal accounts, not admin accounts? What a real yes looks like
- Do you have a one-page written plan for what to do if you're hacked, with a printed copy? What a real yes looks like
- Can you turn off access for outside IT helpers, vendors, and volunteers who step down, and do you remove it when they leave? What a real yes looks like
- Are laptops with member, giving, or payroll data encrypted with BitLocker or FileVault? What a real yes looks like
Not sure on some of them? That's honest, and it's common. "Not sure" is fine on a checklist. It isn't a good answer on an application, so find out before you apply.
What to keep as proof
Some insurers ask you to prove your answers, at renewal or after a claim. You don't need a filing cabinet. You need three simple things, kept in one folder that more than one person can find.
1. Screenshots. Take a dated screenshot of each setting behind a "yes": MFA turned on in your email admin panel, the backup settings, the security tool dashboard, and encryption on each laptop. Think of it as taking a photo of the locks before you leave on vacation.
2. A one-page written policy. Keep it short and in plain words. Cover the call-back rule for any money or bank change, the pastor's "no gift cards by text" rule, how often you test backups, and who to call if something goes wrong. One page that people actually read beats a long binder nobody opens.
3. An access list, reviewed every quarter. List every system (email, giving platform, church management system, payroll, bank, website, social media) and who has access to each one. Every three months, go through it and remove anyone who no longer needs access. Write the review date at the top.
Add a simple log of backup restore tests and a list of who finished training, and you're in good shape for most questions.
Common questions
Do churches really need cyber insurance?
That's a decision for your church leadership and your insurance agent or broker. We don't give insurance advice. What we can say is that churches handle giving, payroll, and member data, so insurers ask them the same security questions they ask businesses.
Does MFA have to cover a shared church mailbox like office@?
Yes, if you want to answer "all users" honestly. If any mailbox, shared or not, can be opened with only a password, the honest answer is "partly." Turn on MFA for the shared mailbox, or give each person their own account with access to it.
What should a church do when a volunteer leaves?
Remove their access to email, the giving platform, the church management system, and social media within a week, and change any shared password they knew. Keep an access list and review it every quarter.
How can a church stop pastor impersonation and gift card scams?
Teach everyone that the pastor will never ask for gift cards or a secret wire by text or email. Use a call-back rule: any request for money or any bank change gets a phone call to a number you already have, never the number in the message.
Is CyberDefense Consulting an insurance agent?
No. CyberDefense Consulting is not an insurance agency or broker. We don't sell insurance or give insurance advice. We help churches understand the security questions and get their systems ready.
Answer truthfully, then make the truth better
Always answer insurance applications truthfully and completely. If the honest answer today is "no" or "partly," say so. Then fix it before renewal so next time the honest answer is "yes."
CyberDefense Consulting is not an insurance agency or broker. We don't sell insurance, recommend policies, or give insurance advice, and we can't promise coverage or a lower price. Only your insurer decides that. Your agent or broker handles the policy. We help you understand the security questions and get your systems ready.
Your next step
Start with the free self-check. Take it here. 12 questions, about 5 minutes, no credit card. You get a score and a plain-language list of gaps.
Then book the church Readiness Review for $199. We go through your church's actual insurer application with you, line by line. You get a one-page fix list in priority order, a short list of the proof to keep for each yes, and a 30-minute call to walk through it. It's $199 for churches and nonprofits ($299 for other organizations). See the Readiness Review.
Need the fixes done? The full Cyber Insurance Readiness project is a flat $1,497. We work the application question by question until each answer is a truthful yes, or we hand you a written gap plan with costs. Hands-on work is quoted at our normal project rates before any work starts.
Want help every year? Stay Ready is $39 a month for renewal reminders, a quarterly check-in, and help with the questionnaire at renewal. Cancel anytime.
CyberDefense Consulting is based in Indio, in the Coachella Valley, California. We are a Service-Disabled Veteran-Owned Small Business, certified by the U.S. Small Business Administration. Call us at (760) 848-0202, Monday to Friday, 10:30 AM to 5 PM Pacific.
Take the free self-check | See the $199 church Readiness Review
Statistics source: Coalition, 2026 Cyber Claims Report, covering claims from January 1 to December 31, 2025, across Coalition policyholders. Not specific to churches.
CyberDefense Consulting LLC is not an insurance broker or agent and does not provide insurance advice. We do not guarantee coverage, approval, or premium amounts. Coverage decisions are made only by your insurer. Always answer insurance applications truthfully and completely. Our services are IT and security readiness consulting only.