January 2026

Why I Built aisy

Bringing the rigour of offensive security to enterprise defense

Shlomie Liberow

Founder & CEO, aisy

Share

I've sat in a room with hackers, staring at vulnerability leads that felt like they should work but weren't quite connecting. An issue here, a misconfiguration there: signs pointing somewhere interesting but no clear path to impact. Then I'd watch them spend 40, 50, 60 hours grinding until it clicked.

The ones who'd been doing this for years got faster. Not because they were smarter, but because they'd seen the patterns before. They knew which behaviors implied what, which scenarios led where. And what I noticed over time: hackers kept getting paid for variants of bugs we'd paid out the year before. Same root cause, different layer. They'd unpack the previous finding, map the constraints, then attack it from a new angle and land the same impact.

These companies weren't failing to fix bugs. They were fixing exactly what was reported. But nobody was giving them the context to see the actual problem: the systemic issue that kept spawning variants, and why it was important or a red herring.

Three Problems I Kept Seeing

In the past ten years hacking and running bug bounty programs for some of the world's leading brands, I identified three key problems:

The gap between offensive and defensive capabilities is widening. Attackers are using AI to find and exploit vulnerabilities at machine speed. Defenders need intelligence that actually understands attacker methodology, and another AI wrapper that just processes tickets faster won't give them that.

Security team burnout is at an all-time high. 46% of organizations report cyber fatigue. Smart people are leaving the field because they're tired of chasing tickets instead of doing meaningful security work. Defenders need to be freed up to be as effective as offensive security practitioners.

Security leaders are seeing their personal liability increase. Legislation means CISOs are personally on the hook. They need to actually know their risk posture, not just hope their tools are catching the right things. CISOs need to be able to say: "I know how we can be compromised, and what we're doing about it."

It's therefore a proud day today where we officially launch aisy, a solution that flips the current security model on its head, with $2.3M in pre-seed funding from AI specialists Flying Fish, cybersecurity focused fund Osney Capital, and early stage champions 6 Degrees Capital. We're bringing the rigour of offensive security to enterprise defense.

Defenders Need Offensive Security

My background is in bug bounty: the most concentrated, no-BS form of security. You show the bug or you don't get paid. No fluff, no false positives. Just impact. It's working for multinationals and governments who recognize the need for collaboration with the most creative minds in security to reduce risk.

That's the lens through which I want to help defenders. Bug bounty built momentum around the good guys finding the bugs in a way that hadn't been done before; a decade of hackers grinding on real systems and getting paid only when they proved impact. That's a lot of concentrated learning about what actually works: what vulnerabilities can be chained and what can't, what's exploitable versus theoretical. aisy brings that methodology to enterprise defense.

Threat Modelling Over Ticket Prioritization

Instead of starting with your ticket queue and filtering it down to answer "which of these 100,000 tickets should we fix?", aisy starts with what you really care about: your threat models. What actually keeps you up at night? Account takeovers? Data exfiltration? Supply chain compromise? Then we connect all the assets, findings, and attack paths that matter to each threat.

Say you're worried about OAuth abuse. aisy finds which assets use OAuth, pulls in bugs that directly and implicitly affect OAuth flows (open redirects, XSS variants, browser quirks), and maps them to intelligently inferred infrastructure relationships. We automatically discover that these 50 assets serve your payment platform, that those 30 are your customer support stack. An OAuth bug in customer-facing transactions gets treated very differently than one in internal CI/CD tooling, allowing correct judgment on priority and approach.

Not Just Another AI

The AI in aisy is the delivery mechanism for real expertise. I didn't just run bug bounty programs; I was a researcher myself. I've sat on both sides: finding the chains that lead to critical impact, and making the calls on thousands of incoming reports. aisy is built on that dual perspective: knowing what attackers look for and how defenders have to prioritize.

Like a bug hunter, we weigh the true worth of a vulnerability against the security makeup of the wider organization where it was found, without relying on CVSS scores.

On a major SaaS platform, I found a path traversal that bypassed an access control list when requests were prefixed a certain way. Minor on its own.

That traversal exposed internal endpoints including Swagger docs. Authenticated, low impact. But it also exposed a cache and routing management endpoint. Now it's a control-plane problem.

I found an XSS in one of the internal views. If a privileged session was in scope, you could move from UI execution into authenticated API access against infrastructure-wide systems.

No scanner flags this as critical. Each finding looks contained. The risk only shows up when you connect how routing, trust zones, documentation exposure, and UI execution interact. aisy is designed to close that exact gap: it looks at the risk in how systems interact, on top of individual vulnerabilities.

On the other side of the story, I've also spent the last decade making those decisions on how much a bug report was worth. I've made a call on over $20M worth of bug bounty rewards for global brands, based on the evidence that demonstrates a vulnerability's true impact to that company. We know how attackers think, how they chain low-severity findings into high-impact exploits, and what they ignore. That methodology is now working for your defense with aisy.

Treat The Cause, Not The Symptoms

Imagine fixing one systematic issue and watching 500 tickets change state. With aisy, you can identify the root causes that you can then address for maximum impact. A single decision can cascade across hundreds of tickets, reducing your backlog along with your risk.

As a CISO, we want to give you that personal confidence to be able to say "I know how we can be compromised, and what we're doing about it." You need to actually know what's going on and know, rather than hope, that your tools are catching the right things.

For security teams that are fed up of being seen as blockers, aisy bridges the gap between security and engineering, acting as a risk visibility and engineering productivity tool that engineering leaders can champion.

A Better Way Of Doing Security

My investors, my team, and I truly believe there is a better way to do security than battling endless backlogs of vulnerability tickets. AI is necessary to scale, but our AI's edge comes from the creative human ingenuity it takes to chain bugs and see the wider context.

Join our movement. Unclutter your backlog, liberate your teams, and regain control with a real risk reduction strategy.

Share

Get new posts by email

New posts only. Unsubscribe any time.

Shlomie Liberow, founder of aisy

Vulnerability management that learns.

Bring a recurring problem from your security backlog. We’ll look at what your team already knows, what it keeps re-checking, and how to get ahead of it.

Shlomie Liberow · Founder, aisy · shlomie@aisy.ai