Who should be on a CIO’s IT risk management team?
A practical takeaway is to define explicit decision rights. Someone must own the risk register, escalation cadence, and acceptance decisions, but ownership should not mean isolation inside IT. The strongest model is a small, durable council with named participation from security, infrastructure or recovery, operations, finance, and vendor management, tied into enterprise risk management. Leaders should ask: which risks can this team accept, which require executive sign-off, and how are unresolved trade-offs surfaced quickly?
The most underdeveloped area is often human-risk capability. Many organizations invest in perimeter defenses yet underfund behavior testing, phishing resilience, role-based training, and response rehearsals. That creates a mismatch between where attacks land and where budgets go. CIOs should examine whether “people risk” has an owner, metrics, and funding, rather than treating awareness as an annual compliance exercise.
External perspective is another governance decision, not just a staffing preference. Independent challenge from advisers, auditors, or specialist partners can expose normalized weaknesses in internal teams. The management question is when to buy that challenge, how often, and how to prevent it from becoming a one-off assessment instead of a recurring discipline.
Most enterprises now embrace risk management, but building a strong, knowledgeable team to shoulder that responsibility means finding the right mix of specialists.
Increasingly sophisticated cyber threats that could derail a company’s earnings require a team on defense that can identify, assess and control these escalating disruptions.
The recent hack of cryptocurrency exchange Binance not only resulted in the theft of $6.3 billion in digital assets but also led customers to withdraw at least $3 billion of their own assets. The attack, which combined social engineering and a fake job interview, highlighted the need for C-suite tech leaders to assemble multifaceted risk management teams.
For example, Chris McGlasson, a fractional CIO for several midmarket firms, said he keeps his teams small and cross-functional by design. “I want someone who owns security, someone who owns infrastructure and backups, a partner in finance, and a leader from operations,” he said.
Seeking qualified candidates
An effective IT risk management team cannot operate as a technical island; it must function as an integrated, cross-disciplinary council aligned directly with enterprise risk management, said Paul Zikmund, who teaches in the chief risk program at Carnegie Mellon University’s Heinz College.
“While core IT operations, infrastructure, architecture and information security leaders are essential foundationally, the team must also extend to key business stakeholders,” he said.
IT risks rarely stay contained within the server room or cloud environment, Zikmund said. “Including business unit leaders ensures that the team evaluates risks based on operational impact rather than managing technical vulnerabilities in a vacuum.” He added that a high-performing IT risk team isn’t an IT committee, but a governance body in which technical, operational, legal and financial leaders jointly own the digital risk profile.
Looking for external partners is always a good idea, said Bryan Martin, CTO at contact center and unified communications firm 8×8, but most leaders wait too long to do so.
“People who have defended the same systems for years stop seeing the gaps in them,” he warned. “What matters more than the resume is whether they can sit down with an engineer and talk through a real system, not just present slides to a board.”
Including a team member in finance is nonnegotiable, McGlasson said, since every risk decision is really a business decision. Operations team members, meanwhile, have to be at the table because they know which systems are actually necessary to keep the doors open, and that’s not always what the architecture diagram shows, he said. At least equally important is that someone owns the vendors.
“Your MSP and your cloud providers are part of your risk surface, whether you’re actively managing them or not,” McGlasson said.
Your internal people know the environment cold, which is valuable, but it’s also a blind spot, because they have quietly learned to live with risks a fresh set of eyes flags on day one, said Mark Sternig, CTO, at healthcare IT, data and security firm Focus.
“An outside hire, or an outside partner, brings pattern exposure,” he noted. “They’ve watched this go wrong at plenty of other organizations, so they can catch the early warning your own team has stopped noticing.”
The blind spot on risk teams
Underestimating the human side is the biggest mistake IT leaders make when building a risk management team, said Tengo Meskhi, former deputy CIO at Bank of Georgia, that nation’s largest bank. “As a result, most teams are built to defend the perimeter and its systems, and almost nothing is built to defend the people.”
He noted that social engineering and phishing can go straight through a technically sound setup, and that most teams rarely include anyone whose job is to test and train the staff members who will be targeted, said Meskhi, currently CEO of Conceptdigital, a London-based consultancy to banks and fintechs. He added that the risk register needs a line for people and the team needs someone who owns it, since this is often the easiest-to-exploit vulnerability.
Decide who owns the risk
Name an owner on the risk management team, one person to be accountable for the risk register, the review cadence, and the uncomfortable conversations, McGlasson advised.
“The biggest risk isn’t a missing control, it’s that risk floats between IT, finance and operations, and belongs to no one,” he said. “Other responsibilities become easier once that seat is filled.”
The ultimate failure in building an IT risk team is inadvertently creating a technical vacuum, Zikmund warned. “A successful team must speak the language of the business, operate hand-in-glove with the central enterprise risk management program function, and evaluate every technology risk through the lens of enterprise resilience and strategic continuity.”
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.
