Risk Management, Vendor Management and Technology Governance
Technology risk registers, cyber and resilience risk, third-party and concentration risk, vendor selection and management, and governance forums for a CTO.
Executive explanation
A CTO is accountable for technology risk (security, resilience, compliance, delivery, key-person and vendor risk) and for governance forums that make decisions transparent. Boards increasingly expect clear reporting on cyber and operational resilience.
Risk management
| Risk | Example | Mitigation |
|---|---|---|
| Cyber | Ransomware, data breach | Zero trust, backups with immutability, incident response, cyber insurance |
| Resilience | Region outage, critical vendor failure | DR tiers, multi-AZ/region, tested exit/contingency plans |
| Compliance | Regulatory breach (privacy, DORA, AI Act) | Compliance by design, control monitoring |
| Delivery | Major program late | Incremental delivery, stage gates |
| Technology obsolescence | End-of-support platforms | Lifecycle management, portfolio roadmap |
| People | Key-person dependencies | Documentation, pairing, succession |
| AI | Incorrect automated decisions, data leakage | AI governance, evaluation, human oversight |
Maintain a risk register with likelihood, impact, owner, mitigations and residual risk; review monthly with leadership and quarterly with the board/risk committee.
Vendor management
- Selection: requirements, RFP/RFI, proof of concept, security and financial due diligence, reference checks, contract terms (SLAs, data ownership, exit, price caps).
- Tiering: critical vendors (cloud, core SaaS, payments) get deeper oversight.
- Ongoing: performance reviews against SLAs, security attestations (SOC 2 reports), roadmap alignment, spend tracking.
- Concentration and exit: documented exit plans for critical vendors (required by regulations such as DORA for financial entities).
Governance forums
| Forum | Purpose | Cadence |
|---|---|---|
| Technology leadership team | Strategy, priorities, org | Weekly |
| Architecture council / ARB | Significant technical decisions | Weekly |
| Investment/portfolio board | Funding and stage gates | Monthly/quarterly |
| Risk and security committee | Risk register, incidents, compliance | Monthly |
| Board technology/risk reporting | Strategy progress, risk posture | Quarterly |
CTO interview questions and model answers
How do you report cyber risk to the board?
In business terms: top risks with likelihood and impact, trend of key indicators (critical vulnerabilities, patch times, phishing resilience, MFA coverage, backup restore success), major incidents and lessons, investments and the residual risk they buy down, and benchmarking against frameworks (NIST CSF 2.0).