Skip to content
Scale To Zero by Cloudanix
W(

Guest

Winthrop (Andy) Welch

Fractional CISO

Andy Welch is a cybersecurity executive who has led security, GRC and risk strategy at companies including Yahoo, IBM and Goldman Sachs. He brings a pragmatic, executive-level lens to building secure, compliant and resilient organizations, from Fortune 500 firms to emerging tech.

Episode with Winthrop

What Winthrop covered

Beyond the Debate: Security as an Enabler & GRC Maturity with Winthrop Welch, Fractional CISO

Winthrop (Andy) Welch argues that security and compliance shouldn't be at odds: good compliance mandates are security requirements that belong on the program roadmap. He sees GRC maturity as low in many enterprises, where GRC acts as an after-the-fact assessments team, and says it earns its value by moving upstream into development, operations and M&A deal teams. Drawing on a penetration testing engagement, a collapsed acquisition and a healthcare breach response, he shows how trust, shared goals and a value-first approach turn security from a blocker into an enabler.

  • Instead of debating security versus compliance, treat compliance as a gateway to security use cases and requirements, and prioritize them on the roadmap like any other requirements.
  • Alignment is the key to collaboration between the security team and the rest of the organization. Building trust and building security champions on the business side goes a long way in designing a successful security program.
  • The way to beat vendor and tool sprawl is to understand your future state architecture and map out a roadmap to it, then choose the best-fit tool or vendor instead of the new shiny toy.
  • GRC earns its place by moving upstream: embedding in development, operations and deal teams early, rather than arriving after the fact with a list of findings.
  • To build a culture of positive friction, start by inviting critique from your direct reports, then widen it once you're comfortable.

Questions Winthrop answered

  • Should security and compliance be treated as separate priorities?

    Andy says security and effective compliance shouldn't be at odds. He defines compliance broadly, covering external requirements such as regulations and contracts and internal obligations such as policies and controls, and argues that good compliance mandates describe what must be done, not how. Clear, traceable compliance requirements then become inputs to the security roadmap and can be prioritized like any other requirements.

  • What is the biggest hurdle to aligning security strategy with the business?

    According to Andy, it is gaining persistent, regular access to the right people on the business side, so you understand their motivators and where the business is headed. Security has to offer those stakeholders value and keep the dialogue open and refreshed, and he thinks many organizations don't spend enough time keeping that alignment steady.

  • How mature is GRC in most enterprises?

    Andy sees GRC maturity as pretty low in many organizations, where GRC is treated as the assessments team that arrives after development with a checklist and a list of problems. That makes it a source of noise and friction, and it quickly gets marginalized. The shift comes when GRC moves upstream, embeds in development and operations, learns their workflows and helps teams make security decisions as they are being made.

  • How should you structure a GRC team?

    Andy starts with clarity: when he built out the GRC program at Yahoo, he defined its vision, scope and value proposition and tied everything back to them. Rather than splitting teams into governance, risk and compliance, he splits them by internal focus (policies, control standards, risk oversight, internal compliance) and external focus (regulatory engagement, third-party risk, M&A contracts, customer and partner assurance). He finds this aligns better with how businesses are structured and builds more natural relationships with stakeholders.

  • How do you fix security tool sprawl?

    Andy sees tool sprawl as a symptom of never having a cohesive security architecture or long-term plan, with tools picked reactively for each problem, leading to overlap, integration gaps and bloated cost. The fix is strategic: step back, map out your future state architecture and build a reasonable roadmap to get there. It takes time and coordination across teams, but the payoff is a leaner, more effective and more affordable program.

  • When should security get involved in M&A deals?

    Andy says security has to be part of the deal from the deal thesis through diligence to execution, not bolted on at the end. He describes a deal that collapsed because the deal team didn't engage IT or security until after close, and the acquired software's architecture proved too expensive to integrate. Once his team started adding insight to deal teams, those teams began inviting them in, which he treats as the sign of success.

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.