Yuri3:28
Thank you so much Thomas and thank you everyone who came and I'm really grateful and I'm also grateful for the work we've done together to build this benchmark which is I think incredibly difficult for the models and actually shows some really really interesting leaps in places that I think we still have way to go. I guess the way we've been thinking about the problem and the reason we set out to do this is it's very clear that the economics of cyber are fundamentally shifting. There's this inherent thing that is inherent to cyber which is that attackers need to choose their resource really wisely. And if you sort of think about cyber as a house in a way then my job is to block every door and close every window and make sure that there's no way in. And the attacker's job is to find at least one seam, one crack, one thing I missed. And then once inside, my job is to put sensors and anything I can to keep them out. And the whole stack, the entire world of cyber that we've been building for the past 20ish years has been based on this economics that the attackers have to choose their targets and we do everything we can across it to protect ourselves. It is true that that is changing in really dramatic ways. The models are incredibly powerful. They're able to find a ton of primitives. They're able to find a bunch of zero day exploits. We're seeing this. There's so many news and chaos around this point. And on the other hand, it seems like we as defenders don't seem to be prepared for this world and the way that it's coming. And I actually think that I might be on the wrong one. What I want to show is sort of this idea of so if you think about the way cyber has been, this is definitely I think the way we've been thinking about AI and cyber for the past many many many months. And it's freaky and it's getting really scary. And this is my point on the house. And part of the reason we think this is happening is if cyber is this game of skill and speed, then a very skilled attacker using something like Mythos can now choose a bunch of targets all at once. That is a real reality that is quite scary. And the truth is the picture really doesn't change that much when we move to a really strong open source model as well. So the question is what do we do in this world where the economics of cyber offense are shifting so much? And part of the problem with the existing stack is that defensive systems have to operate at scale. And that means that we have always very limited human intervention. And so we're sort of bound by what the models can do out of the box. So if we live in this world where the models are becoming so powerful, advancing so fast, we think like Thomas said, the solution also has to be the models themselves. This is our first solution. We can just all go live in the woods and lock ourselves out. Another solution is to figure out how we get the models to be much much much more capable. We have no doubt that open source models have to be part of this solution because they allow for many things that we'll talk about as well and there's this deep need for collaboration. And so what I want to show you today and I see the clock ticking on me is sort of this theory that if we've already done this before for coding, we can do this for cyber. There's a reason to be optimistic, which is really controversial in the context of AI and cyber lately. We've done this before. I think if you go back a year, it was very clear that all of coding was going to be transformed thanks to the models getting better and better and better. And we're sort of seeing the early innings of that with cyber right now where everyone's talking about cyber and everyone's freaking out. But what if through very high quality evals, very high quality data, good benchmarks, we could get to a place where the attackers are simply outperformed by very very very good defenders. And so our goal in Arithmetic is to be able to get the models to be really capable at cyber security to the point where we can rebuild this new stack that's based on the models winning the models on the other side. So I'm really excited to show you Masov. It's our first benchmark that we're releasing. Our first fundamental idea is that we can't capture all of cyber in one singular benchmark. That's a bit like saying that swimming, an F1 driver, and a basketball player is the same thing. It doesn't work. And so we focus specifically on access control. Really quickly, why access control? It's sort of the first door to any target in cyber begins with my ability to get a foothold. So, if you think about an attacker on the one hand, they're trying to get to some privileged thing. If Thomas and I are working on the same company, I'm some ML engineer, he's an admin, what are the things? Can I find a way to do things that I'm not allowed to do? In my current privileged position, it actually leads to being the number one on the OWASP list and has created this sort of $30 billion industry and for years these are number one vulnerabilities. The reason they exist and this is to the ARC AGI point. These are logic based vulnerabilities. So it's not just about bugs in the code that I find and I need to patch. It's about very very very big systems and somewhere between them there's these logic breaks where it's possible that one thing checks for something specific in the code another checks for something else and that sort of leads to everything breaking and so what we're trying to do is we're trying to figure out how we get the models to really reason very very hard and not just do pattern matching that's where a lot of works goes into the data quality and our data is created first by humans I think that's really important right now to find out of distribution things we need humans to go do the search our team is all based on very deep vulnerability researchers and nerds who love to hack who are trying to get really really good at cyber at AI capabilities. So we find our own zero days in widely distributed open source software. We use that to create these real live huge environments of a bunch of different applications chained together that then allows us to basically create this blackbox setting where the model doesn't see the code and it doesn't know about the zero day because we found it ourselves and it has to find a way to reason across this entire surface and understand exactly what the exploitation is. And so to do that, we don't give it access to the internet or the codebase, but we do give it sort of all the basic tooling it would need to be able to execute a task well. And everything because the tasks are so difficult, everything has a deterministic grader. And so across the entire exploitation and the discovery chain, every single step can be deterministically verified, allowing us to see how deep it got within the chain. And finally, this is credit to Eugene from Entropic who we slightly stole this graphic from, but it really does capture really well the way we've set up our eval where basically you have inputs on the one hand based on a real zero days. The agent so we're thinking about as the model plus its harness and some blackbox tooling that has to find. Then we have a verifiable grader which is a binary pass. Was the model able to do something it wasn't allowed to do as an underprivileged user? And then we have our deterministic grading in every step along the way. So what I want to show you now is an illustration for all the security buffs in the room. It's an illustration guys. But the idea is how a real solve looks and fundamentally what we have here is a real task of ours where it's a chain between Keycloak, Vault, and a broker and I start as a very low privileged user. I need to figure out how to get to production code. So what we're going to see is a solve. Each one of our tasks has a solve script of what a real solution looks like. There's a real zero day that we found that we submitted for verification to the maintainers where there's a check whether I'm an admin or not. It only checks by name. And another aspect of this checks whether by ID. So that allows me as a user to change the name of the real admin inherit their privilege and then use that to escalate myself. And what I'm really trying to illustrate is sort of this long chain 16-step type of logic that the model has to do. And if it's not able to understand inherently the system, it's way too broad for it to test everything sort of shoot across the space. So what we're going to see now is a real attempt by GPT 5.5 and then Opus as well trying to solve this task. And what you're going to see is a sort of chaotic trying everything, jumping between everything, probing a bunch of different stuff. It does even reach the check, but it never makes the logical leap that it's supposed to be able to change the admin's own permission, the own name in order to bypass this permissioning. So, this is exactly what we're trying to test. Can the model understand leaps, logic leaps that are inherent to the system? A really important point just like ARC AGI, everything you do in a live system in permissioning changes other stuff in the system. So, the model needs to be able to hold this model of the world it's living in and iterate through it. And then fundamentally at the end of this it writes code. It writes exploitation code and it needs to be able to reason really really thinly and understand exactly what the exploitation is in order to be able to execute. And we can really see the difference between models that have succeeded some of the tests and models that haven't. And then now we're going to do something that I've been told to never do, which is show a live demo of a real system on stage. And so let's hope we don't get there. And I know we're basically out of time. So what we're seeing here is what's called Bach. It's our internal system because it's an orchestrator. This is how we run our actual eval. What we see is the actual results of the benchmark. The benchmark right now is incredibly hard. There's only one solve at K1. And then at K5 there is it remains only GPT and the public models is able to solve this. That's why the partial graders are so critical to be able to really see what the model is able to do and what and how deep within exploitation chain they can get. I'm going to load quickly the sort of the way we think about these environments which is because we're looking for performance over time. We really measure how capable is the model at making specific leaps. And so what you'll see is a results of exploitation on specific one of our environments. And then if we zoom in then you can really see how sort of GPT 5.5 is the only model that's able to make this leap. The model other models sort of have been able to reason across everything. If we look at the discovery phase they do capture nearly all the different information they need and they never are able to make the leap into what is the exploitation they need to do. This is exactly the type of capability that we believe. If every model in the world could get really really really good at doing this and very fast, that should give a lasting defense and capability to the defenders that the attackers simply don't have right now. And then finally, I think the way we sort of reason through these and work through them is quite cool and I want to show you. So again, if we go into one of our tasks called Fall Fall Time, we can really see sort of the way we spend our days, which is really really really trying to understand what are the specific failure modes a model does. You can see that this is longer reasoning, not because it's waiting for code to run. It's constantly working over three hours and it's still been unable to solve the tasks. And then I guess the way I spend all my day is quite literally going through all the traces of what the models did, why, and how. And I think my final point I want to make and I'll pass it back to Thomas is sort of next what if we can not just have this chart which is really cool sort of have this chart of a really super cool future model that's very very fast in its understanding of what the capability leaps need to be and I really believe that with everything happening now it is critical that we get cyber capabilities to the point where we can defend much much faster. The only way to replace the old stack is through the models. And I'll pass it back to Thomas. I think also the only way to do that is through a real array of strong open source models and collaboration that we can post train on and that we can post train to each network and to each environment as well.