Skip to content

Managed IT and Cybersecurity for Columbus Churches and Nonprofits

You hold names, addresses, giving history and bank details for people who trusted you with them, and you run it all on a budget written for the mission rather than for IT. The person who manages your church management system, your giving page and your Microsoft 365 tenant is often a staff member with three other jobs, or a volunteer who is generous with time and unfamiliar with security. Attackers know both of those things.

Why would an attacker bother with an organization our size?

Because the payoff is good and the door is usually open. You hold donor names, addresses, giving history, bank and card details, sometimes background check results on volunteers, and sometimes pastoral or case notes that would be devastating in public.

That data has resale value, but cash is the easier target. The FBI ranked business email compromise the second-largest loss category in its 2025 report, at just over $3 billion. An attack like that breaks nothing. It is one email that looks like it came from the executive director, sent to the bookkeeper, at the moment a real payment is due.

Attackers also do their homework, and a lot of your information is public by design. Charitable organizations that solicit contributions in Ohio generally register with the Attorney General and refile each year, and those filings are searchable. Religious organizations can be exempt, and churches are outside the Form 990 most 501(c)(3)s file. But a staff directory, a campaign goal and a giving schedule are usually right on your own website. Someone can work out who signs, who pays and roughly what is in the account before writing the first message.

Volunteers come and go. How do we keep accounts under control?

Volunteer turnover creates accounts that are easy to make and easy to forget. A shared login for the giving platform. Another for the church management system. Social accounts still signed in on a former volunteer’s phone. An admin password nobody has changed in six years because nobody remembers who set it. Each one is a way in that outlives the person who left.

The fix is unglamorous:

  • Individual named accounts instead of shared ones.
  • Multi-factor authentication on anything that touches money or member data.
  • Permissions granted by role.
  • Removing access as a written step in the volunteer exit process, the same way you collect a key.
  • A scheduled review of who can still reach financial systems.

That is the daily work of our managed IT and cybersecurity services. The policy, the framework choice and the board-level reporting around it are what a virtual CISO engagement covers.

Our insurance renewal asks if multi-factor authentication is enforced. How do we prove it?

It is a yes-or-no box on the questionnaire, and someone on your staff signs it. In a church or nonprofit it is hard to answer from memory, because the accounts that decide it were created by different people over several years and nobody has put them on one page.

Building that list is the work, and it comes before switching anything on. Go system by system, because these platforms do not report into one console:

  • The Microsoft 365 tenant.
  • The giving platform.
  • The church management system.
  • The bank portal.
  • The admin logins on the firewall and the wireless.

For each account, record the named person behind it, whether MFA is on, and what the account can reach.

The roster will not come back clean. Something will not support MFA, or supports it in a way that breaks a process the bookkeeper runs every week. So the answer that holds up is the enforced list plus a written record of the exceptions. Note which accounts, why, what is in place around each one instead, and when it gets looked at again.

That record is also what a board asks for when it wants to know who can reach the money. Our managed IT and cloud IT services keep the account side current day to day, and a virtual CISO engagement keeps the documentation from going stale between renewals.

Donations run through a giving platform. Who is responsible for PCI compliance?

You still are. PCI DSS applies to anyone that stores, processes or transmits cardholder data, or could affect the security of the environment that does. The PCI Security Standards Council says using a compliant provider “does not make an entity PCI DSS compliant, nor does it remove the entity’s responsibility for its own PCI DSS compliance.”

Requirement 12.8 keeps several duties on your side:

  • A list of the service providers you use and what each one does.
  • Written agreements in which each provider takes responsibility for the account data it handles, or for anything that could affect the security of your payment environment. That second part is what pulls in a website vendor or church management platform that never touches a card number but can affect a payment page.
  • Due diligence before signing, and a review of each provider’s compliance status at least once every 12 months.
  • A record of which requirements each provider manages, which you manage, and which are shared.

How you validate compliance is set by your acquiring bank and the payment brands, not the Council. At the size of a typical church or nonprofit it is usually a self-assessment questionnaire, and your bank decides which one applies, so ask.

One newer wrinkle catches church websites in particular. If your giving page is a provider’s payment form embedded in your own site, the current SAQ A criteria call for confirmation that the site is not susceptible to attacks from scripts. You can protect the page directly, or get written confirmation from a compliant processor that its product already protects the page when set up per its instructions. Sites that send the donor away to the processor entirely are treated differently. Most organizations have never checked what their giving page does.

Does Ohio’s data breach law apply to a church or nonprofit?

Yes. Revised Code 1349.19 reaches any business entity conducting business in Ohio, defined as an organization “however organized and whether operating for profit or not for profit.” A 501(c)(3), a church, a foundation or a private school is not outside it by its form alone. The section covers computerized data only, and it exempts HIPAA covered entities and certain financial institutions.

The duty turns on two things. First, someone without authorization accessed and acquired an Ohio resident’s name together with a Social Security number, a driver’s license or state ID number, or a financial account or card number plus the code that opens it. That counts only where the data was not encrypted, redacted or otherwise made unreadable. Second, that the breach causes, or is reasonably believed to cause, a material risk of identity theft or fraud.

When both are true, notice has to reach affected residents in the most expedient time possible and within 45 days of discovering the breach or being told about it. Law enforcement can ask for a delay. More than 1,000 Ohio residents in one breach adds notice to the nationwide consumer reporting agencies.

HIPAA does not simply swap in. A HIPAA covered entity is outside the Ohio law entirely. But HIPAA’s own breach rule reaches only unsecured protected health information, so a covered entity that loses donor records or card data has a question for counsel. And a nonprofit handling health information for someone else is a business associate, not a covered entity. It has to tell the covered entity without unreasonable delay and within 60 days. Both sets of duties can land on one organization at once.

Can a nonprofit use Ohio’s cybersecurity safe harbor?

Yes, on the same terms as a company. Chapter 1354, commonly called the Ohio Data Protection Act, uses the same not-for-profit-inclusive definition. An organization that creates, maintains and follows a written cybersecurity program, reasonably conforming to a listed framework, gets an affirmative defense. It covers tort claims alleging that a failure to implement reasonable security controls caused a breach. It is a defense, not immunity.

The listed frameworks include the NIST Cybersecurity Framework, NIST SP 800-171, the CIS Critical Security Controls and the ISO/IEC 27000 family. Two things to settle first. If you take cards, PCI DSS on its own does not carry the defense; it has to be paired with one of the other frameworks. And the statute expects the current version of whichever framework you pick, so a program left on a superseded edition ages out of the defense.

The program can be scaled to your size, the sensitivity of what you hold and your resources. To extend the defense to pastoral or case notes and volunteer background checks, write the program to cover restricted information as well. Before committing to any of it, our $349 Security Analysis at https://outreach.ttscyber.com/analysis is an independent assessment mapped to 38 compliance frameworks.

Start here

Find out where you actually stand

The Security Analysis is a fixed-scope review of your environment, run independently and mapped to 38 compliance frameworks. It replaces an assumption about your posture with a finding.

Questions we get asked

Our data is in the cloud. Doesn’t that mean it is backed up and secured?

The provider secures the platform, but you still own what is inside it. Microsoft’s shared responsibility documentation puts customer data, settings, and accounts and access on the customer’s side of the line for Microsoft 365. So a volunteer who deletes a year of records, a compromised admin account that empties a mailbox, or a retention window that quietly expires all land on you. Native recovery in Microsoft 365 is limited and time-boxed, so backup and retention are yours to own. Ask your church management system and giving platform the same question, and get the answer in writing.

Microsoft used to give us free licenses. What changed?

Microsoft discontinued the Microsoft 365 Business Premium and Office 365 E1 nonprofit grants at each organization’s next renewal on or after July 1, 2025. What remains is up to 300 granted licenses of Microsoft 365 Business Basic, plus discounts of up to 75 percent on paid nonprofit offers including Business Premium. Business Basic is a lighter plan, so some organizations dropped down at renewal and lost security features without anyone noticing. Check which licenses your tenant is on now and what each one includes.

What should we do first if we think someone got into our email or our giving account?

Do not delete anything or wipe the machine. If money moved, call the bank first, because the odds of stopping a fraudulent transfer drop the longer you wait. Reset passwords and revoke active sessions from a device you know is clean. Preserve mailbox rules, sign-in records and audit logs before they age out, since they are what tell you what was taken.

Ohio’s 45-day notice clock runs from the day the breach is discovered or someone else tells you about it. It does not wait for the investigation to finish, so a call from a bank or giving platform can start it. Whether it runs at all depends on whether the exposure creates a material risk of identity theft or fraud. Get counsel involved before anything goes out to donors or members. TTS Cyber is not a law firm; this is not legal advice.

Primary sources

Read the rules yourself

These are the official texts for the main rules this page covers. The page also draws on other sources named in the text above, which are not linked here. Where a section is named above, it is worth reading in the instrument rather than taking a summary for it, including this one.

Reference

Explained in full elsewhere on this site

TTS Cyber is an IT and cybersecurity company, not a law firm, and nothing on this page is legal advice. This page summarises published rules and cites them so they can be read directly; where this page and the source differ, the source governs. Whether a particular rule reaches a particular business, and what it requires of that business, are legal questions for that business's own attorney.

Page last updated .

Let’s Get in Touch!

Security Analysis

Find out where you actually stand.

Most businesses do not discover a gap until something goes wrong. This is a fixed-scope analysis of your environment, run independently, so you get an answer rather than an opinion.

What the analysis covers