aisy investigates every finding your scanners, pentests and bug bounty produce, and learns how your company works from each one. A new finding then arrives with its cause, its owner and the fix.
Queue
QUA-4411
Apache HTTP Server flaw on billing-02
Qualys · CVE-2024-38476 · Critical
Why it matters here
Returns each time billing-02 redeploys.
Closed as fixed in March and June (SEC-3120, SEC-3877)
Each redeploy rebuilds it from the 2024 image pinned in infra/base.tf
6 other servers run the same image
Recommended fix
Update the image pinned in infra/base.tf
Resolves this finding and 6 other tickets
Works on the findings and tickets you already have.
Gartner now ranks AI discovery of vulnerabilities as the top emerging risk for companies. The median time to patch rose to 43 days, and only 26% of known-exploited vulnerabilities were fully fixed.
Sources: Gartner, August 2026, Verizon DBIR 2026
1
A critical lands. Does it matter here?
aisy answers the questions the scanner can’t, from your own tools and its own checks. When it can’t answer one, it says who can.
2
Leadership asks how bad it could get.
aisy sits on top of the tools you already run and joins what each one knows. This answer came from a Terraform file, an outside scan, a Jira comment and a Wiz permission.
3
Seven tickets turn out to be one cause.
Three sources reported the same flaw as seven tickets. One change closes them all, and the cause is gone.
4
A change is about to undo the fix.
aisy knows why the last seven happened, so it comments on the pull request before the regression ships.

Queue
QUA-4411
Apache HTTP Server flaw on billing-02
What decides it here
4 answered · 1 open
Reachable from the internet?
Reached through the public load balancer
Affected feature in use?
Proxies the invoice backend (httpd.conf)
Exploited in the wild?
No known exploitation or public exploit
A regression?
Regressed twice (SEC-3120, SEC-3877)
Owner known?
infra/base.tf has no owner
What it means
Exposed and regressing: fix the image this sprint.
Ask the platform team who owns billing-base.
1
A critical lands. Does it matter here?
aisy answers the questions the scanner can’t, from your own tools and its own checks. When it can’t answer one, it says who can.

Queue
QUA-4411
Apache HTTP Server flaw on billing-02
What decides it here
4 answered · 1 open
Reachable from the internet?
Reached through the public load balancer
Affected feature in use?
Proxies the invoice backend (httpd.conf)
Exploited in the wild?
No known exploitation or public exploit
A regression?
Regressed twice (SEC-3120, SEC-3877)
Owner known?
infra/base.tf has no owner
What it means
Exposed and regressing: fix the image this sprint.
Ask the platform team who owns billing-base.
2
Leadership asks how bad it could get.
aisy sits on top of the tools you already run and joins what each one knows. This answer came from a Terraform file, an outside scan, a Jira comment and a Wiz permission.

Qualys
Apache flaw reported on billing-02
Code review
billing-02edge load balancerbilling.mostlyfine.ioinfra/edge.tf
Outside scan
billing.mostlyfine.io answers from the internet
SEC-3877
Priya: “Patched and restarted it as the billing service account.”
Wiz
The billing service account can read the payments database
aisy learns
billing-02 is open to the internet, and the account it runs as can read payment data.
3
Seven tickets turn out to be one cause.
Three sources reported the same flaw as seven tickets. One change closes them all, and the cause is gone.

Queue
QUA-4411
Apache HTTP Server flaw on billing-02
Recommended fix
Update billing-base in infra/base.tf and redeploy
Resolves 7 tickets across 4 services
Tickets this fix resolves
7 tickets
QUA-3962
Apache HTTP Server flaw on billing-01
Critical
QUA-4411
Apache HTTP Server flaw on billing-02this ticket
Critical
WIZ-1187
Outdated httpd in the billing-03 image
High
PLAT-2210
Upgrade Apache on invoices-01
High
WIZ-1203
CVE-2024-38476 on payouts-01
Critical
QUA-4127
Apache 2.4.58 multiple vulnerabilities, payouts-02
Critical
QUA-4416
Apache HTTP Server flaw on reports-01
Critical
4
A change is about to undo the fix.
aisy knows why the last seven happened, so it comments on the pull request before the regression ships.

mostlyfine / infra
Add invoices-02 #812
platform-team wants to merge 1 commit into main
aisy
botcommented 2 minutes ago
This pins an image with a known Apache flaw (CVE-2024-38476).
billing-base 2024-11 caused QUA-4411 and 6 other tickets, closed last week. The patched image is 2026-09.
Suggested change
Attackers now use a flaw 7 days before its patch exists, on average. You cannot stop a vendor breach or a zero-day, but you can limit how far one reaches inside your company. aisy shows where that reach is wider than it has to be.
Source: Google Mandiant, M-Trends 2026
212deploys in one week
41new findings
9vendor advisories
3needed you

Stale risk acceptance
SEC-2291
“Unpatched until December. The portal is internal only.”
Outside scan
The partner API exposes it.
Reopen the exception
Sent to
#security

Data sensitivity change
SEC-2067
“Leave the sandbox out of scans. It holds no customer data.”
Access logs
Monday’s export job copied customer records into it.
Bring the sandbox back into scans
Sent to
the cloud team

Third-party access
SEC-1874
“The monitoring vendor needs three integrations.”
Access logs
Two have not been used in 90 days.
Remove the two unused integrations
A breach there then reaches less.
Sent to
#platform
Built by people who have done the work
A decade in offensive security, backed by researchers from DeepMind and practitioners from HP, Cisco, DocuSign, and the security research community.
Designed for real environments
We never train on your data. We come from a world where getting things wrong has real consequences, and that discipline extends to how we handle yours.

Vulnerability management that learns.
See how it would learn your environment.