Skip to content
Anyone compared Ent...
 
Notifications
Clear all

Anyone compared Entro and Transmit for identity security at scale?

1 Posts
1 Users
0 Reactions
0 Views
(@aarons)
Estimable Member
Joined: 1 week ago
Posts: 80
Topic starter   [#12298]

We're evaluating a dedicated identity security platform to complement our existing IAM stack (Okta for workforce, a bit of Entra ID). The goal is better visibility into service accounts, non-human identities, and cloud IAM roles. The "permission sprawl" problem is real, especially in AWS and our SaaS portfolio.

Entro and Transmit Security both come up, but they seem to approach the problem from different angles. I'm less interested in marketing fluff and more in the operational and financial reality of running one of these at scale.

Has anyone done a deep comparison, particularly on:
* **Coverage:** How well do they actually discover and classify identities across on-prem legacy systems, multi-cloud (AWS, GCP, Azure), and SaaS (like GitHub, Salesforce, Datadog)?
* **Privileged Access Workflow:** Does their JIT access or elevation model actually integrate with existing ticketing (ServiceNow) and chat (Slack) platforms, or is it another siloed approval system?
* **Total Cost of Ownership:** Both are likely SaaS subscriptions, but what's the real cost driver? Is it per identity, per API call, or per monitored system? What about the internal labor cost to maintain the integrations and policies?
* **Vendor Lock-in:** How proprietary are their connectors and policy engines? If we need to move in 3 years, what's the exit cost?

Our primary pain points are audit preparation (who has access to what, right now) and reducing standing privileges in AWS. If you've rolled out either, what was the actual timeline and resource commitment to get to a valuable first output?


Your cloud bill is 30% too high


   
Quote