IT Governance for Non-Profit Boards: What Directors and Trustees Should Know
Non‑profit boards increasingly find themselves dealing with questions about cybersecurity, cloud systems, donor databases, and digital strategy. Even if you are not a “tech person,” you are still responsible for overseeing how information technology (IT) supports the mission and how IT‑related risks are managed.
This article explains IT governance in plain language, focusing on what boards and trustees need to know—at a strategic and oversight level, not at a technical level.

1. What Is IT Governance in a Non‑Profit Context?
1.1 A Simple Definition
IT governance is the framework by which a non‑profit’s board and leadership ensure that:
- Technology supports the organization’s mission and strategy.
- Technology‑related risks are identified and managed.
- The organization’s use of technology is responsible, compliant, and aligned with fiduciary duties.
In other words, IT governance is how you, as a board, make sure that technology decisions are:
- Purposeful, not ad hoc
- Connected to impact, not just cost
- Managed with appropriate checks and balances
1.2 How IT Governance Supports Mission and Fiduciary Duties
For non‑profits, technology is not an end in itself; it enables impact:
- Donor management systems power fundraising and stewardship.
- Case management tools support program delivery.
- Email, collaboration suites, and cloud systems enable staff and volunteers to work effectively.
- Security controls protect beneficiaries, donors, and employees whose data you hold.
From a fiduciary perspective, boards have duties of care, loyalty, and obedience. These apply to technology decisions just as much as to financial decisions:
- Duty of care – Ensuring that there are reasonable controls and oversight over IT risk, including cybersecurity and data protection.
- Duty of loyalty – Protecting the interests of the organization and its stakeholders by safeguarding sensitive data and avoiding conflicts of interest in major IT vendor relationships.
- Duty of obedience – Ensuring compliance with applicable laws, regulations, and contractual obligations (for example, data protection laws or funder requirements related to security and privacy). For a non-technical, board-friendly audit checklist, see this guide to IT compliance audits.
1.3 IT Governance vs. Day‑to‑Day IT Operations
It helps to distinguish governance from operations:
- IT Operations (management responsibility):
- Resetting staff passwords
- Fixing laptops and printers
- Configuring firewalls and security tools
- Setting up new user accounts
- Managing vendors and contracts day‑to‑day
- IT Governance (board and senior leadership responsibility):
- Approving IT‑related policies (e.g., acceptable use, data protection, incident response)
- Setting risk appetite for cybersecurity and data privacy
- Ensuring that major IT investments align with strategy and budget
- Overseeing how management identifies, monitors, and reports on IT risk
- Confirming there are plans for continuity and disaster recovery
You don’t need to know how to configure a server. You do need to ask the right questions, understand the trade‑offs, and ensure that management has the right expertise and resources.

2. Why IT and Digital Risk Are Board‑Level Issues
2.1 Reputational Risk and Trust
Non‑profits operate on trust. A data breach involving donor or beneficiary information, or a publicized ransomware attack, can:
- Damage your reputation with donors, beneficiaries, and partners.
- Undermine confidence in your ability to safeguard vulnerable communities.
- Lead to reduced donations and participation over time.
Because reputation is a strategic asset, IT risk is inherently a board‑level concern, not a purely technical detail. For a deeper dive into why charities are targeted and how to respond, see our practical cybersecurity tips for Singapore charities.
2.2 Regulatory and Contractual Compliance
Many non‑profits are subject to data protection and privacy obligations, which may include:
- Region‑wide or national data protection laws (for example, the EU/UK GDPR, or other regional equivalents).
- Sector‑specific regulations (such as health data privacy laws like HIPAA in the US, where applicable).
- State or provincial privacy laws (which can vary significantly by jurisdiction).
- Funders’ and partners’ requirements, which may specify security controls, data handling practices, and reporting obligations.
Boards are not expected to be legal experts, but you are expected to ensure that the organization:
- Recognizes where laws apply.
- Has access to appropriate legal and compliance advice.
- Implements reasonable policies and controls to comply.
Because regulations and case law differ by country and even by state or province, boards should seek professional legal counsel on specific obligations rather than relying only on generic templates or practices.
2.3 Financial Impact
IT incidents can have a direct financial impact:
- Costs of forensic investigations, legal advice, and remediation.
- Ransomware payments (if considered at all) and system rebuilds.
- Fines or penalties for non‑compliance.
- Loss of donor revenue or grants due to reputational damage or contract termination.
In many non‑profits, margins are tight and reserves limited. A major IT incident can threaten the continuity of services and even the organization’s viability.
2.4 Accountability Cannot Be Outsourced
Non‑profits often rely on:
- Managed service providers (MSPs)
- Cloud platforms and SaaS vendors
- Volunteer or part‑time IT support
While these partners can provide expertise and services, the board cannot fully delegate its responsibility for oversight:
- You can outsource work, but not legal or fiduciary accountability.
- Vendors and management must be held to clear expectations, with appropriate monitoring and reporting.
- Boards should insist on clarity: who is responsible for which controls, and how performance and risk are measured.
If you are comparing providers, use these seven questions to choose the right IT service partner in Singapore.

3. Key IT Risk Areas: What Boards Should Know and Ask
This section covers four major IT risk domains relevant to non‑profit boards:
- Cybersecurity
- Data Protection & Privacy
- Vendor & Cloud Management
- Business Continuity & IT Resilience
For each, we focus on plain‑language explanations, why it matters, key questions, and good oversight practices.
3a. Cybersecurity
What It Means in Plain Language
Cybersecurity is how your organization protects its systems, data, and people from digital attacks and misuse. For non‑profits, common threats include:
- Phishing – Emails or messages tricking staff or volunteers into clicking malicious links, entering passwords on fake websites, or sending money to fraudsters.
- Ransomware – Malicious software that encrypts your files and demands payment for their release.
- Business Email Compromise (BEC) – Attackers gain access to or impersonate staff email accounts to redirect payments, steal gift card funds, or convince donors to send money to fraudulent accounts.
- Website attacks – Defacement of your website, inserting malicious code, or using your site to spread malware.
Why It Matters for Non‑Profits
Non‑profits can be attractive targets because:
- They often hold valuable donor and beneficiary information.
- They may have less sophisticated security than large corporations.
- Staff and volunteers may be stretched thin and less likely to detect targeted scams.
- A serious incident can disrupt frontline services, especially if systems are down for days or weeks.
Cybersecurity is not about eliminating all risk (which is impossible), but reducing risk to a level your organization can tolerate.
Minimum Reasonable Expectations
At a board‑oversight level, there are some “baseline” controls you should expect management to have implemented or be planning to implement:
- Security awareness training
- Regular (at least annual) training and reminders so staff and volunteers can spot phishing and understand basic good practices.
- Multi‑factor authentication (MFA)
- Requiring a second factor (like a code on a phone) in addition to passwords for email, financial systems, and other critical applications.
- Strong basic access controls
- Unique logins for each user; no shared accounts.
- Access granted according to role (“need to know”).
- Prompt removal of access when staff or volunteers leave.
- Endpoint protection and patch management
- Up‑to‑date antivirus or endpoint protection on devices, and regular application of security patches to operating systems and key applications.
- An incident response plan
- A documented, rehearsed plan describing what happens if a cyber incident occurs: who is in charge, how it is escalated, who must be notified (including regulators and donors where applicable), and how evidence is preserved.
Questions Boards Should Ask Management
- What are the top 3–5 cyber threats we face as an organization today?
- What baseline security measures do we currently have in place (e.g., MFA, training, backups)?
- How often do staff and volunteers receive security awareness training, and how do we measure its effectiveness?
- Do we have a documented incident response plan, and when was it last tested or used?
- Have we assessed our cyber insurance needs, and how does cyber insurance (if any) align with our controls and incident plans?
Examples of Good Oversight Practices
- Receiving at least annual briefings on cybersecurity from management or an external advisor, including trends and major incidents (even “near misses”).
- Reviewing a simple dashboard at board or committee level, tracking items like:
- Number of phishing simulation failures
- Number of critical patches outstanding
- Progress on key security projects
- Ensuring that critical cyber incidents are explicitly included in the organization’s overall risk register.
- Requiring post‑incident lessons‑learned reports when issues occur, along with updates on how controls are improved.

3b. Data Protection & Privacy
What It Means in Plain Language
Data protection and privacy involve how your organization:
- Collects, uses, stores, shares, and disposes of personal information.
- Complies with applicable privacy and data protection laws.
- Respects the rights and expectations of donors, beneficiaries, staff, and volunteers.
Non‑profits often hold particularly sensitive data, such as:
- Donor data – Contact details, giving history, payment information (usually via payment processors), communication preferences.
- Beneficiary data – Personal circumstances, health or disability information, social services records, case notes, and more.
- Financial records – Bank account details, grant agreements, invoices, payroll.
- Employee and volunteer data – HR records, background checks, performance reviews, ID documents.
Legal and Regulatory Considerations (High‑Level)
- General privacy and data protection laws – Many jurisdictions have comprehensive laws that set principles for how organizations must handle personal data (for example, GDPR in the EU/UK, and comparable frameworks elsewhere).
- Sector‑specific laws – If you work with health or educational data, or with children, additional laws may apply (for example, HIPAA in the US for certain health information).
- State or provincial laws – In federal systems, rules may differ by state or province regarding breach notification, consumer privacy rights, and retention.
Because requirements differ by jurisdiction and sector, boards should not attempt to interpret laws themselves. Instead, ensure access to knowledgeable counsel and compliance advisory capabilities.
Data Governance Basics
Good data protection is underpinned by simple governance concepts:
- Data ownership and accountability – Who is responsible for each major category of data (donor, beneficiary, HR, etc.)? Is there a designated data protection or privacy lead?
- Data classification – Understanding which data is public, internal, confidential, or highly sensitive, and protecting it accordingly.
- Data retention and disposal – How long is data kept, and how is it securely deleted or anonymized when no longer needed or required by law?
- Access control – Ensuring only appropriate people can access certain data, and that access is reviewed periodically.
- Breach response – Having defined procedures for identifying, containing, and reporting data breaches, including timelines and notification requirements where mandated.
Questions Boards Should Ask Management
- What categories of personal data do we hold, and which are most sensitive?
- Which laws and regulations on data protection and privacy apply to us, given where we operate and who we serve?
- Do we have clear data protection and privacy policies, and how are they communicated to staff and volunteers?
- How do we manage data retention and secure deletion? Are there areas where we are keeping data longer than necessary?
- What is our process for responding to a data breach, including legal notifications and communication with donors and beneficiaries?
Examples of Good Oversight Practices
- Approving a data protection/privacy policy and ensuring it is periodically reviewed and updated.
- Confirming that the organization has identified a person or role (for example, a Data Protection Officer, Privacy Manager, or equivalent) accountable for data protection activities, even if this is a part‑time responsibility.
- Requesting periodic reporting on:
- Data breaches or near misses.
- Progress on data clean‑up, retention projects, or policy implementation.
- Ensuring that major projects (e.g., new donor CRM, new beneficiary database) include a privacy impact assessment or similar review.

3c. Vendor & Cloud Management
What It Means in Plain Language
Most non‑profits now rely heavily on third‑party vendors and cloud services for:
- Email and productivity (e.g., cloud office suites)
- Donor and fundraising platforms
- Accounting and finance systems
- Case management and CRM systems
- Website hosting and payment processing
- Managed IT services (remote and on‑site support, device monitoring, backups, security tools, etc.)
These vendors often store and process your most important data. That creates third‑party risk: if your vendor has a security incident, outage, or business failure, your organization is also affected.
Why It Matters for Non‑Profits
- You may have limited bargaining power, but you still need to understand what you’re signing.
- If a key vendor is compromised, you could face data breaches, extended downtime, or loss of historical data.
- Vendor contracts can affect your ability to meet legal obligations (for example, if the vendor does not support required data subject rights in a privacy law).
- Switching providers can be complex and costly if data is not portable or formats are proprietary.
What Boards Should Expect in Vendor Management
At a board oversight level, you are not negotiating each contract, but you should expect management to have:
- Due diligence processes for critical vendors:
- Basic checks on security practices.
- References or track record in the non‑profit sector.
- Understanding of data locations (countries/regions where data is stored).
- Clear contractual protections, including:
- Data protection and confidentiality clauses.
- Service level agreements (SLAs) covering uptime, response times, and support.
- Clear roles and responsibilities for security (who does what).
- Exit and data portability arrangements: how you get your data back if you leave.
- For an overview of key clauses to watch in Singapore IT agreements, see this guide.
- Ongoing monitoring, not just “set and forget”:
- Periodic vendor performance reviews.
- Updates on significant changes, incidents, or sub‑processors.
Questions Boards Should Ask Management
- Who are our “critical vendors” from a data and operations standpoint (e.g., top 5–10)?
- How do we assess the security and reliability of these vendors before we sign contracts?
- Where is our data physically stored, and does this create any legal or compliance implications?
- What does our contract say about data ownership, breach notification, and data return or deletion if we terminate the relationship?
- How do we monitor vendor performance and respond to vendor incidents or outages?
Examples of Good Oversight Practices
- Requiring that major vendor selections (for mission‑critical systems) involve:
- A simple, documented evaluation process.
- Consideration of security, data protection, and long‑term viability—not just price.
- Ensuring that management maintains a register of critical vendors, including:
- Services provided
- Data types processed
- Key contract terms and renewal dates
- Encouraging periodic vendor risk reviews, especially for IT and cloud service providers that handle sensitive data or critical systems.

3d. Business Continuity & IT Resilience
What It Means in Plain Language
Business continuity is about how your organization continues to operate during and after a disruptive event, such as:
- Cyber attacks (e.g., ransomware)
- Natural disasters or extreme weather
- Power or network outages
- Major system failures or vendor outages
- Loss of key staff or volunteers
IT resilience focuses on ensuring that critical technology systems and data are available and recoverable when you need them.
Why It Matters for Non‑Profits
Non‑profits often provide essential services to vulnerable populations. An extended outage can:
- Interrupt delivery of key programs.
- Prevent you from accessing critical beneficiary or health information.
- Disrupt donations and fundraising when you most need support.
- Damage trust with funders, regulators, and the communities you serve.
Backup and Recovery Expectations
At a governance level, boards should expect that:
- Data backups exist for all critical systems and are:
- Regular (daily at minimum for key systems).
- Stored in a secure, separate location—ideally with some form of offline or immutable backup to protect against ransomware.
- Restores are tested periodically:
- It is not enough to assume backups work; organizations should test recovering data and systems at least annually for key workloads.
- Recovery time objectives (RTOs) and recovery point objectives (RPOs) are defined:
- How quickly must systems be restored?
- How much data loss (e.g., hours or days) can be tolerated?
Planning for Outages and Incidents
An effective continuity approach should include:
- A business impact analysis (even a simple one) to identify:
- Which processes are critical (for example, beneficiary services, payroll, donor receipting).
- Which systems support those processes.
- A documented business continuity plan and disaster recovery plan, with:
- Clear roles and responsibilities.
- Communication plans (to staff, beneficiaries, donors, regulators, media as appropriate).
- Alternative methods of working (e.g., manual processes or temporary solutions) if systems are down.
Questions Boards Should Ask Management
- What are our most critical services and systems, and what would happen if they were unavailable for a day, a week, or longer?
- How are we backing up our data, and how often do we test restoring from backup?
- Do we have a business continuity and disaster recovery plan, and when was it last updated or tested?
- If a major cyber incident or outage occurred tomorrow, what would our first 72 hours look like?
- Do we have clear communication plans for beneficiaries, donors, staff, and regulators in the event of a serious disruption?
Examples of Good Oversight Practices
- Including IT disruption scenarios in overall enterprise risk discussions and tabletop exercises.
- Requesting a brief annual update on business continuity and disaster recovery readiness, including results of any tests or exercises.
- Ensuring that lessons learned from real incidents are captured and implemented.

4. Board‑Level Practices for Effective IT Governance
This section focuses on governance mechanics rather than technical solutions: policies, committees, risk appetite, and reporting.
4.1 Policies and Frameworks
Boards should ensure that key, high‑level IT‑related policies exist, are approved, and are periodically reviewed. For most non‑profits, this may include:
- Information security policy – Setting overall principles for how information is protected.
- Acceptable use policy – Outlining how staff and volunteers should use organizational systems and data.
- Data protection/privacy policy – Describing how personal data is managed and protected.
- Incident response and breach notification policy – Defining how cybersecurity and privacy incidents are handled.
- Vendor management policy – Setting expectations for the selection, onboarding, monitoring, and offboarding of key IT and cloud vendors.
You don’t need dozens of policies; you need a small number of clear, practical documents that are actually implemented.
4.2 Oversight Structures and Committees
Boards vary in size and capability. Common approaches include:
- Audit & Risk Committee
Many boards assign IT and cyber risk oversight to the existing Audit & Risk (or Finance & Risk) Committee. This works well if the committee:- Explicitly includes IT/cyber in its charter.
- Has or can access relevant expertise (for example, an external advisor).
- Technology or Digital Committee
Larger organizations sometimes establish a dedicated Technology, Digital, or IT Committee, focusing on:- Strategic technology investments.
- Major transformation projects.
- Cybersecurity and data governance at a deeper level.
- Board‑level sponsor or “IT champion”
For smaller boards, appointing one board member as the sponsor or lead for IT governance can help ensure consistent attention, even if a formal committee does not exist.
Regardless of structure, what matters is that:
- IT risk and digital strategy have a clear “home” in the board’s governance structure.
- Responsibilities are documented and understood.
- Reporting lines between management and the board/committees are clear.
4.3 Risk Appetite and Integration with Enterprise Risk Management
IT risk should not be managed in isolation. Boards should:
- Integrate cyber, data, and technology risks into the enterprise risk register.
- Discuss and articulate a risk appetite for different areas, such as:
- Tolerance for system downtime.
- Tolerance for data loss or manual processes.
- Tolerance for using lower‑cost vendors with limited guarantees versus more robust (but expensive) options.
These discussions help management make consistent trade‑offs:
- For example, is it acceptable to have cheaper systems with lower uptime, if it frees budget for frontline services?
- Where must we invest to protect mission‑critical capabilities (such as case management for vulnerable clients)?

4.4 Reporting and Board Education
Boards should request regular but concise reporting on IT governance topics, such as:
- A short annual or semi‑annual IT risk and security update, including:
- Top risks and recent trends.
- Key incidents and how they were handled.
- Progress on strategic IT initiatives.
- Periodic metrics or indicators, which could be simple for smaller organizations:
- Training completion rates.
- Significant vendor issues.
- Outcomes of backup/restoration tests.
- Open high‑risk audit or assessment findings.
Board members should also receive occasional education sessions on digital risk and governance, tailored to non‑profits and non‑technical leaders, to maintain a baseline understanding.
4.5 Realistic Actions for Small and Mid‑Sized Non‑Profits
Limited budgets and staff do not remove the need for IT governance. They do mean you must prioritize. Practical steps include:
- Start with a short IT risk discussion at the board level
- Identify the top 5–10 technology‑related risks in simple terms.
- Agree which ones are highest priority.
- Assign responsibility
- Designate a board member and a senior staff member as leads for IT risk.
- Ensure IT topics appear regularly on the Audit & Risk or full board agenda.
- Develop or update a small set of core policies
- Focus on acceptable use, data protection, cybersecurity basics, and incident response.
- Use sector‑appropriate templates if available, but adapt them to your reality.
- Work with trusted IT partners
- Where you use managed IT services or MSPs, ensure contracts and scopes of work clearly address:
- Security measures (e.g., device monitoring, patching, endpoint protection).
- Backup and recovery responsibilities.
- Support for compliance and reporting.
- Schedule periodic reviews with these partners to discuss risk, not just break‑fix issues.
- Where you use managed IT services or MSPs, ensure contracts and scopes of work clearly address:
- Prioritize the “vital few” controls
- MFA on critical systems.
- Reliable backups with tested restores.
- Basic security awareness training.
- Up‑to‑date devices and software.
- Make IT incidents reportable events
- Ensure that serious data breaches, cyber attacks, or extended outages are promptly reported to the board or relevant committee, just as financial irregularities would be.

5. Balanced, Non‑Technical Oversight
You do not need to become cybersecurity engineers or cloud architects. Your role is to:
- Ask informed, mission‑focused questions.
- Set expectations and boundaries (risk appetite, policies, oversight structures).
- Ensure that management has the resources and expertise to implement reasonable controls.
- Monitor, challenge, and support management’s efforts over time.
Avoiding both extremes is crucial:
- Not enough concern – Treating IT as purely operational and underestimating its strategic and risk implications.
- Too much fear – Being paralyzed by cyber risk to the point of blocking useful innovation or demanding gold‑plated solutions you cannot afford.
A thoughtful, proportionate approach enables non‑profits to leverage technology for impact while managing risks responsibly.
Top 10 Questions Non‑Profit Board Members Should Ask About IT Governance
- How does our current technology environment support our mission and strategy—and where are the biggest gaps or weaknesses?
- What are the top 5 IT and digital risks on our enterprise risk register, and who is accountable for managing each one?
- What basic cybersecurity measures do we have in place (e.g., MFA, backups, training, patching), and where are we most vulnerable today?
- What types of personal and sensitive data do we hold, which laws likely apply to us, and who is responsible for data protection and privacy?
- Do we have clear, board‑approved policies for information security, acceptable use, data protection, and incident response—and are they actually being implemented?
- Who are our most critical technology and cloud vendors, how do we assess and monitor their security and reliability, and what rights do we have in our contracts?
- How are our critical systems and data backed up, how quickly could we restore them after an incident, and when did we last test this in practice?
- What is our process for responding to a serious cyber incident or data breach, including required notifications to regulators, donors, and beneficiaries?
- How is IT risk overseen at board level (which committee, which board member leads), and how often do we receive structured reports on these topics?
- Given our size and resources, what are the next 3–5 practical steps we should take over the next 12–18 months to strengthen IT governance and resilience?
If your board can confidently ask—and get clear answers to—these questions, you will be well on your way to providing effective oversight of IT governance in your non‑profit.