Jakson OpenClaw täydellinen litterointi

platform. 00:05:09.279 --> 00:05:11.680 How hard is it to actually set this up? 00:05:11.680 --> 00:05:13.920 You mentioned VM and sandboxing. 00:05:14.319 --> 00:05:18.560 Well, it's it's it's fair, it's fairly simple, depending on which operating system you have. 00:05:18.560 --> 00:05:31.759 It's like one command line that you run, and then it does this type of interactive uh setup where you can define okay, which language model do you want to connect it to, which communication channel, how do you want to manage it? 00:05:31.759 --> 00:05:42.160 And then you define uh what kind of permissions you want it to run, and then you get access to a web dashboard that you can go in and set up agents and set up session control and so on. 00:05:42.160 --> 00:05:46.720 And the same also applies for the all the other options from Nvidia and Cisco as well. 00:05:46.720 --> 00:05:49.360 It's to like one command line, and you get it up and running quite quickly. 00:05:49.360 --> 00:05:59.199 But but if you want to have it like in a virtualized environment, sandbox running, there's some additional configuration, but it's not that much work as long as you know the correct parameters. 00:05:59.920 --> 00:06:03.600 So this is literally a YouTube video way, like a tutorial. 00:06:03.600 --> 00:06:04.319 Yeah. 00:06:04.319 --> 00:06:07.519 But I should not be doing that on my work computer. 00:06:08.160 --> 00:06:10.000 No, it's not a good idea. 00:06:10.000 --> 00:06:10.560 Why not? 00:06:10.560 --> 00:06:14.240 I don't think your IT department's gonna be fairly uh happy for that. 00:06:14.240 --> 00:06:17.279 But I think I think the problem is okay, I can install it. 00:06:17.279 --> 00:06:22.879 Nothing bad is gonna happen unless I give it full permissions and I have full administrator rights on my machine. 00:06:22.879 --> 00:06:27.040 I can give you one scenario which I saw with this was on social media. 00:06:27.040 --> 00:06:40.240 There was some VP at Meta which set up OpenClaw against their email or Gmail account, and then it started going in and deleting a bunch of different emails because of the instructions that she gave the chatbot. 00:06:40.240 --> 00:06:48.000 So, of course, as long as they have, as long as the agent has permission to do so and you give it wrong instructions, well, bad things can happen. 00:06:48.639 --> 00:06:50.240 I was really surprised by that story. 00:06:50.240 --> 00:06:53.600 It's just like you work for Meta and you posted this openly. 00:06:53.600 --> 00:06:54.160 Like, why? 00:06:54.160 --> 00:06:55.199 It doesn't make you look uh. 00:06:55.199 --> 00:06:58.720 But she did get a lot of attention and uh made me smile. 00:06:58.720 --> 00:07:06.560 So I'm wondering with this connection with I heard that the whole world was sold out for Mac Mini, which I don't understand. 00:07:06.560 --> 00:07:08.720 What does that Apple product have to do with this? 00:07:08.959 --> 00:07:10.319 Yeah, well, there's two parts. 00:07:10.319 --> 00:07:19.519 Uh, first off, that you can cluster together Mac minis and get a fairly good set of uh virtual remains running, so you can run local language models. 00:07:19.519 --> 00:07:31.279 Now there's also additional framework that you you can cluster together like three, four, five Mac minis, so and have like uh big virtual graphic cards on to on top, which you can run local language models. 00:07:31.279 --> 00:07:36.079 But the other part is that you get access to the Mac ecosystem, so iMessage and so on. 00:07:36.639 --> 00:07:36.879 Right. 00:07:37.120 --> 00:07:41.600 So that way you can connect OpenClaw to iMessage and manage it remotely from there. 00:07:41.600 --> 00:07:42.319 Yeah. 00:07:42.879 --> 00:07:44.480 And that made them sell out, yeah. 00:07:44.720 --> 00:07:44.959 Yeah. 00:07:44.959 --> 00:07:51.920 And so it's it's not that you use the Mac Mini for local processing, it's just that you get access to those Apple ecosystems. 00:07:51.920 --> 00:07:54.480 You know, and it looks like it looks nice on your desk, right? 00:07:54.879 --> 00:07:55.439 Right, right. 00:07:55.680 --> 00:07:56.560 Did you buy one? 00:07:56.560 --> 00:07:57.680 No, I didn't. 00:07:57.920 --> 00:07:58.240 No. 00:07:58.480 --> 00:08:06.079 You have this from I I have some dedicated Nooks with some uh like a little bit more graphics uh power or graphics card installed. 00:08:06.079 --> 00:08:09.920 So it's uh has a little bit more horse horsepower than the regular Mac Mini. 00:08:10.319 --> 00:08:10.720 Yeah. 00:08:10.720 --> 00:08:17.120 When it comes to the the risks associated with this, uh you know, the skills. 00:08:17.120 --> 00:08:19.680 So you're telling me about virus total and the skills. 00:08:19.680 --> 00:08:25.439 Run us through the skills risks and any other risks that you see with operating this type of technology. 00:08:25.839 --> 00:08:26.560 Yeah, sure. 00:08:26.560 --> 00:08:31.680 So skills is a fairly new standard in AI terms, at least. 00:08:31.680 --> 00:08:35.279 Not in personal life, but in AI terms, skills is a fairly new uh term. 00:08:35.279 --> 00:08:48.639 It was introduced by Entropic um not so long ago, but skills is essentially a markdown file, which can which tries to provide uh how you provide expertise to your virtual agents within a specific uh specific domain. 00:08:48.639 --> 00:08:55.360 Could be that you have a skill set for how you manage virtual machines, a skill set for how you do security. 00:08:55.360 --> 00:09:03.440 And these skills contain prompts and ways, how the language models is just like instructions. 00:09:03.440 --> 00:09:08.879 But of course, these skills can also reference scripts, CLI scripts, command line scripts. 00:09:08.879 --> 00:09:24.320 And the initial problem what happened was that uh OpenClaw had this marketplace, I don't remember the name Claude, Claude Hub or something, which people can create their own skills, publish it to a marketplace, and people could download them and use

them on their own OpenClaw instance. 00:09:24.320 --> 00:09:39.039 But what we saw is there was a lot of new skills that was published which contained malicious instructions, which could say that okay, I have this skill which is used to manage my Google Cloud or my Google email calendar. 00:09:39.039 --> 00:09:59.360 So uh when people downloaded the skill, they had a lot of uh hidden instructions and scripts included as part of the skill, which said that okay, when uh agent runs the skill, it would go in, fine-sensitive information in my email or calendar and send it to our third party. 00:09:59.360 --> 00:10:04.080 And there were thousands of different malicious skills being published to the marketplace. 00:10:04.080 --> 00:10:07.919 So when they saw that, okay, this is this is becoming a big problem. 00:10:07.919 --> 00:10:15.279 So what happened was that OpenClaw and Peter, the creator of uh OpenClaw, uh went to the interim partnership with VirusTotal. 00:10:15.279 --> 00:10:27.279 So now they uh VirusTotal will go in and scan every new skill that's being published to see if there's any type of malicious um malicious content uh as part of the skill that's being published. 00:10:28.960 --> 00:10:33.519 Why has nothing really bad happened yet? 00:10:33.519 --> 00:10:44.799 It's very underwhelming, I feel like, when uh everybody's talking about how you know scary the Segentic future is and everything, but I I've literally the headlines maybe there's just so much other drama going on in the world. 00:10:44.799 --> 00:10:49.919 Uh I mean, besides that meta incident, there really hasn't been that much else. 00:10:50.000 --> 00:10:52.320 Or no, no, not that I've seen. 00:10:52.320 --> 00:10:57.919 Uh I think it's as I said, I think it's drowning in other things that are happening uh worldwide. 00:10:57.919 --> 00:11:02.240 Um well, I have one part though that I know happened. 00:11:02.240 --> 00:11:18.080 Uh AquaSecurity, which is a company that has created an open source framework called Trivi, which is used to scan uh for, let's say, bad configuration or uh bad settings in Terraform code and so on. 00:11:18.080 --> 00:11:27.759 Now they also have their uh their tool publicly available on GitHub, and their uh GitHub of repository was compromised a couple of weeks ago. 00:11:27.759 --> 00:11:38.320 What happened was that when you ran and installed Trivi, it would also install OpenClaw automatically because of the way that they compromised the GitHub repository. 00:11:38.320 --> 00:11:46.639 So even though anything bad didn't happen, but what happened was that all the users that ran Trivi would also install OpenClaw automatically. 00:11:46.639 --> 00:11:54.559 And uh two weeks later, probably one week from now, or one week back in time, um, their entire GitHub repository was also compromised. 00:11:54.559 --> 00:12:09.200 Oh, which also made this supply chain attack because a lot of companies are running Tree, and attackers gained access to a lot of different organizations now, and this is now populating it into different organizations and companies worldwide. 00:12:09.200 --> 00:12:12.799 I which I just read a little bit earlier today on an article. 00:12:12.799 --> 00:12:33.840 And of course, this might stem from one person inside running OpenClaw and installed a malicious skill, and suddenly some credentials or API keys were sent to somewhere somewhere else, and then okay, now we got access to this GitHub repository, and then we can start moving forward and try to gain access to other parts as well. 00:12:33.840 --> 00:12:40.480 Could be, I'm speculating, but uh I think this is something that we're gonna see more and more, right? 00:12:40.480 --> 00:13:09.200 Where some individual could be a developer, could be some working on the IT department or some regular per person working in administration installing this agent, not setting it up properly because you know it requires some skill to understand how you can set it up in a secure manner, and suddenly you give the agent too much access to something, could be application or files or calendar or whatever, and then suddenly you have this malicious skill coming in, and then uh information is flying somewhere else. 00:13:10.799 --> 00:13:18.960 We mentioned um Cisco's defense claw, which is supposed to be a more enterprise, uh if I could say enterprise, a more business friendly version of this. 00:13:18.960 --> 00:13:22.320 What are some of the like legit use cases that you can immediately see there? 00:13:22.320 --> 00:13:29.519 And are are they the same, I guess, is it the same risks for a business, just a bigger scale than it is for personal use? 00:13:30.000 --> 00:13:32.799 Well, let's look at the blast radius. 00:13:32.799 --> 00:13:42.559 If someone were able to access my open claw instance, of course, the blast radius would be that machine that is running on or my local network. 00:13:42.559 --> 00:13:45.919 Your light yeah, my Philips U lights. 00:13:45.919 --> 00:13:47.120 That's the blast radius. 00:13:47.120 --> 00:13:49.919 Of course, I'm gonna get annoyed, but it's not more than that. 00:13:49.919 --> 00:14:14.240 Of course, if someone set up an open claw instance running within their infrastructure, exposed it to the internet using some form of community, let's say IRC, you have an agent there, and then someone gets access to that agent and says, Oh, I want you to install this executable file on that machine so that they can get access remotely through some form of VNC view or something like that. 00:14:14.240 --> 00:14:19.360 And then it's one way to get through your firewall and then get to the inside of your infrastructure. 00:14:19.360 --> 00:14:23.120 So of course the blast radius can now suddenly become a lot larger. 00:14:23.120 --> 00:14:31.519 But again, it's I think it's how you set it up properly to make sure that the blast radius is uh as small as possible. 00:14:32.799 --> 00:14:42.399 How I assume that companies

should be right now sort of scanning their environment for just to make sure that they have governance over who has installed this. 00:14:42.399 --> 00:14:44.639 That's possible to do, right? 00:14:44.639 --> 00:14:45.279 Correct? 00:14:45.840 --> 00:14:46.320 Yeah, yeah. 00:14:46.320 --> 00:14:51.360 Most EDR tools you can scan for executables and new installed software. 00:14:51.360 --> 00:14:57.600 So it's uh as long as you have EDR capabilities in place, it's fairly easy to find if the employees have installed this or not. 00:14:58.000 --> 00:15:07.759 What other things would you be doing if you were head of security for a company, knowing what you know on the defensive side, just to make sure that this bad things don't happen through the use of this technology? 00:15:08.320 --> 00:15:27.200 Well, we have well we'll always see that employees are fairly a lot of people are really very curious and very forward or very open to try out new things, and they see that, oh, this is something that I can try out, and they try it at home, and then they see different use cases, how they can use this at work as well. 00:15:27.200 --> 00:15:35.919 And I've had so many talks about this last couple of months saying that, oh, we can't we just install OpenClaw for our business and try to solve these and these issues. 00:15:35.919 --> 00:15:46.799 But I think it's from a like CISO perspective, see that okay, what kind of alternatives do we have where we can have better control but still try and solve the same use cases? 00:15:46.799 --> 00:16:01.360 Because the way that I see now, and as you said, like I OpenClaw is not an enterprise-friendly tool, it lacks insight and policies that allow us to manage and control this in a centralized way. 00:16:01.360 --> 00:16:09.600 So I would look for alternatives if you have a lot of people using OpenClaw, say that okay, what's the use case that you see using this tool for? 00:16:09.600 --> 00:16:16.879 And secondly, okay, can we have alternatives in place that can provide its capabilities but allow us to manage it properly? 00:16:17.759 --> 00:16:26.000 It just makes me, I think we talked about this last time that uh the CISO is the HR for AI usage or should be. 00:16:26.000 --> 00:16:43.679 Because it would be ideal if you know the developers, and I've had this conversation with uh clients already, that a developer or people in the business come to security and say, I want to do X, Y, and Z, and then they just say no, where they should be saying, Yeah, give me a week and I'll figure it out or something like give me give me some time. 00:16:43.679 --> 00:16:47.519 What has your experience been with dealing with security teams? 00:16:47.519 --> 00:16:51.600 Have you met any security teams that have actually taken that responsibility and and done good things so far? 00:16:51.919 --> 00:16:52.399 Yeah, yeah. 00:16:52.399 --> 00:16:55.200 Well, I've met on both parts of that scale. 00:16:55.200 --> 00:17:02.960 We've had those, I say, gatekeepers saying that no, no, we uh we don't know what this is, and therefore we don't approve it yet, so we'll have to wait. 00:17:02.960 --> 00:17:13.519 And then we have those other parts saying that okay, this these new capabilities and agents are something that's gonna empower our developers because they see a lot of benefit using it already. 00:17:13.519 --> 00:17:16.240 So we we need to figure out how we can solve this. 00:17:16.240 --> 00:17:39.039 So I'm now seeing more and more IT security teams trying to be more proactive, trying to understand the needs of the business and the developers, saying that okay, we need to make sure that we can provide capabilities that allow us to remain control, uh, but still allow them to use these new tools capabilities that are being uh being um delivered to the market. 00:17:39.039 --> 00:17:52.000 I think that the main problem is that there's so many different tools and agents and capabilities, and there's no single way to let's say govern these agents on a large scale. 00:17:52.000 --> 00:17:55.519 So it's a fairly fairly young ecosystem. 00:17:55.519 --> 00:17:58.559 So it also makes it even more complex to manage. 00:17:58.559 --> 00:18:03.839 Um, so many cases we need to define okay, these are the pre-approved tools that you can use. 00:18:03.839 --> 00:18:09.440 And if you have a specific use case for a new tool, then we need to discuss it and figure out how we can solve it. 00:18:09.759 --> 00:18:14.000 It's like security needs to go in a bunker for a few weeks and just go figure shit out. 00:18:14.000 --> 00:18:22.160 Uh, but they have to worry about the rest of the real job, which is security operations and everything else that we had to deal with before AI. 00:18:22.559 --> 00:18:26.640 And then you come back after those two weeks and the landscape is totally changed, right? 00:18:26.960 --> 00:18:27.519 Yeah. 00:18:27.519 --> 00:18:28.640 Typical. 00:18:28.640 --> 00:18:30.720 Get used to it, it's not gonna change. 00:18:30.720 --> 00:18:34.880 Uh I'm gonna I want to get back to the governance part because that's the question I get the most often. 00:18:34.880 --> 00:18:36.079 How do we govern these things? 00:18:36.079 --> 00:18:38.240 But another thing I want to talk about is the benefits. 00:18:38.240 --> 00:18:40.640 You know, you mentioned the benefits to developers. 00:18:40.640 --> 00:18:47.920 Like AI, I feel like AI has mostly benefited developers of all these cases I've heard. 00:18:47.920 --> 00:18:51.920 Developers have the the largest change in their daily life. 00:18:51.920 --> 00:18:54.160 What are some, or first of all, do you agree to that? 00:18:54.160 --> 00:19:03.200 And second of all, what are some of the other use cases that you've actually seen like value being brought to the business using agentic features? 00:19:03.839 --> 00:19:13.839 Yeah, when it comes to agents, I I totally agree that uh I've talked with so many different developer teams saying

that uh the use of AI has made their job a lot easier. 00:19:13.839 --> 00:19:23.519 And of course, with the new improvements, with the new models that are coming constantly, that makes it easier and easier to see all the improvements that they get. 00:19:23.519 --> 00:19:38.559 And I I saw a blog post on GitHub a couple of weeks ago where they published and research or some research on how much code is automatically approved based upon which kind of language model that they had. 00:19:38.559 --> 00:19:53.920 I think that when it came to the latest versions of Claude, uh Cloud 4.5 or 4.6, uh, close to 80% of the code was automatically approved because the quality was so good compared to the older versions, which were close to 50, 60 percent. 00:19:53.920 --> 00:20:03.039 Now, of course, I think there's a lot of ongoing discussions in terms of okay, but how much time does each developer save by using these new tools? 00:20:03.039 --> 00:20:11.759 And of course, it might not be that they save a lot of time, but of course, it makes it a lot easier for them to actually troubleshoot or understand. 00:20:11.759 --> 00:20:17.359 And else I think that's gonna give a lot of additional value for security as well. 00:20:17.359 --> 00:20:21.440 Just like understanding, okay, what kind of security bugs do we have in this code? 00:20:21.440 --> 00:20:37.039 And just deploying an agent which goes through every part of the source code and tries to see, okay, these and these vulnerabilities are something that we might might not have been able to detect before until we unleash this language model on it. 00:20:37.599 --> 00:20:41.359 It's funny because now we're using some technology to make the code. 00:20:41.359 --> 00:20:49.119 You're probably using the same technology to scan it for vulnerabilities, which is an interesting sort of situation we've ended up at. 00:20:49.119 --> 00:20:54.240 When a client comes to us and says, hey, we need governance around this, where do we even start? 00:20:54.240 --> 00:21:07.119 Because I feel like that is the that is probably the top top thing that every security team this year should be putting, using, dedicating some time to is how do you govern this agentic future? 00:21:07.119 --> 00:21:11.680 What is your answer to that as of the 31st of March 2026? 00:21:12.000 --> 00:21:12.559 Yeah. 00:21:12.559 --> 00:21:15.119 I would say I would say I don't have an answer. 00:21:15.119 --> 00:21:33.519 I I think the issue is that the the ecosystem is quite fragmented because if we look at developers, they have well GitHub Copilot, uh cursor, cloud code, open AI code codex, so many different AI or developed agent frameworks. 00:21:33.519 --> 00:21:48.400 Then we have the more let's say line of business automation agents, which are built using some form of agent SDK, so Microsoft Agent Framework or Google Agent Development Kits or Langgraph Langchain, so many there as well. 00:21:48.400 --> 00:21:57.359 And then we have like the more

power users or office users, which use Copilot 365 or Cloud Cowork or something like that. 00:21:57.359 --> 00:21:59.759 So, of course, we have all these different use cases. 00:21:59.759 --> 00:22:02.640 Now, which are using genitive AI. 00:22:02.640 --> 00:22:11.519 And some of them are running agents that interact locally with the machine, some are running in cloud, some are just regular chatbots which has some form of automation. 00:22:11.519 --> 00:22:19.200 And there's no single way to control all of these using the same set of tools. 00:22:19.200 --> 00:22:44.880 So we need to create some common guidelines to say that okay, if you run some form of agent, you have to write you have to make sure that you can use the you have to make sure that you have these guidelines in place, follow these rules, might have some uh way to provide insights or uh observability into the how the agents are used, but you need to have multiple ways to manage them properly. 00:22:44.880 --> 00:23:01.680 So for if you have a lot of agents using GitHub Copilot, well, you need to set up policies there to make sure that you control what kind of features are in place or can be used, what kind of features there, what kind of language models that can be used, what kind of insight that you get to make sure that it's used properly. 00:23:01.680 --> 00:23:07.680 And you need to set up the same if you want to use um other frameworks using public cloud providers. 00:23:07.680 --> 00:23:14.160 So when you have something that's talking directly with a language model through their API, which has their own set of tools. 00:23:14.160 --> 00:23:22.160 So you need to have different toolboxes in place to try to govern these agents across different areas or different parts of the workforce. 00:23:22.720 --> 00:23:31.599 It sounds like you are a proponent or you're a fan of the platform team, I guess, then kind of like developers, you know, these guardrails. 00:23:31.599 --> 00:23:34.720 That needs to be done today, but with AI. 00:23:34.720 --> 00:23:41.440 And then I do agree to do you use the same people, or should that be a security team now? 00:23:42.559 --> 00:23:45.599 Um I haven't figured that out yet. 00:23:45.599 --> 00:23:55.599 I think it all depends on because it requires it requires a new set of uh expertise or knowledge, if you will, to understand how to use this properly. 00:23:55.599 --> 00:23:59.680 I think it all depends on how mature the team is. 00:23:59.680 --> 00:24:10.559 Uh of course, if the platform team is loves to play around with new technology, has a fairly good understanding of the tools and ecosystem finals, put the put the responsibility there. 00:24:10.559 --> 00:24:18.640 Of course, the central security team is, of course, in most cases still responsible for having these common set of guidelines, if you will. 00:24:18.640 --> 00:24:23.839 Uh that always that should always be applied to every part of the organization. 00:24:24.720 --> 00:24:34.559 There was a report that came out and it was like only 4% of those that have invested in AI, whatever that means under the umbrella term AI, have seen enterprise benefits. 00:24:34.559 --> 00:24:36.960 Is that still how you look at it? 00:24:36.960 --> 00:24:41.039 Or what's your view again as of the 31st of March 2026? 00:24:42.400 --> 00:24:48.079 Well, I can just start with a simple example, simple example that provides referred investment. 00:24:48.079 --> 00:25:10.240 I and I'm not trying to advertise for some specific company now, but let's say that we have a certain collaboration platform where you have now virtual agents that can do transcription and do um write uh create meeting notes reference or create a create a summary of the meeting summaries, thank you, and also create to-do lists or to-do tasks automatically. 00:25:10.240 --> 00:25:12.880 That there just saves a lot of time. 00:25:12.880 --> 00:25:14.400 Absolutely. 00:25:14.400 --> 00:25:19.839 Um even though it's probably well, and of course, this is something that these tools are being used every day. 00:25:19.839 --> 00:25:38.400 And of course, if you can figure okay, how many meetings do we have within this company in a week, how many hours are being saved on a daily basis just by having this single, pretty simple uh virtual agent that is running and collecting all the notes that's being set and creating to do to do tasks automatically. 00:25:38.400 --> 00:25:41.279 So, of course, pretty simple. 00:25:41.279 --> 00:25:51.200 And then we have uh use cases to do um automatic uh or OCR, digitalizing paper with content. 00:25:51.200 --> 00:25:55.200 That's something that still still takes a lot of time because you need to scan the content. 00:25:55.200 --> 00:26:02.640 Now we have language models that can do this uh 10 times faster and much more accurate compared to traditional OCR. 00:26:02.640 --> 00:26:05.599 And this that's a fairly good use case, but it's simple. 00:26:05.599 --> 00:26:20.240 And then we have a lot more complex use cases now, which can uh automatically handle every email that's coming in, uh look at correspondence, and define okay, which direction should this email being sent to. 00:26:20.240 --> 00:26:30.799 Because let's say you're a municipality, you need to sort out all emails incoming and need to reroute it or redirect it, forward it to the right um um right recipient. 00:26:30.799 --> 00:26:35.119 Of course, there's some additional use cases that we also see uh sparing save a lot of time. 00:26:35.119 --> 00:26:42.079 And um I had another use case that I thought of, but now it slipped my mind. 00:26:42.400 --> 00:26:56.319 I'll I'll take one for uh that I heard at the conference, um, or two actually, why you think one of them was a it was a guy that was uh trying to revolutionize the renewal process, uh, you know, selling licenses for on behalf of vendors. 00:26:56.319 --> 00:27:10.799 And he actually uh he has a bunch of junior salespeople and he

transcribes everything they're saying, runs it through an agent so that they they get feedback based on their call, uh, which I would be super scared if I had some agent listening to everything I'm saying with my clients. 00:27:10.799 --> 00:27:18.720 Number one, because that's kind of like a security risk, or it would be in my line of work, but also just because now my boss knows how bad I am at my job. 00:27:18.720 --> 00:27:25.920 So that was one, and one of the other startups, um, yeah, I you know how call centers are being tricked into giving credentials away and whatnot. 00:27:25.920 --> 00:27:37.440 Um that it was just analyzing the uh the calls or the you know chats going towards service desk to understand all it's very it's sentiment analysis. 00:27:37.440 --> 00:27:38.480 Like, are they asking for something? 00:27:38.480 --> 00:27:39.759 Are they asking for it now? 00:27:39.759 --> 00:27:46.799 Uh gives them a risk score and it lets the help desk know on the other side that like you are likely trying to, this is likely bullshit, right? 00:27:46.799 --> 00:27:48.079 Really simple use cases. 00:27:48.079 --> 00:27:51.440 So I guess the people started with the low-hanging fruits, which is good. 00:27:51.759 --> 00:28:02.160 Yeah, and and I I know there's a lot of the use cases in Norway which are using some some simple, some more advanced uh agents that being set up. 00:28:02.160 --> 00:28:11.359 I know that the public um public roads, Southern Zweg Westin also has some examples that it published online on um webinar that I saw a couple of weeks ago. 00:28:11.359 --> 00:28:21.359 So I see that I think that uh the most companies have like this uh when they look at AI and say, okay, how can we do some quick wins? 00:28:21.359 --> 00:28:24.480 We have this specific use case and we have this budget. 00:28:24.480 --> 00:28:26.640 How can we use AI to try and solve this? 00:28:26.640 --> 00:28:29.440 And they create a kind of could be fairly simple one. 00:28:29.440 --> 00:28:41.519 Okay, they get knowledge, they get more understanding, and um then they mature a little bit more in terms of using AI, and then they start to uh add more and more use cases uh on top. 00:28:41.519 --> 00:29:06.720 So I think that uh after like the 31st of March 2026 and the remaining or remaining of 2026, we'll see a lot more use cases and agents being uh created and also more public references because I think we got to the point where these agents or these language models have much higher accuracy, can handle much more content than they could before. 00:29:06.720 --> 00:29:24.240 And of course, now that they can interact with uh command line, they can interact with the with a with your machine so they can move around uh in a machine to actually do things that traditional RPA has done before, uh, which much higher accuracy as well compared to the traditional human. 00:29:24.240 --> 00:29:28.640 I think we'll have more of these, let's say, enterprise use cases being solved with agents. 00:29:30.720 --> 00:29:41.279 And uh based on your Stouton's Vivest example, and yeah, they're the ones that control the roads basically, a bunch of cameras reading what are those car car licenses numbers. 00:29:41.279 --> 00:29:47.920 There's also a case here for what they call it, multimodal, where pictures and voices are being used. 00:29:47.920 --> 00:29:57.200 So I guess as technology advances in those fields, like I I have for some reason I have a feeling that Google is best with like picture generation and understanding pictures and stuff. 00:29:57.200 --> 00:30:01.119 Then once that gets really good, then there'll be even more use cases that are going to be available. 00:30:01.119 --> 00:30:03.440 And it's not just text, I guess. 00:30:03.759 --> 00:30:05.680 If that made any sense, yeah, yeah, yeah. 00:30:05.680 --> 00:30:07.039 So it totally makes sense. 00:30:07.039 --> 00:30:19.440 And just think about like surveillance, where you can attach a video stream to a language model and see, okay, if there's anything suspicious going on or certain things you actually should look for. 00:30:19.440 --> 00:30:26.000 Uh the language model cannot and uh let's say let's go good, let's take Google, for example, Gemini. 00:30:26.000 --> 00:30:37.680 Uh, it can handle upwards to one and a half hour of video content, analyze it and specify okay, what happened in this video, uh, what were the persons involved or objects and that in this view. 00:30:37.680 --> 00:30:41.680 Let's say, like OCR, that's a capability that multimodal has. 00:30:41.680 --> 00:30:49.920 We also have now uh language models that create smaller language models that can run on your phone for image recognition. 00:30:49.920 --> 00:31:10.559 So let's say you're like an electrician working in the field and you need to troubleshoot something, and then you can have an assistant running on your phone, and you can just take a picture of the instrument panel or something that you're troubleshooting, and then the agent can talk to you directly on your phone where you might not have internet access access at all and say, okay, this is the way to troubleshoot this and this. 00:31:11.039 --> 00:31:11.920 Awesome. 00:31:11.920 --> 00:31:14.000 Ah, the feature is so cool. 00:31:15.039 --> 00:31:27.519 Yeah, and the the cool part is that we're just getting started because uh if we look at the let's say last year or so, it's quite it's been quite hectic, like so many new capabilities being pushed out. 00:31:27.519 --> 00:31:35.119 And now we have uh investments up towards 900, uh 9,000 billion dollars. 00:31:35.119 --> 00:31:36.480 No, billion dollars. 00:31:36.480 --> 00:31:37.440 9 trillion dollars. 00:31:37.440 --> 00:31:46.079 Being invested into building new AI data centers, including two small ones in Norway, but on a global scale. 00:31:46.079 --> 00:32:10.319 And of course, the the big problem that has been for these big uh AI vendors or AI companies, Google, uh Anthropic, and OpenAI has been access to computing hardware or AI hardware, and now this is being uh solved, and this that means that we'll get new models quicker, stronger, faster, and more powerful compared to the models that we have today. 00:32:10.720 --> 00:32:11.359 Yeah. 00:32:11.359 --> 00:32:13.839 Myus, thank you so much for your time. 00:32:13.839 --> 00:32:14.640 You're a legend. 00:32:14.640 --> 00:32:18.400 Uh, and I am as always looking forward to speaking with you next time on the podcast. 00:32:18.400 --> 00:32:18.880 Take care. 00:32:18.880 --> 00:32:19.200 Thank you. 00:32:19.200 --> 00:32:20.160 Thank you for having me. 00:32:20.160 --> 00:32:20.720 Bye. 00:32:20.720 --> 00:32:21.680 Ciao. 00:32:23.519 --> 00:32:25.359 Well, that's all for today, folks. 00:32:25.359 --> 00:32:28.079 Thank you for tuning in to the mnemonic security podcast. 00:32:28.079 --> 00:32:37.519 If you have any concepts or ideas that you'd like us to discuss on future episodes, please feel free to hit me up on LinkedIn or to send us a mail to podcast at mnemonic.no. 00:32:37.519 --> 00:32:40.960 Thank you for listening, and we'll see you next time.