Asymmetric vs symmetric encryption for mobile access
Traditional access credentials relied on symmetric encryption, using shared keys to authenticate identity. Today, asymmetric cryptography is redefining mobile access, enabling more secure, scalable, and truly interoperable credentials protected by public-private key pairs.
Why encryption matters?
Enterprises looking to adopt mobile credentials for access must carefully consider how their credentials are encrypted to eliminate key-sharing risks and unlock secure, interoperable mobile access at enterprise scale.
Asymmetric encryption
Built for secure, scalable mobile access
Asymmetric encryption uses a public-private key pair. The private key is never shared, it stays securely in the secure element of the device. The public key is shared and acts as a secure identifier.
Maximum security
Private keys are never shared or exposed, they are stored securely in the device’s secure element, completely reducing the risk of being compromised.
True interoperability
Public keys can be shared and work across multiple systems, devices, and applications.
No vendor lock-in
Adopt open standards and maintain full control of your ecosystem.
Built for scalability
Deploy across global sites without complexity, delays, or added cost.
Full ownership of credentials
You control your keys, your users, and your ecosystem.
Symmetric encryption
Introduces risk, cost, and vendor dependency
Symmetric encryption uses a single shared key to authenticate credentials. This key must be kept secret and securely exchanged between the communicating parties, otherwise it can pose vulnerabilities.
Shared keys, shared risk
Every system, partner, or manufacturer with access to the key becomes a potential vulnerability.
Vendor Lock-In
Dependency on one provider to manage and distribute keys, limiting flexibility and innovation.
Hidden Costs
Licensing fees and key management add ongoing operational expenses.
Limited Interoperability
Integration across multiple systems is complex and restrictive.
How Sentry mobile credentials use asymmetric encryption
When the Sentry Interactive app or any third-party app with our SDK embedded is first set up, a unique public-private key pair is generated on the user’s mobile device.
- The private key is securely stored in the smartphone device’s secure enclave and protected by biometrics or a password.
- The public key is safely transmitted to the cloud services over a TLS-secured connection with TLS pinning to prevent interception.
Mobile credentials built on the highest security standards
As organizations scale across multiple locations and adopt mobile access credentials, encryption becomes the foundation of security, flexibility, and growth. That’s why Sentry Interactive built mobile credentials with asymmetric encryption, based on the Public Key Open Credential (PKOC) specification.
Find out how our mobile credentials deliver to PKOC specifications, pioneering the future of open standard credentials.
Find out about the benefits of mass enrollment capabilities of Public Key Open Credentials (PKOC) for enterprises.
Learn more in an article exploring how the Sentry Interactive SDK is enabling mass enrollment of PKOC credentials for enterprises.
Unlock mobile access credentials based on the highest security standards
Integrate the Sentry Interactive SDK with your access control systems and enroll your users with mobile credentials that are secured with asymmetric cryptography.
Connect with a member of our team within 24 hours.
Get a system audit for integration.
Deploy and activate mobile credentials within days.
Frequently asked questions
Symmetric encryption uses a single shared key to authenticate credentials, meaning that key must be distributed and kept secret across every system and partner involved — creating potential vulnerabilities. Asymmetric encryption uses a public-private key pair, where the private key never leaves the user’s device and is never shared, significantly reducing the risk of credentials being compromised or cloned.
With symmetric encryption, every party that holds the shared key is a potential security risk, if the key is intercepted or leaked by any one system or vendor, all credentials using it are exposed. Asymmetric encryption eliminates this entirely because the private key is stored securely in the device’s secure enclave and is never transmitted or shared, making it far harder to intercept or exploit.
Yes. Because symmetric encryption relies on a single shared key managed and distributed by a specific vendor, organisations become dependent on that vendor to maintain and update their credentials. This limits flexibility, restricts integration with other systems, and often introduces ongoing licensing costs. Asymmetric encryption, by contrast, uses open standards that work across multiple platforms and providers without dependency on any single vendor.
When the Sentry Interactive app, or any third-party app with the Sentry SDK embedded, is first set up, a unique public-private key pair is generated directly on the user’s device. The private key is stored in the smartphone’s secure enclave and protected by biometrics or a password, while the public key is transmitted to cloud services over a TLS-secured connection with TLS pinning to prevent interception.
Sentry Interactive’s mobile credentials are built on asymmetric cryptography in line with the Public Key Open Credential (PKOC) specification. This is an open, license-free standard that delivers the highest levels of security for mobile access, enabling credentials that are interoperable across systems, free from vendor lock-in, and scalable across global enterprise deployments.