Frequently Asked Questions

aisy works the security findings you already have, from scanners, pentests, bug bounty and old tickets. It maps your systems from the outside the way an attacker would, traces each finding to what caused it and what it can reach, and builds on what it learns. Then ask it anything in your own words: does that new CVE reach anything we care about, is anything like last month’s incident still out there, which of these 400 findings matter this week.

Security leaders whose scanners work fine but whose risk isn’t dropping. If deciding what to do about findings is now the hard part, we built aisy for you, whether you’re a mid-market team of three or an enterprise with sprawling surface. Your people stay in control. aisy does the gathering and the investigation, so your team starts every problem at the decision.

Vulnerability management treats your backlog as work to get through. We treat it as the best record anyone has of how your environment fails: every finding in it is evidence of something that already went wrong, and what caused one usually caused others. aisy works the backlog end to end, which is also the hardest way to learn an environment. That is why the understanding it builds answers questions well beyond which ticket is next.

Read: vulnerability prioritization beyond CVSS

A proactive check aisy runs for you. Take exceptions: aisy reads the ticket to learn why you accepted the risk and what that depends on, then tests those reasons as new findings arrive. When a finding breaks one, the team that owns it hears what changed and what to do.

The models write good code, and they get better every month. What they can’t see is your environment. A coding agent doesn’t know that a CloudFront domain came up twenty minutes ago on a route close to the finding in front of it, or that three teams have already broken this same auth flow in different ways. aisy works that out from your findings and hands it to whichever agent your developers already run, so what they write fits how your systems work.

Most reachability stops at the network: the vulnerability is real, but something in front of it blocks the path. We correlate code and dependencies as well. aisy traces which routes reach the vulnerable path, what conditions an exploit depends on, and whether those conditions hold in your environment. If a bug needs a parameter your code never passes, it isn’t your problem, and aisy shows you the code path that proves it.

Everyone can connect to the same data. The hard part is knowing what to ask of it. We don’t hand a model ten terabytes and ask it to find something interesting. aisy goes looking for specific patterns, because years of offensive work tell us which ones matter, and each answer narrows the next question. That is the difference between telling you an IP address exists and telling you why it matters.

Closer to continuous threat and exposure management than to an ASPM. An ASPM ranks findings by metadata you configure: service tiers, CMDB tags, policy rules. aisy works outside-in, chains findings the way an attacker would, and ties them to the outcomes you’re protecting. Your scanners and bug bounty feed it. The reasoning is aisy’s.

Yes, and validation is where we do the most work. Scoping and discovery tell you what exists; validation tells you what genuinely reaches something that matters, which is where most programs stall because it takes an expert an hour per finding. aisy does that work at the code and dependency level, then carries what it learned into the fix, so the same class of issue is less likely to ship again.

aisy doesn’t push code into your repos, so you stay in control of what ships. It works out the root cause, what an attacker gains and the pattern behind it, then hands that to the coding agents your developers already run: Claude Code, Cursor, Copilot. The fix happens in their workflow, as guidance while they build rather than a ticket six months later.

No, and most teams don’t have formal ones. Say what you’re worried about in plain language ("can anyone take over a customer account?", "tell me if that exposure comes back") and aisy works your findings against it. aisy builds the threat model for you, so there’s no document to maintain.

aisy ingests from wherever your findings already live: scanner output, pentest and bug bounty reports, compliance reviews, ticketing. Whatever shape it’s in, we’ll pull it in. It also builds its own view of what you expose to the internet before you connect anything, and pushes what it learns into the coding agents your developers already run.

Very little, and nothing in your stack changes. Developers keep their coding tools, security keeps its scanners. In return, aisy works the pattern behind the symptoms, so one root-cause fix can close dozens of findings. Your best people spend their time on the problems that need them.

Your Boundary Map comes first, within the first hour. aisy builds it from the outside, using only publicly observable data, before you connect anything. Once you connect your finding sources read-only, aisy completes its first investigation in that session.

Never. We don’t train on customer data, and what aisy knows about your environment stays yours. It is protected with end-to-end encryption, zero-trust access, and continuous monitoring. aisy is built by security professionals with deep bug bounty experience, including work alongside the UK MoD and the Pentagon.

Still have questions?

Can't find what you're looking for? We're here to help.