Hey everyone, been diving deep into SaaS security posture lately, especially around secrets and non-human identity management. We're a mid-sized shop with a growing stack (think 50+ services, mix of cloud and on-prem legacy stuff), and the spreadsheet of API keys, service accounts, and cloud access roles is... terrifying.
I'm evaluating solutions that can discover, classify, and monitor these assets without needing a massive team to run them. **Identiq** and **Entro Security** keep coming up. Both seem strong on discovery and risk scoring, but the pricing models and implementation overhead feel quite different.
From my initial digging:
* **Identiq** appears more API-driven, which appeals to my integration brain. I like the idea of pulling risk events into our existing SIEM or workflow tools. Their cost seems to scale with the number of "entities" tracked.
* **Entro** seems to offer a more all-in-one platform with a heavier focus on the full lifecycle, including automated remediation workflows. Pricing looks more tiered based on features and scope.
For those in the mid-market who've implemented either:
1. How was the integration effort? Did you need a ton of custom connectors, or did the out-of-box coverage work for most SaaS tools (like Salesforce, AWS, GitHub, etc.)?
2. What does the actual ongoing management look like? Are you constantly tuning rules, or does it run fairly autonomously after setup?
3. Any gotchas with the pricing? For example, did a surge in discovered identities blow up your bill?
I'm leaning towards something that gives me good API hooks so I can build custom alerts and automations. For instance, if a high-risk secret is detected, I'd want to automatically create a ticket and temporarily restrict access. Can you easily trigger external actions from these platforms?
```json
// Example of the kind of webhook payload I'd want to consume
{
"alert_type": "stale_admin_key",
"identity_id": "azure_service_principal_123",
"risk_score": 0.87,
"recommended_action": "rotate"
}
```
Would love to hear real-world cost-to-value comparisons. Not just license costs, but also the internal hours saved (or spent) managing the system.
I'm a senior security engineer at a 200-person fintech, managing a sprawling AWS/Azure/GCP footprint with a tail of on-prem legacy systems. We've been running Entro Security in production for about eight months after a short POC with Identiq.
Core comparison:
1. **Real Pricing and Model:** Entro's licensing was based on a "protected assets" bundle, which they defined pretty broadly. For our mid-market scope, we landed in the $25k-40k annual bracket. Identiq's model was per entity, which felt clearer but introduced forecasting anxiety; our quote was closer to $45k+ once we translated our actual environment count. The hidden cost with Entro is the platform fee that gates the automated workflows, which is a separate tier.
2. **Integration and Deployment Effort:** Identiq was indeed more API-first. We'd have needed to build our own connectors for about a third of our services, particularly the legacy on-prem ones. Entro had more built-in connectors, but the "effort" shifted: we spent about 40 hours of engineering time tuning their discovery scans to not blow up fragile old systems. Their SaaS platform meant no infra to manage, which was a win.
3. **Where It Breaks / Limitation:** Identiq's risk scoring felt more like a feed of events. You get a list of "here are the risky things" but the "so what now?" is on you to build. Entro's platform promises remediation, but for anything complex, you're just building a glorified Jira ticket. The automated secret rotation only worked seamlessly for mainstream cloud providers; for anything custom, it was a DIY project.
4. **Where It Clearly Wins:** For pure, continuous discovery and classification, Entro's dashboard gave my team a single pane of glass we could actually use. Identiq felt more like a developer tool for a security engineering team that had cycles to build around it. Entro's support was responsive on setup, but now it's mostly ticket-based.
My pick is Entro, but only if your primary goal is immediate visibility and your team lacks the bandwidth to build integrations. If you have a strong engineering team that wants to pipe risk data into existing SIEM/SOAR workflows and you're prepared to build some connectors, Identiq's API model might be more cost-effective long-term.
Tell us: what's your team's size, and is your environment mostly modern cloud or a true hybrid mess?
— skeptical but fair
Oh man, the integration effort question is where this gets real. You're spot on about Identiq being API-driven, but that's a double-edged sword for mid-market. That integration appeal is high, but it means you're building the plumbing yourself. Their out-of-the-box connectors exist but are leaner; expect to write more adapters for your legacy on-prem stuff and niche SaaS tools.
I found the real integration cost wasn't the initial setup, but the maintenance. Every time someone adds a new service or an API changes, that's on your plate. With Entro's heavier platform, you're paying for them to handle that drift, but you're also locked into their workflow rhythms. So it's a trade-off: engineer hours versus platform fees.
For a shop your size with a mixed environment, the custom connector workload could easily eat up the perceived savings from Identiq's clearer pricing model. Been there, got the t-shirt, and it's a devops time-sink.
Demos are just theater. Show me the real workflow.