The week Gal Ordo joined Amazon Web Services as the Product Leader for AWS Security Hub, he did something his colleagues thought was unnecessary. Instead of using the internal templates that AWS provided to get the product up and running, he insisted on installing it from scratch the way a customer would – no shortcuts or help from the team that built it.<\/p>\n\n\n\n
But then he said it took him four to five days.<\/p>\n\n\n\n
\u201cIt was so hard for me to install,\u201d said the co-founder and CPO of Native Security. \u201cAnd I am within AWS! I\u2019m the product leader for that. What does it mean for a customer going in the first time trying to use that? At best, they give up; at worst, they misconfigure it, and then they don\u2019t have active security coverage.\u201d<\/p>\n\n\n\n
That initial moment planted the first seed. But the second came a month later, when Ordo attended his first Executive Briefing Center session on behalf of Amazon. There, a room of executives from Fortune 100 and Fortune 50 companies had one message for the young product leader sitting across from them: \u201cWhy are you showing us the problem after it happens? Why can\u2019t we just prevent it?\u201d<\/p>\n\n\n\n
\u201cI remember them telling me, \u2018Why do you even allow me to get to that place? Why don\u2019t you just give me the knob to say this can never happen in the first place?\u2019\u201d Ordo recalled.<\/p>\n\n\n\n
It was those two experiences, operating a product too complex for its own builders to operate, and a customer too exhausted to keep reacting, that became the founding logic of Native Security. The Tel Aviv-based cloud security startup emerged from stealth in March 2026 with an official $42 million<\/a> in funding (he says they have already secured more, up to $55 million), and a collection of Fortune 100 customers already running its platform in production.<\/p>\n\n\n\n