Technology
Zero-trust architecture
WWPass zero-trust authentication assumes no safe perimeter and no central store of identities. Data is encrypted, split, and held in distributed data storage, so no single point holds enough to expose a user.
Technology
Zero-trust architecture
WWPass zero-trust authentication assumes no safe perimeter and no central store of identities. Data is encrypted, split, and held in distributed data storage, so no single point holds enough to expose a user.
Technology
Zero-trust architecture
WWPass zero-trust authentication assumes no safe perimeter and no central store of identities. Data is encrypted, split, and held in distributed data storage, so no single point holds enough to expose a user.
What zero-trust means at WWPass
No implicit trust
Every request is authenticated on its own, regardless of where it comes from or who's asking.
Keys apart from data
Encryption keys never sit alongside the data they protect, and are usable only at authorized endpoints.
Anonymous by design
All users are anonymous to WWPass. Data arrives encrypted, with keys unknown to WWPass, and is returned intact.
What zero-trust means at WWPass
No implicit trust
Every request is authenticated on its own, regardless of where it comes from or who's asking.
Keys apart from data
Encryption keys never sit alongside the data they protect, and are usable only at authorized endpoints.
Anonymous by design
All users are anonymous to WWPass. Data arrives encrypted, with keys unknown to WWPass, and is returned intact.
What zero-trust means at WWPass
No implicit trust
Every request is authenticated on its own, regardless of where it comes from or who's asking.
Keys apart from data
Encryption keys never sit alongside the data they protect, and are usable only at authorized endpoints.
Anonymous by design
All users are anonymous to WWPass. Data arrives encrypted, with keys unknown to WWPass, and is returned intact.
Traditional security assumes a trusted inside and an untrusted outside. Zero Trust assumes no safe perimeter.
Cloud services, remote work, and distributed teams have made that boundary unreliable. An attacker who reaches one server, one employee account, or one misconfigured service can often move freely once inside. The Zero Trust approach assumes threats are possible from any location, internal or external. Every request is authenticated and authorized on its own, so no single point of entry gives an attacker a path to everything else.
No safe perimeter. No implicit trust. No single point that unlocks everything.
Traditional security assumes a trusted inside and an untrusted outside. Zero Trust assumes no safe perimeter.
Cloud services, remote work, and distributed teams have made that boundary unreliable. An attacker who reaches one server, one employee account, or one misconfigured service can often move freely once inside. The Zero Trust approach assumes threats are possible from any location, internal or external. Every request is authenticated and authorized on its own, so no single point of entry gives an attacker a path to everything else.
No safe perimeter. No implicit trust. No single point that unlocks everything.
Traditional security assumes a trusted inside and an untrusted outside. Zero Trust assumes no safe perimeter.
Cloud services, remote work, and distributed teams have made that boundary unreliable. An attacker who reaches one server, one employee account, or one misconfigured service can often move freely once inside. The Zero Trust approach assumes threats are possible from any location, internal or external. Every request is authenticated and authorized on its own, so no single point of entry gives an attacker a path to everything else.
No safe perimeter. No implicit trust. No single point that unlocks everything.
A breach in one place shouldn't expose everything else
That's the real test for zero-trust design: not how hard it is to break in, but how much damage a break-in actually causes.
A breach in one place shouldn't expose everything else
That's the real test for zero-trust design: not how hard it is to break in, but how much damage a break-in actually causes.
A breach in one place shouldn't expose everything else
That's the real test for zero-trust design: not how hard it is to break in, but how much damage a break-in actually causes.
Distributed data storage, no single point of failure
Data is distributed across multiple geographic locations
WWPass distributes data content redundantly across multiple geographic locations.
Data is encrypted, split, and stored across separate nodes
Each data container is encrypted, split, and stored across several separate storage nodes, and reconstructing it requires a majority of those nodes together, not just one.
Multiple front ends and data miners run concurrently
Multiple front ends and data miners run concurrently, making it possible to implement a reliable system without any single point of failure.
Container names cannot be reversed
Container names are generated using a one-way transformation applied to the user's identifier and the service provider's identifier. That transformation can't be reversed, so the original identifiers can't be recovered from a container name, not even by WWPass.
Distributed data storage, no single point of failure
Data is distributed across multiple geographic locations
WWPass distributes data content redundantly across multiple geographic locations.
Data is encrypted, split, and stored across separate nodes
Each data container is encrypted, split, and stored across several separate storage nodes, and reconstructing it requires a majority of those nodes together, not just one.
Multiple front ends and data miners run concurrently
Multiple front ends and data miners run concurrently, making it possible to implement a reliable system without any single point of failure.
Container names cannot be reversed
Container names are generated using a one-way transformation applied to the user's identifier and the service provider's identifier. That transformation can't be reversed, so the original identifiers can't be recovered from a container name, not even by WWPass.
Distributed data storage, no single point of failure
Data is distributed across multiple geographic locations
WWPass distributes data content redundantly across multiple geographic locations.
Data is encrypted, split, and stored across separate nodes
Each data container is encrypted, split, and stored across several separate storage nodes, and reconstructing it requires a majority of those nodes together, not just one.
Multiple front ends and data miners run concurrently
Multiple front ends and data miners run concurrently, making it possible to implement a reliable system without any single point of failure.
Container names cannot be reversed
Container names are generated using a one-way transformation applied to the user's identifier and the service provider's identifier. That transformation can't be reversed, so the original identifiers can't be recovered from a container name, not even by WWPass.
A zero trust security model from the ground up
Keys separate from data
Information is encrypted at every stage, with encryption keys kept separate from the data and accessible only to authorized users at secure endpoints.
Authenticated before access
Users are authenticated before they can access any information.
Revoked access, revoked keys
Keys are transferred securely and redundantly, but are not extractable by users. If access is revoked, the keys become unavailable.
A zero trust security model from the ground up
Keys separate from data
Information is encrypted at every stage, with encryption keys kept separate from the data and accessible only to authorized users at secure endpoints.
Authenticated before access
Users are authenticated before they can access any information.
Revoked access, revoked keys
Keys are transferred securely and redundantly, but are not extractable by users. If access is revoked, the keys become unavailable.
A zero trust security model from the ground up
Keys separate from data
Information is encrypted at every stage, with encryption keys kept separate from the data and accessible only to authorized users at secure endpoints.
Authenticated before access
Users are authenticated before they can access any information.
Revoked access, revoked keys
Keys are transferred securely and redundantly, but are not extractable by users. If access is revoked, the keys become unavailable.
The same keys protect more than your login
The WWPass Key can generate a master encryption key that stays on the device rather than being sent anywhere. From it, the key generates a provider-specific encryption key, sent securely to the application that needs it.
That provider-specific key encrypts individual project and file keys, and the stored files themselves. The master key is not revealed to the application, the cloud provider, or WWPass at any point.
The same keys protect more than your login
The WWPass Key can generate a master encryption key that stays on the device rather than being sent anywhere. From it, the key generates a provider-specific encryption key, sent securely to the application that needs it.
That provider-specific key encrypts individual project and file keys, and the stored files themselves. The master key is not revealed to the application, the cloud provider, or WWPass at any point.
The same keys protect more than your login
The WWPass Key can generate a master encryption key that stays on the device rather than being sent anywhere. From it, the key generates a provider-specific encryption key, sent securely to the application that needs it.
That provider-specific key encrypts individual project and file keys, and the stored files themselves. The master key is not revealed to the application, the cloud provider, or WWPass at any point.
Designed for environments where the perimeter can't be trusted
Keys stay separate from the data they protect
Encryption keys are accessible only at authorized endpoints, never bundled with the data itself.
Every user and device is authenticated individually
Access is granted per request, not inherited from a network location or prior login.
Distributed data storage, no single point of failure
Data is dispersed across multiple nodes, with no single facility or server representing a single point of failure.
Designed for environments where the perimeter can't be trusted
Keys stay separate from the data they protect
Encryption keys are accessible only at authorized endpoints, never bundled with the data itself.
Every user and device is authenticated individually
Access is granted per request, not inherited from a network location or prior login.
Distributed data storage, no single point of failure
Data is dispersed across multiple nodes, with no single facility or server representing a single point of failure.
Designed for environments where the perimeter can't be trusted
Keys stay separate from the data they protect
Encryption keys are accessible only at authorized endpoints, never bundled with the data itself.
Every user and device is authenticated individually
Access is granted per request, not inherited from a network location or prior login.
Distributed data storage, no single point of failure
Data is dispersed across multiple nodes, with no single facility or server representing a single point of failure.
Common questions
Learn more about WWPass and contact us to discuss your use case and get a demo.
What does zero-trust architecture mean at WWPass?
How is this different from a firewall or VPN-based security model?
What happens if one storage node is compromised?
Can WWPass itself access user data?
What happens to a user's access when it's revoked?
Common questions
Learn more about WWPass and contact us to discuss your use case and get a demo.
What does zero-trust architecture mean at WWPass?
How is this different from a firewall or VPN-based security model?
What happens if one storage node is compromised?
Can WWPass itself access user data?
What happens to a user's access when it's revoked?
Common questions
Learn more about WWPass and contact us to discuss your use case and get a demo.
What does zero-trust architecture mean at WWPass?
How is this different from a firewall or VPN-based security model?
What happens if one storage node is compromised?
Can WWPass itself access user data?
What happens to a user's access when it's revoked?
Get WWPass
Download the WWPass Key app and test authentication without a username or password.
Get WWPass
Download the WWPass Key app and test authentication without a username or password.
