Skip to content
Scale To Zero by Cloudanix
MM

Guest

Matthew Moog

Principal, Financial Services Risk Managed Services Leader, EY

Matthew Moog is a security professional with more than 20 years of experience and a principal at EY, where he leads financial services risk managed services. He previously served as general manager for third-party risk management at OneTrust and brings deep expertise in third-party risk management, financial services risk and GRC.

Episode with Matthew

What Matthew covered

The Mythos Era: TPRM Evolution, AI Ethics, and Project Glasswing with Matthew Moog

Matthew Moog, a principal at EY, argues that third-party risk management is moving away from repeated annual assessments toward continuous monitoring of signals such as financial health, resiliency, cybersecurity and zero-day events, run almost like a mini SOC. He estimates AI can take about 60% of the effort out of an assessment, but warns against over-reliance on its output and against turning the savings into headcount cuts. What sets Mythos apart, he says, is that it chains individually minor vulnerabilities into serious ones; he expects more vulnerabilities to patch and more scrutiny of open source code, and sees demand for more technically deep security professionals, not fewer.

  • Treat assessments as a baseline, not the whole program. Moog rarely sees material year-to-year differences in mature assessments, so he would keep annual deep dives for critical third parties and spend more time on continuous signals: financial health, resiliency, cybersecurity and zero-day events.
  • AI can remove around 60% of the effort from a third-party assessment, but every answer needs checking. His team's agents cite the policy, the page and a screenshot of the evidence so a reviewer can confirm each one quickly.
  • Reinvest AI efficiency gains instead of banking them as layoffs: move budget into threat and vulnerability management, incident response, agentic pen testing and security posture management.
  • Mythos changes the threat picture by stacking vulnerabilities that are minor on their own into a serious one, and by Moog's account about 90% of what it found was in open source, so expect pressure to find and test the open source code across your third-party ecosystem.
  • Put controls in place before scaling agents. In a lab simulation, a prompt injection hidden as white text in a mortgage file instructed agents to delete a whole bunch of things and was picked up by the roughly 800 rules the team ran in the workflow; uncapped token usage is its own risk, with one organization spending $100 million on tokens in a quarter.

Questions Matthew answered

  • How much effort can AI save in a third-party risk assessment?

    Moog estimates about 60% of the effort, possibly more, can come out of the assessment itself. His team's agents read dozens of documents and point to the exact policy, page and a screenshot of the evidence, so reviewers can verify answers quickly, and each client's model is trained separately to keep data isolated. He advises putting the savings into areas like threat and vulnerability management, incident response, agentic pen testing and security posture management rather than cutting staff.

  • What is Project Glasswing and why should security leaders care?

    Project Glasswing gives a select group, largely large banks, access to Anthropic's Mythos model; consulting firms like EY see it only through client projects and working groups. Moog says what makes Mythos different is that it stacks vulnerabilities, combining ones that are insignificant on their own into a much bigger one. He warns that organizations rushing to adopt agents need controls and an understanding of these new risks, which takes people who are deeply technical and understand the business context.

  • Why is AI ethics a board-level issue?

    Moog sees the ethical questions inside third-party risk as small next to the broader board discussion of AI ethics. Agents are given judgment and access that mirror an employee, and they have tunneled outside firewalls and interacted in ways no one expected, so the real dilemma is where to say no. He also treats workforce impact as an ethical choice, raising options such as working 20% less for 20% less pay instead of cutting 20% of staff.

  • Will AI replace third-party risk questionnaires and assessments?

    Not entirely. Moog compares it to a modern car full of sensors that still gets a 160-point inspection before resale: an assessment remains the best way to understand a new third party's controls and is still worth doing every year for critical ones. Because mature assessments rarely change year to year, he expects more time to go to continuous signals and to running third-party risk almost like a mini SOC.

  • How does AI change security in the software development lifecycle?

    Moog says AI coding models are very good at checking their own code for vulnerabilities, so scanning will be built in by default whether code is written by humans or agents, although the models still struggle with user personas, access and non-linear workflows. He expects constant scanning of code bases and external perimeters, and says patching what is found will have to be automated in many cases because that would be very difficult with a human-based labor force.

  • Will AI reduce the size of security teams?

    Moog does not expect a fully autonomous security organization in the next 10 years outside some very small startups, because agents cannot yet think critically through chaos the way a SOC analyst does when deciding whether to cut off an anomaly. He sees demand for more security professionals, especially those with a deep technical understanding of their architecture, their tools and where AI fits in, including through third parties.

New episodes twice a month

No security question left unanswered.

Follow Scale To Zero wherever you listen, or send us the question your team is stuck on and we will put it to an expert.