# Marina Segal's cloud that says no > Tamnoon's CEO argues cloud security spent a decade finding problems it never fixed. Her company publishes what its machine refuses to do. - Title: Marina Segal's cloud that says no · The Next Web | Shortify - Summary: Tamnoon's CEO argues cloud security spent a decade finding problems it never fixed. Her company publishes what its machine refuses to do. Tamnoon publishes… - Keywords: tamnoon, marina segal, cloud security, cloud remediation, automation, security posture management, technology, startups, Marina, Segal's, cloud, The Next Web - Source: The Next Web — https://thenextweb.com/news/marina-segal-tamnoon-cloud-remediation-say-no - Author: Veronika Furs - Published: 2026-10-13T20:35:59+00:00 - Read time: 3 min - Topics: tamnoon, marina segal, cloud security, cloud remediation, automation, security posture management, technology, startups ## Detection is done. Healing is stuck. Cloud security can now spot misconfigurations within minutes of creation. But more than half of everything ever detected remains open, and critical findings take one hundred fifty days on average to fix. ## The attacker's clock runs in minutes By CrowdStrike's count, an attacker moves from first foothold to lateral movement in twenty nine minutes. The defender's clock, once the alert has fired, runs in months. ## Marina Segal built the machines that see Segal was at Dome9 Security when it defined cloud security posture management, then at Check Point after it bought the company.She co-founded Tamnoon in twenty twenty one to close the gap between detection and healing. ## The industry automated the yes Nearly every cloud security platform now ships an agent offering to make remediation changes itself. But most of those switches stay off because nobody approves a change a machine cannot explain. ## Fear of the wrong fix is rational In production, every change is somebody's responsibility. A wrong remediation does not look like a security failure. It looks like an outage, with a ticket that says who approved it. ## Speed was never the problem Segal says every vendor in the market is selling speed.Nobody was ever afraid the fix would be slow. > Every vendor in this market is selling speed. Speed was never the problem. Nobody was ever afraid the fix would be slow. They were afraid it would be wrong, and that they would be the one who said yes to it. ## A machine that cannot say no is a liability Segal argues that automation without refusal is not automation at all. A machine that cannot say no is a liability with an API, not a tool a team can trust in production. > A machine that cannot say no is not automation. It's a liability with an API. ## Tamnoon taught restraint first Every remediation product is built to act.Tamnoon's engine was built to decide, and the first decision it learned was no. > The first thing we automated was restraint. That order is the whole company. ## One alert. Three correct answers. In a demo, six identical open storage buckets trigger the same alert. The engine closes three safely, declines two because the change would sever something live, and asks about one because the owner is unknown. ## A refusal needs evidence to matter A decline from the engine carries the finding, what was read first, the verdict, the reason, the one fact that would change the verdict, and the steps to do it by hand. > A refusal without evidence is a shrug. A refusal with the evidence is a decision you can defend at nine in the morning. ## Autonomy is earned, not granted Tamnoon's engine starts read-only and changes nothing. It is granted the right to act on a class of finding only after its record on that class holds, and the customer keeps the veto throughout. > You keep the veto. It earns the keys. And it can lose them. ## Every decision becomes a receipt Every decision the engine makes, closures and refusals alike, becomes a receipt with six fields readable by an auditor. When a customer's engineer overrides the engine, the override goes into the record too. ## Tamnoon publishes what it refused Today Tamnoon publishes the Cloud Remediation Index showing more than half of everything ever detected in the cloud is still open, and a public page of remediations its engine declined, each with the six fields. ## The industry publishes wins. Tamnoon publishes refusals. Segal says every company in the industry publishes its wins.Tamnoon is publishing the changes it did not make. > Every company in this industry publishes its wins. We are publishing the changes we did not make. ## Ask vendors to demo the decline Tamnoon has published six questions buyers should put to any remediation vendor, itself included.The first: can it refuse a change and show one refusal with the evidence attached.Everyone demos the fix. > Everyone demos the fix. Ask them to demo the decline. ## Customers report three times fewer findings One customer went from six thousand seventy four open findings to two thousand forty one over four quarters, with ninety three percent fewer new alerts by the end.Warner Music Group is a named customer. ## Key takeaway Tamnoon publishes refusals its remediation engine makes and a Cloud Remediation Index showing more than half of detected cloud problems remain open, arguing automation must learn restraint before speed.