IdCloud

IdCloud is a digital identity and authentication platform that provides identity verification (IDV/KYC), strong customer authentication (SCA), and risk-based authentication decisioning, with an enterprise deployment model oriented toward regulated and mid-to-large organizations.

10 Ref Customers

Website

MarketsData Security Platforms

Published Oct 15, 2026

01Common complaints

- If the buyer specifically needs CIAM / customer identity and intended Imperva - Imperva is not primarily positioned as a CIAM vendor; evaluate Okta, Ping, ForgeRock, or Microsoft Entra External ID instead. - If transparent pricing and short contracts are required - Many enterprise identity/security products are quote-based and may require annual commitments. - Organizations with cloud-heavy database environments evaluating Imperva DAM - At least one community report suggests Imperva DAM may not perform as expected in certain cloud-heavy setups; validate with a proof of concept. - If a large volume of independent customer reviews specifically for "IdCloud" is required - Public review coverage for "IdCloud" under imperva.com was not found; buyers who require extensive third-party validation may prefer tools with larger review footprints. - Current limitations acknowledged by the vendor - No product limitations for an "IdCloud" product were found on imperva.com. - Features on the roadmap - Not found in accessible sources. - Scale limitations - Not documented for IdCloud on imperva.com. - Security or compliance gaps - For "IdCloud" tied to imperva.com: certifications are not discoverable in public sources. - For Thales IdCloud: certifications are documented (SOC Type II, ISO 27001; CSA STAR references). - API limitations or integration constraints - Not assessed due to limited IdCloud-specific Imperva documentation.

Deal disqualifiers

Need for fully transparent self-serve pricing and short procurement timelines without annual commitments.
Lack of internal integration engineering capacity.

Why some customers left for competitors (churn reasons)

Cloud-fit and architectural mismatch in certain deployments (anecdotally for DAM in cloud-heavy setups).

02Why they buy

- Validated by customer feedback (not just vendor claims) - For Imperva, anecdotal community feedback references quick trial enablement and successful mitigation in some cases. - For Thales IdCloud, the primary vendor-stated unique selling point is an integrated set of capabilities for onboarding, SCA, and risk decisioning. - Unique features and capabilities competitors lack - Not enough IdCloud-specific public documentation under imperva.com to assert unique features definitively. - Areas where competitors clearly have advantages - CIAM leaders (Okta, Ping) often provide more extensive developer documentation and a broader CIAM ecosystem.

Why customers chose this product over alternatives

From community discussions, buyers sometimes prefer Imperva due to simpler bundling or quicker enablement compared to alternatives (anecdotally).

03Field reports

Direct quotes from Gartner Peer Insights, Reddit, TrustRadius, G2, HackerNews

- Constraint: Direct, product-specific customer reviews for "IdCloud" on imperva.com were not found on the major review sites during this research. - What was accessible: - G2 / TrustRadius reviews for Imperva WAF (Imperva as a vendor) are available. - G2 / Gartner Peer Insights reviews for the identity platform that integrates IdCloud are available. - Reddit community feedback about Imperva (not IdCloud-specific) surfaced topics such as trial responsiveness, pricing complexity comparisons, and cloud-fit concerns for DAM.

Balanced highlights (what users praise vs complain about) from accessible community signals

- Praises (community anecdotes; not controlled reviews) - Anecdotal reports reference quick trial enablement and at least one sysadmin account of successful mitigation when comparing responsiveness to a competitor. - Criticisms / concerns - A cybersecurity subreddit thread highlights bundling versus competitor pricing complexity and potential cost differences. - A cloud-focused DAM implementation thread reports that the DAM offering did not meet expectations for that user in a cloud context and they were evaluating alternatives. - A sysadmin post references appliance/product lifecycle (EOL and version lag) concerns for older offerings.

Specific outcomes customers achieved (with metrics when available)

Vendor-published Imperva case studies exist, but these are vendor marketing materials and not independently validated.

Deal-breakers and reasons customers didn’t purchase

Not enough IdCloud-specific customer feedback was accessible to conclusively list IdCloud deal-breakers; however, common deal-breakers for enterprise identity/onboarding platforms usually include pricing opacity, integration complexity, and regulatory requirements.

Case Studies

- Detailed customer success stories with metrics - Imperva publishes case studies (example: a large enterprise IT services customer using SecureSphere virtual appliances). - Implementation details and time to value - Public case studies typically provide high-level narratives; detailed implementation timelines and resourcing are usually not disclosed. - Challenges faced during adoption and how they were resolved - Vendor case studies usually underreport challenges; treat as directional. - CRITICAL: Note when metrics are vendor-published without independent verification - Imperva case studies are vendor-published marketing documents; metrics should be validated with references, architecture review, and (ideally) customer references.

04Best fit

Company sizes

Likely appropriate fit (if Thales IdCloud): mid-market to large enterprises, especially regulated financial institutions.
Likely appropriate fit (if Imperva ecosystem): mid-market to enterprise organizations with multiple web applications/APIs and a substantial attack surface.

Industries and verticals

Banking, payments, insurance (explicitly highlighted for Thales IdCloud).
E-commerce and SaaS (common WAF/WAAP buyers; supported by Imperva positioning).

Roles and personas

Decision makers: CISO, Head of IAM, Head of Digital Channels (banking), Security Engineering leadership.
End users: IAM engineers, fraud/risk teams, SOC, application security engineers.

Qualification criteria

Need for regulated onboarding (KYC/IDV), SCA/PSD2-style requirements, and risk-based decisioning.

05The pitch

What the product does (core value proposition in objective terms)

- Important naming ambiguity (high risk of confusion): The term "IdCloud" does not appear to be an Imperva-branded product in Imperva’s publicly accessible materials uncovered during this research. Imperva’s public portfolio focuses on application security (WAF/WAAP), DDoS, API security, bot management, and data security. - The most consistently documented "IdCloud" product in the market is Thales IdCloud (formerly Gemalto IdCloud), positioned as a digital banking identity platform for onboarding (IDV/KYC), strong customer authentication (SCA), and risk-based authentication (RBA). - Given the Imperva domain specified in the request, this report treats the request as: - Primary lens: "IdCloud" in the context of Imperva’s domain and ecosystem (Imperva product + legal/support docs + customer feedback on Imperva). - Secondary lens (most likely true match): the Thales IdCloud product that is widely documented and reviewable, and may be the intended product when searching for "IdCloud."

Target market and market positioning

Imperva (as referenced by Imperva’s domain)
- Enterprise and mid-market organizations needing application and data security across cloud/hybrid environments.
Thales IdCloud (market reality for the term "IdCloud")
- Financial institutions and regulated businesses needing digital onboarding, strong authentication, and risk-based decisioning.

Get a comprehensive analysis of IdCloud including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →