Native Security

Native Security is built around a simple but important observation: the major cloud providers already expose extensive security primitives, but most enterprises only use a fraction of them, and usually in a fragmented way. As organizations adopt multi-cloud architectures and layer AI workloads on top, the gap between what the cloud can technically enforce and what security teams can reliably operate becomes a real risk. Native positions itself as the control layer that closes that gap by translating security intent into provider-native guardrails instead of asking teams to bolt on yet another monitoring tool. That is strategically relevant in Israel because the company sits at the intersection of cloud infrastructure, cyber defense, and the broader AI-security problem.

The product is designed to let teams express a desired policy in natural language or structured intent, then map that intent into controls enforced through AWS, Azure, Google Cloud, and Oracle Cloud Infrastructure. Native's platform emphasizes impact simulation before rollout, staged deployment, exception handling, and drift detection after deployment, which reduces the operational risk that normally comes with hardening production cloud environments. This matters because cloud security failures are often not caused by a lack of tools, but by misconfiguration, drift, inconsistent policy execution, and the difficulty of applying the same rule set across different providers. Native is trying to make security architecture itself the enforcement point.

Technically, the company appears to be aiming at an architecture-first model rather than a threat-detection model. Its platform organizes workloads and identities into zones, analyzes gaps between intended and installed controls, and then generates provider-specific enforcement recipes that can be deployed, exported as code, or managed through change workflows. That approach is different from alert-centric cloud security products because it tries to reduce the number of decisions a security team must make after the fact. The value proposition is not merely visibility; it is consistent execution of architectural intent, including controls around data perimeters, least privilege, AI governance, and blocked actions that would otherwise happen in production.

Native's public traction is meaningful for an early-stage company. It emerged from stealth in March 2026 with $42 million in total funding, including a $31 million Series A led by Ballistic Ventures and support from General Catalyst, YL Ventures, and Merlin Ventures. Globes and SecurityWeek both describe the company as founded in 2024 by Amit Megiddo, Gal Ordo, and Eyal Faingold, all of whom have substantial cloud-security backgrounds at AWS and Check Point. The company reported 41 employees across Tel Aviv and the US at launch, with a plan to roughly double by the end of 2026, and it claims Fortune 100 customers in finance, technology, and media. That combination of experienced founders, a relatively narrow but valuable problem statement, and early enterprise validation makes the company worth tracking.

From a strategic diligence perspective, Native sits in a crowded but important market. It is adjacent to cloud security posture management, CNAPP, and policy automation, but the company is trying to carve out a distinct category: operationalizing native cloud controls as an enforcement plane. The main question is whether buyers will treat this as a new control layer that deserves budget, or as a feature set that existing cloud-security vendors and cloud providers can absorb over time. The strongest strategic signal is the dual-use fit: the same enforcement logic that protects commercial cloud estates can also help governments, defense contractors, and critical-infrastructure operators harden AI-enabled systems, prevent unauthorized network paths, and keep security posture aligned as environments evolve. The open diligence questions are integration depth, measurable reduction in drift, and how much of the value remains if cloud providers keep expanding native policy tooling.