SafeNet Authentication Service Private Cloud Edition (SAS PCE)
Multi-factor authentication (MFA) software
Identity management software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if SafeNet Authentication Service Private Cloud Edition (SAS PCE) and its alternatives fit your requirements.
Contact the product provider
Free Trial unavailableFree version unavailable
Small
Medium
Large
- Energy and utilities
- Professional services (engineering, legal, consulting, etc.)
- Banking and insurance
What is SafeNet Authentication Service Private Cloud Edition (SAS PCE)
SafeNet Authentication Service Private Cloud Edition (SAS PCE) is an on-premises/private-cloud multi-factor authentication platform used to protect access to enterprise applications, VPNs, and remote access gateways. It supports a range of authentication methods, including hardware and software tokens and push-based authentication, and integrates with common identity stores and access infrastructure. SAS PCE is typically used by organizations that need MFA while keeping authentication services within their own environment for regulatory, data residency, or operational reasons.
Private-cloud deployment control
SAS PCE is designed for deployment in customer-controlled environments rather than a vendor-hosted service. This helps organizations meet internal security policies and external compliance requirements that restrict use of public cloud authentication services. It also allows customers to manage network placement, segmentation, and operational procedures around the MFA service.
Broad token and method support
The product supports multiple authentication factors, including hardware tokens and software-based OTP, as well as push-based authentication options. This flexibility helps organizations standardize MFA across different user populations and risk profiles. It also supports phased migrations where legacy token users and newer mobile users coexist.
Enterprise access integrations
SAS PCE commonly integrates with enterprise access points such as VPN and remote access systems and can work with existing directory services. This makes it suitable for workforce access scenarios where MFA must be enforced consistently across multiple entry points. It can reduce the need for custom development compared with building MFA enforcement into each application separately.
Less CIAM breadth than suites
SAS PCE is primarily an MFA platform and does not typically provide the full set of customer identity and access management capabilities found in broader CIAM offerings. Organizations needing advanced customer onboarding, identity proofing, and rich customer profile management may require additional products. This can increase architectural complexity for customer-facing use cases.
Operational overhead of self-hosting
Running SAS PCE in a private cloud/on-prem environment shifts responsibility for availability, patching, monitoring, backups, and capacity planning to the customer. This can require dedicated IAM operations skills and supporting infrastructure. For smaller teams, the operational burden may be higher than using a vendor-hosted MFA service.
User experience varies by factor
End-user experience depends on the chosen factor (for example, OTP tokens versus push), and token-based approaches can introduce distribution and lifecycle management work. Hardware token programs add procurement, replacement, and inventory processes. Organizations aiming for passwordless-first experiences may need to evaluate whether the available factors align with their UX and security roadmap.
Seller details
Thales Group
Meudon, France
1893
Public
https://www.thalesgroup.com/
https://x.com/thalesgroup
https://www.linkedin.com/company/thales/
