Dear Board, How are you overseeing IT Risk?

Introduction: Navigating IT Risks at the Board Level

In today’s digital-first banking landscape, information technology (IT) risks are front and center for boards of directors. With the banking sector increasingly reliant on technology (primarily those of vendors) to drive operations, deliver services, and manage regulatory compliance, the complexity of IT risks has skyrocketed. From cyber threats and system outages to data breaches and third-party vendor risks, the evolving nature of IT risks presents a challenge that boards can no longer afford to approach passively. And certainly, Boards cannot sit back and wait for Management to tell them what is going on.

In addition, it is not sufficient for boards to merely be informed of these risks; they must actively engage with IT risks in a way that actually drives strategic decision-making. Effective governance requires that boards be presented with comprehensive transparency on IT risks and a clear pathway to making informed decisions that reduce exposure, safeguard operations, and ensure long-term resilience of the businesses they advise.

This article will outline the regulatory expectations for boards, explore the diverse set of comprehensive IT risks that banks face, and discuss best practices for actionable board reporting. By framing IT risk discussions around clear decisions, information, approvals, and risk, banks can ensure their boards are empowered to make informed, timely decisions that align with the institution's risk appetite. If you are currently a board member, buckle up!

Regulatory Expectations for Financial Institutions in IT Risk Governance

Given the critical role of IT in banking operations, financial regulators worldwide have emphasized the importance of robust IT risk governance at the board level. For example, banking regulators such as the Federal Financial Institutions Examination Council (FFIEC), the Office of the Comptroller of the Currency (OCC), and the Basel Committee on Banking Supervision (BCBS) require boards to be actively involved in overseeing IT risks, ensuring that they are aligned with the institution’s overall risk management strategy. Actively!

  1. FFIEC IT Handbook:
    The FFIEC expects boards to play a direct role in overseeing IT risk management strategies. Boards must ensure that appropriate cybersecurity measures, business continuity plans, and incident response protocols are in place to safeguard the bank's technology infrastructure.

  2. OCC Guidelines on IT Risk:
    The OCC has heightened standards for IT risk governance, particularly for large banks. Boards are expected to oversee IT risk management frameworks, approve cybersecurity budgets, and review incident reports. The OCC also emphasizes the importance of aligning IT risk management with the bank’s overall risk appetite.

  3. Basel III and IT Resilience:
    Basel III guidelines extend to the role of IT in ensuring operational resilience. Boards must ensure that IT systems can withstand operational shocks, including cyberattacks and system failures. Basel III also encourages stress testing for IT systems to evaluate their robustness under adverse conditions.

Comprehensive Decision-Making: Boards must also ensure they are approving IT risk frameworks, allocating resources for cybersecurity investments, and making informed decisions on vendor risks, cloud security, and data privacy measures. It’s critical that IT risk discussions result in clear, actionable decisions that align with regulatory requirements and the bank's risk tolerance.

A Comprehensive Set of IT Risks for Bank Boards

Below is a comprehensive list of IT risks that banks must govern actively. Each risk category includes key decisions the board must make and metrics to monitor whether the bank is effectively mitigating these risks.

1. Cybersecurity Risks

Cybersecurity remains the top IT risk for financial institutions, as the frequency, sophistication, and impact of cyberattacks continue to escalate. Banks are prime targets for ransomware, phishing attacks, DDoS attacks, and advanced persistent threats (APTs) that aim to disrupt operations or steal sensitive data.

Key Board Decisions:

  • Approve cybersecurity budgets for tools like threat detection, firewalls, and MFA.

  • Decide whether to purchase or expand cyber insurance policies.

  • Review and approve the incident response plan for various attack scenarios.

  • Mandate cybersecurity audits for key third-party vendors.

Key Risk Appetite Metrics:

  • Number of significant intrusions or data loss events per month.

  • Mean Time to Detect (MTTD) and Mean Time to Respond (MTTR) for security incidents.

  • Percentage of critical systems not protected by MFA.

  • Proportion of the IT security budget spent on proactive measures.

  • Frequency and participation rate in employee security training.

2. Cloud Security Risks

As banks increasingly rely on cloud platforms, cloud security risks like poor configurations, shared responsibility models, and data breaches become more prominent. Ensuring regulatory compliance in cloud environments is critical.

Key Board Decisions:

  • Approve cloud migration strategy (e.g., public, private, hybrid).

  • Review and mandate encryption policies for data in the cloud.

  • Approve cloud provider selection based on due diligence.

Key Risk Appetite Metrics:

  • Percentage of cloud data encrypted in transit and at rest.

  • Number of security incidents/misconfigurations in cloud environments.

  • Average uptime percentage for critical cloud services.

  • Percentage of cloud infrastructure covered by automated monitoring tools.

3. Data Privacy and Protection Risks

With increasing regulatory scrutiny, banks must ensure strong data protection to safeguard sensitive customer information. Non-compliance with privacy laws (e.g., GDPR, CCPA) can result in severe financial and reputational outcomes.

Key Board Decisions:

  • Approve data privacy frameworks for regulatory compliance (GDPR, CCPA).

  • Mandate data loss prevention (DLP) investments to monitor movement of data.

  • Establish breach notification policies for customers and regulators.

  • Mandating that third-party vendors adhere to the bank’s data privacy standards and performing regular audits of their data protection practices.

Key Risk Appetite Metrics:

  • Number of reported data breaches or violations per quarter.

  • Percentage of sensitive data covered by DLP solutions.

  • Time to notify regulators/customers of data breaches.

  • Percentage of third-party vendors audited for data privacy compliance.

4. Third-Party Vendor Risks

Banks rely heavily on third-party vendors for critical IT services, such as payment processing and cybersecurity monitoring. This exposes the bank to third-party risks if vendors fail to meet security or operational standards.

Key Board Decisions:

  • Approve third-party vendor risk management frameworks.

  • Implement continuous vendor monitoring solutions for performance issues and adherence to SLAs.

  • Mandate regular cybersecurity audits of critical vendors.

Key Risk Appetite Metrics:

  • Percentage of high-risk vendors audited annually.

  • Number of vendor-related incidents impacting critical operations.

  • Percentage of third-party vendors covered by real-time monitoring.

  • Compliance rate of third-party vendors with the bank’s security policies.

5. System Downtime and Resilience Risks

Banks depend on complex IT systems for operations. System downtime can disrupt services and damage reputation, especially as regulators focus on operational resilience.

Key Board Decisions:

  • Approve business continuity plans (BCPs) and disaster recovery (DR) strategies.

  • Mandate regular DR testing for recovery time objectives (RTO) and recovery point objectives (RPO).

  • Requiring stress testing of critical IT systems to simulate worst-case scenarios and ensure systems can withstand prolonged outages.

Key Risk Appetite Metrics:

  • Average downtime per month for critical systems.

  • Percentage of critical systems covered by DR testing.

  • MTTR (Mean Time to Recover) after system outages.

  • Percentage of systems with redundancy for failover capabilities.

6. Emerging Technology Risks

Emerging technologies like AI, blockchain, and quantum computing offer opportunities but also introduce new risks related to bias, security, and compliance.

Key Board Decisions:

  • Approve governance frameworks for AI/ML and blockchain.

  • Mandate quantum-resistant encryption to prepare for future quantum computing risks.

Key Risk Appetite Metrics:

  • Number of AI/ML models reviewed for bias and regulatory compliance.

  • Rate of AI-driven decisions reversed due to errors or bias.

  • Compliance rate of AI models with regulatory standards.

7. Legacy System Risks

Many banks still operate on legacy systems, which are vulnerable to security breaches and integration issues. These systems can be costly to maintain and expose the bank to operational risks.

Key Board Decisions:

  • Approve modernization efforts to transition from legacy systems to modern infrastructure.

  • Decide on decommissioning old systems that no longer support compliance or security standards.

Key Risk Appetite Metrics:

  • Percentage of critical operations still dependent on legacy systems.

  • Number of security vulnerabilities detected in legacy systems.

  • Cost of maintaining legacy infrastructure vs. potential modernization savings.

8. Insider Threat Risks

Insider threats, whether accidental or malicious, can lead to data breaches or fraud. This includes employees who have access to sensitive systems and information.

Key Board Decisions:

  • Approve policies for monitoring privileged access and user behavior.

  • Implement insider threat detection systems and continuous monitoring.

Key Risk Appetite Metrics:

  • Number of incidents caused by insider threats (intentional or accidental).

  • Percentage of employees with privileged access under monitoring.

9. Software Supply Chain Risks

With an increase in attacks targeting the software supply chain, vulnerabilities introduced via third-party software can compromise bank systems and data.

Key Board Decisions:

  • Approve software procurement and third-party code audit policies.

  • Mandate regular patching and vulnerability testing for third-party software components.

Key Risk Appetite Metrics:

  • Time to patch known vulnerabilities in third-party software.

  • Number of security incidents resulting from software supply chain issues.

10. Shadow IT Risks

Shadow IT refers to unauthorized technology and systems used by employees without the approval of the IT department. This can expose the bank to security risks and compliance violations.

Key Board Decisions:

  • Approve policies to monitor, manage, or integrate shadow IT systems.

  • Mandate regular audits to identify unauthorized tools or platforms.

Key Risk Appetite Metrics:

  • Number of unauthorized systems identified per quarter.

  • Compliance rate of unauthorized systems with IT governance standards.

11. Mobile and Endpoint Security Risks

As banks adopt mobile banking and remote work solutions, mobile and endpoint security becomes a priority. Poorly secured devices can lead to unauthorized access and data breaches.

Key Board Decisions:

  • Approve mobile device management (MDM) solutions for securing employee devices.

  • Ensure endpoint security solutions (e.g., antivirus, encryption) are up-to-date.

Key Risk Appetite Metrics:

  • Percentage of mobile devices enrolled in MDM programs.

  • Number of mobile/endpoint security incidents per quarter.

  • Compliance rate of remote devices with encryption and firewall standards.

12. API Security Risks

APIs are used extensively for integrations between banks and fintechs, but poorly secured APIs can expose sensitive data or compromise critical systems.

Key Board Decisions:

  • Approve API security frameworks, including access control and encryption.

  • Mandate regular security testing and vulnerability assessments for APIs.

Key Risk Appetite Metrics:

  • Number of security incidents caused by API vulnerabilities.

  • Percentage of APIs subjected to regular security audits.

  • Compliance rate of APIs with access control and encryption policies.

Best Practices for IT Risk Reporting to the Board

Boards need more than just updates on IT risks—they also need actionable reporting that drives decision-making. Here are best practices to ensure that IT risk reporting is effective:

  1. Action-Oriented Insights: Every IT risk report should include decision points for the board, such as approving new cybersecurity investments, adjusting vendor contracts, or approving changes to the cloud strategy.

  2. Risk Appetite Monitoring: IT risk reports should highlight where the bank’s current IT risk exposure exceeds the board-approved risk appetite, ensuring that boards are aware of areas requiring immediate action.

  3. Regulatory Compliance Updates: Boards should receive regular updates on the bank’s compliance with regulatory requirements related to IT risks, such as data privacy laws or cloud security standards.

  4. Dynamic Dashboards: Use real-time dashboards to present IT risk metrics in a clear, concise format, enabling boards to monitor risk levels between formal meetings.

  5. Scenario Analysis: Provide scenario analysis for high-impact IT risks, showing the potential consequences of incidents such as a major data breach or system outage.

Conclusion: Strengthening the Boards IT Risk Governance

The board’s role in governing IT risks has never been more critical. As banks continue to embrace digital transformation, the board must take an active role in overseeing IT risk management, ensuring that the bank is protected against the growing array of cyber threats, operational disruptions, and data privacy risks.

By focusing on actionable insights and comprehensive reporting, banks can empower their boards to make informed, strategic decisions that protect the bank’s infrastructure, customers, and long-term resilience.

Empower Your Board with Proactive IT Risk Oversight

Don’t let your board sit back and wait for management to hopefully provide the right information. Our consultancy ensures that your board has an independent expert guiding the design and delivery of actionable IT risk reports, tailored to the decisions they need to make. By building a framework that drives transparency, strategic decision-making, and regulatory alignment, we help your board take control of IT risks rather than reacting to them. Contact us today to give your board the tools to confidently oversee the bank’s IT risk landscape.

Previous
Previous

Dear Internal Audit, What is Your Value?

Next
Next

Cutting Through the Complexity in IT Auditing: The Power of Tough, Impactful Questions