CLEARTECH LOOP | AI SECURITY SERIES 

Your AI Can Fix an IT Problem. But Should It?

How NinjaOne Katana AI brings operational intelligence, technician expertise, and governance together in modern endpoint management.
https://youtu.be/BIx5plv1OK0
Jo Peterson
Jo Peterson

CIO, Clarify360 Chief Analyst, ClearTech Research

Host, ClearTech Loop 

Jeff Hunter
Jeff Hunter

Field CTO

NinjaOne

Can AI help IT teams resolve problems faster without sacrificing human oversight?

In this sponsored episode of ClearTech Loop, Jo Peterson welcomes back Jeff Hunter, Field CTO at NinjaOne, to explore Katana AI, the company's new approach to AI-powered endpoint management.

Turning Endpoint Data Into Actionable Intelligence

Katana AI helps technicians interpret alerts, device histories, and operational data to identify potential root causes and recommend next steps.

Making Technician Expertise Scalable

Jeff explains how Katana turns resolved tickets into reusable knowledge base articles, allowing IT teams to share expertise and access recommended remediation scripts.

AI Governance and Human Oversight

Katana operates within NinjaOne's role-based access controls, supports granular AI permissions, and keeps technicians involved in operational decisions.

As Jeff explains: "The very last thing you want to have happen in IT is making a bad decision fast."

Discover how NinjaOne is approaching human-centered AI to improve IT operations while maintaining security, governance, and accountability.

What We Cover

  • How NinjaOne Katana AI brings operational intelligence to endpoint management
  • Turning endpoint alerts, device histories, and operational data into actionable insights
  • Identifying potential root causes and recommending next steps
  • Transforming resolved tickets into reusable knowledge base articles
  • Scaling technician expertise with recommended remediation scripts
  • Role-based access controls and granular AI permissions
  • Balancing AI-powered automation with human oversight, security, and accountability

Episode Participants

Jeff Hunter

Field CTO, NinjaOne

Jeff Hunter is the Field CTO at NinjaOne, bringing 15 years of IT industry experience to helping organizations simplify and modernize IT operations.

Previously, Jeff served as Director of Technical Services at CMX Cinemas. At NinjaOne, he hosts technical webinars and educational sessions, sharing insights on endpoint management, automation, security, and emerging technologies.

Jeff is a returning guest on ClearTech Loop, having previously joined Jo Peterson to discuss IT asset management and endpoint visibility.

Jo Peterson

CIO, Clarify360 | Chief Analyst, ClearTech Research

Jo Peterson is CIO of Clarify360 and Chief Analyst at ClearTech Research, where she focuses on technologies reshaping enterprise IT, cybersecurity, cloud, AI and digital transformation. As host of ClearTech Loop, Jo speaks with industry leaders about emerging technologies, operational challenges, and the practical implications for IT organizations.

Worth Reading + Watching

About ClearTech Loop

Hosted by Jo Peterson, ClearTech Loop explores the technologies and decisions shaping enterprise IT, cybersecurity, cloud infrastructure, and artificial intelligence. Through conversations with industry leaders, the series examines emerging technologies, operational challenges, and the practical implications for IT organizations.

This episode of ClearTech Loop is sponsored by NinjaOne.

Introduction to Jeff Hunter

Jo Peterson: Hey everyone! Thank you so much for joining this edition of Clear Tech Group. I am here with Jeff Hunter, Field CTO NinjaOne. Hi, Jeff.

Jeff Hunter: Hi, Jo. Pleasure to be on the show again.

Jo Peterson: Ah, thanks for coming. So, super excited to have you here and talking about the new product that you’re rolling out, and that is Ninja One Katana AI. And so, you know, in our normal hot and take format, we’re just going to start by asking you questions, and and you can fill us in on what’s new and exciting about Katana AI. So you and I have had a chance to talk, and you showed me a product demo and got me

Turning Endpoint Data Into Actionable Intelligence

Jo Peterson: thinking about some things. Every endpoint throws off signals, alerts, patch events, performance data, activity logs. Individually, none of it’s hard to read, but here you are, you know, as an analyst trying to look at what’s really going on across your environment, and at scale across a growing fleet of devices, it becomes noise that you got to dig through before you can find anything that actually matters or kind of piece together a picture of what’s going on. How does Ninja One Katana AI help prioritize that noise and what actually matters?

Jeff Hunter: Yeah, and and you bring up a great point, which is that an endpoint management platform generates a massive amount of data, a massive amount of information, and at a certain point, you start to reach this bottleneck where context gathering, information gathering, is a key part of most tickets because it’s unrealistic for a technician to immediately know every bit of information they need to know in order to to solve whatever ticket that they’re presently faced with, and so with Katana, our goal here is to shortcut that process. Our goal is to shortcut that information gathering, that context gathering, that is a bottleneck in so many tickets, and so with our tool, because we’re integrated into the platform already, we have access to the data points. But more than that, we know what the data points actually mean.

Jeff Hunter: So that when you ask a question to Katana, it is not just a general AI model that’s trying to figure out, okay, what does this data point mean? What does this data point mean? And then sort of stitching together some sort of context that may or may not be accurate. That context is already pre-loaded into Katana while you’re in the platform and you’re actively using it, and so you’re able to to get that quick summary. You’re able to have those alerts surfaced, and you have the confidence that Ninja One is is going to provide a more accurate summary because we have all that contextual data already in the platform, so we’re going to be able to give you that answer of okay, we have these alerts that are triggering. This means that these services are then down, which then means that you’re going to have critical disruption for this particular server here.

Jeff Hunter: That is something that I think could take you 10 taps that you need to open if you’re a lower-level technician before you sort of realize the full import of what’s going on here, and then of course how does it actually get fixed? And this is, I think, again where Katana is going to excel because we’re able to take all that massive amount of data, we’re able to show you what really matters there, and then we’re able to allow you to quickly act on it while keeping that human being in the loop, so that we’re not substituting a human’s judgment for something that an LLM is going to spit out.

Making Technician Expertise Scalable

Jo Peterson: Yeah, and that’s important. And I think as we all get further in our learning journey with AI, it feels like the thing that is happening right now that’s bubbling up is just what you’re talking about. It’s context and it’s trust. So, if you’ve been around for a while in the IT field, you know the traditional monitoring tools show you the data. And to your point, they don’t tell you what it means or what to do about it. So the burden falls on the technician to correlate an alert with a with a device’s history, cross reference it against past issues, decide whether it’s worth escalating, all the things right before even touching a fix or you know. So why is Katana AI different, and how does it help every technician build expertise faster?

Jeff Hunter: Yeah, and that’s I think a very good point there, which is that we’ve explicitly you know designed Katana with the idea that it is going to be a human in the loop. That the goal of the tool is to make the human being who’s using it better at their job, more effective at their job, and so. So you know we’re able to go ahead and provide what the root causes are, recommend what the likely next step is, but how do we get to that point? How do we know what the likely next step is? And I think this is where it’s the power of taking you know your best technician and allowing them to be sort of a force multiplier for all your other technicians.

Jeff Hunter: If you imagine that a senior-level tech is going and they solve two of the same type of ticket, same sort of problem in one day, and they go, “Well, we should probably go ahead and create a KB article for this.” With Katana, they just go to Katana and say, “Hey, this ticket that I’m currently on right now, and Katana has the context for whatever you’re looking at within the platform. Hey, Katana, go ahead and create a KB article for this ticket. And Katana just takes what’s inside the ticket and it creates a KB article that goes into the NinjaOne knowledge base in the documentation section.

Jeff Hunter: And so now, the key thing about Katana is that it does not have internet access. It is not going to go out and try to figure something out from the the general internet. It’s going to use what’s inside the Ninja One platform, and so now you have NinjaOne consuming its own knowledge base, preferring that, or Katana preferring its own knowledge base. So that’s where the the information is coming from, and so now, when a level one technician, somebody who’s brand new, comes in and they see this issue, they go to Katana and they say, “How do I fix this? You know, this ticket that I’m on right now.” Katana is going to prefer the knowledge base. It’ll go and find that article that was earlier created by a senior level technician, and it will spit back out to the level one technician, the the brand new guy. They’re going to say, “Hey, this is how you fix the issue. Here’s all the relevant information that you need.”

Jeff Hunter: And as it turns out, the senior-level technician actually created a script that goes through and automates the fix for this particular problem. Do you want to go ahead and run it? And at that point, it is a simple matter of going and just running the script, clicking the button to actually execute it, confirming that it actually fixed the issue, and then from there, Katana could even summarize a response indicating that the issue has been solved back to the requester who is having the issue.

Jeff Hunter: And so, right there, it’s that that you know one to many. You know, we’re going one to many here from you know maybe one high-level technician who knows everything. That knowledge can now be easily consolidated inside of Ninja One, and then Katana is going to make sure that that information is easily accessible to all the technicians who are using it. And that over time is going to naturally uplift those technicians. It makes it easier for them to find the answer. It makes it easier for them to find the answer independently, which I think is going to improve not just speed, but I think is also more effective for somebody’s own learning, their own education when they’re doing it independently. I think that that sits better in their brain, and so again, we’re going from your your best technician. It’s no longer just your best technician as one person. That best technician is now somebody whose knowledge can be consolidated inside of NinjaOne, can be accessed by Katana, and can then flow to all of your other technicians, just as a rising tide lifting all boats.

AI Governance and Access Controls

Jo Peterson: I love that analogy, the rising tide, because it is, it feels like that. It feels like everybody’s getting a benefit here. The seasoned techs are able to share their knowledge. The newer, fresher techs on the scene are able to just, you know, take that knowledge when they need it. That’s so important. So along with context and trust, it feels like access is also one of the AI tools’ hot topics right now. Every CIO and CISO that I’m speaking with is concerned about, and rightly so, AI access. How does Ninja One control Katana AI access?

Jeff Hunter: A great question, and one that we wrestled with, I think, quite a bit before we started to enter the realm of actually putting hands on keyboard to actually write code, and it’s because you know we we have seen in all our conversations that AI is not going to be used if AI cannot be governed. You know the control has to come first before the raw capabilities of the AI model or the AI tool actually matter, and I think that’s the correct tack to take. You know, this this massive amount of information that AI is able to consume, you know, it means nothing if you’re not able to effectively govern it. And so we thought deep and hard about governance, you know, for a very long time before we actually started building code.

Jeff Hunter: And so with Katana, it’s going to respect the role-based access controls that you’ve already established within NinjaOne. And so if you have access to workstations but not servers because you’re not on the server management team, you’re not going to be able to use Katana AI to do something potentially dangerous with the servers. You’re not even going to know. They exist, and so right there, that’s one element of of role-based access control, so that you don’t have somebody with kind of broad access to the entire system.

Jeff Hunter: But there’s also the individual tools that Katana is going to have access to. Case in point, I mentioned earlier, Katana recommending a script and saying, “Hey, do you want to go ahead and run this script?” And you just need to click a button for that. If you’re not comfortable with that, you know you want to be able to turn that feature off. You might not want an AI tool to recommend a script that a low-level technician can run. And so we’ve got multiple kill switches here. We’ve got sort of an overall kill switch at the the top level where you can say, I don’t want Katana to use information or use these features at all. I don’t want Katana to recommend a script at all. I don’t want Katana to recommend any knowledge base articles to solve problems at all.

Jeff Hunter: But then we go down to the RBAC level, and so we can say, all right, for a level one technician, they can’t use the script search feature to run a recommended script. They can’t create KB articles because they’re a lower lower level technician. I don’t want them to go and end up creating a KB article that’s going to be incorrect. And so then Katana starts consuming information that is incorrect from this knowledge base article that was created by somebody who shouldn’t have had permission to do that. And so that’s why having these effective permissions over what somebody is able to do, not just in terms of the devices or device types that they can access, but in terms of what features of the AI tool can they they use.

Jeff Hunter: We’re talking about Katana today, but you know, do we not want them to have the ability to use this as an MCP? And so we can go ahead and turn that off, so that way they’re restricted to only being able to use the AI tool actually inside of the platform, as opposed to it being a little bit more portable if they have access to the MCP.

Data Boundaries and Knowledge Base Security

Jo Peterson: Yeah, that’s really important. And when you and I were talking offline, you know, we were talking about what Katana can access as training data, and I think it’s really important to note kind of the hard line in the sand that Ninja One has put in here to protect users. Can you talk about that a minute?

Jeff Hunter: Yeah, 100%. There, there is no internet access. I think we’re all very used to whatever LLM is your favorite. You can ask it a question, and it’ll go and search web pages, and it’ll come back with information, and that’s great. But that can also lead to hallucinations. That can lead to things being made up. And so, at Ninja One, that’s a hard firewall. There is no internet access for Katana. Katana has access to a limited set of information.

Jeff Hunter: It’s great, for example, at searching our our Dojo, which is the Ninja One knowledge base, so that you can find out where you need to go next inside the platform and how to take certain actions, like integrating Microsoft 365 into Ninja One. But then it also is going to prefer information from the knowledge base, and so again, this is a way to customize Katana to your own processes and procedures. You go and you put in all of your knowledge base articles that dictate how help desk technicians should operate. That information is preferred first. That is the thing that Katana is going to reach for first when providing an answer. It’s going to look at all those knowledge base articles. It’s going to try to find the right one, and so when it is providing that information, that is not something that is you know just pulled from the internet out of a hat. It is not going to be just general inference. It is going to be pulled from the information that you store within NinjaOne that you know is good and valid in the works for your organization.

Jo Peterson: And that is so important. But the other side of that coin is that NinjaOne is not using some other company’s information, nor sharing my information outside of my organization. Right? The firewall is works on both sides.

Jeff Hunter: 100%.

Katana AI as an Operational Force Multiplier

Jo Peterson: You know, so you had alluded to it earlier, the training aspect of Katana AI. But let’s talk about the workforce aspect of it. So, as organizations grow, the volume of endpoints and service desk service desk tickets, or say that three times fast, usually demands this proportional increase in IT staff. Makes sense. How does Katana AI act, kind of as an operational force multiplier?

Jeff Hunter: Yeah, and and to the point that we discussed a little bit earlier, Jo, we discussed, you know, the information gathering stage, the context gathering stage. You know, any technician is going to need to gather information at some point during their day. Maybe not for every single ticket, but at some point throughout their day, they’re going to need. Oh, okay, I don’t remember how what this procedure is. I need to go and look this up, and so. We find that that ends up being a bottleneck, and organizations that deal with it well, they have much more streamlined IT departments and help desks. And organizations that don’t deal with it well, it’s typically because they’re not able to shortcut this process. They’re not able to effectively shortcut the context gathering and information gathering stage so that they can operate effectively, this is what Katana does very well.

Jeff Hunter: To me, this is the force multiplier of Katana: is the ability to go and make it so that this knowledge gathering stage is a is shortcut, so that you don’t spend an hour and 10 or 15 tabs of doing research to find the information you need to be effective at the task at hand, you’re able to get that in a much shorter time frame, right inside the console where you’re already using Katana AI, and so being able to shortcut that process right there, I think is tremendously useful.

Jeff Hunter: And again, speaks to the point I made earlier about you know uplifting all of your technicians. You have your your you know your rock stars. You know you have your S tier technicians who are going to always do a great job. But being able to take all your other technicians and make them better through this tool that’s absolutely key. And then there’s the other portion that we talked about earlier, which is taking that that best technician or those best five technicians that you have, and now you have the capacity to go ahead and take their knowledge and insight and put it into Ninja One, where Katana is going to process it and then convey that information downstream to all of our other technicians.

Jeff Hunter: So it’s not just that Katana is going to, you know, make your your level one technicians operate that much better. It’s going to give you the ability so that your best technicians can be, you know, mavens to borrow an old term about sort of a pre-influencer term, but to be a maven and and to you know provide all this information downstream to lower-level technicians that can you know right there that’s that’s a huge problem, especially if you’re working in sort of geographically disparate regions where your best technician is in the middle of nowhere, and then they don’t have a ton of communication with your lower level technicians.

Jeff Hunter: Now you end up in this space where your best technicians are putting all their knowledge in the Ninja One, and then Katana is relaying all that information to your your entire help desk. And overall, that is just going to be something you know a tired metaphor, I know, but a rising tide that lifts all boats. It’s going to make your tech all your technicians better, whether that’s your technicians, your your level one technicians. It’ll make them better at their job, and it’ll make your most effective technicians better teachers and better communicators to the rest of your organization, which I think is a tremendous value.

Human-Centered AI and Human Judgment

Jo Peterson: I love that. You know, in sales and marketing, they have this term. It’s called win wire. This feels like an IT win wire, right, for the whole IT staff to to share. So I’d read through some of the technical documentation that was sent to me before we sit down to chat, and we sat down to chat, and I came across a couple terms and really liked them, and I wanted you to share what the thinking was behind them. So, Katana AI is what you folks are calling human-centered AI, and it’s focused on pragmatic force multipliers rather than completely replacing human technicians. Talk to me about what those terms mean to you organizationally, and what would you like the folks watching to know about them.

Jeff Hunter: Yeah, I think the fundamental piece for me to communicate here would be that you know we don’t believe that in endpoint management, in IT operations, that judgment can be substituted. AI can be great at surfacing information, providing information to a technician. It can be great at making decisions. It can be great at implementing those decisions very quickly. I think where we see the difficulty here is about the very last thing you want to have happen in IT is making a bad decision fast, and that is the recipe of AI in conjunction with the raw power of an endpoint management platform.

Jeff Hunter: There’s so much you can do with the endpoint management platform. You have this AI that can make you know very rapid decisions. Things can get out of hand very fast, and so we see that a human being being in the loop from the judgment layer that’s absolutely key towards effective and safe IT operations, and so that’s why we talk about human-centered AI. We fundamentally, at our core level, believe that the human being is inseparable from endpoint management.

Jeff Hunter: The day-to-day tasks may change, and we expect that they are going to change. They, in fact, have already changed rapidly in the last, I’d say, three to three to four years. But we expect that human beings still need to be involved. There is still an intrinsic element of a human being being required to provide that level of judgment, despite all the very impressive capability. Of AI, I think we still recognize that there is an element of judgment there that is missing.

Jeff Hunter: And again, if we take that bad judgment or you know failure in judgment during one critical moment, you end up in a situation where an AI thinks that the solution to a problem is to format the C drive. You know, and without any data, there can be no problems whatsoever, right? And so this is, you know, we just fundamentally believe that human beings and endpoint management; those are not things that are going to be separated. The nature of the work may change. You may go from being more of a musician who plays an individual instrument to more of a conductor who kind of plays the entire orchestra, you know. the The role may change, but fundamentally, the judgment of human beings in the decision making process for IT operations, I think, is is integral to to being successful, and will continue to be so.

Closing Remarks

Jo Peterson: Yeah, really important stuff. It’s great to keep learning with you, so thank you for taking time to visit today. And audience, thank you for joining. I hope you enjoyed this. I learned a lot, and I hope you did as well. We’ll see you next time.