SPKI issues certificates, but they are not the same as X.509 certificates used on networking devices or servers for enabling HTTPS. For HTTPS and related server authentication, X.509 remains the standard option.



Supported Cryptographic & Security Operations with SPKI
Requires both "SPKI_CryptoOps_App" and "SPKIML_EU_App".


Simpler Code Signing

Files such as archives or executables can be cryptographically signed and verified using SPKI_CryptoOps_App. This provides integrity assurance, though it is not a full replacement for industry-standard X.509 code signing certificates.

Software-Level Phishing Prevention

By signing and verifying messages within SPKI_CryptoOps_App, users can ensure authenticity of text-based communications, significantly reducing risks from phishing or spoofing attempts.

Fine-Grained Access Control

Applications and storage systems can leverage SPKI certificates to enforce more precise access policies. This allows resources to be protected at a granular level, tied directly to user identity.

Passwordless Authentication

SPKI digital signature operations enable secure, passwordless logins. This enforces a Zero Trust approach by verifying users cryptographically instead of relying on shared secrets.

Mutual Trust Verification

In private deployment modes, both parties can exchange and verify hashes before starting encrypted communication. Comparison of both parties’ received digital signature public keys ensures mutual trust.