Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Aim Security announced an $18 million Series A on June 17, 2024, led by Canaan Partners, with seed investor YL Ventures participating. The round brought its reported funding to $28 million. Aim is no longer an independent startup: Cato Networks announced its acquisition on September 3, 2025, and said it planned to integrate Aim’s capabilities into its SASE platform. For investors and enterprise buyers, the funding story is now also a story about how AI security became part of a broader security platform.
What Aim Security raised and when
The Tel Aviv-based company announced its $18 million Series A on June 17, 2024. Canaan Partners led the round, and YL Ventures—already an investor—participated. Aim reported that its total funding had reached $28 million, including a $10 million seed round announced when it emerged from stealth in January 2024. The round’s stated uses included product development and global go-to-market expansion.
As an Amazon Associate I earn from qualifying purchases.
Aim was founded in 2022, according to Cato’s later acquisition announcement. Its co-founders were CEO Matan Getz and CTO Adir Gruss, whose backgrounds included cybersecurity and AI work associated with Israel’s Unit 8200. The phrase “four months out of stealth” describes the interval between the January public launch and the June Series A announcement; it does not mean the company had only four months of operating history. Aim’s funding announcement and SecurityWeek’s funding coverage provide the round and seed context.
The announcement characterized the financing as unusually fast, citing early enterprise traction, the founders’ experience, and reported revenue growth. It did not disclose revenue figures or provide data establishing an industry ranking for the speed of the Series A. The funding release also did not disclose valuation, customer count, retention, breach-prevention results, or independent product-performance testing.
#1 Best Overall
Why enterprises were looking for AI security controls
Aim’s investment case centered on a practical tension: employees and developers were adopting public AI tools, copilots, and internally built applications, while security teams still had to protect confidential data and meet privacy and compliance obligations. A blanket ban could obstruct useful work; unrestricted use could expose sensitive information or create new attack paths.
- Unmanaged AI use: Employees may use public chatbots or productivity tools outside approved processes, leaving security teams with limited visibility and policy control.
- Data exposure: Prompts, uploaded files, application context, or agent actions may carry confidential, regulated, or personal information to an AI service.
- Prompt injection and jailbreaks: Crafted instructions can try to override a model’s intended behavior or manipulate an AI application. Detection and filtering can reduce some risks, but are not a guaranteed defense against every attack.
- Tools, integrations, and supply chains: Models, plugins, data sources, agents, and connected tools introduce dependencies and permissions that need to be assessed alongside the model itself.
- Unsafe outputs and internal applications: A response may create operational, legal, compliance, or reputational risk, while a custom assistant may expose data or invoke tools in unintended ways.
Existing data-loss prevention, identity, application-security, and secure-access controls remain relevant, but each sees only part of the picture. AI-specific controls may need to inspect prompts, responses, model selection, and agent tool calls, while conventional controls still address permissions, endpoint security, network access, and application design. Filtering an interaction alone cannot correct excessive permissions, insecure agent workflows, or poisoned data, and it cannot guarantee that an AI answer is factually correct.
What Aim’s platform was meant to cover
The 2024 Series A positioning
At the time of the funding announcement, Aim described an enterprise-wide platform for public AI applications, enterprise copilots and chats, employee assistants, internally developed generative-AI applications, and developer use cases. The company said its controls addressed data security and privacy, compliance guardrails, prompt injection and jailbreaks, AI supply-chain vulnerabilities, and harmful or manipulated outputs. Those were company-stated capabilities, not an independent evaluation of their effectiveness.
Cato’s later product description
In its September 2025 acquisition announcement, Cato grouped Aim’s capabilities into three areas. This is a post-acquisition description and should not be read as proof that every capability was publicly available in the same form when Aim raised its Series A.
Rank #3
- Employee use of public AI: Discovery of shadow-AI use and monitoring or protection of end-user interactions. Cato also described support for public and enterprise AI agents, coding agents, and local agents using MCP servers.
- Private AI applications and agents: An “AI Firewall” for runtime AI attacks, with policy enforcement across users, agents, applications, and models, including on-premises and cloud data-center deployments.
- AI security posture management: Discovery and remediation of AI security and compliance risks, lifecycle checks during AI development, and scanning internal models for misconfiguration and vulnerabilities.
Cato said it acquired Aim to add these capabilities to its SASE Cloud Platform. The acquisition announcement described the product strategy; it did not publish comparative results showing that Aim outperformed other AI-security tools. Cato’s announcement sets out its acquisition rationale and its retrospective account of Aim’s product.
What the customer evidence does—and does not—show
Aim’s 2024 announcement cited traction in banking, insurance, healthcare, manufacturing, and defense. It included a testimonial from Finance of America CISO Drew Robertson describing coverage across public SaaS AI applications, enterprise chat, and internal development, with controls intended to reflect financial-sector regulation and customer-data concerns. That testimonial is evidence of a customer use case, not independent proof of security efficacy, prevented incidents, or return on investment.
Cato later said Aim served Fortune 500 and Forbes Global 2000 organizations, but its announcement did not name those customers or provide a customer count. The funding announcement likewise supplied no revenue amount. Investors therefore had a public account of enterprise interest, but not enough disclosed information to calculate customer penetration, growth rates, or a valuation from the funding news alone.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What Cato’s acquisition means for Aim
Cato announced on September 3, 2025, that it had acquired Aim Security. The acquisition price was not disclosed in Cato’s announcement. Cato said Aim’s capabilities would be integrated into the Cato SASE Cloud Platform and offered through it in early 2026, with a migration path for standalone Aim customers.
Best Value
The strategic fit is that a SASE platform can serve as a control point for network access and interactions with cloud services, while AI-security capabilities can extend policy enforcement to AI use. That does not make AI security synonymous with SASE: development security, model configuration, application design, identity, and data governance may still require separate controls. Nor does the acquisition announcement establish that Aim remains available as a separately branded or independently licensed product. Buyers considering the technology should confirm current packaging, deployment options, support, and migration terms with Cato.
What enterprise buyers should evaluate
A broad platform description is a starting point, not a substitute for a technical and commercial evaluation. Buyers should establish where controls operate and which AI workflows they actually cover.
- Coverage: Test public AI services, enterprise copilots, custom applications, APIs, coding assistants, agents, models, and MCP-connected tools that employees use.
- Enforcement points: Identify whether policies apply at the browser, endpoint, web gateway, API, application runtime, or model layer—and what happens when traffic bypasses a control point.
- Policy detail: Check whether rules can vary by identity, department, data classification, application, model, prompt, response, tool call, and jurisdiction.
- Data handling: Ask where prompts, responses, telemetry, and policy events are processed and stored, how long they are retained, and what residency and contractual terms apply.
- Operational impact: Pilot with legitimate workflows as well as risky ones. Measure false positives and determine how users can request exceptions without making controls ineffective.
- Runtime and posture scope: Distinguish interaction filtering from AI asset inventory, model configuration checks, access controls, secure development, and supply-chain review.
- Integrations: Validate connections to identity providers, SIEM, DLP, CASB, secure web gateway, endpoint tools, cloud platforms, ticketing, and data classification.
- Regulatory fit: Confirm audit, retention, residency, and compliance requirements for the relevant jurisdictions and industry rather than relying on general enterprise claims.
- Product continuity: Because Aim was acquired, establish whether the proposed purchase is an Aim capability within Cato, what platform commitments it entails, and how migration and support will work.
How to read the funding story now
Aim’s Series A was a 2024 signal that investors saw demand for controls that could let enterprises adopt generative AI without treating every AI tool as either prohibited or risk-free. The $18 million round backed a broad security proposition at an early point in enterprise AI adoption; the disclosed record does not establish how effective the product was relative to competitors. The later acquisition is the more important update for anyone assessing the company today: Aim’s AI-security work became part of Cato’s broader platform strategy, rather than remaining an independent startup.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
