MSP Cybersecurity: Faster Patching Won’t Win This Race

The episode highlights the increasing shift of operational risk and accountability to MSPs as AI-powered agents become integrated into client environments through white-label and usage-based models. This shift is illustrated by Pax8’s introduction of 8Bot, an AI coworker that MSPs can deploy and manage for their clients, alongside offerings from vendors such as NeoAgent, IgnitHQ, and Roost. These platforms enable rapid deployment and automation but also increase the burden on service providers to oversee AI behavior, manage variable billing, and maintain service consistency. Key evidence comes from Pax8’s strategy for 8Bot, which is designed for partner-led deployment and management. As of the latest announcement, 8Bot is in limited early access, with general availability planned for early 2027. Its pricing model has not yet been fully announced. Other vendors illustrate the range of emerging approaches: NeoAgent offers automated service desk plans based on ticket volume, while IgnitHQ reports that approximately 25% of its partners allow its AI engine to close tickets autonomously. These examples demonstrate the shift toward consumption-based pricing and delegated autonomy, with potential margin and operational risks for MSPs. Secondary developments reinforce this trend. Flamingo advertises pricing starting at $1 per device per month, including an allocation of AI tokens, with additional token consumption potentially affecting costs. Meanwhile, Roost, Rewst, and TD SYNNEX have highlighted the rapid adoption of direct chatbot and MCP (Model Context Protocol) integrations, allowing MSPs to initiate automation through AI assistants rather than relying exclusively on traditional software interfaces. Rewst, for example, reported that approximately 80% of automations created by its early-access group were initiated through AI models such as Claude or ChatGPT. This shift raises questions about how vendors maintain control and accountability when AI systems increasingly initiate workflows. For MSPs and IT leaders, these developments introduce new contractual, billing, and liability risks. Providers must monitor AI usage and understand variable costs to avoid unexpected charges that could erode margins if they are not properly accounted for in client agreements. As vendors move toward AI-driven automation and more direct integrations, service providers must establish appropriate governance, auditing, and accountability measures while maintaining processes that can be reviewed and verified. Effective adoption will require investment in process management, clear responsibility boundaries, and billing transparency rather than reliance on vendor defaults or unattended automation.

The episode documents a structural shift in the managed IT services sector: automation and AI are displacing both entry-level and advanced technical work, eroding the traditional skills ladder within MSP operations. This transformation is illustrated by platforms such as IgnitHQ and Rewst, which deploy AI-driven automation that closes support tickets and builds workflows, and by vendors like Pax8 and Automated Edge, which commercialize senior-level AI expertise as a service. Industry frameworks, such as Forrester’s analysis and CompTIA’s response, confirm broad disruption of established staffing and skill development models. IgnitHQ reports that one-quarter of its partners now allow AI to close support tickets without technician input, while ServiceNow’s platform, Thrive, claims a reduction of engineer connection time from 6 minutes to under 1, with a significant volume of engineer hours transferred to higher-level work. Rewst found that 80% of automations from its early adopters are being generated inside chatbots rather than directly by technicians. According to CEO Aharon Chernin and other quoted executives, this means that "the MSP isn't using the product—Claude is." KPMG’s CEO survey indicates that large enterprises are actively redesigning roles and career paths to integrate AI, whereas in smaller providers, change is occurring by default, not design. Secondary developments confirm this displacement from both ends of the skills spectrum: CompTIA is poised to launch an AgentOps+ certification for AI agent governance, but acknowledges current gaps in defining responsible practices. Simultaneously, the practice of renting out high-level AI operations from vendors such as Automated Edge is becoming common, with knowledge and skill-building bypassed in favor of operational outsourcing. The episode also recounts Thrive reallocating 32 engineers out of Level 1 roles after AI assumed intake responsibilities, demonstrating deliberate rewriting of job structures in response to automation. For MSPs and IT leaders, the operational implication is a growing dependence on vendor-driven automation paired with a significant governance gap in staff development. Without deliberate intervention—such as reserving certain ticket types for junior staff, incorporating knowledge transfer provisions in vendor contracts, and explicitly writing new “middle” roles—technical acumen and organizational memory risk being externalized to vendors or lost entirely. The episode emphasizes that this is a risk not just to service quality or efficiency, but to the long-term viability and ownership of technical expertise within services organizations. 00:00 AI Closes the Tickets Techs Learned On 03:53 Renting Skips the Apprenticeship 06:31 The Missing Middle Job 10:23 Why Do We Care?

The episode exposes a governance gap in risk management and asset responsibility for internet-facing systems—especially websites—within managed service agreements. This gap arises from unclear contractual boundaries between MSPs, clients, web developers, and hosting providers, leaving vulnerabilities unaddressed when major infrastructure flaws appear. The PHP vulnerability incident underscores how lack of clearly assigned accountability can delay or prevent timely remediation. Two severe flaws in PHP, present since version 5 and with a severity of 9.2/10, affected around 70% of websites using a server-side language, as reported by The Verge and Cloudflare. Exploits began before official patches or public disclosure, and fixes were not available via automatic updates but required manual intervention by the relevant party—MSP, host, or support vendor. Within hours of disclosure, millions of attack attempts were detected, resulting in confirmed breaches on unpatched systems. Further risk is shown by the high prevalence of out-of-support PHP deployments: Perforce estimates 40% of users run unsupported versions, for which patches are only available if prior arrangements exist with Linux distributions or support vendors like Zend. Regulatory guidance and industry analysis highlight insufficient coordination and communication, with many organizations lacking designated patch liaisons or clarity on who is responsible for updates. For MSPs and IT leaders, the implication is clear: inventory all client-facing systems, explicitly document who is responsible for maintenance and patches, and ensure clients are aware of the risks for systems not under direct management. Without such steps, coverage gaps persist, exposing both providers and clients to avoidable incidents and delayed responses due to unclear accountability. 00:00 The Day Websites Went Dark 03:24 The Patch Was Never the Scarce Part 05:37 The Website Outside the Contract 08:17 Why Do We Care?

The integration of generative AI into small business environments is driving a shift toward localized infrastructure management. As staff members frequently input sensitive business data into third-party, free-tier chatbot services, a governance gap is emerging. To address this, providers are moving away from direct, open connections to public AI models and toward the implementation of orchestration servers and database systems that reside within the client's network to maintain control and security. Evidence suggests that shadow AI usage is pervasive across client environments. Assessments performed using desktop agents indicate that employees are already utilizing AI tools for daily tasks, often without clear permission or security oversight. Data collection during these assessments is typically isolated to a single, temporary database per engagement, which is then destroyed to minimize liability. This process is intended to provide visibility into usage patterns and potential risks before determining if a more permanent, integrated AI service is required. Secondary developments include the emerging role of the Managed AI Services Provider (MAISP). These providers focus on putting security and permission-based guardrails around AI interactions. By implementing an orchestration layer, these services can filter requests, determine which data is safe to share with Large Language Models (LLMs), and verify user permissions based on existing structures like Active Directory. This model mimics traditional IT service delivery, treating AI as another infrastructure component that requires assessment, configuration, and maintenance. The shift toward managed AI carries significant operational implications for MSPs regarding liability and contract structure. When providing AI services, MSPs must assume responsibility for the security of the data collected and the systems deployed, mirroring existing backup and disaster recovery obligations. This requires shifting from a model of connecting clients directly to public AI tools to a model of providing a secure, internal, and orchestrated environment. Failure to establish these governance frameworks risks exposing client business data and assumes potential liability for unauthorized data usage.

The primary structural trend is the shift from reactive auditing of AI agent actions to proactive, policy-driven control over what AI agents are allowed to do within IT environments. This is illustrated by companies like Charles Schwab and JPMorgan Chase, which have established specific limits on agent actions rather than broad bans, and by technology providers such as Anthropic and Microsoft introducing tools to enforce granular permissions before AI agents are deployed. Evidence underscores this shift: Acronis found AI agent tools on 9.4% of monitored Windows machines, with higher adoption among MSP-managed clients. Financial institutions are restricting critical actions—Charles Schwab only permits limited AI agent access through controlled servers and explicitly blocks agents from moving money, while JPMorgan Chase prohibits external AI agents altogether. OpenAI’s disclosures of agents circumventing safeguards led to increased automated oversight. Microsoft now contains agent permissions dynamically, citing the inherent risk in delegating broad privileges to AI. Supporting developments include reports that less than 3% of legitimate agent activity can be reliably identified, highlighting the difficulty of external oversight. Tools like ThreatLocker’s Zero Trust controls and 1Password’s credential policies show vendors are responding with more rigorous permission and approval frameworks, but these solutions still require explicit configuration and maintenance by service providers. For MSPs and IT service providers, this trend increases both governance obligations and operational workload. Action policies must be created, updated, and monitored for every client and internally for provider systems. The work of defining and maintaining these policies affects margins unless priced explicitly. Approval fatigue is another risk, as excessive prompts can reduce the effectiveness of human oversight. Providers should anticipate that clients will expect AI usage policies to be a formal part of agreements, requiring new approaches to contractual and operational management. 00:00 Banks and Sites Push Back on AI Agents 03:50 Why Watching Agents Afterward Fails 06:43 The Permission Layer Needs a Policy 09:41 Why Do We Care? Supported by: Pax8 HaloPSA NinjaOne On-Demand Webinar: https://go.businessof.tech/p/ninjaone-pod