thebiginterview
Zero trust: the misunderstood foundation Zero trust has become one of the industry’s most overused phrases, but Jenkins argues that MSPs still misunderstand what it actually requires. Te biggest misconception? Tat it’s too difficult, or that clients
will resist it. “Tey want to be able to do whatever they want on their machines,” he says. But in practice, when MSPs explain the risks clearly, customers accept the need for tighter controls. Jenkins emphasises that zero trust is not a product category but a
mindset: allow by exception, not by default. In practical terms, this means: • blocking all untrusted soſtware • limiting what applications can do • restricting access to cloud services to trusted devices • reducing admin rights • closing unused network ports. Tese are simple principles, but they require discipline. Jenkins is clear that MSPs who fail to adopt them are facing real risk. “It’s not a case of maybe getting hit by ransomware, it’s a case of when.”
Where ThreatLocker fits — and where it doesn’t TreatLocker’s platform has expanded significantly, now offering eight or nine modules across endpoint security, cloud protection, network controls and more. But Jenkins is adamant that MSPs should focus on the fundamentals before anything else. Te four most important controls, in his view, are: • closing network ports • stopping untrusted soſtware • limiting application behaviour • shutting down access to SaaS services from untrusted devices. Other tools such as EDR, patch management, web filtering, etc., matter, but they are secondary. “Tat’s how you win the war,” he says of allow listing and ring fencing. “If those controls are in place, then EDR, for example, becomes like having a motion sensor on the inside of a bank vault.” For MSPs, this clarity is useful. TreatLocker is not trying to
replace the entire stack. It is trying to harden the parts that attackers target first.
The operational reality Jenkins’ view on operational mistakes is simple. Te biggest issue is not misconfiguration, misunderstanding or lack of expertise – it’s simply failing to follow through. “All mistakes can be addressed by solving one problem, and that’s
showing up,” he says. TreatLocker’s onboarding process includes weekly calls with highly trained engineers, but many MSPs fail to follow up consistently. Te result is predictable: agents deployed but not fully secured,
ports leſt open, allow listing incomplete. For MSPs juggling dozens of clients, Jenkins’ advice is
straightforward: make the routine calls, follow the guidance, and let specialists handle the complexity.
What MSPs should be asking vendors Jenkins believes MSPs need to be more assertive when evaluating vendors. Te key question these days is: prove you won’t become the source of an attack.
www.pcr-online.biz He suggests asking vendors to demonstrate their own internal
controls – just something as simple as attempting to run TeamViewer on a sales laptop. If they can run untrusted soſtware, that’s a red flag. “If your laptop isn’t secure, then I don’t have much confidence your
business is secure.” With MSP tools increasingly targeted by attackers, this scrutiny
is overdue.
Cyber insurance: tightening requirements and rising expectations Cyber insurers are becoming more demanding, though Jenkins says they are still “three years behind the curve.” Some insurers now refuse to cover organisations with exposed RDP ports. Others require allow listing, EDR or adherence to frameworks such as Australia’s Essential Eight. TreatLocker has seen customers sign up aſter losing coverage
because they couldn’t prove they had allow listing in place. Jenkins expects this trend to accelerate as insurers analyse recent claims and adjust requirements accordingly.
Continuous verification: a simple idea wrapped in complex language Continuous verification has become another buzzword that confuses MSPs. Jenkins says that the concept is simple: continuously validate the device, the user and the connection. Te problem is the terminology. “It’s become a marketing term which
has over-complicated it,” he says. Many MSPs have already implemented technologies that provide continuous verification without realising it. Te solution is to focus on tangible actions rather than abstract labels.
If a device remains compliant, tokens remain valid, and connections remain brokered through secure agents, continuous verification is already happening.
Keeping things simple for MSPs TreatLocker’s strategy for supporting generalist MSPs is built around three pillars: • sticking to core security principles • providing specialist engineers for weekly guidance • delivering constant updates through webinars, alerts and community content.
“No one can be a specialist in everything,” Jenkins says. Te goal is to ensure MSPs don’t need to be. By denying by default and reducing privilege, most new threats become irrelevant before they can cause harm.
A new MSP reality Te interview paints a picture of an industry undergoing rapid transformation. AI has changed the threat landscape, and attackers are moving faster than ever. For MSPs, Jenkins’ message is both a warning and an opportunity.
Te fundamentals of zero trust are achievable, practical and increasingly non-negotiable. Te challenge is committing to them consistently. Te next two years will be defined by how quickly MSPs adapt to
AI-driven threats and cloud-centric security. As Jenkins puts it, controls matter more than predictions, and the organisations that implement them will be the ones that stay ahead.
July/August 2026 | 15
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52
