Couverture de The Business of Cybersecurity

The Business of Cybersecurity

The Business of Cybersecurity

De : Neil C. Hughes
Écouter gratuitement

Offres de saison | 0,99 € par mois pendant les 3 premiers mois

5,99 €/mois par la suite. Des conditions s’appliquent. Annulation mensuelle possible.
À propos de ce contenu audio

The Business of Cybersecurity is a podcast from the Tech Talks Network that explores where security and business strategy converge.

Hosted by Neil C. Hughes, creator of the Tech Talks Daily Podcast, this series examines how today’s enterprises are managing cyber risk while still moving fast and innovating. Through insightful conversations with industry leaders, CISOs, product strategists, and security architects, the podcast brings clarity to the real-world decisions shaping cybersecurity in modern business.

Each episode dives into how companies are responding to regulatory pressure, increasing complexity in cloud environments, and rising expectations from boards and customers. From AI-driven defense and zero trust to skills gaps and risk quantification, we go beyond technical jargon to explore what actually works—and what doesn’t—on the road to building resilient organisations.

Whether you're leading a security team, sitting at the executive table, or simply want to understand the business impact of cybersecurity, this podcast offers honest, grounded perspectives designed to help you make better decisions in an environment that never stands still.

Search Tech Talks Network to discover more shows covering the voices at the heart of enterprise technology.

Tech Talks Network 2025
Economie
Épisodes
  • Who Should Own AI Risk With StackAware
    Nov 17 2026

    Who should accept the risk of an AI system when the benefits belong to the business but security and compliance teams are expected to manage the consequences?

    In this episode of Business of Cybersecurity, I speak with Walter Haydock, founder and CEO of StackAware, about the decisions behind responsible AI adoption. Walter's background spans Marine Corps reconnaissance and intelligence, national security and enterprise technology. He explains how those experiences shaped his approach to uncertainty and why delaying a decision can create risks of its own.

    We discuss his argument that the business leader benefiting from an AI system should own the associated risk decision. Security, legal and compliance teams bring expertise to that assessment, but Walter questions what happens when they are asked to accept responsibility without receiving the business benefit. I also ask what evidence a board should request before approving autonomous AI. Walter recommends comparing expected value, operating costs and error rates with the existing process, alongside the effects on confidentiality, integrity and availability.

    The conversation includes his account of working with Embold Health on governance, risk assessment and security testing for EVA, its virtual assistant for healthcare navigation. We consider how natural language can help people find appropriate providers and why the controls around an application need to support its intended purpose. Walter also outlines questions smaller organizations can ask AI suppliers about data use, retention and output quality, while recognizing that the answers depend on the service and agreement involved.

    We then discuss governance as ongoing work. Models, interfaces and integrations can change after a system is approved, so teams need a way to notice different behavior and reassess whether the service still meets their expectations. Walter describes how a tiered approach can give lower-risk activities a clearer path forward while reserving greater scrutiny for more consequential uses. For leaders trying to make decisions without waiting for perfect certainty, the discussion connects opportunity with responsibility. How is your organization deciding which AI risks to accept, and who remains accountable afterward? Please share your thoughts with me.

    Afficher plus Afficher moins
    29 min
  • Securing identity for the age of AI agents with CrowdStrike
    Nov 10 2026

    What happens to identity security when the actor requesting access is an AI agent rather than a person?

    In this episode of The Business of Cybersecurity, I speak with Zeki Turedi, CTO for Europe at CrowdStrike, about the changing relationship between artificial intelligence, identity, software supply chains, and cyber defense. Our conversation draws on CrowdStrike’s 2026 Threat Hunting Report, which presents AI as a tool, a target, and a force multiplier across modern adversary activity.

    Zeki explains how attackers are using AI to produce convincing phishing messages, research organizations, and complete technical tasks faster. We also discuss how publicly disclosed vulnerabilities can be reverse engineered soon after fixes appear, leaving security teams with a smaller response window. Rather than place the focus on any single country, Zeki describes a wider pattern involving state-linked groups, criminal operators, compromised packages, information stealers, and other forms of software supply-chain abuse.

    The conversation then moves inside the enterprise, where AI agents are creating a rapid increase in non-human identities. Zeki says some organizations are already seeing 140 or 150 agents for every employee. That creates immediate questions about permissions, model choice, data access, monitoring, cost, and accountability. His advice begins with visibility. A company cannot set useful policies or respond to abnormal behavior if it does not know which agents are operating or what they are doing across their lifecycle.

    We also consider the opportunity for defenders. Cybersecurity teams have accumulated years of threat data that can help AI systems identify patterns and support faster action. Zeki believes this can move people away from repetitive alert handling and toward work that anticipates threats, provided organizations first address identity, vulnerability management, and software supply-chain controls.

    Can businesses adopt AI agents at speed while keeping access understandable, limited, and accountable? Listen to the episode and share your thoughts with me.

    Afficher plus Afficher moins
    24 min
  • Breaking attacker tactics with cyber containment and Illumio
    Nov 4 2026

    What if the best way to prepare for the next cyberattack is to stop obsessing over every new tool and study the moves attackers still need to make?

    In this episode of The Business of Cybersecurity, I welcome back Raghu Nandakumara, VP of Industry Strategy at Illumio, for a practical conversation about attacker tactics, lateral movement, zero trust, microsegmentation, and cyberattack containment.

    Security news often emphasizes the latest exploit, malware strain, or AI capability. Raghu argues that the underlying structure of an attack remains much more predictable. Whether the intruder is a nation-state actor, a less experienced criminal, or an autonomous system, it still needs to enter a target environment, find a route through it, and reach an objective such as stealing data or taking systems offline.

    That distinction between tactics and techniques matters because defenders cannot anticipate every future method. They can, however, make each stage of an intrusion harder. Raghu compares the sequence he describes in a recent frontier-model security incident with the Target breach from over a decade earlier. The technology and procedures differed, but both involved access, credentials, lateral movement, and a final objective.

    We also discuss the difficulty created by the volume of security telemetry. More alerts do not automatically produce better decisions. Raghu explains why data needs context about applications, identities, connections, and vulnerabilities before an analyst or AI system can connect events and identify the risks that deserve attention.

    For Raghu, zero trust reduces the implicit access attackers rely on after entering a network. Microsegmentation can limit how far they move, force them to take additional actions, and create signals that improve the chance of detection. This reframes containment as a control designed before an incident rather than a response improvised after one.

    The conversation also challenges the idea that initial access proves prevention has failed. Preventing every attack is unrealistic, but leaders can measure whether controls contained the blast radius, protected business operations, and stopped the intruder from reaching valuable systems. Raghu describes prevention, detection, and containment as a three-legged stool, because relying on only two leaves the defense far less stable.

    Finally, we consider tool sprawl and testing. Raghu uses the Swiss cheese model to explain why identity, endpoint, network, cloud, and incident-response teams must understand how their controls overlap. Mapping those controls against MITRE ATT&CK or the Lockheed Martin Cyber Kill Chain can reveal an open path through the organization. He also argues that red-team exercises should resemble real attacks rather than rehearsals announced inside a comfortable change window.

    Would your security controls interrupt an attacker under real conditions, or have they mainly proved themselves when everyone knew the test was coming? Listen to the conversation and share your thoughts with me.

    Afficher plus Afficher moins
    32 min
adbl_web_anon_alc_button_suppression_t1
Aucun commentaire pour le moment